Hi everyone,
When I try to use my phone while charging, the touch screen sometimes becomes almost unresponsive.
However, it starts running perfect as soon as I unplug it. Is this the normal scenario for most of the Galaxy S users out there?
The only application I have running at the time is LauncherPro.
Sent from my GT-I9000 using Tapatalk
Related
Hello,
I am new to Nexus one coming from Iphone 3G. the phone is quite good but i experience a little problem.
When the phone is plugged in and is charging, the touch screen becomes very inaccurate. Typing on keyboard is impossible...etc, the only solution is to use the trackball. Everything is gone after unplugging it from the power cord.
Do you have any advice for solving this ?
Best Regards,
I've heard that if you press the power button to put the phone asleep and then press it again to wake the phone would reset the touchscreen
Sent from my Nexus One using XDA App
Is the phone getting hot while you are charging it?
I found that when it gets really hot that it can mess up the touchscreen a little.
Common problem, no fix for it. Just black out the screen, and the problem resets itself and goes away. Takes 1 second. It's a hardware issue.
i have same problem too....
sorry... wrong post
Thank you for your answer, i understand that plugged or hot can mess the touch screen. It's not "fixable", i will live with it.
I sent mine back 3 times and it is finally fixed. I have a perfect touch screen. Have not had san issue in over 2 weeks. Send back and leave note with your phone. As I said I would not except no for an answer.
Vinny
Sent from my Nexus One using XDA App
hmm just had this problem for the first time... searched "captivate touchscreen problem" and what do you know? found out its because im charging....!!
best bug fix for nexus on display problem after plunin to power
nolan76 said:
Hello,
I am new to Nexus one coming from Iphone 3G. the phone is quite good but i experience a little problem.
When the phone is plugged in and is charging, the touch screen becomes very inaccurate. Typing on keyboard is impossible...etc, the only solution is to use the trackball. Everything is gone after unplugging it from the power cord.
Do you have any advice for solving this ?
Best Regards,
Click to expand...
Click to collapse
after plugin to power
JUST....
turn off display(press power button)
clean display with hand..
and turn on again
I just rooted the Nook Color with Auto Nooter 3.0. It was all working perfectly for the first few hours, then screen just turn unresponsive from time to time. had to try so many times to get the unlock screen to unlock. and while typing, it just hits random keys that I wasn't even close to be touching. It's like the screen is sensing the touch in the wrong spots.
Anyone ever experience this? anything I can do to fix this?
Thanks!
Clean the screen and see if that doesn't fix it.
We seem to have a lot of screen issues in the last few days.
Try recalibrating your screen if cleaning doesn't work.
Unplug it from the charger if it is plugged in.
Sent from my PC36100 using Tapatalk
Can anybody suggest what is going on here?
I have found that if I install the Skyscanner flight app (which is very good for flight searches), then the screen starts to flicker and jitter. Once the flickering starts, then it happens everywhere, and only stops after a full reboot (it seems that a software reboot isn't enough to clear it).
The flickering starts as slight jittering, often jumping to the right a little - it's as though the screen loses sync. Then, there is colour flicker, and sometimes coloured pixels are left behind at the bottom of the screen.
I have tried this on two different stock ROM Droid 4s, and both exhibit the behaviour.
Does anybody know what's going on, and if there is a fix/solution?
I noticed this after opening snap chat once, running cm 10.2
Reboot was all that worked here but it has stopped since an update to the app came out. Not sure if that is really what did it though.
Sent from my XT894 using Tapatalk
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Probably software issue.
If your using a magnetic case (problem)
You could try disabling the lockscreen if its enabled.
Daydream could in my theory affect that time frame.
The backlight should last years longer. The gpu should as well. I can't think of any other hardware issue.
If you have an sdcard try cm11 [or the bn rom] and see what happens. OR full backup of current rom in cwm and flash cm11 to internal. Clean and restore 10.1.3 and be back to right where you left off.
lmacmil said:
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Click to expand...
Click to collapse
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case but it happens without it. Before this happen, my slide to unlock screen would act up by not unlocking when I slide to unlock; it would just go back to the initial lock screen. Slide to unlock would not work so I turn off the lockscreen, now experiencing blackout screens when I try to wake it up by pressing either buttons. This problem happens infrequently but it is annoying.
kinvid said:
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case...
Click to expand...
Click to collapse
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
lmacmil said:
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Works like this on my HD+, too. Sometimes requires opening case cover twice, but the screen always comes on.
Hey guys, this is a weird error that just started for no reason that I can think of. I had the latest nightly build on my Nook HD when all of a sudden various parts of the screen would just be auto tapping. I tried restarting multiple times, I even went for a factory reset but ended up simply flashing TWRP on it and flashing the latest AOSP Rom.
The problem is, when I load over to TWRP, I'm still getting these touch errors. Does that mean that it's something hardware wise that was broken? Does anyone have any advice on what to do next?
All and any help is appreciated, thank you.
Try cleaning the screen thoroughly. It gets very sensitive when dirty.
Sent from my SM-T707V using XDA Premium HD app
Sometimes putting the nook to sleep and waking it up again with the power button is enough to fix "stuck touches", something gets reset when the screen is switched off.
Also, some 3rd party chargers can cause continuous random "ghost" taps all over the screen while the charger is plugged in, but the problem goes away as soon as the charger is unplugged.
One thing that can help you figure out what's going on is going into developer options and enabling the "show touches" option. That way you can at least see when a "ghost" or "stuck" touch happens. Be careful when entering passwords in this mode though, since it makes it easier for someone else to follow what you're tapping too.
Sent from my BN Nook HD using Tapatalk