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?
Related
Hello all.
I have an sensation. 5 months ago it fell. Screen was cracked. Some shop repaired it for me back then. Since then I have been getting more and more touchscreen issues. Sometimes it doesn't even respond at all. What I will have to do then is put screen on sleep again and activate it again. I have been trying different ROMs and kernels so I have a feeling it isn't the software.
Yesterday I went back to the shop and he blamed it on the different ROM. So I'm now installing my old 2.3.3 backup. He said that with 2.3.3 my screen would work again. However, I don't believe him. I think he just messed up my digitizer.
Anyone got any ideas on how to fix this issue?
UPDATE #1:
Installing my old backup didnt even work. It hung on the white startup screen.
Please someone help me!
me too. having screen problems after changing digitizer.
changing the digitizer on this device is a major catastrophe...
Hi all, I have a weird problem with the proximity sensor in my HTC Titan. I got a new Titan about a week ago, to which I immediately installed HSPL and Dynamics rom. After I did all the tweaks and installs I like, I noticed that every time I dial a phone call the screen goes off and stays that way until the number I called answers. If the number does not pick up, only thing I can do is remove the battery basically to hang the call up. I noticed that removing the back cover slightly affects the issue and its easier to get the screen back on (by pressing the power button), but still removing it does not solve the problem. With a handsfree I can actually stop the call as it has an accessible end call button.
I tried flashing another custom rom and also a stock rom, both had the same issue. So, I took the device for warranty repair. I got it back today from HTC, with a note saying that software has been updated and problem has been fixed. I tried the device and surely it was working. Well I can’t live without an fully unlocked device and against my better judgment flashed a custom rom again… And surprise surprice the problem appeared back.
Im thinking here that could I adjust the proximity sensor from the registry, if its somehow too sensitive or something. Strange part naturally is that other people with same rom are not experiencing this behavior, so it is device specific problem. Also I don’t think I can take the device back again and say yeah I was flashing some custom roms on it and lost whatever you did with it.
There a Proximity folder at HKLM and I tried changing some values there but no affect at all. It probably would be better to have someone who understands about the values little try to take a look.
Thanks a lot!
It's a hardware problem. I got the same issue after 2 months of use. I sent to repair but they wanted to charge me to do that, so I haven't fixed it but I still can get the screen back by pressing and rubbing my finger on top of the sensor.
But when I got it back from repair today it was working. I made few phone calls and it was working totally like normal.
you are not alone
Loco5150 said:
But when I got it back from repair today it was working. I made few phone calls and it was working totally like normal.
Click to expand...
Click to collapse
I can tell you that you are not the only one with this problem, it happened the same to me. I'm still unsure if the problem is hardware or software, but I think it's software because it happened just after I install Dynamics_2.0_Titan. I really wish that someone will bring a good solution for it.
I've got an odd problem with my Excite 10. A few weeks ago it started acting funny. What happens is every once in a while the screen will flash off and then back on again. When it does that it messes with my system, I have an app locker, and it re-locks the app when the screen refreshes, also, I'm trying to use an emulator that works with a bluetooth controller, but when the screen flashes the connection to the controller is lost, just as if I had gone out of the app and then back in. I'm running the latest OS as of this date, and any help would be appreciated.
Thanks,
TechPlease
google your phone and issue, and see if anyone else has your issue with current update.
if you think its hardware problem go to your provider and tell them the issue.
or you can go to ebay and order the LCD if you think the screen is responsible... dropping a phone can hurt the delicate ribbons inside... does squeezing different spots or shaking your phone cause any issues?
Ok..
I had this phone for a while and I started using it again recently. I have fully replaced the digitizer/lcd bezel before with no problems (been a phone repair tech for 10 years) And it has worked fine.
The other night I reverted it back to stock because it seems to be the only way to get a constant data signal. Worked fine. I then updated it to the newest OTA update without a problem.
I then rebooted it and it stuck on a black screen loop with the buttons going on and off for hours. I spent 7 hours trying to figure out what was wrong, flashing, re flashing.. Nothing. Finally I get CWM recovery installed and find out my SD card is fried. So I put a new one in, and transfer over the roms I want t flash. 3 different roms, all with no touch screen.
Revert back to stock, still no touch screen.
Could something have gone bad on the board to have caused this? Is there something system wise not getting wiped that may cause this? Its to much of a coincidence that the touch screen and buttons would go out after all this happened.
Any help would be appreciated. Im waiting on a new digitizer now to check because Ive already gone over all the connections. But if its something software wise, Id like to try that before doing another digitizer replacement.
Thanks
funny you made this thread. i just got my hands on a soft bricked g2x that was stuck on the blue lg logo. after a quick nvflash it boots right up......but with no touchscreen. not sure if it ever worked as im not the original owner.
but i'll be keeping my eyes out on this thread for sure!
Id give a pretty to see inside both of your phones. Sounds like a bad contact on the ribbons.or one of them may have been ripped during a screen installation. I've never heard of the screen just up and quoting working without some major stuff happening to the phone. My guess is these screens were replaced with the wrong screen.just a guess though.
Sent from my LG-P999
grantusmantus said:
Id give a pretty to see inside both of your phones. Sounds like a bad contact on the ribbons.or one of them may have been ripped during a screen installation. I've never heard of the screen just up and quoting working without some major stuff happening to the phone. My guess is these screens were replaced with the wrong screen.just a guess though.
Sent from my LG-P999
Click to expand...
Click to collapse
I have done phone repairs for quite a few years, It wasnt a wrong screen and has worked fine for a year since its replacement. I have already opened the phone again and made sure all contacts were fine. What Im trying to figure out is if there is maybe some part of the system/boot that holds the touchscreen drivers and they have bee erased?
Again, I find its a huge coincidence that it worked fine up until this happened then as soon as its booting again, stops working... Which is why I think its a software issue.
Try touching the corners of the screen after booting up start with the top left and go clockwise. One of the roms used to mess up the connectivity between phone and screen. And that is supposed to reset the touch screen. A old g1 trick
Sent from my SGH-T999 using xda premium
A couple weeks into using my new nexus 5, half the touch screen stopped working (if you really had to, you could still press buttons by pressing the thing really hard). It seemed like it was a hardware issue so I unrooted and wiped the device with this guide
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
with the intent of returning it. Part of this process involved TWRP (where there are touch controls), and the problem occurred even there. (to me, that seemed to confirm it must be a hardware issue).
Now after everything is factory-reset, the touch screen has magically started working again. I'm extremely confused how this could have happened. My best guess is that the issue was intermittent and i accidentally jiggled the phone in a certain way to make it start working again.
Does anyone have an idea what could have happened, or how I could stress-test things to find out? If it is indeed an intermittent issue and the phone needs to be replaced I'd like to do that ASAP because I'm leaving the country and dealing with warranty will be difficult from overseas.