My A100 occasionally on booting for sure, not sure about waking, has an issue with the touch screen not responding. I use a numeric lock due to exchange server requiring it. Obviously this creates a problem getting in. After a several minutes it has always become responsive and let me in. At times it will respond erratically but eventually smooths out. Has anyone had this problem? Any ideas? I finally got in this time and killed my exchange account and the lock. I don't know how it will respond if it does it again without the lock. Any help would be appreciated!
Thanks!
Related
Hi All,
I am using an IMATE Pocket PC 2003 since the last 6-8 months. Over the last few weeks I am facing a problem with the Touch Screen. ALl of a sudden the Touch Screen fails to respond although the buttons are still working.
Sometimes after several reboots, the Touch Screen responds sometimes it doesn't. Sometimes I just keep it IDLE for 2-3 Hours and the Touch Screen starts responding. There is no fixed time of the error also the error is random. Sometimes everything is normal for one week and there is no problem at all. Sometimes the problem persists continously.
I have Hard Resetted it atleast 4 times but the status still remains the same.
If anybody has experienced this, do share your thoughts.
Regards
Jinesh
I read somewhere that if you re-align your screen it may help.
Do your hardware buttons still work? You could try mapping tpenable.exe to a hardware button and select this when the screen locks up.
Touch screen problem
Jinesh,
did you ever manage to fix this?? This is exactly the problem I've been having on my MDA Compact (Magician) for ages: screen unresponsive, buttons still working. I started a thread on this topic as well and got some suggestions, but never managed to sort it out. I'm a bit wary to resort to flashing a new ROM or something like that since it seems to open up a whole new set of potential problems and will cost me my warranty with T-Mobile at the least (Not that they're much help, but still)...
Thanx,
Joost
Maybe the cover
The Qtek9090-screen is sometimes locked (e.g. when it's in a car holder which causes too much pressure on both sides of the display.) The same happens sometimes without any cause - pressing on both sides unlocks the screen.
Hi,
I am using an O2 Mini now and have sold off that Imate. But what I came to know that the touch screen problem was due to the irregularities in the network. The screen stops responding fast when network is weak and the device keeps on searching the network.
I have faced this problem once or twice in my O2 mini also.
Regards
Jinesh, I don't know if you checked out my thread on this, but indeed this is the conclusion I've reached: bad network causes the unresponsive screen. I think it might have something to do with the priority windows gives to the screen routine compared to (searching for) network. As of yet I have been unable to find a way to increase priority for the screen or lower it for network, though I browsed through the registry pretty extensively. Suggestions from anyone on this would be most welcome.
Using the stock ROM for the Galaxy Nexus, Android 4.04 from Google, I'm finding this bug (which has been elsewhere reported, but not acted upon by Google) where the touch screen is unresponsive. You press the 'power' button, the 'slide to unlock' screen appears, but the touch screen doesn't respond to anything.
If I get a call while the phone is sleep, the same thing occurs - can't answer the phone.
I usually have to put the phone to sleep/wake it up 5, 6, or more times before the touch screen again becomes enabled in these situations.
Does anyone know why this happens? There has been much conjecture about this, but I have yet to see anyone say for sure why this would be happening. A disabled touchscreen at such a crucial point in a GUI is pretty horrific.
- Tim
was gonna make a new thread on this but since i found one with the exact same thing happened figured why waste space, but anyway this just happned to me running stock 4.0.4 cdma unrooted. was just charging my phone unlocked it to check twitter and the lock screen was completely unresponsive for whatever reason. I continued to turn the screen off and on several times and then just decided to pull my battery and it worked fine.
This is the first time its happened to me and its kinda troubling as I dont want this to be a recurring thing and was wondering if this continues to happen or its just some single random occurence?
Dear Friends,
After updating my htc one m8 to Android 5.0.2 and resetting the phone as needed, i am facing the problem of switching off the screen randomly while i am using it. can anyone help me.
appreciate the support.
thnx
hogrsq said:
Dear Friends,
After updating my htc one m8 to Android 5.0.2 and resetting the phone as needed, i am facing the problem of switching off the screen randomly while i am using it. can anyone help me.
appreciate the support.
thnx
Click to expand...
Click to collapse
Have you checked the screen timeout settings in settings/display & gestures? That's the most likely possibility.
It's not a timeout problem for me.
My timeout settings are at one minute or more and the screen will blank on me in the middle of active use. If I tap the power button repeatedly (the number of times required varies, but it takes fewer if the taps are spaced by a second or so), the screen will come back on, but more often than not, the screen will black again immediately (i.e. in the middle of the unlock process). The screen blacks, but remains responsive to touch. If I tap where a button was before pressing the power button, when I can see again, the app (or launcher screen) has changed accordingly. The problem has gotten more frequent, to the point that my phone is almost unusable as of yesterday afternoon.
I have tried a factory reset as of this morning, which didn't remove the problem. My battery seems to be OK. I'm still getting roughly the same battery life I've always had. I'm stuck, and I'm not finding abundant references to it anywhere, so any help would be appreciated.
A brief history of my interaction with this problem: I bought the phone used about 3 months ago. about 3 weeks in, the blanking problem started to appear, but only in landscape mode apps (games). This was not frequent until about a month ago, when it started becoming more frequent and affecting everyday activity, not just games. About 3 weeks ago, I started having problems with image persistence (which may not be relevant, but I'm not sure either way). Yesterday afternoon it started blanking repeatedly. Restarting the phone had helped in the past, but not this time. Leaving the phone shut down for 2-3 hours also failed.
I am getting very frustrated, and I really like this phone.
Please help, if anyone can.
Thanks very much.
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.
I was wondering if anyone else is experiencing the following issue, perhaps it's related to https://forum.xda-developers.com/mi-9-se/help/ghost-touch-mi-9-se-t3953616 ?
Sometimes, when trying to unlock the phone from the lock screen, it will not register my touches. Or perhaps more likely, only register them partly.
First I need to swipe up to get to the unlock pattern. This step will sometimes not work at all, or sometimes swipe up a bit.
If I get past the first step and get to the pattern screen, it will no let me draw the pattern. It might recognize one of the points you're supposed to touch to draw the pattern, or it might just vibrate whenever it's touch.
Waiting a while, or furiously cleaning the screen will sometimes work, sometimes not.
Did a factory reset, but the problem came back after a few days. Sent to service (purchased from eGlobalCentral). Did another factory reset before sending it in, but they couldn't reproduce it of course, even though I gave instructions that it was intermittent and needed to be used daily for a few days after factory reset.
Wasted around $60 on this.
No touch issues when I finally manage to unlock it.
Anyone had similar issues?