Related
So I got the Galaxy Nexus GSM today and it's one hell of a sexy device.
It obviously came with Ice Cream Sandwich out of the box. And errors out of the box. Right when I start the phone, Talk FCs. When I try to start the Camera, it FCs.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
I tried 3rd party apps (Zoom Camera, Paper Camera and a few others) and none of them work.
So it seems that everything that has something to do with the Camera doesn't work.
I tried everything that I could think of;
Reflashing
returning to stock
force stop Camera
Disable and enable all network related functions in G+ and Gallery
Clearing cache - both for individual apps and the option from the recovery
Trying 3rd party apps
Googling everything I could think of
Installing G+ (that made me able to open Gallery, but Gallery still force closes when I open Camera)
Changing battery
Of course I can't see it being anything but a hardware issue, but some people who have compiled CM10 by themselves have the same errors. I don't know if that helps me.
So before I return it some time this week, does any one have any suggestions to what I could try?
I'll give this thread two days before I return it.
Thanks in advance.
You rooted? If not and you know how to root, root it, replace the app (gallery, camera, whatever is not working) with stock JB version. Hopefully it's just corrupted apps... That's easy to fix
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
Click to expand...
Click to collapse
mrhaxx1 said:
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
Click to expand...
Click to collapse
Might be a long shot, but have you tried fixing permissions in recovery?
Sent from my Galaxy Nexus using xda premium
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
mrhaxx1 said:
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
Click to expand...
Click to collapse
Any solutions for this yet? having the same problem.
Nope, nothing yet.
And to make the bad things worse, I've lost the receipt. So I can't even return it.
Bumpity bump!
mrhaxx1 said:
Bumpity bump!
Click to expand...
Click to collapse
I just went ahead and called verizon.. and they're shipping me a new phone today. I see a lot of posts about this, with no solution. It'll be quicker to do it this way. Except you call whatever your carrier is. Or samsung, if nothing else.
Well, you see, I bought the phone refurbished. There was a guarantee on it, but I lost the receipt, so I can't return it or get a new phone.
I ordered a rear- and front-facing replacement camera. It should arrive in 7-15 days because I'm ordering from the USA.
I looked into it, and disassambling and assembling it should be fairly simple. Nearly the same process as the Nexus S, which I've disassembled before.
If it doesn't work, I've only lost $22 and it's not like I have a valid guarantee on it anyway.
Oh well, replacing the cameras didn't work.
And I even managed to break the volume buttons.
Even if I got hold of the receipt, there would be no way they would repair it now.
I can as well just go buy a new phone. Next month. Maybe. At least everything else still works.
When you flash ROM, do you ensure you completely wipe previous ROM and data? Also, if you use something like Titanium Backup to restore your apps after flashing a new ROM, make sure you don't restore system apps or data. That will definitely screw things up in every ROM as incompatible files are mixed.
Try doing a full wipe of your device it could help
Sent from my Galaxy Nexus using xda app-developers app
It was like that on the stock rom.
And yes, I always ensure to wipe everything. As said in the OP, I even tried returning back to stock.
I got the same problem, I GOT IT FIXED NO HARDWARE FAILLURE!!
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
I can second this fix!
IvanGrozni87 said:
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
Click to expand...
Click to collapse
So, I was having this exact same issue and was ready to call Verizon for a replacement, when I tried this as a last resort and VOILA!! IT WORKED! I am still unsure of how this all came about, but for the purpose of hopefully helping someone with the same issue, I will second this quick fix as IT DID WORK FOR ME.
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
navjas73 said:
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
Click to expand...
Click to collapse
Thanks for this information, I'll try to do it with mine too. Any results I will post here.
I've had my nexus 5x since it came out and fingerprint unlock has always works. That is, until a couple of days ago. Now the sensor doesn't work at all (doesn't even vibrate at all when touched). Also, I can't even find the fingerprint settings in the settings menu at all. It seems to have completely disappeared. Anyone else with similar experience or suggestions?
I have tried a reboot, but didn't do anything. Any further suggestions?
I'm running stock android, unrooted with all the latest updates.
Mithrandir1119 said:
I've had my nexus 5x since it came out and fingerprint unlock has always works. That is, until a couple of days ago. Now the sensor doesn't work at all (doesn't even vibrate at all when touched). Also, I can't even find the fingerprint settings in the settings menu at all. It seems to have completely disappeared. Anyone else with similar experience or suggestions?
I have tried a reboot, but didn't do anything. Any further suggestions?
I'm running stock android, unrooted with all the latest updates.
Click to expand...
Click to collapse
You don't see it under security?
Sent from my Nexus 5X using Tapatalk
I've had this same exact problem the past couple days as well. Fully stock, unrooted, latest updates. No mention of fingerprint scanner under Security. I've tried rebooting into Safe mode multiple times over the past couple days without success. Unrelated: each time I return to normal boot after safe mode, all my widgets disappear, and I have to re-select my default keyboard.
Go to recovery and clear cache. Reboot all better.
Sent from my Nexus 5X using XDA-Developers mobile app
bobby janow said:
Go to recovery and clear cache. Reboot all better.
Click to expand...
Click to collapse
Didn't work, nor did Factory Reset. Called Google and they're sending a warranty replacement.
This happened to my 5x just recently... Trying to find a fix, but I don't think there is one.. I think it's just a crappy design on the fingerprint scanner and Google knows it.
gr5 mini huawei fingerprint id solison
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??
Hi everyone,
So I just got my screen replaced by UBreakIFix, and now, the fingerprint sensor is getting the "Enrollment was not completed. Can't use fingerprint sensor" message. Since I remember reading about Google releasing a calibration tool, I just tried it. I tried in fastbootd (which gets stuck on downloading) and fastboot (gets stuck at installing). I was wondering if root might be an issue? Or if anyone knows any way to get it working?
Please note that I am trying to avoid factory resetting, but if it really seems like my final option, then I will try it out since I read that people still could not get the fingerprint sensor working after the factory reset.
I don't know if this still applies: Official Google Pixel Install fingerprint calibration software
I think I remember reading in this section about various users saying they couldn't get it to work on their P6P, either.
roirraW edor ehT said:
I don't know if this still applies: Official Google Pixel Install fingerprint calibration software
I think I remember reading in this section about various users saying they couldn't get it to work on their P6P, either.
Click to expand...
Click to collapse
It still does. I have been lurking around the Google Pixel community, and it seems the issue still persists, with no one able to figure out how to get the tool working. The article does say that it would require users to factory reset their phone after, but I have been reading that people still had the same issue after running the calibration tool and factory resetting. I am just questioning if it is only happening to users with root. I am even considering reflashing the official Feb OTA update and then try without root (pray that it is the issue), but if that does not work, I might have to factory reset and pray that it works.
This was happening to me recently but I got it to work on my third try. The only thing I did differently on my third try was press my finger on the sensor harder with each scan and then it worked without issue.
*Edit* - @NelsonTheMoron I couldn't tell if you were joking or not due to your username, haha (and I guess my username is pretty goofy as well lol). But I added a few words to my comment in case there was some confusion.
NippleSauce said:
This was happening to me recently but I got it to work on my third try. The only thing I did differently was press my finger on the sensor harder with each scan and then it worked without issue.
Click to expand...
Click to collapse
Did you just keep trying it until it worked on your third try? Or did you do something different?
I've been digging through my logcats late;y. I pushed the current build a bit too far and certain apps now refuse to accept the fingerprint as a authentication method. The ones that are throwing the errors always come with CA cert errors. The biometrics is tied into the security od the device. Being root is making that more janky one way or the other.
Redid my phone, stock (for me) with bare essentials as far as
I have just replaced my screen as my other developed a random crack in it... No I didn't drop it and it wasn't huge but I'm anal and ocd so I bought a replacement.
The replacement seemed to go well although I did get some of the factory glue on the sensor. I carefully cleaned it with microfiber and isopropyl alcohol. It looked good. Attached it to my new screen and connected the cable.
It seemed fine. Before glueing my new display down I tested it and the display worked but it didn't even see my fingerprint sensor. Reseated it multiple times and I've had no luck.
The fingerprint calibration won't work and it reports my version is too new. I'm tempted to factory reset but I don't know if it will work and I don't want to if I can help it. Any thoughts? It just doesn't see it at all.
awarman said:
I have just replaced my screen as my other developed a random crack in it... No I didn't drop it and it wasn't huge but I'm anal and ocd so I bought a replacement.
The replacement seemed to go well although I did get some of the factory glue on the sensor. I carefully cleaned it with microfiber and isopropyl alcohol. It looked good. Attached it to my new screen and connected the cable.
It seemed fine. Before glueing my new display down I tested it and the display worked but it didn't even see my fingerprint sensor. Reseated it multiple times and I've had no luck.
The fingerprint calibration won't work and it reports my version is too new. I'm tempted to factory reset but I don't know if it will work and I don't want to if I can help it. Any thoughts? It just doesn't see it at all.
Click to expand...
Click to collapse
Yes, this is a known issue. And it happened to me as well in February. My phone slipped off my desk and caused a big crack at the top corner, and me being anal like you, I took it to the local authorized screen repair. I didn't research beforehand, and learned that replacing the screen breaks the fingerprint sensor. The fingerprint calibration software doesn't seem to work for most people. What I learned is that it's a software issue and could be fixed with a software update. I haven't seen any update since then as there is still no fix.
I look forward to any others' feedback or knowledge because with no Face ID and no fingerprint unlock it gets annoying unlocking via PIN all the time.
darbylonia said:
Yes, this is a known issue. And it happened to me as well in February. My phone slipped off my desk and caused a big crack at the top corner, and me being anal like you, I took it to the local authorized screen repair. I didn't research beforehand, and learned that replacing the screen breaks the fingerprint sensor. The fingerprint calibration software doesn't seem to work for most people. What I learned is that it's a software issue and could be fixed with a software update. I haven't seen any update since then as there is still no fix.
I look forward to any others' feedback or knowledge because with no Face ID and no fingerprint unlock it gets annoying unlocking via PIN all the time.
Click to expand...
Click to collapse
I hoped for the best with it. I guess it's better than having a cracked screen but even this triggers me. Did you try a factory reset?
Have you tried installing a custom ROM? I'm currently using Spark OS and it has Face-ID enabled. I ran into the same problem but since I got face id I even forgot my phone had a fingerprint sensor haha
awarman said:
I have just replaced my screen as my other developed a random crack in it... No I didn't drop it and it wasn't huge but I'm anal and ocd so I bought a replacement.
The replacement seemed to go well although I did get some of the factory glue on the sensor. I carefully cleaned it with microfiber and isopropyl alcohol. It looked good. Attached it to my new screen and connected the cable.
It seemed fine. Before glueing my new display down I tested it and the display worked but it didn't even see my fingerprint sensor. Reseated it multiple times and I've had no luck.
The fingerprint calibration won't work and it reports my version is too new. I'm tempted to factory reset but I don't know if it will work and I don't want to if I can help it. Any thoughts? It just doesn't see it at all.
Click to expand...
Click to collapse
I know it's a little late but when something like this happens, its best to contact Google. There have been many reports of people getting replacements for small cracks or screens that won't turn on.
As for your issue - this is a known problem with the calibration tool. Some users have stated it takes 20 tries (on a windows system) in order to get it to work. A few also stated that they re-flashed Android with the web flash tool, and it worked after that.
Your last option would be to contact Google Support and see if they can provide any fix for the calibration tool.
There are a lot of users who are experiencing this issue on Google's Issue Tracker. Hopefully we'll see an update soon enough.
Alekos said:
I know it's a little late but when something like this happens, its best to contact Google. There have been many reports of people getting replacements for small cracks or screens that won't turn on.
As for your issue - this is a known problem with the calibration tool. Some users have stated it takes 20 tries (on a windows system) in order to get it to work. A few also stated that they re-flashed Android with the web flash tool, and it worked after that.
Your last option would be to contact Google Support and see if they can provide any fix for the calibration tool.
There are a lot of users who are experiencing this issue on Google's Issue Tracker. Hopefully we'll see an update soon enough.
Click to expand...
Click to collapse
There wasn't really any point for me to reach out to them because I don't have insurance and it's outside of the warranty period. They'd want me to send it in for repair which is not an option because I can't be without my phone due to work. It was a crack in the screen so there wasn't any way for them to fix remotely.
Perhaps I can try the android flash tool. Just didn't want to do a factory reset.
I might look into the custom rom. I heard about a rom having face ID, so I may head that direction
darbylonia said:
I might look into the custom rom. I heard about a rom having face ID, so I may head that direction
Click to expand...
Click to collapse
You can do it without a custom ROM. It's an Xposed module. I'm not running it and it's much better than fingerprint. I don't even care anymore about my fingerprint reader.
awarman said:
You can do it without a custom ROM. It's an Xposed module. I'm not running it and it's much better than fingerprint. I don't even care anymore about my fingerprint reader.
Click to expand...
Click to collapse
Can you link the module?
BlakeSm said:
Can you link the module?
Click to expand...
Click to collapse
Here it is. I'm using lsposed.
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com
awarman said:
You can do it without a custom ROM. It's an Xposed module. I'm not running it and it's much better than fingerprint. I don't even care anymore about my fingerprint reader.
Click to expand...
Click to collapse
I've been using it on my P6P and 3xl for a couple weeks now. It works awesomely
awarman said:
Here it is. I'm using lsposed.
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com
Click to expand...
Click to collapse
Wow this works flawlessly. This is a whole new phone now. Fingerprint reader can suck it
awarman said:
Here it is. I'm using lsposed.
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com
Click to expand...
Click to collapse
Awesome! I shall try this out! Thanks!
Hi all! I wanted to come back to this thread and report that I installed this module yesterday and it is fantastic! After installing the June build and I installed Lsposed then the Universal Face Unlock module and it's much better than a fast fingerprint unlock! Totally worth trying out!
Wanted to share in case this helps anyone with a replaced screen or anyone who wants to try another option to FP unlock
Something similar happened to me. The solution was to use the fingerprint calibration tool and instantly reboot the phone. Not sure if it will work, but worth a shot.
mkhcb said:
Something similar happened to me. The solution was to use the fingerprint calibration tool and instantly reboot the phone. Not sure if it will work, but worth a shot.
Click to expand...
Click to collapse
I tried that solution but it didn't work for me. It was reported to have minimal success rate. This face unlock module has been great so far for me!
awarman said:
I hoped for the best with it. I guess it's better than having a cracked screen but even this triggers me. Did you try a factory reset?
Click to expand...
Click to collapse
I did a factory reset which didn't resolve the fingerprint detection issue after my screen replacement last week. It did resolve the "newer version" message but resetting took me back to Android 12 as I was on 12 quarterly.
The calibration tool will not download and errors out. As @roirraW "edor" ehT mentioned, there is a defect opened in bug tracker since February but no status on ETA. A user reported success downloading the calibration tool when using a Chromebook. For me, download failed on both Mac and Windows.
johninsf said:
I did a factory reset which didn't resolve the fingerprint detection issue after my screen replacement last week. It did resolve the "newer version" message but resetting took me back to Android 12 as I was on 12 quarterly.
The calibration tool will not download and errors out. As @roirraW "edor" ehT mentioned, there is a defect opened in bug tracker since February but no status on ETA. A user reported success downloading the calibration tool when using a Chromebook. For me, download failed on both Mac and Windows.
Click to expand...
Click to collapse
Since my phone was still under warranty I went into a ubreakifix and after several trips, because my spectral sensor was bad too, I now have a fully repaired phone. Everything is working great on it now. Nice to have the fingerprint sensor back but I'm still using the face unlock mod except for with banking apps and gpay.
Ubreakifix let me know that you can't successfully move your old fingerprint to a new display as it won't pair. They had to replace using a kit with the display and a new fingerprint sensor included.
Thank you!
Interesting that ubreakifix said that you can't "move" a fingerprint to a new screen. Maybe that is what they did for you since you didn't factor reset? Honestly, I don't understand much of this but I performed a full factory reset so, for me, this isn't about moving a fingerprint. What do I know though!
The screen installed on my phone has a fingerprint reader and came from the screen supplier. I have read that others successfully installed and calibrated their screens if they got the calibration tool to download. I am hoping I can do the same once Google fixes the issue with the calibration tool download. I will also borrow a Chromebook from work and give it a try on there in the interim.
Thanks again for the insight! I appreciate your response.
I think that the calibration tool only work if the fingerprint setting still available and when the enrollment fail.
If the fingerprint setting is gone seems like the sensor is damaged or not connected correctly.
I have same problem after replacing my screen,the fingerprint print setting has gone.