This just started today. If I go to open the Camera, the screen goes black and then a few seconds later the force close window pops up.
I tried closing everything with Advanced Task Manager. Same problem.
Powered off the phone and rebooted. Same problem.
It was working a few days ago and I haven't installed any new apps or done anything drastic since.
I have a feeling wiping will fix it, but I wanted to see if anyone else had this problem and fixed it before doing that.
Running JF1.5 ADP currently.
RueTheDay said:
This just started today. If I go to open the Camera, the screen goes black and then a few seconds later the force close window pops up.
I tried closing everything with Advanced Task Manager. Same problem.
Powered off the phone and rebooted. Same problem.
It was working a few days ago and I haven't installed any new apps or done anything drastic since.
I have a feeling wiping will fix it, but I wanted to see if anyone else had this problem and fixed it before doing that.
Running JF1.5 ADP currently.
Click to expand...
Click to collapse
Try using adb to delete the camera.apk and then redownload JF and pul the apk out of it and repush it to your phone
****. Just upgraded to JF 1.51 ADP and wiped, but camera still not working. Will now try the US CBR43 version of JF1.51 to see what happens. I hope this isn't a hardware issue.
Same problem with JF1.51.
Then I did a Nandroid restore to a date when I know the camera was working. - Same problem.
Then installed the latest Cyanogen ROM. Same problem.
I'm out of ideas. Help!
Try the camcorder? They're technically seperate apps. Also, go download some third party camera or recorder, like Qik or SnapPhoto. If none of those work, it's most likely a hardware problem.
When the camera app can't access the camera (such as a malfunction or other problem) it returns an error because part of its components (in this case, the most important) isn't working. Try even going to another build, like Cyan's, to see if anything else gets resolved.
lukekirstein said:
Try the camcorder? They're technically seperate apps. Also, go download some third party camera or recorder, like Qik or SnapPhoto. If none of those work, it's most likely a hardware problem.
When the camera app can't access the camera (such as a malfunction or other problem) it returns an error because part of its components (in this case, the most important) isn't working. Try even going to another build, like Cyan's, to see if anything else gets resolved.
Click to expand...
Click to collapse
Tried Cyan's ROM. Same problem. Moved apps off SD and back to memory, same problem. I'm going to try the phone with a different SD card as a long shot. If that doesn't fix it, I'm thinking definitely hardware.
RueTheDay said:
Tried Cyan's ROM. Same problem. Moved apps off SD and back to memory, same problem. I'm going to try the phone with a different SD card as a long shot. If that doesn't fix it, I'm thinking definitely hardware.
Click to expand...
Click to collapse
Did you try a third party app?
lukekirstein said:
Did you try a third party app?
Click to expand...
Click to collapse
Yeah same problem.
If it's hardware, do I need to unroot it before going back to T-Mobile?
Yep, sounds like a hardware problem. It'd be a good idea to try to unroot it, unless you're on T-Mobile's phone insurance, in which case it's no-questions-asked.
What in the blue ****?
I was having issues with Touchdown (Exchange sync) force closing, so I upgraded to the latest version which fixed that. Then just for ****s and giggles I tried the camera and it's working now. I doubt the two are related, but man WTF.
Anyway, on the plus side, I do like the latest Cyanogen ROM better than the JF1.5.
eh..okay then. Change the thread title to [SOLVED] please
Edit thread doesn't let me change the title.
Anyway, it was the SD card. Reformatted my EXT2 partition and redid apps2sd and it started working again. Then started getting a bunch of force closes on other apps. Ultimately reflashed back to JF1.51 and moved all my apps back to main memory. Everything works flawless now.
I rooted my G1 the day I bought it in April and did app2sd shortly after. Nothing but problems. Tried every apps2sd method. They all work fine for a few weeks and then start falling apart.
Related
So I have a ADP-1 and about once a day it freezes after you put it in standby I end up having to take the battery out and putting it back in and reboot, when I say it freezes it is unresponsive to any buttons you push. I thought it was an app causing this so I run advanced task manager and kept only weather widget running as far as apps go. as far as processes go i don't know what can be turned off or not so I have not alltered them. I am running cyan 3.6.5. Any way to tell what is causing this. It boots back up fine everytime and only does this once a day. Any Ideas?
gtrplr71 said:
So I have a ADP-1 and about once a day it freezes after you put it in standby I end up having to take the battery out and putting it back in and reboot, when I say it freezes it is unresponsive to any buttons you push. I thought it was an app causing this so I run advanced task manager and kept only weather widget running as far as apps go. as far as processes go i don't know what can be turned off or not so I have not alltered them. I am running cyan 3.6.5. Any way to tell what is causing this. It boots back up fine everytime and only does this once a day. Any Ideas?
Click to expand...
Click to collapse
Try wiping and reflashing the newest cyanogen mod.
anything I should know about the latest? everything the same.
gtrplr71 said:
anything I should know about the latest? everything the same.
Click to expand...
Click to collapse
Pretty much the same, auto a2sd if you have card partitioned right. I'm liking it alot. The latest is 3.6.7.2
I keep reading about compcasche do I have to do that I am not comfortable in the console.
I've never had to do much in console with Cyanogen's but thats just me. I just flashed this on there and away I went.
http://forum.xda-developers.com/showthread.php?t=537204
do you know if android plus theme works with the new ROM? Just looked it does not
Post back with how it works out for you
Try turning off your data roaming.
Settings -> Wireless Settings -> Mobile Network -> Data Roaming
or something like that
That should fix it, if not, reflash your ROM
P.S Android + will not work with Cyan 3.6.7-2
Cyan will be releasing 3.6.8 today, and OhMarni will port it as soon as everyone thinks its stable.
thanks! You guys are great
after disabling data roaming the phone went about 48 hours and froze again tmobile said there is basically no info about that problem that they could give me being that I upgraded the recovery the warranty has been voided. Any other Ideas?
it froze up again and I called it from My wifes phone and It unfroze the buttons blinked twice and the screen came on so this is app or ROM related. is there an app that can record the functions on the phone to see what the last function was that is causing the problem?
gtrplr71 said:
it froze up again and I called it from My wifes phone and It unfroze the buttons blinked twice and the screen came on so this is app or ROM related. is there an app that can record the functions on the phone to see what the last function was that is causing the problem?
Click to expand...
Click to collapse
read up on adb, get it to work and type adb logcat
you shouldn't have told tmo you upgraded your recovery, rooted......
if all else fails, flash RC29 (DREAIMG.nbh) and start over
So yesterday my wife sat her g1 in a cuphold with just the tiniest amount of liquid...she dried it out and it worked fine for a while
Then she started getting force closes on everything (myspace, facebook, weatherbug) Then the touchscreen quit working. She decides then to tell me about the liquid thing, but im thinking "this doesnt sound like liquid, it sounds like a software/rom issue"
So this is what I have done thus far.
Reflash CM-same issues
Wipe-didnt fix
Thinking it may be an SD card problem (apps force closing), I put my SD card in it-didnt fix it
Next step was reflash signed_dream_devphone_userdebug....whatever
Wiped, reflashed the above, then flashed CM to it.
Still no touchscreen!
Any ideas?
If not, its for sale!
UPDATE: Home for lunch, and im downloading a new copy of signed-Dream_devphone...going to try again
The force closes are software, I'd bet, but if after a full wipe and flash of CM the touchscreen isn't working, you may very well be looking at a hardware problem.
Long time reader, first time poster (hello everyone!). I was wondering what the opinion of the folks here might be and if they've any suggestions. Today my rooted Nook Color suddenly started acting up. Applications are very often not responding as they should, bringing up the 'Wait' and 'Force Close' box (happens when pressing the soft back and menu buttons as well). It's really quite weird, earlier today I was using it just fine, and suddenly it started acting like this. I tried the usual things like fixing permissions and clearing the dalvik cache, nothing helps. Also, annoyingly restoring a backup from a previous 'known working' state didn't help either. (I suppose I should note that I'm not running CM7 or anything like that)
Any suggestions or ideas on what could have happened? Should I perhaps return it to stock and try to exchange it for a new one (I've only had it for about a month)? The fact that it seemed to still be happening when I restored a back up makes me wonder if it's some kind of hardware issue.
The thing driving me crazy is how it's so suddenly acting strangely. I've been using it rooted (and overclocked, on dalingrin's excellent kernel) just fine for about a month and it's never seemed unstable or anything.
I forgot to mention (not that it probably matters) but the volume buttons caused the wait/force close thing too. Guess I'll be calling them tomorrow.
Having same problems. And VERY SLOW. Wait or Force Close
Very weird, but I noticed today that it started acting flaky in my Nookie Froyo 0.6.8.
I installed Amazon's app store on there today and angry birds rio. The apps seem to be okay, but general opening and navigating are herky jerky.
Something else that is weird, I was just using it and it completely locked up on me to the point of needing to do a hard shutdown by holding down the power. At the exact same time, I happened to look at my phone and it also had rendomly rebooted itself at the exact same time. My phone is running CM7 (Droid1).
Coincidence?
HI,
I had a variety of problems with similar symptoms as you describe, but I had
been playing with several uSD installs of HC/Froyo/CM7 internal/Froyo internal etc.
I believe that the main cause of my problem was due to an interaction between
the EXT3 and EXT4 formatting of the cache partition. The solution for me was to
reformat the cache partition for my current installation.
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Not sure if any of these are relevant to you though.
Good luck.
Peter
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
pmilford said:
HI,
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Click to expand...
Click to collapse
Thanks, but I tried those already (I forgot to mention it in the first post, but I did try reformatting the cache partition).
JLCollier2005 said:
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
Click to expand...
Click to collapse
Yeah, I guess that's a good idea. Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
9thSage said:
Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
Click to expand...
Click to collapse
All I'd need to do to install Froyo from here is format/factory reset everything with clockwork and then install the zip from within CWM, correct?
Couldn't get it to work for some reason. Since I wasn't sure, I decided to format data, cache, and system, then use one of the excellent "Nook Color Restore to Stock" zips. It seemed like it was ok (couldn't test it more since I forget my B&N password and evidently made a typo when tying my mother's maiden name ), decided to try that back up again since I knew the back up worked at one time with no problem (and the md5 was fine, so that shouldn't have changed) and it worked fine for maybe 20 minutes, but now it's weird again.
I'll have to try Froyo again tommorow when I'm hopefully less out of it. I suppose that's probably a more meaningful test.
I know I said I was going to install Froyo, but I decided to try bringing it back to stock and re-rooting it from scratch. I've been using it for a while (reinstalling apps, changing settings back...etc) and it's worked absolutely fine. Been using it on and off for a few hours.
I'll be sure to really bang on it today to make sure it's stable, but so far so good.
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
9thSage said:
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
Click to expand...
Click to collapse
Glad to hear! I actually just had a similar problem (again on my Droid) that it ended up being the ROM, but yet everyone else I know had no problem on that rom....just goes to show you Android is different for every unit.
Hi,
A few weeks ago I moved from the Evervolv ICS rom to Kang's CM7. When I did my camera stopped working. I get a black screen and eventually a FC.
I did a full wipe of the device, factory reset and even reformatted the SD card. I did this again and went back to ICS, and also gave JB a try but still no luck with the camera. I found this thread and even ordered a new camera module off of ebay. I put the new module in this week but it still does not work. I suppose it's possible that the second module is bad, but seems more likely something is corrupt.
How can I fix this?
TIA
camera and black screen
Did you ever get this figured out. I'm having a similar problem. Here are my details...
using HTC Google Nexus One, Android 2.3.4
This is very strange, but I noticed today that my camera is no longer working. I have no idea why, but it just goes black when I select camera. I have restarted my phone, took out the battery, etc. and nothing. Also, I even tried downloading other camera apps, and they won't work either.
Even more frustrating, though, is that my phone goes black when I make or receive a call. The calls do not get dropped, but when the call is over, I can't even hang up, as my screen is black. It's weird because my phone is still "ON," but I obviously can't do anything. The only thing I can do is take out the battery, put it back in, and turn the phone back on. Then, it works perfectly normal...until I make or receive another call. I have no idea what to do.
Can anyone help? I'd really appreciate it, as I use my phone for everything!
rts58 said:
Hi,
A few weeks ago I moved from the Evervolv ICS rom to Kang's CM7. When I did my camera stopped working. I get a black screen and eventually a FC.
I did a full wipe of the device, factory reset and even reformatted the SD card. I did this again and went back to ICS, and also gave JB a try but still no luck with the camera. I found this thread and even ordered a new camera module off of ebay. I put the new module in this week but it still does not work. I suppose it's possible that the second module is bad, but seems more likely something is corrupt.
How can I fix this?
TIA
Click to expand...
Click to collapse
No I never figured it out. I may try to go back to stock or non cm anyway. I'm pretty much out of ideas. I haven't had any call issues. I remember others having the same issues as you. Good luck.
Sent from my Nexus One using Tapatalk 2
Hello to you all,
I've looked and couldn't find a similar thing happen to anyone else!
So, I have a X8 with locked bootloader and stock Ginger DX 29, and although it used to work fine, I now am experiencing this problem with my camera.
Basically, the camera button isn't recognized to launch the app from the homescreen for a start, and then if I do open it from the app drawer, I can see the image fine, but nothing works (accessing the settings, changing from camera to video, taking a picture, etc) and after a few second I get a Close app/Wait kind of dialogue and I'm back to square one.
this is annoying because I tried pushing older camera.apks that I knew worked with no problem, no change. I tried doing a factory reset, no luck, flashing gdx again from scratch (didn't try the SEUS reset because it's a pain to root again and all that, and gdx used to work fine) I've also checked that it wasn't a hardware problem by mapping the camera button to an action in snesoid and it worked fine.
I don't really know what to do from that point! I was thinking maybe it's got to do with my image folder on the sd card, or something like that since it's the only thing that stays there throughout the wipes? Anyone knows what could be at fault? It's annoying not able to use the camera!
Thank you in advance.
Re: [Q] Weird camera problem, any ideas?
Settings ,applications,manage applications,find camera.apk and wipe cache and data.
If it doesnt help,try to download a camera app from play store and see if it works.
so, wiping the data didn't work, however I did two things : download a third party app and renamed my DCIM folder to another name, and one of them worked!
I'm suspecting the second one because as I tried my original app again, everything worked as well...
It must have been write protected for some reason, and that's why my camera app would be stuck at the begining I guess...
I'll try to copy my files back in the new folder that was created and see if it happens again.
Thank you!
Re: [Q] Weird camera problem, any ideas?
nice to hear you solved it. :thumbup: please do indicate in the thread title that it's solved. it may help other users with a similar issue.
Sent from my rooted tomato using tapatalk
All done!
I'm still not able to use the camera button when on my home screen but I'm guessing it's a rom issue, as I don't remember how it behaved before...
awkXda said:
All done!
I'm still not able to use the camera button when on my home screen but I'm guessing it's a rom issue, as I don't remember how it behaved before...
Click to expand...
Click to collapse
i'vw never really experienced that before... so i can't help. just a suggestion though, have you tried using a different sdcard? if it still persists, maybe you're right and it's a rom issue.
Sent from my rooted tomato using tapatalk