I bought a used Nexus 5X off eBay. It was running 7.1.2. I did a factory reset, and when I get to setting up fingerprint, it will not read my fingerprint at all. Even worse, about 1 min after it started reading my fingerprint, even if I'm no longer at the fingerprint setup page, the phone will crash and won't boot up until I hard reset it (long press the power button)
I searched online and saw some issue about Google breaking the fingerprint sensor with the 7.1.2 update. I then let the phone update to Oreo 8.0 but the same problem persists.
Is this a known issue? Or is my phone bad?
Related
Today i received my Nexus 5x, however during and after initial install i cannot use the fingerprint security. It tells me to put my finger on the scanner and wait for it to vibrate, however nothing happens. I tried factory reset and wiping through the bootloader. Has anyone encountered similar issues? Is this a hardware failure?
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.
After setting up the phone, i started to get "fingerprint scanner hardware not available" whenever I tried to unlock. I rebooted the phone. After the phone came back, I no longer received this message however couldnt unlock the phone with my fingerprint anymore. I then checked under settings->security and no fingerprint / nexus imprint settings were found.
I got online with google support who had me factory reset, boot into safe mode, wipe data from bootup menu to no avail.
Terrible.
You're not alone.
I regeat to say that I'm having these exact same issues. So you're not alone in this.
I've had my Pixel 3 XL for about 3 weeks now, not been dropped or damaged or anything like that, also not rooted. Its fully up to date, Android 9, security patch 5th Jan 2019.
Yesterday it stopped unlocking properly - the screen takes 20-30 seconds to respond after either pressing the lock button to wake it, touching the fingerprint sensor or double tapping the screen. I occasionally get "System UI has stopped responding" when I get it to eventually unlock.
So far I've tried:
* Full restart of the phone
* Force reset by long press power button
* Boot into Safe Mode
* Factory reset
None of the above have fixed the issue. Its weird - for a few minutes after a fresh boot, the issue doesn't happen then slowly creeps in. Is it perhaps a memory issue?
Has anyone else seen this issue? If you have, what's the fix for it - or is it a faulty phone?
phantomlore said:
I've had my Pixel 3 XL for about 3 weeks now, not been dropped or damaged or anything like that, also not rooted. Its fully up to date, Android 9, security patch 5th Jan 2019.
Yesterday it stopped unlocking properly - the screen takes 20-30 seconds to respond after either pressing the lock button to wake it, touching the fingerprint sensor or double tapping the screen. I occasionally get "System UI has stopped responding" when I get it to eventually unlock.
So far I've tried:
* Full restart of the phone
* Force reset by long press power button
* Boot into Safe Mode
* Factory reset
None of the above have fixed the issue. Its weird - for a few minutes after a fresh boot, the issue doesn't happen then slowly creeps in. Is it perhaps a memory issue?
Has anyone else seen this issue? If you have, what's the fix for it - or is it a faulty phone?
Click to expand...
Click to collapse
You apparently tried everything that google would have you do. I see no reason to continue trying to fix it. RMA that puppy :good:
Not sure there would be much difference compared to a factory reset, but you could try sideloading the OTA again. The other option (assuming it is the Google variant and not Verizon) would be to unlock your bootloader and flash the factory image.
Badger50 said:
You apparently tried everything that google would have you do. I see no reason to continue trying to fix it. RMA that puppy :good:
Click to expand...
Click to collapse
Think I'll take it back tonight :/
So after this morning's post, I've found that keeping it face up on my desk seems to prevent the issue from occuring (i.e. so the always on display stays on)... Turn it over (Flip to Shh is disabled) or put it in my pocket and the issues start. Is it maybe a faulty proximity sensor? The glass protector I've got on the screen has a cutout around the notch so shouldn't be over the proximity sensor.
Edit: the above was done with it plugged into a charger. Unplug it, leave it face up and the issue returns? WTF?
So youve never tried to root or flash anything?
hilla_killa said:
So youve never tried to root or flash anything?
Click to expand...
Click to collapse
Nope.
phantomlore said:
I've had my Pixel 3 XL for about 3 weeks now, not been dropped or damaged or anything like that, also not rooted. Its fully up to date, Android 9, security patch 5th Jan 2019.
Yesterday it stopped unlocking properly - the screen takes 20-30 seconds to respond after either pressing the lock button to wake it, touching the fingerprint sensor or double tapping the screen. I occasionally get "System UI has stopped responding" when I get it to eventually unlock.
So far I've tried:
* Full restart of the phone
* Force reset by long press power button
* Boot into Safe Mode
* Factory reset
None of the above have fixed the issue. Its weird - for a few minutes after a fresh boot, the issue doesn't happen then slowly creeps in. Is it perhaps a memory issue?
Has anyone else seen this issue? If you have, what's the fix for it - or is it a faulty phone?
Click to expand...
Click to collapse
just sideload an ota and then factory reset.
Hi guys,
I am having a very strange issue with my Pixel 2XL, being that the phone will crash whenever I lock it and leave it for 3 seconds or more. Any less and I can unlock the phone again just fine. Also I tried playing some music through chrome and locking the phone, which carried on playing for 20 minutes and I could unlock the phone again with no issues. It gets stuck on the ambient display with the time when the phone crashes and I have to restart it (With power and volume + buttons).
I have tried to factory reset and even flash older factory images (I am by no means an expert and just gave it a try).
As of now I am out of ideas as to what it can be. I can only assume that a service or something is in standby and is causing an error when it goes to ambient/standby. I have also tried to change all settings in battery optimisation to not optimised, which did nothing.
Has anyone else had a similar issue and know how to fix it.
TIA!!
The same with me
Hi My Pixel 2 XL has exactly the same issue. Have you found any fixing method? Thank you:crying: