As the title states, I rooted and flashed the latest cm11 nightly onto my OPO today. Now the camera doesn't work. It doesn't matter if I use the included camera apk, or install one of the OPO camera apk's . I get the error " cannot connect to camera". Restarting the app and the phone don't help. Has this happened to anyone else? Is there a solution? Thanks in advance for your ideas.
Have you tried reflashing yet?
Transmitted via Bacon
You cannot use gapps that includes the Camera. If the Camera is included with the gapps, it will give you the error, "Cannot Connect to Camera."
Do a wipe, use http://forum.xda-developers.com/showthread.php?t=2397942 Pico version (or a version that does not include Camera. Read the description of the gapps and you will see whether or not Camera is included).
After using that, you should be able to use 1) AOSP Camera included with the ROM 2) CameraNext.apk http://d-h.st/dBc just fine.
zephiK said:
You cannot use gapps that includes the Camera. If the Camera is included with the gapps, it will give you the error, "Cannot Connect to Camera."
Do a wipe, use http://forum.xda-developers.com/showthread.php?t=2397942 Pico version (or a version that does not include Camera. Read the description of the gapps and you will see whether or not Camera is included).
After using that, you should be able to use 1) AOSP Camera included with the ROM 2) CameraNext.apk http://d-h.st/dBc just fine.
Click to expand...
Click to collapse
Thanks for the info, ill give that a try. I half a dozen combos of different nightlies and gapps packages and ended up with the same issue. I reverted back to the stock rom and everything works at the moment.
I have an additional question I dont want to create a new thread for. Does anyone happen to know if there is a difference between the 30O and 33R camera apk's? I want to stick with the OPO camera but I have only seen the 30O camera and the previous version posted. Will i be losing anything going back to that from 33r? Thanks again for the help.
The camera is the same across both versions.
Transmitted via Bacon
Thanks for the quick reply.
As what timmaaa said but..... attached is XNPH33R camera, its the same thing as XNPH30O but eh... why not.
Press the thanks button instead of saying it
That happened to me now. Except I flashed the 05Q modem to cause it. Now the camera will only work in the CM11S rom. Tried CM11 nightly, Liquidsmooth 3.2 and other KitKat roms. Play store cameras don't work either. I tried flashing the 44S modem since it was working before on that and still nothing. Completely wiped the phone and fastboot flashed the entire factory image 44S and still the camera will not work on any other rom. HELP!!!
Related
I have 2 of the same phones (i747M with twrp 2.7.1 for d2att installed)
On one, everything worked flawlessly (the older one)
On the other, I had to talk to a developer of twrp to get twrp working...
Now I just realized that the camera app isn't working. It works fine when I restore to the touchwiz stock rom.
I tried wiping my entire device before installing the new stable build 6 rom for d2lte. I also tried flashing the weekly roms for that device on both phones
the result is the same: camera works fine on the older phone while on the newer one, it doesn't
Someone suggested that this might be a hardware issue.. Basically, the TWRP guys fixed my other problem by pulling the latest cyanogenmod build and compiling a recovery. -So I'm wondering if something can be done to make my camera work again on my new phone...
(Before all of this, I of course tried rebooting, closing other apps, clearing data, etc...)
Update: I tried flashing the latest cyanogenmod nightly (June 30) and the camera app worked, but I prefer slimrom
Another update: all the bug report shows when I reproduce the error is
Device: Slim-d2lte-4.4.4.build.6-OFFICIAL-5242
Kernel: 3.4.95-cyanogenmod-gd56ed95 [email protected] #1
help please. the camera works fine with stock roms, but since I flashed DU official 8.1, any intention to take a photo (regardless of camera app) makes the screen freeze (not force close, it just freezes while generating the photo, and the save animation does not play, and no photo is created ) except for the nav bar back and home buttons. this happens with every custom roms I have tried after the first event. I used to think it was a matter of DU rom, but it also happens with mokee, pa, liquidsmooth, mahdi, spirit and pac. I have tried several solutions like flashing cam libs, stock cam apps, reflashing custom rom, flashing custom kernels, but the only method that makes camera apps work again is flashing stock roms through fastboot. I have an xt1032. it only happens with the back camera, photos taken with the front camera are saved as usual and the apps don't freeze. please bring a ray of light into my case, I don't know what else to try.
tenjou_89 said:
help please. the camera works fine with stock roms, but since I flashed DU official 8.1, any intention to take a photo (regardless of camera app) makes the screen freeze (not force close, it just freezes while generating the photo, and the save animation does not play, and no photo is created ) except for the nav bar back and home buttons. this happens with every custom roms I have tried after the first event. I used to think it was a matter of DU rom, but it also happens with mokee, pa, liquidsmooth, mahdi, spirit and pac. I have tried several solutions like flashing cam libs, stock cam apps, reflashing custom rom, flashing custom kernels, but the only method that makes camera apps work again is flashing stock roms through fastboot. I have an xt1032. it only happens with the back camera, photos taken with the front camera are saved as usual and the apps don't freeze. please bring a ray of light into my case, I don't know what else to try.
Click to expand...
Click to collapse
​
Bro really strange error . I am with PAC man ROM latest nightly I never faced any camera bug even pic r great bro just try a clean install and see or try any nice kernel and check
tenjou_89 said:
help please. the camera works fine with stock roms, but since I flashed DU official 8.1, any intention to take a photo (regardless of camera app) makes the screen freeze (not force close, it just freezes while generating the photo, and the save animation does not play, and no photo is created ) except for the nav bar back and home buttons. this happens with every custom roms I have tried after the first event. I used to think it was a matter of DU rom, but it also happens with mokee, pa, liquidsmooth, mahdi, spirit and pac. I have tried several solutions like flashing cam libs, stock cam apps, reflashing custom rom, flashing custom kernels, but the only method that makes camera apps work again is flashing stock roms through fastboot. I have an xt1032. it only happens with the back camera, photos taken with the front camera are saved as usual and the apps don't freeze. please bring a ray of light into my case, I don't know what else to try.
Click to expand...
Click to collapse
Go to dhacker's cyanogenmod thread and search for a zip on the last pages. It flashes the stock camera + libs and everything else needed.
I was going through the same things you are and it worked perfectly
helinhof said:
Go to dhacker's cyanogenmod thread and search for a zip on the last pages. It flashes the stock camera + libs and everything else needed.
I was going through the same things you are and it worked perfectly
Click to expand...
Click to collapse
I have the same problem
I searched the thread you said , and I did not find the zip , you still have it there and could send me ? Thanks!
rogeraugusto_ said:
I have the same problem
I searched the thread you said , and I did not find the zip , you still have it there and could send me ? Thanks!
Click to expand...
Click to collapse
Here you go, just flash this zip
https://docs.google.com/file/d/0B7U5fbfp5U27cDlwdmVzeWRLVzQ/edit?usp=docslist_api
I uploaded it for you and everyone else having this problem. Hope it works
thank you, it seems the camera works for now. it is nice that it now receives updates in spite of using a custom rom. however after flashing this zip, dalvik cache for user apps was wiped (without me performing any wipe) and then the theme engine broke. I can't install any theme apks manually, and if I try to install one from the playstore, I get an error notification and the " uninstall" button becomes "install" again. also, themes installed manually appear to be of 0.00MB. I will reflash my current rom and post the results later.
EDIT: clean reflashed and immediately flashed the cam+libs zip. everything works thanks a lot!!
NOTE 4 sm910f trite qualcom CUSTOM ROM CAMERA FREEZES re
helinhof said:
Here you go, just flash this zip
https://docs.google.com/file/d/0B7U5fbfp5U27cDlwdmVzeWRLVzQ/edit?usp=docslist_api
I uploaded it for you and everyone else having this problem. Hope it works
Click to expand...
Click to collapse
...................................................................................................................................................
Newbie here.. note 4 sm910F quacom 6.01 then root twrp and res remix 16, sometimes, not allways, camera freezes. take batt out restart and ok again. Any help to sort out really appreciated. Remix takes about 50 seconds to load from cold start.
---------- Post added at 02:27 PM ---------- Previous post was at 02:24 PM ----------
gwm121 said:
...................................................................................................................................................
Newbie here.. note 4 sm910F quacom 6.01 then root twrp and res remix 16, sometimes, not allways, camera freezes. take batt out restart and ok again. Any help to sort out really appreciated. Remix takes about 50 seconds to load from cold start.
Click to expand...
Click to collapse
If I cant sort the camera out Anyone know how I can flash a copy of the stock 6.01 with twrp or odin, samsung wont let me have a download
[Q&A] [ROM][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/
Q&A for [ROM][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/9/15]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/9/15]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
GPS?
Does the gps work on this rom?
gapps info
MC, could you provide a link to dhackers29 gapps and a little more info on deleting unwanted stuff from zip? This d2 is my DD, so I need my ducks in a row when I flash. Thanks.
Also, please reconsider this q&a bs. It's really just counter productive--that is, if you or anyone else ever even sees it.
BTW, downloaded 4/10 build with dolphin mini and it saved correctly as a zip.
darknite39 said:
Does the gps work on this rom?
Click to expand...
Click to collapse
It's working fine for me. Previously I couldn't get GPS locks on any AOSP ROM, but before switching to these builds from KitKat I flashed to Alliance ROM (stock-based TouchWiz - this is important) and got a GPS lock there. After a wipe I flashed the 4/6 build and GPS still worked.
Cool! Thank you for the tip.
Load rom from phone after wipe
Pardon my ignorance, but if i copy a rom and gapps to my phone and then do a full wipe, won't that wipe out the rom and gapps files? Is it stored in 2 different partitions, or do I put it on an external SD? I have TWRP 2.8.5, cm-12.1-20150407-UNOFFICIAL-d2vzw and gapps-L-4-15-15. Currently running cm11x.
1) Make sure you're on the latest TWRP
2) Download gapps from euroskank's site
3) Full wipe, flash ROM and gapps
Mc633 said:
Pardon my ignorance, but if i copy a rom and gapps to my phone and then do a full wipe, won't that wipe out the rom and gapps files? Is it stored in 2 different partitions, or do I put it on an external SD? I have TWRP 2.8.5, cm-12.1-20150407-UNOFFICIAL-d2vzw and gapps-L-4-15-15. Currently running cm11x.
1) Make sure you're on the latest TWRP
2) Download gapps from euroskank's site
3) Full wipe, flash ROM and gapps
Click to expand...
Click to collapse
Correct. If you put it on your internal and then wipe it the files will be gone
Sent from my Nexus 5
Advice on which version is consider to be a Stable Daily Driver
Hello everyone I'm currently using version date 4/7 however I'm having problems with Bluetooth when playing music and battery life is horrible. I'm going to try and go with 4/10 which from what I read seems to be very stable and great battery life. I simply want a good daily driver. Has anyone perform a dirty upgrade to a newer version successfully without issues. I want to perform this since it is quicker and I won't have to re-add my email exchange accounts again. How is the latest version 4/15?
Please advise,
TS
MMS and bluetooth audio (music) not working.
I'm using the lastest build 4/15 with 4/15 gapps which is running great. The only 2 problems i'm seeing is not being able to receive and send MMS and blue tooth audio isn't working properly. Are these know issues? Thank you guys for all the work that you have been doing thus far. My phone is like new again!!!
Thank you,
TS
agree textra as alternative msg app
Been using textra for about a year and like it better than stock and other apps. Would use it even if stock worked.
need to cut invisi-k a break
That's rough indeed. I for one would be fine with him doing weeklies, instead of nightlies, so dude can have time to live and work.
Latest Gaps 4/18 installation procedure.
Can I dirty install the latest gaps over our current installation or do I need to perform and clean installation of both zip files with the latest gaps? I'm currently running zips 4/15 with 4/15 gaps. Therefore can I just in recovery mode installed 4/18 gaps over the 4/15 gaps successfully without issues? Has anyone seen a big difference in the 4/18 gaps opposed to the 4/15?
Thank you,
TS
Latest Gapps 4/18 installation procedure.
Can I dirty install the latest gapps over our current installation or do I need to perform and clean installation of both zip files with the latest gapps? I'm currently running zips 4/15 with 4/15 gapps. Therefore can I just in recovery mode installed 4/18 gapps over the 4/15 gapps successfully without issues? Has anyone seen a big difference in the 4/18 gapps opposed to the 4/15?
Thank you,
TS
techysandy0504 said:
Can I dirty install the latest gaps over our current installation or do I need to perform and clean installation of both zip files with the latest gaps? I'm currently running zips 4/15 with 4/15 gaps. Therefore can I just in recovery mode installed 4/18 gaps over the 4/15 gaps successfully without issues? Has anyone seen a big difference in the 4/18 gaps opposed to the 4/15?
Thank you,
TS
Click to expand...
Click to collapse
I don't think there would be any true difference between the two gapps. I don't really see a need to update the gapps unless your updating to a newer android version. I know android 5.1.1 was released recently but I doubt the S3 could even run this version
Sent from my Nexus 5
Bluetooth (Audio) and MMS
Has anyone tested Bluetooth (Audio) and being able to send and receive MMS? Is that working successfully on the 4/19 build?
Thank you,
TS
4/22 wont boot for me!!! (Beware)
Just a heads up I just tried to install zip file 4/22 and my phone wont boot therefore I had to restore back to 4/21. I performed a full wipe before trying to install 4/22 however no luck. Yes MMS are now working on 4/21 !!!
Thanks for all the great work,
TS
I recently flashed this on my Verizon S3, however it seems that it has borked my SMS, possibly MMS (tested much less). I cannot send/receive SMS messages whatsoever. I have tried to manually set my SMSC, and have updated to the newest modem. Any ideas why this could be happening and how to fix it?
dirty flash 4/22?
anyone tried a dirty flash (I'm lazy) over 4/7? I'm stuck on "Android is starting.... starting apps". Never could get 4/15 to work. Tried dirty, clean, gapps, no gapps. Guess I'll give this an hour and then try a clean flash.
Mc633 said:
anyone tried a dirty flash (I'm lazy) over 4/7? I'm stuck on "Android is starting.... starting apps". Never could get 4/15 to work. Tried dirty, clean, gapps, no gapps. Guess I'll give this an hour and then try a clean flash.
Click to expand...
Click to collapse
I cleaned flashed 4/22 and my phone would not boot therefore I flashed 4/21 which is working well for me.
Good luck,
TS
---------- Post added at 02:18 PM ---------- Previous post was at 01:47 PM ----------
Bluetooth Audio not working using 4/21 build however I know they will get this figured out soon.
Thanks for all the great work thus far!!!
TS
Tried the 4/22 release and phone would not boot up. I got no boot animation, but eventually the Updating apps showed up. Got to the starting apps screen and after 35 minutes, nothing changed.
This was on a dirty flash. So I wiped everything and started from scratch and had the same problems. Back to 4/15 for now for me.
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
hjrry said:
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
Click to expand...
Click to collapse
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Nitefire77 said:
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Click to expand...
Click to collapse
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
hjrry said:
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
Click to expand...
Click to collapse
Try a different GAPPS package, maybe a larger one. Just to see. For one, some people complained of missing features like notification bar pulldown with the very smallest GAPPS package. Now this isn't a reason it shouldn't install, but try a different package to see if it make a difference in completing the installation.
hjrry said:
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Click to expand...
Click to collapse
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
plasticdoc said:
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
Click to expand...
Click to collapse
First, restore your backup. You did make a backup, right?
Then re-flash after you download a different GAPPs package. Some say Open Gapps works great for them, while others say Slim GAPPS is best. We don't know why some don't work for some people but work for others.
If that doesn't fix your issue, then try this:
Download the unofficial CM13 found here in this forum and try it.
Also, download Resurrection Remix (Marshmallow) and try it.
Both are variants of CM13 anyways. Just trying to see if something is wrong with your phone and you can't flash any ROM whatsoever or if it's something your phone doesn't like about official CM13.
The unofficial CM13 is CM13 with just a few of the Resurrection Remix tweaks thrown in, like permissions to download Moto apps from the Google Store, etc. It's 90% CM13, 10% RR.
If none of those CM13 variants work, you can alway try AOSP Mokee (Marshmallow).
IF NONE of those work, either your phone is severely messed up or you are doing something wrong.
ChazzMatt said:
Download the unofficial CM13 found here in this forum and try it.
Click to expand...
Click to collapse
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
plasticdoc said:
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
Click to expand...
Click to collapse
I don't know. Not everything with our phones is completely logical. Occasionally more of an art than science. Same reason one GAPPs package works well for someone but won't install for another person. Open GAPPS vs Slim Gapps.
Here's a personal example... My wife and I both have XT1225 with CM12.1 and yet hers can't run BHB27 kernel. Occasionally I'll get it to install, and run OK for a day or two but then next time I reboot it it does endless bootloops. I even tried different governors and I/O schedulers. Nada.
Mine is a Puerto Rico (unlocked Claro) XT1225 I flashed to India 5.0.2 before flashing to CM.
Her's is a Mexico direct-from-China-Motorola factory XT1225 I flashed to India 5.0.2 before flashing to CM.
Later I flashed Puerto Rico XT1225 radio over both.
There's just some difference there in her XT1225 which does not like BHB27 kernel.
Maybe if I did an exhaustive formatting of the entire internal memory and reinstallation of everything on her phone, it would work. But instead I take the easy way out and she's just running CM12.1 with default CM kernel, and that's running well. So, I go with what works.
phone app not working
unfortunately telephone has stopped working.
wajid1213 said:
unfortunately telephone has stopped working.
Click to expand...
Click to collapse
What does that have to do with this thread? > cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)
I don't even think you are using this phone, to be honest. So, why did you post here? You posted same thing in another thread, for ANOTHER PHONE, not even related to Quark.
You seem to be using this phone: Xiaomi Redmi 2 -- since all your other posts before this and after this are over there.
http://forum.xda-developers.com/search.php?searchid=422491957
Ever since I upgraded to android 10, I haven't been able to get OK Google to enable on any ROM (tried ArrowOS, AOSiP, Evolution X, AICP); in every ROM, switching on OK Google in Assistant settings just has it turn right back off after a few seconds, with a driving warning and "Something went wrong. Try again." at the bottom of the screen. I grabbed a logcat while running Evolution X, but I took a peek at logcat on other ROMs and the error is identical:
https://pastebin.com/Ryqz1iww
For the record, this is a Perseus global model on 11.0.3.0.QEEMIXM firmware that's had MIUI 11 then Xiaomi.EU's latest MIUI 11 stable on it prior to going to custom android 10 roms.
If any more info would be helpful toward solving this, let me know and I'll grab it.
EDIT: OK Google IS WORKING under Xiaomi.EU's latest MIUI 11 build, but still no dice on any custom ROM.
EDIT 2: If a ROM has gapps included, it works. If I have to flash opengapps, it doesn't.
EDIT 3: Solved! Just flash the latest firmware again after you flash everything else - you can get the firmware here.
I'm on the latest Xiaomi.EU weekly ROM and OK Google works just fine.
Official ROMs are the only things I CAN get it to work on. Vanilla MIUI 11 and Xiaomi.EU both work for this, so it's not just an issue with my Google account or something - but something is preventing OK Google from working on any of the custom ROMs, including the latest versions of the ROMs mentioned in my OP, even those that include GApps, so it's not like I'm using a bad GApps package. Literally all I do is wipe everything (incl. formatting data), flash the ROM, flash Magisk (which I also did on the MIUI ROMs it works with), reboot, connect to wifi, log in to google (I've tried declining to restore a backup), go straight to Assistant settings and it fails, same error as in that logcat in OP on every ROM it happens on.
Hey, I have the same issue on Evo X. Have you managed to work it out? Thanks
Same issue here on AOSIP. Interestingly, I have two identical devices (Mi Mix 3), running the same version of AOSIP, and on one it works fine, and the other does not!
In case it makes any difference, I am using a gsuite account.
Solved! Thanks to a tip from @Caccu, I now have it working. The secret was to flash the latest firmware over the ROM, even if you're already on the latest firmware. I'm not clear on why, but it works. If you need the latest firmware, you can get it from here. For reference I'm using V12.0.1.0.QEEMIXM on my global Perseus model.
if you flash the latest firmware over a ROM. then you'll be using the latest firmware, and not the ROM you wanted. is that right?
bluviper said:
if you flash the latest firmware over a ROM. then you'll be using the latest firmware, and not the ROM you wanted. is that right?
Click to expand...
Click to collapse
No no, just the firmware, not the whole MIUI package/ROM. The link I provided only has the firmware, with the rest of MIUI stripped out. The ROM is unaffected, the only change I notice after flashing it is that OK Google works now.