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.
Related
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.
Im not sure if im posting in the right place, but i think my phone doesnt like CM roms. Ever since i switched from JF to CM 3.6.8, my phone is constantly freezing up, in wich i have to remove the battery and put it back in so i can use it again, or in some cases is very slow and sluggish. This is completly random, as no specific event triggers this behaviour. The phone has never been dropped and has never touched water. Right now im using CM 4.0.1 and i still get the same behavior and even removed the partitions from SD card leaving only the Fat32 partition, thinking that might be causing it. No themes are installed at the moment either, and have tried several times wiping/reflashing.
Anyone can point me to what could be causing this ?
skat325is said:
Im not sure if im posting in the right place, but i think my phone doesnt like CM roms. Ever since i switched from JF to CM 3.6.8, my phone is constantly freezing up, in wich i have to remove the battery and put it back in so i can use it again, or in some cases is very slow and sluggish. This is completly random, as no specific event triggers this behaviour. The phone has never been dropped and has never touched water. Right now im using CM 4.0.1 and i still get the same behavior and even removed the partitions from SD card leaving only the Fat32 partition, thinking that might be causing it. No themes are installed at the moment either, and have tried several times wiping/reflashing.
Anyone can point me to what could be causing this ?
Click to expand...
Click to collapse
I it might be a problem when you flashed try flashing older version of cyanogen and the flashing 4.0.1. again. Worth a shot
my stock nexus one becomes highly unstable after booting up. im running strock 2.2.1, and this issue started apearing recently (after 2.2.1 update). the phone has never had any problems in the past.
whenever i turn the phone on, if i touch it it becomes really laggy and freezes, requiring me to pull the battery. however, if i let it sit for 15-20 minutes and then play with it it works fine, until the next time i shut id down (which can be days). i have performed a factory reset without reinstalling all of my old applications, i have formatted my sd card, and i have checked all the applications that start on boot up, but none of them seam to be the issue (when there was nothing on the phone it still reacted this way)
any suggestions? should i contact htc? this is really annoying.
Before you do, you could try to root and check the logs for anything suspicious (logcat and kmesg). Also you could try to install custom ROM and see if the problem still exists.
If it doesn't help - you should contact HTC.
EErez said:
my stock nexus one becomes highly unstable after booting up. im running strock 2.2.1, and this issue started apearing recently (after 2.2.1 update). the phone has never had any problems in the past.
whenever i turn the phone on, if i touch it it becomes really laggy and freezes, requiring me to pull the battery. however, if i let it sit for 15-20 minutes and then play with it it works fine, until the next time i shut id down (which can be days). i have performed a factory reset without reinstalling all of my old applications, i have formatted my sd card, and i have checked all the applications that start on boot up, but none of them seam to be the issue (when there was nothing on the phone it still reacted this way)
any suggestions? should i contact htc? this is really annoying.
Click to expand...
Click to collapse
Factory reset with formatted card? Has to be something wrong with the phone.
Go to recovery, wipe cache and dalvik cache, and try to boot phone again, often that helps.
tried wiping everything i can through recovery, yet my phone still freezes soon after start up. any chance htc will fix this? i dont want a refurb
Because when system has just booted up, it needs to check SD card and mounts all App2SD applications.
Try to boot your phone without SD and SIM card, see if it solves the issue.
tried removing sim and microsd and all th possible combinations.
it runs great without the microsd, so im guessing that was the issue. ill try another microsd to make sure its not a hardware/software bug related to sds in general but rather an issue with my specific microsd (which isnt the stock one).
thanks for the suggestion. i was very close to sending my phone in to htc (already had a ticket open and a fedex label)
that sounds good perhaps your SD card was corrupted. Connect it to your computer using a card reader, and do a disk check in Windows, see if it can fix any problem. Also try to degragment your SD card.
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.
So, my SGS has been giving me some problems lately and i'd like an opinion from the community about it.
So i was a happy Cyanogen user but about 4 or 5 days ago everything started giving force closes for no good reason. Installed nothing new, did nothing different. Just pressed the front button to check the time and everything started acting up. No wipe, regardless to what, got it working, it would always start FC'ing again.
So i changed to a stock JVT rom with semaphore kernel 2 days ago. Everything smooth again.
Today, everything was going great but i decided to reboot my phone for no particular reason. I powered off and on, very normally. Got stuck and constantly rebooting by itself to the black screen with white Samsung Galaxy S GT-I9000 message right at the start. Taking off the battery did nothing to help. Rebooted into recovery and noticed the phone wasn't able to mount any partition from the internal SD. no system, no data, nothing. Was behaving as if my internal sd just wasn't there. I could see the external sd perfectly though.
Plugged to Odin in download mode and reflashed my network's latest rom (JVQ) and everything's working again. Noticed my internal SD has everything it had from my previous setup.
So... could it just had been bad luck? i'm wondering if my internal SD is starting to physically fail... maybe it's time to just sell my phone?
Thanks!