So, quite simple to explain, but can't figure out what the problem may be. This started happening randomly, I haven't modified the device, and didn't actually change anything in the system. It is running marshmallow 6.0.1.
The problem: the sensor works, but for some reason, randomly, it gives me the "too many attempts" error, even when I haven't even tried to unlock it. With that I mean, I turn my screen off, start doing something else, after maybe 5 minutes or more, I pick up the device, and when I turn the screen on, I see the too many attempts error. Even if I didn't even touch it. Tried removing all the fingerprints and setting them back but nothing changed.
When sensor get in touch with skin, will try to detect fingerprint. Should not happen in the pocket through cloth but if is thin...
If the phone is, for example, on the desk and after picking up reports again "to many attempts" then sensor may be malfunctioning.
Sent from my XT1635-02 using Tapatalk
Related
The touchscreen simply stops responding every now and then, witjout any pattern related to external or internal factors. When this happens, battery pull or a restore to factory do not help. After a while, everything starts working normally again.
Any idea what's causing this and how to cure it?
If it survives restarting and resetting, and then suddenly goes away again...
Sounds like a hardware problem, e.g. a not-so-good connection from the screen to the main board. Might need repairs!
Do you have a screen protector? I had a vikuiti one and after a while the display became eratic.
-------------------------------------
Sent via the XDA Tapatalk App
Iv found if I hold the device and my fingers are very close to the screen it effects the screen sensing my input.
Fon22
Hi i have this supper anoying problem after 5.0.2 update! So basicaly What it does is when ever i will pick up the phone it would turn off like the screen would dim (not rebbot or shut down) and after a little tapping on a screen it would turn on again and sometimes when it does that it would glitch a little. While typing this it happened twice its sooooo anoying idk what to do now if i wont find any solutions i will just buy samsung galaxy or something like that. Also my carrier is Virgin Mobile thanks
Same problem, same phone.
Definitely annoying! Seems random but especially while rotating for me. I have not been able to dig up any solutions thus far.
Check out your proximity sensor settings in the HTC testing app, or try Gravity screen. Mine did the same thing a couple times, also clean off your screen at the very top left, if you look real good you can see the sensor just under the front camera hole in the glass, also sometimes a screen saver will mess with this sensor. One more thing is the stock lock screen can cause an issue similar to what you are talking about, hope one of these help yo out, cane0716
Sent from my 710C using XDA Free mobile app
hi
thanks for information i already gave that phone to my friend and i think he fixed it by actually having different lock screen i currently have samsung galaxy s5 its wayyyy better lol
Phone turns off during use and will not complete boot unless plugged to charger even when the battery is almost full.
This error started last night after I did factory reset because of observed phone lag. I did mistakenly "wiped internal storage" but got the alert of "no OS during reboot", so I restored from my backup from SD.
the phone started properly but went off during initial setup and will go back off each time I tried turning it back on. I thought it was battery so I plugged it to power.
it did boot but will go back off once I have few touches on the screen.
I had to leave it plugged to setup my accounts else it will go off.
I'm using its Wi-Fi to send this message via my PC because any 2 - 3 touches will switch the phone off.
once it does that, it won’t even boot to bootloader before it goes off again unless plugged to power.
what I do to solve this please??
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.
Hi all,
I've recently got this tablet from Google store (and out of stock now).
After installed all things needed, a serious problem has appeared during in use. Its screen unexpectly trembles, pops notification out, runs and closes apps randomly then unable touchscreen at all. These make me crazy even in screen saver, and power button doesn't work sometimes to stop those happenings.
The device hasn't rooted and staying as 'pure' with only afew apps, so I've done erasing system cache partition on recovery mode and factory reset twice to solve this problem.
Nothing happened so far since reset the device but is still unsettling.. and now I just supposed touching screen badly (with sweaty fingers for example) or the screen protect film I affixed since unboxing might cause the problem.
Does anyone faces a problem like this?
Regards,
Allen
If it was greasy fingers my tablet would be completely unusable. Luckily a quick clean sorts any issues that causes.
My first suspicion would be the screen protector, as mine has done similar when there was something touching the screen. Maybe try taking it off and seeing how it goes? You can also turn on show taps in the Developer Options to be able to see what touches the tablet is detecting when it goes mad.
Better than before
The Real Dannilion said:
If it was greasy fingers my tablet would be completely unusable. Luckily a quick clean sorts any issues that causes.
My first suspicion would be the screen protector, as mine has done similar when there was something touching the screen. Maybe try taking it off and seeing how it goes? You can also turn on show taps in the Developer Options to be able to see what touches the tablet is detecting when it goes mad.
Click to expand...
Click to collapse
Thanks for your reply. Now I've used a BT mouse to match with mine and less touch on the screen apparently. Nothing happened so far.
It's not a problem of hardware I supposed and pretty sure that the screen protector interferes a certain touch as you commented. Still my eyes are keeping on what caused the problem.
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?