Hi guys,
I resently installed CM12.1-20151117 on my Moto X XT1052.
The reason I installed CM is that I got the "couldn't connect to camera" bug a lot. Unfortunately the bug is still there. I tried the restart camera apk with the cm camera fix app, renaming the DCIM folder, clearing the app data (camera and gallery) and multiple reboots as well as any combination of these fixes.
Sometimes one of the above solutions will work, but most of the time I end up with only the front camera working.
Does anyone have a working solution for this very annoying bug?
Thank you in advance!
Gesendet von meinem SHIELD Tablet mit Tapatalk
Hi
I had a very similar issue for months now. Had rooted stock 5.1 before, now running CM12.1 release version by SNAPSHOT for a week or so on my XT1052 ghost. Initially that didn't help and I was just about to start living with that, my camera app exclusively started my front cam, not even any error about the camera being busy or something came up, it was simply not there (as Apps like Droid Info didn't find it eihter). I tried many different camera apps, no improvement. Just today it works again (let's see how long it lasts). Can't really figure out why, the only thing I changed yesterday was erasing the modemst1 and modemst2 via fastboot to get my GPS fixed (which worked btw). So if you want (and we seem to have the same model and software) you can try that, but no guarantee

(Actually I don't see how that should be connected, but whatever) Good luck!
---------- Post added at 21:54 ---------- Previous post was at 21:26 ----------
Hello everybody,
as I now read all 48 pages of this thread, I feel free to ask a few questions that bother me. Please be patient.
I'm using CM12.1 by SNAPSHOT release (
https://download.cyanogenmod.org/?de...&type=snapshot ) for 7 days now. No problems of any kind with the ROM itself, exceptfor a GPS bug, which I could fixwith erasing the modemst1 and 2. My XT1052 was rooted before already by it's previous owner, bootloader unlocked.
----CM 12.1-20151117-SNAPSHOT-YOG7DAO1K9-ghost
Baseband MSM8960PRO_BP_23255.138.89.00R
Kernel 3.4.42-gd544eb6
[email protected]#1
build date Tue Nov 17 01:42:25 PST 2015
build number cm_ghost-userdebug 5.1.1 LMY48Y c9cc14bc94 test-keys----
Some tweaks done: Xposed with modules, especially Gravity Box, Greenify...
BUT now some questions came up, since I read a lot about Ambient display/Active display/Moto display and got confused about the differences in wording. So, imho "Active display" was the 4.4 feature, which was simply perfect (unfortunately I smashed the display and bought a used, rooted MOTO X with Android 5.1), "Moto display" the 5.1 feature and still good, and now "Ambient display" wants to be the successor (for any model). Am I right here? However, it's hard to believe that. I activated it in the CM12 settings (like everything, under "Gestures" I activated "Ambient display", "Pick-up", "Hand wave"). So far I can't really say the result satisfies me in any way. After reception of a notification Ambient display activates a couple of times, so far so good. Hand waving doesn't work, activating it by picking it up doesn't work. I have no possibility to activate it intentionally. So what's that for then? Is that a bug or normal behaviour? A websearch gave me contradictory results, maybe someone can clarify that for me.
Thanks