I had been running CM 10.2 for a while. Last night did a factory reset/wipe cache/dalvik and installed latest CM11 snapshot (M12). Stock camera app was crashing upon startup ("Unfortunately, camera has stopped."). Tried using 2 other camera apps (Google camera and open camera) and neither worked as well. Then tried flashing SlimKat and had the same problem. Already tried reflashing, rebooting, etc. multiple times. Anyone know why this is happening or have a fix?
I am using ClockworkMod Recovery 6.0.5.1, if that matters.
Also, already tried the CMFix thing from the play store, if anyone is planning on suggesting that, and it didn't work.
Also, I had unsuccesfully tried using the fix posted here: http://forum.xda-developers.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973 not realizing it was meant for the international version. Has that ****ed me over? I have since done a clean reflash of CM11
Update: Downgraded to CM 10.2. Camera does not even work here now! Gives the error, "Unfortunately, Gallery has stopped working". Please help
Related
I have been running nightlies of CM9. My camera was working yesterday, I know for a fact, but today any time I open it, I get the message "Unfortunately, Camera has stopped.
I flashed the RC2 thinking that would fix it, but I'm still getting the same message. I even used Odin to flash back to stock and I get the message "camera has failed" I am running touch recovery and I ave wiped system and data and everything multiple times.
Is this potentially a hardware problem?
yes
I went from bone stock to the most recent PAC-man nightly (22.0.1) and its fine with a couple of exceptions. When the phone tries to re-download my apps each one gives me an error message. That's not a big deal since I can still manually re-download them. But the issue that does concern me is that every time I try to use voice-to-text, I get "Unfortunately, Google Search has stopped." Maybe not the worst thing in the world but it's getting in the way of my normal usage. I've tried wiping and re-flashing and I've flashed the latest modem but no luck so far. I tried the CM10.1 M2 snapshot too but I get the same issue. What am I missing?
SuperBrother said:
I went from bone stock to the most recent PAC-man nightly (22.0.1) and its fine with a couple of exceptions. When the phone tries to re-download my apps each one gives me an error message. That's not a big deal since I can still manually re-download them. But the issue that does concern me is that every time I try to use voice-to-text, I get "Unfortunately, Google Search has stopped." Maybe not the worst thing in the world but it's getting in the way of my normal usage. I've tried wiping and re-flashing and I've flashed the latest modem but no luck so far. I tried the CM10.1 M2 snapshot too but I get the same issue. What am I missing?
Click to expand...
Click to collapse
Apparently, I didn't search hard enough for an answer before. Turns out I just needed to update Google Search manually. Help on particular apps not downloading is still welcome though!
This morning, when I tried to use my camera, it force closed immediately when I tried to open it. The last time I took a picture was 3 days ago, and that worked fine. I haven't installed any new mods since then. I've been using Jishnu's v1.4 camera mod since it was released. Here's a list of everything I've tried:
Cleared data/cache in both camera and gallery
Booted into recovery to wipe cache and dalvik
Booted into safe mode - still force closed
Flashed back to stock 4.4.2 camera found in Jishnu's thread
However, other camera apps work. For example, both Jishnu's LG G2 and MotoX camera ports work fine. Other apps that use the camera, such as DailyRoads also work. I just don't know why the default camera app isn't working.
Additional info:
Stock ROM, 4.4.2 rooted
TWRP 2.7.0.0
Xposed Framework running Gravity Box
Faux Kernel (Camera was working fine previously on v012 until today. I flashed to v014 in a desperate attempt to see if it would fix the problem.)
Mod - Increased volume
Mod - MotoX optimized dalvik
Mod - Jishnu's V1.4 camera, now reverted back to stock
Mod - KitKat UI
I would like to avoid factory resetting currently, but I will do it over the weekend if I have to.
Thanks in advance for your input!
EDIT
Solved
See post #6
kered424 said:
This morning, when I tried to use my camera, it force closed immediately when I tried to open it. The last time I took a picture was 3 days ago, and that worked fine. I haven't installed any new mods since then. I've been using Jishnu's v1.4 camera mod since it was released. Here's a list of everything I've tried:
Cleared data/cache in both camera and gallery
Booted into recovery to wipe cache and dalvik
Booted into safe mode - still force closed
Flashed back to stock 4.4.2 camera found in Jishnu's thread
However, other camera apps work. For example, both Jishnu's LG G2 and MotoX camera ports work fine. Other apps that use the camera, such as DailyRoads also work. I just don't know why the default camera app isn't working.
Update:
Re-installed v1.4 of Jishnu's Camera and all is working fine.
Additional info:
Stock ROM, 4.4.2 rooted
TWRP 2.7.0.0
Xposed Framework running Gravity Box
Faux Kernel (Camera was working fine previously on v012 until today. I flashed to v014 in a desperate attempt to see if it would fix the problem.)
Mod - Increased volume
Mod - MotoX optimized dalvik
Mod - Jishnu's V1.4 camera, now reverted back to stock
Mod - KitKat UI
I would like to avoid factory resetting currently, but I will do it over the weekend if I have to.
Thanks in advance for your input!
Click to expand...
Click to collapse
I just found out I had the same problem you are having. I flashed back the stock camera from Jishnu and it works again. I am going to re-install his camera fix and see what happens *fingers crossed*
Update - Flashed Jishnu's fix back again and it still works... not sure what's going on with yours :[
railed said:
I just found out I had the same problem you are having. I flashed back the stock camera from Jishnu and it works again. I am going to re-install his camera fix and see what happens *fingers crossed*
Click to expand...
Click to collapse
I'm not as lucky as you. I tried flashing back to stock, but it still crashes
kered424 said:
I'm not as lucky as you. I tried flashing back to stock, but it still crashes
Click to expand...
Click to collapse
Steps I followed:
1) Reboot recovery and flash 4.4.2 stock from Jishnu
2) Wipe Cache/Dalvik
3) Reboot and Camera worked
4) Rebooted to recovery and flashed Fix and Video Fix
5) Wiped Cache/Dalvik
6) Rebooted and still worked
railed said:
Steps I followed:
1) Reboot recovery and flash 4.4.2 stock from Jishnu
2) Wipe Cache/Dalvik
3) Reboot and Camera worked
4) Rebooted to recovery and flashed Fix and Video Fix
5) Wiped Cache/Dalvik
6) Rebooted and still worked
Click to expand...
Click to collapse
Just attempted the first 3 steps. Did not work for me. Oh well, I'll tinker with my phone over the weekend.
Thanks for your help though!
Solved!
I figured it out because I wanted to update my camera to the new version. I ran into problems, and fixed both at the same time.
Anyway, here's what I did.
Delete GoogleCamera.apk in /system/app
Flash stock 4.4.2 camera found in Jishnu's thread
Camera should now work!
I am on the Elix-R Rom and after a few days the Google Dialer force closes on me. I flashed only that particular Gapp with Elix-R. I noticed this same thing happened when using the Paranoid Android Rom as well. I have tried re-flashing, changing kernels, updating TWRP, flashing the dialer again and nothing. Does anyone know why this might happen?
Maybe you need more gapps to enable it to work. Try flashing full gapps first
Sent from my Nexus 5 using Tapatalk
My phone is currently running off of cm-12-20150324-NIGHTLY-m8.zip and gapps-lp-20150222-singed.zip
I recently downloaded the latest nightlies (from 0603 and 0604), and I'm having some issues. Either the phone app keeps crashing or google play keeps crashing or settings keeps crashing.
I've tried factory resets, and I can get it to the point where one of the latest nightlies is working, but when I subsequently install, gapps-5.1-2015-06-02-15-19.zip, then after I reboot, my phone app starts crashing again.
The only thing that seems to fix this is to do a factory reset and revert to the older versions of both CyanogenMod and gapps. So now, I turn to the community that is wiser and more experienced than I and ask ... why?
hadji369 said:
My phone is currently running off of cm-12-20150324-NIGHTLY-m8.zip and gapps-lp-20150222-singed.zip
I recently downloaded the latest nightlies (from 0603 and 0604), and I'm having some issues. Either the phone app keeps crashing or google play keeps crashing or settings keeps crashing.
I've tried factory resets, and I can get it to the point where one of the latest nightlies is working, but when I subsequently install, gapps-5.1-2015-06-02-15-19.zip, then after I reboot, my phone app starts crashing again.
The only thing that seems to fix this is to do a factory reset and revert to the older versions of both CyanogenMod and gapps. So now, I turn to the community that is wiser and more experienced than I and ask ... why?
Click to expand...
Click to collapse
There have been reports that some of the latest gapps are causing play services to force close. I would recommend using a different gapps. Maybe give banks gapps a go and see if that helps. Also, some nightlies might not be as stable as previous ones. I know some were having issues with june 2 gapps.
sjpritch25 said:
There have been reports that some of the latest gapps are causing play services to force close. I would recommend using a different gapps. Maybe give banks gapps a go and see if that helps. Also, some nightlies might not be as stable as previous ones. I know some were having issues with june 2 gapps.
Click to expand...
Click to collapse
Still having issues. I've tried newer nightlies and two other gapps packages, including Banks. All with the same results. I even wiped the cache, dalvik, system and data partitions. Same behavior.
Looks like I finally got this fixed.
I posted the details here: http://forum.xda-developers.com/verizon-htc-one-m8/help/fixed-update-issue-t3145751