I recently installed some alternative camera apps (camera 360 and paper camera) onto my cm7 desire. Soon after that, camera 360 would tell me that the camera was occupied, flashlight and stock camera would not work. The camera just showed a black screen and a "app not responding, force close or wait?" message would appear.
Not sure if this is related, but shortly after i wanted to make a nandroid backup before trying a factory reset. In the middle of the backup i got an error and could not access sd card from clockworkmod any more.
I fixed this however, so i put a fresh cm on, the camera/flashlight still didn't work (still black screen). So i reverted to stock rom and an old radio, but still no change. Removing sd card also does nothing.
I found this multiple questions about this on the internet, but the only solution was rebooting/resetting.
Any idea how to get this fixed, other than unrooting and sending it in?
Edit: It seems this is a support case
Related
Hey everyone,
I've been using CM7 since the stable build was released for the G2 and today my Camera App stopped working and just force closes anytime I try to start or when any other application tries to access it.
I thought maybe this was just a bug, so I backed up, cleared data,cache,dalvik cache,fixed permissions and installed a fresh CM7 and the camera app still didn't work. Then I reverted all the way back to my stock 2.2 and for some reason that's not working either. I thought maybe it was a Kernel problem, so I flashed some fresh ones and some stock ones and still no dice.
What am I missing?! I JUST used the camera earlier today and it was fine, then it just stopped working for some reason. I can still access the Gallery, just not the Camera.
Any suggestions would be awesome!
Thanks for the help
I would think that installing a fresh CM7 would fix it, but since camera is a system app there is a chance that whatever the problem was, it may not have been remedied by the methods you've tried.
did you do a full wipe when you went back to froyo? if not, that would explain why the camera still wasn't working (among other things I imagine)
I've attached the camera.apk from CM7.0.0 stable. try pushing it to /system/app and see if that fixes.
Try switching to an freshly formatted SD. I had the same problem after installing an app called Daily Driver that I used for a time lapse video. I think it corrupted some files on the SD card. I try restoring to a previously good nandroid and it still wouldn't work. Switched out my SD and it works fine now. Hope that helps.
Hi all,
Just installed Android Revolution HD version 7.0.0.0 and now the camera isn't working properly:
When the photo is taken, there is no "confirmation" with the small animation that shows the picture zooming out in the corner.
When you try to watch videos the phone reboots or / video does not appear in the camera folder list.
I tried installing the stock version again, but the camera problems are still there. Could this be because of an edited Camera.apk file? Could it be one of the tweaks in the installation screen? (writeback , etc) ? I also installed again without the tweaks but the problems are still there.
I now installed Android_Revolution_HD-One_X_7.1.0 and the camera seems to work better but when I have low battery neither the camera or the video work, the buttons are disabled and it takes no pictures. Is this a tweak or a bug?
Finally, I think that version 7.0.0.0 changed a setting that affects the whole phone and all other roms that I flash, since even the stock rom is affected now by this camera problem. I 'think' it might be the data_writeback tweak, but now I can't disable it?
Any help very appreciated.
htckt said:
Hi all,
Just installed Android Revolution HD version 7.0.0.0 and now the camera isn't working properly:
When the photo is taken, there is no "confirmation" with the small animation that shows the picture zooming out in the corner.
When you try to watch videos the phone reboots or / video does not appear in the camera folder list.
I tried installing the stock version again, but the camera problems are still there. Could this be because of an edited Camera.apk file? Could it be one of the tweaks in the installation screen? (writeback , etc) ? I also installed again without the tweaks but the problems are still there.
I now installed Android_Revolution_HD-One_X_7.1.0 and the camera seems to work better but when I have low battery neither the camera or the video work, the buttons are disabled and it takes no pictures. Is this a tweak or a bug?
Finally, I think that version 7.0.0.0 changed a setting that affects the whole phone and all other roms that I flash, since even the stock rom is affected now by this camera problem. I 'think' it might be the data_writeback tweak, but now I can't disable it?
Any help very appreciated.
Click to expand...
Click to collapse
All the issues you mentioned above seems to work perfectly for me. Did you do a full wipe when installing 7.0.0? Has is ever successfully worked on any other rom?
dr9722 said:
All the issues you mentioned above seems to work perfectly for me. Did you do a full wipe when installing 7.0.0? Has is ever successfully worked on any other rom?
Click to expand...
Click to collapse
All other versions of ARHD used to work normally, including the camera. Now watching videos freezes the phone or restarts.
I also installed Insert Coin yesterday in case it fixes the tweaks from ARHD but the camera is still not working properly.
Did u do full wipe?
I'm also experiencing this problem. What should I do?
shiningarmor Did u do full wipe?
I did a full wipe yes, before the installation. Not sure if I did one afterwards (when installing the stock rom or ARHD v 6.0.0.0). You think that would reset all the tweaks?
monchee said:
I'm also experiencing this problem. What should I do?
Click to expand...
Click to collapse
The only thing that fixed the camera file system (saving videos and viewing them and also the crashes) was installing Pro Capture or some other alternate camera app and saving the files with that one, afterwards the default camera started working properly as well.
BTW, I installed Insert Coin 7.0.0.0 and that fixed the camera as well, but try using Pro Capture free also and saving some picture with that one.
SOLVED:
This resets the camera app and all the file saving/video playback becomes normal.
If you had enabled the data_writeback tweak there are chances that the camera will stop saving pictures normally (At least the Data_writeback seems to be the most relevant tweak towards file handling).
In case your camera is stuffed up in ARHD 7.0.0.0, install Insert Coin 7.0.0.0, then do a ARHD Super Wipe and then install ARHD 7.0.0.0 again without any of the tweaks. Now you can also update to ARHD 7.1.0.0 with a working camera.
My camera for my Galaxy Nexus has been broke for the last several weeks.
When opened, a black screen opens before shortly thereafter giving the message "gallery is unresponsive" and force closes.
I restored to AOKP build 3, updated the ROM to build 4 and flashed that (after corresponding factory reset, wipe data/cache/dalvik).
Now the camera opens, shows the "take picture" etc buttons but still has a black screen and force closes.
I assume while flashing different ROMs I had restored using Titanium backup a system setting/app that caused this problem.
I understand this question has been asked, but I have to find a solution to my problem (I have done battery pull etc.)
Any help will be appreciated.
I should mention that I have had a couple messages over the previous couple weeks where it says "SIM card invalid" and phone restarts.
I have not had this message is several days.
have you tried a different ROM?
use RootBox 4.2.2
ive been using it no problems and amazing battery life, not to mention the smoothness and pure awesomeness of the ROM
Jack Jake said:
have you tried a different ROM?
use RootBox 4.2.2
ive been using it no problems and amazing battery life, not to mention the smoothness and pure awesomeness of the ROM
Click to expand...
Click to collapse
Yes. Originally this problem happened shortly after flashing codename. With this ROM, a black screen would show and then "gallery is unresponsive."
I reverted to AOKP and flashed updated version. Now camera app opens, shows the take picture etc. buttons on bottom but where the actual picture should be stays black and gallery goes unresponsive.
Have also tried deleting camera apk and re-flashing a downloading camera zip file. Same problem.
biggie3201 said:
Yes. Originally this problem happened shortly after flashing codename. With this ROM, a black screen would show and then "gallery is unresponsive."
I reverted to AOKP and flashed updated version. Now camera app opens, shows the take picture etc. buttons on bottom but where the actual picture should be stays black and gallery goes unresponsive.
Have also tried deleting camera apk and re-flashing a downloading camera zip file. Same problem.
Click to expand...
Click to collapse
have you tried clearing data and cache for the gallery app? try that
Jack Jake said:
have you tried clearing data and cache for the gallery app? try that
Click to expand...
Click to collapse
Cleared data and cache for the app. Same issue.
Very frustrating issue.
Fast boot flash back to stock. If camera is still acting up then its more than likely hardware issues
Sent from my Galaxy Nexus using Tapatalk 2
do you get any messages after boy saying something like: com.xxx.xxx has unexpectedly stopped. this has happened to me to. you have to format your sd card. try that
remember to backup all your important file from the sd card to your computer EXCEPT the DCIM (where a'll your pictures and stuff are. anything related to the gallery don't backup)
Why not try a complete wipe.
fastboot erase boot
fastboot erase recovery
fastboot erase userdata
fastboot erase system
In that order
then fastboot back to stock as mentioned by namtombout.
If that doesn't work it is indeed a hardware issue.
Jack Jake said:
do you get any messages after boy saying something like: com.xxx.xxx has unexpectedly stopped. this has happened to me to. you have to format your sd card. try that
remember to backup all your important file from the sd card to your computer EXCEPT the DCIM (where a'll your pictures and stuff are. anything related to the gallery don't backup)
Click to expand...
Click to collapse
I don't think I've got any of these messages..
I will attempt the complete wipe per instructions in this thread (simply working up to the time that I actually will go through with it). I'm thinking I must have restored some system settings/camera settings from titanium backup during one of my recent ROM changes.
My battery life has been awfully poor lately as well....wondering if the restore of some system setting screwed with that as well...
Hopefully the complete wipe will get things back in order.
biggie3201 said:
I don't think I've got any of these messages..
I will attempt the complete wipe per instructions in this thread (simply working up to the time that I actually will go through with it). I'm thinking I must have restored some system settings/camera settings from titanium backup during one of my recent ROM changes.
Hopefully the complete wipe will get things back in order.
Click to expand...
Click to collapse
after you complete the wipe, DO NOT use titanium backup to restore your apps (even user apps). try fresh ones from the play store and see if that helps. if not im afraid you will have to go back to stock and then root again, flash a new ROM again, and then download your apps from the play store.
this problem has happened to me with my old phone (Samsung Captivate) but the formatting of the SD card fixed that for a while, when it started again i did the steps above and the phone worked better than ever.
Yesterday my phone was acting weird - Poweramp was starting at boot, Poweramp told me it couldn't verify my license, I had no media volume (but system volume was ok), my lock screen was being bypassed on boot, S-voice was starting whenever I put headphones in, no sound from bluetooth, etc. Weird stuff.
After troubleshooting and coming up empty, I took a backup with Clockworkmod, then restored to a backup I took on the 4th. When I rebooted, apps started crashing non-stop. Not only gapps, but also twitter, dropbox, etc. Every 1-3 seconds I'd get a couple of crashes. I also get a lot of notifications (not in crash windows) that it "cannot open database". These appear across the bottom of the screen, like when I'm notified that an app has received superuser access. It happens so often I can't even shut the phone off - I have to pull the battery.
I restored to a backup I took on January 10th and got the same thing. I restored back to the backup I'd just taken, same thing. I wiped the cache and the dalvik cache, same thing. I reflashed my gapps, but that didn't fix anything. I tried to remove my google account, but I can't get into the menu because the phone's crashing too fast.
So far, the only way I can get a usable phone is by performing a factory reset and setting up my phone again.
Does anyone have any suggestions on how I can get my data back? I have an app backup from January some time using My Backup Pro, but I don't want to lose a month's worth of data if at all possible.
I'm running a rooted Galaxy S3 (AT&T) on Stock 4.3. I've been messing with Xposed for the past couple days, but disabled almost all of the modules while trying to troubleshoot the issue (and it seemed stable before it started acting weird while I was shoveling snow). Also, only the most recent backup has Xposed installed.
Thanks in advance.
UPDATE: I was able to remove my Google account and this initially stopped the Google apps from constantly crashing, but other apps continued to crash. After a minute or so, the Google apps started crashing again.
I was able to restore a much older backup (4.0) and this seemed to work ok for the few minutes I tested it.
I did a factory reset on 4.3, which seemed ok, but when I started restoring my apps through My Backup Pro, android.process.acore started crashing every second or so. I cleared the cache, but it didn't fix the problem (in fact, it started crashing on the lock screen, which hadn't happened before.)
I'm starting to wonder if I need to flash a new ROM because something not backed up by Clockworkmod is FUBAR.
As far as I can tell, the causes of my issues were:
I think my CWM was messed up. When I flashed CM11 to get a working ROM, I saw there was an update pending. I installed that and it seemed to fix the problem with making new backups. I don't think I'll be able to recover the backups from before, but at least I can make new backups now.
I think the android.process.acore issue was the result of the My Backup Pro backup being from CM10.1 when I was trying to restore to Stock 4.3. I think there was some system data in there that wasn't compatible with stock. Selecting only the 3rd party apps that I "needed" to install seemed to resolve this.
I don't know about the original sound issue. I got a ticket response from Poweramp saying it was a Google account mismatch issue. I hadn't made any changes, so my guess is that somehow the account was corrupted. I don't know if removing/adding the account would have made a difference, since the whole thing blew up before I could try. It's also possible that something else got corrupted that caused the volume issue. Volume works fine now that I have a new ROM, so it was definitely not a hardware issue with the headphone jack. I backup restore or factory reset might have fixed the problem, but I don't know for sure.
Yesterday, I opened up the camera app and tried to record only to find it with the error, Warning: Recording Failed, then the app shuts down.
I have a rooted Samsung Galaxy Note 8.0 and I have used pimp my rom to edit camera quality, but I believe my camera was working after that. I hadn't backed up original pimo my rom settings before config so nothing can be done there.
I have tried the following things:
Cleared cache and data, reboot
Cleared cache and data, wiped cache partition
Installed other camera apps (They showed similar errors)
Factory reset
Plain reboot
Edit camera settings (resolution lowered, quality lowered)
The only thing left to do would be update to the latest firmware, but my rooted tablet doesn't allow it, so I would need to do it manually.
Is there a way to fix this problem? I have looked for answers to not prevail.
dronekillerdude1 said:
Yesterday, I opened up the camera app and tried to record only to find it with the error, Warning: Recording Failed, then the app shuts down.
I have a rooted Samsung Galaxy Note 8.0 and I have used pimp my rom to edit camera quality, but I believe my camera was working after that. I hadn't backed up original pimo my rom settings before config so nothing can be done there.
I have tried the following things:
Cleared cache and data, reboot
Cleared cache and data, wiped cache partition
Installed other camera apps (They showed similar errors)
Factory reset
Plain reboot
Edit camera settings (resolution lowered, quality lowered)
The only thing left to do would be update to the latest firmware, but my rooted tablet doesn't allow it, so I would need to do it manually.
Is there a way to fix this problem? I have looked for answers to not prevail.
Click to expand...
Click to collapse
lets see here... you rooted your phone, then pimped it out to peeps to make money when they need a camera?
The hardware is not gonna get any better by tweaking something in android. 720p is as best as you will get.
I bet your SD card is corrupt try refomating to allow camera to save to SD.
gooberdude said:
lets see here... you rooted your phone, then pimped it out to peeps to make money when they need a camera?
The hardware is not gonna get any better by tweaking something in android. 720p is as best as you will get.
I bet your SD card is corrupt try refomating to allow camera to save to SD.
Click to expand...
Click to collapse
Thanks, I'll try it and I'll get back to you.
dronekillerdude1 said:
Thanks, I'll try it and I'll get back to you.
Click to expand...
Click to collapse
Nope, didn't work.
Formatted SD card
Tried with every single setting on the camera.
Nothing works.
I'll try taking out the battery and sd card and putting em back in like I saw on a similar thread, but it's proabably not gonna work.