Found some threads mentioning digitizers causing issues with this on other models of hardware, but doesn't sound the same.
Been holding off on rooting my Note that I've had for a week to wait for stock recovery, kernel, etc. to be out in case I had issues.
Rooted no issues, went back to stock just to make sure I could, then rerooted.
Not sure if coincidence, but now if I let the screen time out or manually do it, then wake it up.. my touch screen stops working. I can hard reset and it works until I do the same thing, then stops working again.
Anyone else seen this?
Reseil said:
Found some threads mentioning digitizers causing issues with this on other models of hardware, but doesn't sound the same.
Been holding off on rooting my Note that I've had for a week to wait for stock recovery, kernel, etc. to be out in case I had issues.
Rooted no issues, went back to stock just to make sure I could, then rerooted.
Not sure if coincidence, but now if I let the screen time out or manually do it, then wake it up.. my touch screen stops working. I can hard reset and it works until I do the same thing, then stops working again.
Anyone else seen this?
Click to expand...
Click to collapse
multiple threads:
http://forum.xda-developers.com/showthread.php?t=1849618
http://forum.xda-developers.com/showthread.php?t=1851387
http://forum.xda-developers.com/showthread.php?t=1854665
http://forum.xda-developers.com/showthread.php?t=1848261
http://forum.xda-developers.com/showthread.php?t=1847054
i was not rooted so I returned mine. sounds like some people have been able to get it working again
Related
My HTC Touch Pro from Sprint has always had problems. 3 times in a row the keyboard has stopped working and I've gotten it replaced. It's always been very laggy and since it's Sprint I haven't flashed any new roms or anything, just some reg edits an stuff. This most recent time though not only did the keyboard stop working but so did the audio stop working completely. I couldn't hear calls or music or anything, and when the guy tried to "fix" it, it stopped running in portrait as well. He ordered me a replacement a few days ago and it's supposed to come on Monday or Tuesday, he's gonna call me to go get it I have no clue how thats gonna work.. But the problem has gotten even worse. At first whenever I plugged in the earbuds that came with it, the audio would somehow magically return. Not through the buds mind you, they would just hang, through the phones actual speakers. I could make calls and everything again, but suddenly it started lagging like crazy and now it won't even get past the load-up "touch pro" screen. It just freezes there, I can't really go without a phone for 2 or 3 days and I need it on to receive their call. Is there anything I can do to get it running in some working manner?? And what can I do to stop these hardware issues from happening again??
EDIT: Another question, no reason for a new post. Is it possible to store my texts on my computer so I can delete em from my phone? I could never find the files!
It sounds like something is corrupted on your phone. Have you tried a hard reset? That is what returns the phone to "factory fresh". It will wipe out all of your data and any settings you may have changed which is not fun. However, it may solve more problems that it creates.
To Hard reset, turn the power off. Press and hold the volume down and Center button. Use the stylus to soft reset. Keep holding the volume down and center buttons. The screen will then give you instructions. Release and follow instructions.
Another option is to try a custom ROM. If you go this route, read the instructions carefully. Most importantly, USE A CDMA ROM!! Do not use the GSM ROM or much unhappiness will insue.
The downside to a Custom ROM would be that if you determine you need to replace your device under warranty, you have to undo everything. That takes a while and requires some reading.
Good Luck,
Doug M.
Thanks dwmackay! Appreciate the advice and I'll definitely keep all of that in mind when I get the replacement. I've always been curious about flashing ROMs and MightyRom looks very promising, is it safe to do? I'm sure atleast the keyboard will stop working again if not even more than that, would I be able to restore to stock and relock it easily? Appreciate all the advice!
I've been having a reoccurring freeze issue with my HD2 no matter what build I am using. On the initial first time startup everything works fine until the display goes to sleep. Once it does, the touch pad freezes. Hard buttons still work although don't do anything since it's stuck on the lock screen, and even if I soft reset or reflash anything, the problem persists.
Not even disabling the lock screen helps. Even if I install lock screen disabling apps (I've tried them all), the touch screen is still non-responsive when I wake the display.
Whether I use stock winmo, custom winmo or android (NexusHD2 gingerbread 2.3.4 as of late, but I've also used the old Desire Android 2.1) makes no difference; neither does reflashing HSPL, radio, ROM, Recovery CWM, reformatting SD card, fixing file permissions or even performing Task29. I've even restored everything all the way back to stock winmo which didn't work, so I performed every step along the road to getting back to Android. No success. I'm at a loss because I've tried every solution I have found online in just about every order imaginable.
There has to be some solution to this issue and I'm hoping that SOMEONE out there will rescue me. It's been a problem since I first got the phone and although even once in a while it will work for no apparent reason, it has been in this status for some time.
PLEASE help. I'm tired of paying a bill for a phone I can't use.
It's most likely a hardware problem. Your digitizer has most likely went out, I'm not a pro but it happened to me before.
little13193 said:
It's most likely a hardware problem. Your digitizer has most likely went out, I'm not a pro but it happened to me before.
Click to expand...
Click to collapse
Is the digitizer easily fixable or would I need to replace it? Or would it just be overall cheaper to replace?
Hi, I have a i9020T and just gotten it about 10 days ago.
Long story short the phone was dropped and the screen quickly started changing colors until it completely failed. So I order a new screen replace it, now everything looks good, the phone starts up normally, at this point everything is stock, factory reseted and everything.
Good right, well as soon as I put the phone to sleep it fails to wake up. It seems to function perfectly, buttons work I can unlock, I just can't see anything. Now matter how many times I restart and sleep the phone just doesn't wake up.
So I decide maybe another ROM/KERNEL could fix the problem, I was wrong. I have tried about 2 kernels, and 5 different roms, still nothing.
I am going to try and disassemble to see if there is a possible error, but other than the fact the phone wake up, it seems to work perfectly, CWM everything.
I cannot figure out if this is a hardware issue, but I am sure its not screen related. Hopefully not a motherboard issue.
I have searched google, xda everywhere yet no solution only few cases, but no real solution.
Thanks.
TheLegace.
I'm having the same issue. Then sometimes it randomly starts working again, but soon goes back to not waking up.
Had the phone since August, and never really had any of the touchscreen issues that people typically post about. Over the months I flashed many roms, always successfully, however at some point I noticed that my capacitive buttons stopped responding at all. I always had the nav bar enabled so it was fine, however recently I've wanted to get them working again. I followed the guide to restore to 100% stock CM12S, thinking that may fix it, however it did not. I haven't found anyone else that has this issue...is it likely hardware related and an RMA is my only hope of fixing this?
So I've been having this weird problem for the past few weeks, where on some occasions I would wake my phone, but instead of getting any image, I just get a entirely black screen with the backlight on. At first I thought it was from CM12.1, so I tried another ROM (Euphoria OS) but got the same problem. Flashed back to stock from Google which seemed to have fixed things, until today where it happened yet again. Does anybody happen to know what is causing this problem? I want to see if there's something I could look at before I get it try and get it sent off for repairs (I flashed back to stock and locked the bootloader again).
Thanks.