In a shocking case of déjà vu, I am in the midst of re-living an astoundingly frustrating issue from the past. Back almost exactly one year ago, when first deploying CyanogenMod on my then new Galaxy S3, i was unbelievably frustrated by the constant failure of the camera. See this thread here for full details if you wish. In then end, it was necessary to pull some files from the /system/cameradata folder of a stock Samsung ROM (almost all of which began with "SlimISP") and drop them either in /system/cameradata or just /data of that device (other folk with similar issues reported needing to chmod 777 them) and the camera magically worked.
Now I have been modding a co-worker's Galaxy S4 (jfltespr) and, much to my chagrin, ran into the same issue. TWRP installed clean via ODIN, CyanogenMod 10.2 Stable was great, and (something else i'm going to try to isolate in a sec) the PDroid framework went in without a hitch. However, just as before, if one attempts to launch the camera, all you see is the briefest of previews through the camera lens (so it's not a hardware issue) and then the camera (gallery) app crashes and closes.
Now, for the list of what we've tried already...
Tried alternate camera tools, with the same result.
Tried force-stopping the gallery process, clearing data, etc. Same result.
Tried wiping cache. Same result.
Tried wiping all of user data (factory reset) and cache/dalvik cache. Same result.
Used TWRP to migrate back in the stock backup we made. Camera is fine.
Poked around the /system partition and looked in the stock /cameradata directory...
found assorted files like M10MO_SWF.bin, RS_M10MO_OL.bin, RS_M10MO_OS.bin, RS_M10MO_SL.bin, & RS_M10MO_SL
Copied those files from the stock ROM, used TWRP to restore back to the CM 10.2 environment, dropped the file into /system/cameradata. Still not working.
Checked permissions, also copied those files to /data ... still not bloody working.
Gave up, recorded a catlog dump of the camera app crashing, came here and posted on XDA...
Here's the catlog of the camera / gallery app crashing... http://pastebin.com/JgdGdDNg
Thoughts?? Why on earth are Samsung Galaxy devices so prone to crap out on the camera side of things with custom ROMs? i've seen threads and questions going back to the Galaxy S2 or even the Galaxy S on this kind of matter. Ugh.
Related
I am running Cyanogenmod 5.0.8 on a T-Mobile Mytouch3G (I tried upgrading twice to CM 6.0.0 but due to issues (lots of Force Quits due to running out of memory - I did not try swapping), went back to Android 2.1).
After running into the issue where creating a new folder would generate a Force Quit (ACore) message, I followed the advice here of running su -> fix_permissions which did solve that issue. However, it created the issue where the Phone Lock (i.e. slide to unlock) no longer appears. It also reset several passwords but that is manageable and also reset my Android Market list so it thinks my downloads were not installed, which was also manageable.
I have tried other lock programs (Lock 2.0, myLock) from Android Market but they don't always work.
I'd greatly appreciate suggestions on how to fix this problem.
Thank you
You can try reflashing CM without a wipe.
Sent from my HTC Magic using XDA App
I tried that but ended up having lots of issues with my phone so I restored my Nandroid backup. I may try flashing it again sometime in the near future.
I encountered further problems with my phone last week, especially with no missed call messages or flashing LEDs being displayed when I missed several calls one evening.
After using multiple backup utilities (just in case) to backup all of my call logs, SMS, MMS, Applications and Data, I dropped into Nandroid last night and did a full user data wipe along with the Cache and Battery Status. (It was a good thing I had used multiple utilities as the first program I tried couldn't find my backup after the install).
I then updated to CyanogenMod 6.0.0 and Gapps-tiny 09302010 and downloaded fresh copies of my applications (moving them to the SD Card where possible) and restored my backups. After completing that, I was pleased to note that the phone lock was restored along with the missed call LED and title bar notifications.
Has anyone else encountered problems running Fix Permissions from Rom Manager lately?
After Steven's warning here http://forum.xda-developers.com/showpost.php?p=49990427&postcount=62, I did a clean install and did not replace Browser or Gallery, all went well for a while, but then I began getting Trebuchet FC errors, rebooted to recovery to run Fix Permissions, but it is not avalible in the 6.0.4.7 CWM recovery, so I tried it through Rom Manager - noticed that it now has "toasts" rather than the old console type display, set it aside and let it run. Came back to my homescreen rather than the "reboot now" message that I was expecting. Re-booted and noticed a few user apps were missing, also got a few "android.process.media has stopped" errors as well as Trebuchet FC's. Convinced that I had a bad install, I formatted system, data and cache and flashed the latest nightly - 2/19 - oops, see http://forum.xda-developers.com/showpost.php?p=50470383&postcount=119 - getting stuck on the bootloader convinced me that I had something wrong with the EMMC, so I followed Leapinlar's (thanks again) Partition Repair guide at http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 - of course, the same thing happened again because of the bad nightly. Finally re-flashed the 2/15 nightly and got everything working again, ran fix permissions just to make sure. Actually sat and watched about a half dozen "toasts" and then my display went black, with occaisional SU "toasts" popping up until my homescreen came back on after about 10 minutes - not back to Rom Manager, no reboot warning, just sitting at my homescreen. I let it sit for another 10-15 minutes and rebooted, after starting, a few user apps missing, "android.process.media has stopped" errors as well as Trebuchet FC's. I started a Logcat and ran Fix Permissions again, same thing. Logcat is at https://dl.dropboxusercontent.com/u/20993724/lc022014.txt if anyone is interested, I am going to report to ClockworkMod.
After re-formatting system, data and cache, 2/20 nightly installed fine, all has been well for the last few days, but have not run fix permissions.
I believe koush and cm decided that fix permissions is not needed anymore.
Hi, I recently was on paranoid android and was getting ready to sell my galaxy s4 I9505 so restored a back up I made of the stock rom which was what came on the phone when I bought it.
I restored the back up, but once the phone had booted it was really slow and I kept getting loads of error messages saying different processes had kept failing. The same as in this thread.
http://forum.xda-developers.com/gal...restoring-stock-rom-cwm-t2882455#post55566370
I then booted back into recovery and wiped data and dalvik cache, which after rebooting sorted the problem. The device was running smoothly and so I went on downloading my apps from the play store.
But I've since noticed apps like swift key, instagram, whatsapp and snap chat seem to be having issues. I don't have any SD card installed just the phones internal memory, which I have ample space (9GB) but whatsapp won't let me download images.
Snapchat says I need to install an sd before viewing video and Instgram mentions I need an SD before being able to take a picture.
Also the language pack for Swiftkey won't download and when I try and download a theme it says it can't save it.
So it seems there's something wrong with the way it's trying to store certain files. Has anyone else come across this yet?
I'm planning on following the whole unroot process anyway documented here: http://forum.xda-developers.com/showthread.php?t=2265477 which I'm hoping will fix it.
But I wondered if anyone knew what it is that's caused it?
Rezaei12 said:
Hi, I recently was on paranoid android and was getting ready to sell my galaxy s4 I9505 so restored a back up I made of the stock rom which was what came on the phone when I bought it.
I restored the back up, but once the phone had booted it was really slow and I kept getting loads of error messages saying different processes had kept failing. The same as in this thread.
http://forum.xda-developers.com/gal...restoring-stock-rom-cwm-t2882455#post55566370
I then booted back into recovery and wiped data and dalvik cache, which after rebooting sorted the problem. The device was running smoothly and so I went on downloading my apps from the play store.
But I've since noticed apps like swift key, instagram, whatsapp and snap chat seem to be having issues. I don't have any SD card installed just the phones internal memory, which I have ample space (9GB) but whatsapp won't let me download images.
Snapchat says I need to install an sd before viewing video and Instgram mentions I need an SD before being able to take a picture.
Also the language pack for Swiftkey won't download and when I try and download a theme it says it can't save it.
So it seems there's something wrong with the way it's trying to store certain files. Has anyone else come across this yet?
I'm planning on following the whole unroot process anyway documented here: http://forum.xda-developers.com/showthread.php?t=2265477 which I'm hoping will fix it.
But I wondered if anyone knew what it is that's caused it?
Click to expand...
Click to collapse
Did you install the stock rom before or have you just restored your old backup?
If I were you, I would clean everything, install the stock sammy firmware (with latest base) and after that restore your backup
Tkkg1994 said:
Did you install the stock rom before or have you just restored your old backup?
If I were you, I would clean everything, install the stock sammy firmware (with latest base) and after that restore your backup
Click to expand...
Click to collapse
No it's not a rom, I just restored my old back up of my OS before I started flashing any custom roms.
I did a factory reset on the phone hoping it might resolve it. Which hasn't, but I'm not sure now if it's got rid of CWM. Would as I can't seem to get it to boot into recovery (it maybe just me not releasing the volume up button at the right time).
Think I'm going to have to flash a clean stock firmware following the unroot process and hope that fixes it.
Hi all,
Been having some fairly major issues with this tablet recently. Sorry for the back story, but I'm unsure whether it's related or not...
I primarily use the tablet to watch videos on while I'm commuting from an external USB stick. Always used to be 100% fine, running AOKP ROM for around a year. In the last month or so, I would watch a video and it would work for a couple of minutes, then the video would freeze and the audio soon after. To fix it I'd have to close MX Player, and unplug/plug back in the USB stick. Then it would happen again.
I therefore copied files onto the internal storage, and didn't have problems with this (a 4GB video file would copy with no issues). Then watch from internal storage with no issues.
I decided to try a different ROM and see if it helped the USB OTG issues. This is where the real problems started. I changed to a different Android 4.4 ROM (Purity I think?), and had Google Play Store crashing soon after starting, if I tried to download an app. After the initial crash, I would continually get 'Google Play Store has stopped working' messages. Rebooting etc made no difference. I would also get the same issue if I tried downloading an APK through the built in browser (it crashes).
I have since tried about 5 different ROMs (Android 4.2, 4.4 and 5.0 based) flashed through TWRP 2.8.4.0, with different Gapps, each time performing full or partial wipes/factor resets.
I have also tried restoring to stock settings through NTK, flashing factory images of 4.2, 4.4 and 5.0 builds through the 'restore stock and unroot' option (whatever it is called). I have also re-locked and unlocked the bootloader again.
Basically, I don't know what else I can do. Every time I get into a new ROM, I complete the initial setup, I can't go into Google Play store without the app force closing. I can't think of what would be causing this if it's the same between a lot of different ROMs, with the same issue.
Does anyone have any ideas..?
Thanks in advance.
scorpii said:
Hi all,
Been having some fairly major issues with this tablet recently. Sorry for the back story, but I'm unsure whether it's related or not...
I primarily use the tablet to watch videos on while I'm commuting from an external USB stick. Always used to be 100% fine, running AOKP ROM for around a year. In the last month or so, I would watch a video and it would work for a couple of minutes, then the video would freeze and the audio soon after. To fix it I'd have to close MX Player, and unplug/plug back in the USB stick. Then it would happen again.
I therefore copied files onto the internal storage, and didn't have problems with this (a 4GB video file would copy with no issues). Then watch from internal storage with no issues.
I decided to try a different ROM and see if it helped the USB OTG issues. This is where the real problems started. I changed to a different Android 4.4 ROM (Purity I think?), and had Google Play Store crashing soon after starting, if I tried to download an app. After the initial crash, I would continually get 'Google Play Store has stopped working' messages. Rebooting etc made no difference. I would also get the same issue if I tried downloading an APK through the built in browser (it crashes).
I have since tried about 5 different ROMs (Android 4.2, 4.4 and 5.0 based) flashed through TWRP 2.8.4.0, with different Gapps, each time performing full or partial wipes/factor resets.
I have also tried restoring to stock settings through NTK, flashing factory images of 4.2, 4.4 and 5.0 builds through the 'restore stock and unroot' option (whatever it is called). I have also re-locked and unlocked the bootloader again.
Basically, I don't know what else I can do. Every time I get into a new ROM, I complete the initial setup, I can't go into Google Play store without the app force closing. I can't think of what would be causing this if it's the same between a lot of different ROMs, with the same issue.
Does anyone have any ideas..?
Thanks in advance.
Click to expand...
Click to collapse
Are you sure you're using correct gapps versions? They're specific gapps packages for 4.2, 4.4 AND 5.0.
If you're sure of the above, then yes, I suggest you capture `adb logcat` output when Play Store is crashing. Then share the log with us.
Basically some of the components of play store are located in the system partition and most of custom roms don't come with gapps packages you need therefore to flash them after installing a new rom. PA provides very nice and up to date solution. PA gapps on Google.
Sent from my Xiaomi MI2s
Thanks for the suggestions guys. I had flashed correct Gapps packages for each ROM when required, but was still having the issue.
Somehow, after many hours spread over the last week, last night I seem to have fixed it.
I had suspected that it was an issue with a corrupt partition, (or permissions, or something!) on the internal storage, as it was only when I tried to download something that the browser crashed, and Play Store would generally only start crashing after a first time browsing with it. Also sometimes from within Recovery I wouldn't be able to wipe data properly (it would complete almost instantly, sometimes not removing a previous ROM...). Sometimes it did seem to work properly though.
I can't pin down exactly what I did that fixed it though. I tried 2 things at once: I manually wiped each of /system, /cache, etc through fastboot in the bootloader, and I also (from adb in recovery) manually did mkdir /data and mkdir /data/media
I'm not sure which of these worked, but I flashed a ROM and Gapps (AOKP again), and I haven't had any crashing so far...
I'm afraid to flash any other ROMs as it seems to be working now, so I think I'll leave it!
Probably should have looked at the adb logcat output, but didn't think of that while I was still having the issue.
Thanks
So far I've yet to get this new version to work with the fancy new backup and organization features that just came out. When I first installed it would just crash immediately when trying to boot. What I've now tried is Force Stopping and clearing cache and data. This gets me into the "intro" screen, but as soon as I hit 'get started' It just crashes. Any ideas what's going on? I just updated to 5.1.1, had issue on 5.1.0 a well. I am rooted.
:highfive:
Tried force stop and clearing data and cache for both the camera and photo's app. Then tried rebooting and opening camera (worked fine) then photo's (crashed as usual). Tried doing it again but opening photo's first, still crashed on the screen where it looks like you turn backup on or off. I think there is a backup issue. I had auto backup off for photo's previously by the way.
the same here
AAhrens said:
So far I've yet to get this new version to work with the fancy new backup and organization features that just came out. When I first installed it would just crash immediately when trying to boot. What I've now tried is Force Stopping and clearing cache and data. This gets me into the "intro" screen, but as soon as I hit 'get started' It just crashes. Any ideas what's going on? I just updated to 5.1.1, had issue on 5.1.0 a well. I am rooted.
Click to expand...
Click to collapse
I am experiencing the same issue since yesterday after flashing Google Play Edition 5.0.1 【JFLTE-GPE】ROM on Galaxy S4. Looking for the solution...