-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Touchscreen unlock problems?
- Thread starter Gnok31
- Start date
-
- Tags
- galaxy nexus
Yup!! That happened to me on Monday night. I was nearly crying!!! And I called tech support and they had to help me do a factory reset through boot menus. And then it didn't work so they had me to go Verizon to get a new one. The whole walk to the store my phone was still completely stuck. Of course, I get all the way there and the manager tries and it unlocked. I told him I'd give it a few days to see if it happens again and decide if need a THIRD device. I just am losing total confidence in this phone!
I hope it won't be a recurring problem. This phone has been good to me for the most part but I do see little quirks here and there:
-press the home button and sometimes the home screen takes a few minutes to re-populate the widgets and icons (this was a common thing with my old Eris because of the tiny onboard memory but it's kinda surprising to see this happen a few times with the latest and greatest Nexus phone)
-random rebooting (happened 4 or 5 times)
But this phone is still light years ahead of anything I had before.
overbyc1
Well-Known Member
Ive had this happen about 3 times. Freaks me out.
This is how I fix it. Hold the power key down, it pops up the power menu. From there, it should start registering your touches. Turn it off and then back on, "should" be good to go. Worked for me the last 2 times. Didnt have to reboot.
This is how I fix it. Hold the power key down, it pops up the power menu. From there, it should start registering your touches. Turn it off and then back on, "should" be good to go. Worked for me the last 2 times. Didnt have to reboot.
when it happened to me on monday, it wouldn't recognize my touch at all. even after several battery pulls. so vzw tech support said only option was a factory reset.
Well, it happened again mysteriously yesterday for no good reason. And it was frozen for about 3 hours. If I hit the screen hard (which i shouldn't have to do!) it will then become slightly responsive and I could enter my pin to unlock the phone. But the home keys would not work at all!! And while it was frozen, I got a phone call and couldn't swype to answer it. SO that being said, I am not onto my THIRD Nexus. Verizon graciously exchanged it for me again last night. So frustrating!!
VoidedSaint
Resident Ninja
its probably just a small glitch in the system, reboot to stock recovery, and wipe system cache (if you are not afraid that is)
or you can just wait for the update, and it may be addressed. just remember with all new products there are bound to be small bugs here and there, nothing is ever perfect anymore.
or you can just wait for the update, and it may be addressed. just remember with all new products there are bound to be small bugs here and there, nothing is ever perfect anymore.
Mr. Poppalopolis
Member
I'm curious, are all of you on stock? I have never had this happen to me before. Closest thing I've ever had happen is occasionally if I press something while the phone is in heavy use (loading an app or something), it will register a long press even though I only touched the screen briefly. Not really a huge deal though, and it mostly happens when I press the search button immediately after opening an app like Market or something.
zeppelin101
Newbie
I'd just like to chime in here. I've been having these kinds of errors quite a bit nowadays. I've owned this phone for about a month and I would say this started occurring about a week. But to me, this problem manifests itself a bit differently sometimes. For example, sometimes, instead of just being extremely unresponsive (sometimes completely unresponsive), the phone will actually become hyper responsive to input or even act like I'm providing touch input, when I'm doing none. It's hard to accurately describe, but it makes using the Swype keyboard essentially impossible when it happens.
I'm running a custom rom, custom kernel, @ stock voltage & cpu frequency. However, seeing how this behavior persisted across several custom roms, I'm doubtful that it's really a problem with the roms. I do still plan to try a stock 4.0.2 rom. If anything, to get this phone replaced, it will need to be unrooted & with its bootloader locked.
Also, pressing the power button to try to escape the nonresponsiveness doesn't always help.
I'm running a custom rom, custom kernel, @ stock voltage & cpu frequency. However, seeing how this behavior persisted across several custom roms, I'm doubtful that it's really a problem with the roms. I do still plan to try a stock 4.0.2 rom. If anything, to get this phone replaced, it will need to be unrooted & with its bootloader locked.
Also, pressing the power button to try to escape the nonresponsiveness doesn't always help.
zeppelin101
Newbie
Alright so I got the stock 4.0.2 image from google, installed it, along with CWM & proceeded to root the phone. So far, I'm having no problems whatsoever. I guess I'll know soon if staying stock is the way to go.
BubbaNexus
Android Enthusiast
this. people are posting about minor glitches with a new phone that has a new operating system-and on a new LTE network. i bought this phone fully expecting bugs. it's still the best thing out there
zeppelin101
Newbie
Aaaand another follow-up post. The problems persisted - they always came back, no matter what kernel or rom the phone was running. Finally I got a replacement GNex from Verizon. This only happened today. So far, the replacement has worked perfectly. I'm assuming everything will continue to be fine. I will post if anything changes.
Roaddog
Well-Known Member
I'd be interested in hearing if the issue pops back up for you or if it appears to be a hardware issue. I've recently started having this issue on my phone as well. It's usually in the morning when I wake up and go to unlock my phone. It will just flat refuse to register any touch input. The hold the power button to bring up the reboot menu trick worked fine for me both times, and it seems to register touch after that. Overall not a dealbreaker bug, but something that I hope they resolve in a future patch.
zeppelin101
Newbie
B-b-b-b-ump FOR GREAT JUSTICE!!
So I finally got a replacement for my original Galaxy Nexus. The last one, I figured, had its touchscreen broken in some way. Now I have my doubts. Thankfully its volume up button truly was broken, so it was not for naught.
I say I have doubts, because this new phone also seems to have this issue. But the important bit is that the occurrence of this issue is much less frequent this time around. I would say it barely happens, and when it does, 99.9999% of the time it seems to be when the phone charger was plugged in. I can't really recall a time when it decided to flip out on its own. Moreover, when it does become unresponsive, it's almost never 98+% unresponsive as it was with the previous model. I sometimes don't even have to go for a restart - I just unplug the charger and that fixes it sometimes, as well.
All in all, this bug is no longer a big deal for me. I hope I helped someone.
zeppelin101
Newbie
You may have a good point. I'm using a totally nonstandard one.. In fact, it just happens to be one that's micro-usb. I hope I'm not damaging my battery or anything?
colchiro
Extreme Android User
I use my 2 amp HP Touchpad charger for 3 devices. I like to use the stock cable for them, but it doesn't always happen. When out of town, I used my wife's LG charger for my Motorola DroidX for 2 years with no problem.
They standardized the plugs for a reason. They should all be 5 volt, but some use a custom cable (like the Nook Color to show orange when charging and green for 100% charge).
If your phone doesn't get hot or act goofy, I wouldn't worry about it. Oh wait, your phone DOES act goofy.
They standardized the plugs for a reason. They should all be 5 volt, but some use a custom cable (like the Nook Color to show orange when charging and green for 100% charge).
If your phone doesn't get hot or act goofy, I wouldn't worry about it. Oh wait, your phone DOES act goofy.
psycho_maniac
Member
Happened to me really bad on stock modified rom. I am now running akop and it kinda happens it just takes a 2nd touch. the 1st rom i would have to put it back to sleep and wake it up then it would work.