Hello there,
My Flo-Device keeps locking me out, resulting in a short black screen and throwing me back to the lockscreen. Based on the behaviour it seems that this is related to the sensor that is use for magnetic cases.
Unfortunately, I never used such a case, most threads I found are talking about cheap cases with a poor placing of the magnet itself - which does not help me out here.
Any hints on overriding that sensor by software or hardware? Any way of fixing the sensor or even a hint on the location on the Motherboard? I have read about an exposed module disabling it, but to configure the module it may be neccesary to be able to use the tablet in the first place. Currently it is still completely stock.
I appreciate your help or any reference to a solution that I may have overseen in my search. Thanks!
AeroplaneMode said:
Hello there,
My Flo-Device keeps locking me out, resulting in a short black screen and throwing me back to the lockscreen. Based on the behaviour it seems that this is related to the sensor that is use for magnetic cases.
Unfortunately, I never used such a case, most threads I found are talking about cheap cases with a poor placing of the magnet itself - which does not help me out here.
Any hints on overriding that sensor by software or hardware? Any way of fixing the sensor or even a hint on the location on the Motherboard? I have read about an exposed module disabling it, but to configure the module it may be neccesary to be able to use the tablet in the first place. Currently it is still completely stock.
I appreciate your help or any reference to a solution that I may have overseen in my search. Thanks!
Click to expand...
Click to collapse
Hall effect sensor's location is on the first attachment. I can assure you that there is no need to fix it directly because this and many other sensor problems are caused by the LCM connector. Disconnect the battery and just re-seat the LCM connector but be careful, watch this first https://www.youtube.com/watch?v=C9PwK9eGrCY
k23m said:
Disconnect the battery and just re-seat the LCM connector
Click to expand...
Click to collapse
Thanks for the fast reply and for pointing out the sensors' location on the PCB. Unfortunately, this did not solve the problem. Do you have any other ideas?
AeroplaneMode said:
Thanks for the fast reply and for pointing out the sensors' location on the PCB. Unfortunately, this did not solve the problem. Do you have any other ideas?
Click to expand...
Click to collapse
Please also re-seat the other end of LCM cable.
Check if a magnet placed over the sensor's position (top or bottom) has any impact.
Perhaps ROM builders know if something can be changed in /system/build.prop
Remove lock password - start ADB and do:
rm /data/system/locksettings.db
rm /data/system/*.key
Finally, we'll consider a hardware mod.
:good:
I already reseated both end of the ribbon cable to be sure - and again after the first unsuccessful test run. I never used a magnetic case on the device and there ar no other magnets near - my other Nexus 7 is fine though
What exactly does the locksettings.db do? I deleted It and rebooted, but no change in behaviour.
btw, as I am unable to properly use the touchscreen, I tried to enable usb debugging via an usb-otg cable and an attached mouse - which worked fine so far. It seems that there might be some interference or mechanical problem. Maybe the first thought with the hall sensor was wrong track I repaired a lot of devices over time, but (un)fortunately none of them showed that behaviour before, so I'm somewhat out of ideas in this case.
AeroplaneMode said:
What exactly does the locksettings.db do? I deleted It and rebooted, but no change in behaviour.
....
I repaired a lot of devices over time, but (un)fortunately none of them showed that behaviour before, so I'm somewhat out of ideas in this case.
Click to expand...
Click to collapse
It removes the lock password and makes it go into LOCKSCREEN-NONE mode, but you have to also remove all files with the ".key" extension from the folder.
Since you repair such devices, then measure voltage on the output pin of the sensor, and measure it again with a magnet over it.
Good idea. Without the magnet I get 2.98 V and with the magnet 0.001 V between GND and out. So I guess the sensor itself may not be the problem? As I recognized that it might be a mechanical problem, I got a friend to use the touchscreen and measured output at the sensor again, it seems to work as intended.
As the lockscreen does not have any further protection set up after a factory reset, I guess this could be the reason that I did not find any *.key files in that directory? So currently it is just 'swipe to unlock'.
Problem with the lockseetings file is: The device is all stock, locked and has no root - and to get a bit more weird, is not recognized when in recovery. My other Nexus 7 with twrp already on it is recognized instantly. I may have to fix that first, as in a weak moment I may have overseen the "access denied" while trying to delete that file and already typing the nex command. My bad - it was already late.
Honestly, I wonder what the problem really is and really appreaciate your help so far.
AeroplaneMode said:
Good idea. Without the magnet I get 2.98 V and with the magnet 0.001 V between GND and out.
.....
As the lockscreen does not have any further protection set up after a factory reset, I guess this could be the reason that I did not find any *.key files in that directory? So currently it is just 'swipe to unlock'.
.........
Problem with the lockseetings file is: The device is all stock, locked and has no root - and to get a bit more weird, is not recognized when in recovery.
Click to expand...
Click to collapse
The sensor is OK indeed.
As you did factory reset, there is no issue of user data loss anymore, so just unlock it and do factory flash https://developers.google.com/android/images
This should fix the recovery recognition problem too.
Yeah, so I unlocked it, reflashed it with the stock rom, installed twrp and su...and finally got to delete the mentioned files. But still - the issue continues to exist. Also, I see no difference after deleting the files. Does something else prevent that no locksreen-mode?
Do you have any more ideas? I could wildly start changing parts, but unfortunately the device isnt worth that much anymore :-/ As mentioned, using the device with the Mouse hooked up via otg, the screen behaves normal.
AeroplaneMode said:
the issue continues to exist. Also, I see no difference after deleting the files. Does something else prevent that no locksreen-mode?
....
Do you have any more ideas?
Click to expand...
Click to collapse
No worries, we'll fix it, but it seems that my opening statement "this and many other sensor problems are caused by the LCM connector" still holds true. On the schematic, R150 and R151 are presumably located next to the sensor on the daughterboard, so if LCM cable connection to main mobo is open, the CPU will constantly sense 0V level, right? And as you measured earlier, 0V means that magnetic flux is detected. Now, about the ribbon cable... you did re-seat it, but this thing is awful and tends to fail repeatedly because of contact oxidation and weak connector lock pressure. Two solutions:
spray with https://www.amazon.com/CRC-5103-Quick-Electronic-Cleaner/dp/B000BXOGNI/
apply a thick tape/spacer over the lock so N7's back cover will add extra pressure on it
Finally, here is a brute-force workaround fix, go: settings - system profiles - default - lock screen - disable :highfive:
I'll test the points you mentioned.
I have to get a can of cleaning spray in the workshop, as I only have other fluids here which leave a oily coating. Or Brake Cleaner Fluid Thanks so far, I'll keep you updated.
Disabling the Lockscreen still gives me blackouts but okay, i dont have to swipe anymore - that will do for the moment. I haven't had similar problems in a while, so I tend to forget some points as repairing phones from time to time is only some sort of occupational therapy for me besides my other work ^^
k23m said:
[*]spray with https://www.amazon.com/CRC-5103-Quick-Electronic-Cleaner/dp/B000BXOGNI/
[*]apply a thick tape/spacer over the lock so N7's back cover will add extra pressure on it
Click to expand...
Click to collapse
I was finally able to continue here. I cleaned the connection and applied some tape to thicken up the spacers. Still, I am not able to resolve the problem. I also tried to manually apple more pressure on the back, still not getting better unfortunately.
AeroplaneMode said:
I was finally able to continue here. I cleaned the connection and applied some tape to thicken up the spacers. Still, I am not able to resolve the problem. I also tried to manually apple more pressure on the back, still not getting better unfortunately.
Click to expand...
Click to collapse
I know you're not happy about it but this is the best N7 hardware issue to resolve we've had so far this year
I opened up my N7 to check the sensor's connection to main PCB - it goes to LCM pin #41 - note the attached pictures. Disconnect the battery and use an ohmmeter to measure the two points - I get around 8 oHm. If you measure open circuit, then look for broken or corroded track somewhere along the way. If you measure proper connection, then the problem is on the motherboard and there is nothing else we can do - case closed unfortunately.
/EDIT
Here is a software workaround:
install ElementalX kernel
during installation select the "Disable magnetic cover on/off" option
:victory:
k23m said:
I get around 8 oHm.
Click to expand...
Click to collapse
I get 3 Ohms, so I flashed the suggested Kernel. It seems to solve the problem, won't get any better I guess. Thanks for your support!
k23m said:
I know you're not happy about it but this is the best N7 hardware issue to resolve we've had so far this year
Click to expand...
Click to collapse
Now is that a good thing? :silly:
Related
New member here, first post.
I had my g4 several weeks ago (uk version). Great phone, however recently the screen seems far too sensitive. Sometimes apps or other features are activating on their own without me pressing on them.
I looked in the settings but havent found a way to resolve this. Can anyone offer any suggestions?
Just to clarify a bit more about my issue.
Its like the "floating touch" some phones have, where i can be an inch or two away from the screen but it still activates. More rarely, it seems as if it was activating by sensing light or movement. Strange. Is the g4 supposed to have this type of function?
pholmes38 said:
Just to clarify a bit more about my issue.
Its like the "floating touch" some phones have, where i can be an inch or two away from the screen but it still activates. More rarely, it seems as if it was activating by sensing light or movement. Strange. Is the g4 supposed to have this type of function?
Click to expand...
Click to collapse
That sounds like a problem. The G4 is actually known for lacking sensitivity and yours is doing the opposite. enable this settings to see if it is actually detecting ghost touches.
Settings, About Phone, Software Info and tap on 'Buidld number' 7 times. Then go back to settings and tap Developer options, enable 'Show Touches'
if the dots show without your intervention, then it's likely due to faulty touchscreen.
Anyways, do a factory reset and see if it helped.
GUGUITOMTG4 said:
That sounds like a problem. The G4 is actually known for lacking sensitivity and yours is doing the opposite. enable this settings to see if it is actually detecting ghost touches.
Settings, About Phone, Software Info and tap on 'Buidld number' 7 times. Then go back to settings and tap Developer options, enable 'Show Touches'
if the dots show without your intervention, then it's likely due to faulty touchscreen.
Anyways, do a factory reset and see if it helped.
Click to expand...
Click to collapse
Thank you. I will give that a try,
As it happens intermittently, i cant say how quick i will find out if that is the solution, but you have been helpful.
:good:
I remember seeing a sensitivity setting somewhere..
Outta said:
I remember seeing a sensitivity setting somewhere..
Click to expand...
Click to collapse
Its under Accessibility
pholmes38 said:
Thank you. I will give that a try,
As it happens intermittently, i cant say how quick i will find out if that is the solution, but you have been helpful.
:good:
Click to expand...
Click to collapse
Does reset solve the issue? , happening on mine right now. Appreciate your feedback. Thanks
Same here, on Imperium and Stock rom, I have the phone since 6 months and it is a really random issue... my bootloader is unlock so I don't know if I can send it to warranty.
For information I have enable the touch "tracing" in developper menu, and when the issue occurred it's getting me perfect vertical line from bottom to top screen, and open a lot of apps..
leclampin said:
Same here, on Imperium and Stock rom, I have the phone since 6 months and it is a really random issue... my bootloader is unlock so I don't know if I can send it to warranty.
For information I have enable the touch "tracing" in developper menu, and when the issue occurred it's getting me perfect vertical line from bottom to top screen, and open a lot of apps..
Click to expand...
Click to collapse
And from the sound of it... Yours pretty much ****ed, at least to my knowledge. Hardware screwed and no warranty. Just bought mine like 3 weeks ago, and hated it so much. So much hyped, but the experienced is so far ****ty at best.
I suspect mine hardware issue. This seems like it's gonna be the first, and the last LG for me. Even mine with warranty still intact. Blackberry used to give this feeling long ago with their ****ty storm. Now, LG and blackberry can share that same ****ed up grave.
As madgibbon indicates, I was on Accessibility / Motricity / Response time (my phone is in french so i'm not sure if it will be exactly like that on yours) and I have set to "Long".
Since that, the issue is no longer appear, I have also switch to rom V20F (Turkey) with still the same setting for accessibility, and I don't have the issue anymore.
I don't know if it is a hardware issue, my phone falls maybe 4 times but with a case and from a little height, no broken glass or something else.
This is all the things I tried before that ;
Using flipcover (QI charge and quick circle), I have tested the "normal" case but same issue
I had a glass protection, I have removed it and cleaned my screen, same issue
I have done lot of hard reset (i'm kind of full wipe addict), same issue
Only the solution of madgibbon works fortunately, thanks mate
I'm also a bit disappointed by this phone, it is great sure I mean fluid, great camera etc... but I have some little issue that ruin the experience unfortunately (this issue with touchscreen, i'm experiencing issue with my Chromecast too that i don't have with other phones, some heating, I don't find the battery usage so good since MM, can't relock bootloader since now). I don't blame LG because i'm using some of their products and I'm / was really satisfied with : Optimus 2x, Nexus 5, TV, Monitor, Sound Bar. Anyway, waiting for 2016's Nexus and I will see if I switch or not.
leclampin said:
As madgibbon indicates, I was on Accessibility / Motricity / Response time (my phone is in french so i'm not sure if it will be exactly like that on yours) and I have set to "Long".
Since that, the issue is no longer appear, I have also switch to rom V20F (Turkey) with still the same setting for accessibility, and I don't have the issue anymore.
I don't know if it is a hardware issue, my phone falls maybe 4 times but with a case and from a little height, no broken glass or something else.
This is all the things I tried before that ;
Using flipcover (QI charge and quick circle), I have tested the "normal" case but same issue
I had a glass protection, I have removed it and cleaned my screen, same issue
I have done lot of hard reset (i'm kind of full wipe addict), same issue
Only the solution of madgibbon works fortunately, thanks mate
I'm also a bit disappointed by this phone, it is great sure I mean fluid, great camera etc... but I have some little issue that ruin the experience unfortunately (this issue with touchscreen, i'm experiencing issue with my Chromecast too that i don't have with other phones, some heating, I don't find the battery usage so good since MM, can't relock bootloader since now). I don't blame LG because i'm using some of their products and I'm / was really satisfied with : Optimus 2x, Nexus 5, TV, Monitor, Sound Bar. Anyway, waiting for 2016's Nexus and I will see if I switch or not.
Click to expand...
Click to collapse
I will try what you suggested, will report back.
Thanks for the tip.
bloodsuckingcomputer said:
I will try what you suggested, will report back.
Thanks for the tip.
Click to expand...
Click to collapse
Nope, doesn't work, it is indeed, a hardware issue.
Thanks anyway. ?
bloodsuckingcomputer said:
Nope, doesn't work, it is indeed, a hardware issue.
Thanks anyway. ?
Click to expand...
Click to collapse
Screen problem after all, just picked my phone up from the place that I bought for under warranty fix, and they told me they did replace for a new screen, and all is looking fine and dandy for now. Hope it stay this way, finger crossed. 3 weeks purchased and already this problem. I doubt this thing will last.
Hey guys i have noticed since replaacing my screenmy gps wasnt working great and now not at all.....
I have tried faster fix
I have tried 2 different roms
I have opened the back up and checked the connecting pins
I have tested the 3 antennas on the top plate with my multi meter all have connectivity
Anyone any other ideas?.....
goofylad said:
Hey guys i have noticed since replaacing my screenmy gps wasnt working great and now not at all.....
I have tried faster fix
I have tried 2 different roms
I have opened the back up and checked the connecting pins
I have tested the 3 antennas on the top plate with my multi meter all have connectivity
Anyone any other ideas?.....
Click to expand...
Click to collapse
Anyone????
goofylad said:
Anyone????
Click to expand...
Click to collapse
You've done all of the diagnostic steps I would start with. In the GPS Status app, is your fix/sats ratio 0/0? Or does it at least show satellites like 0/22?
The symptoms you are describing point towards lack of pin contact. I know you checked them already, but it's extremely difficult to tell if the pins are actually making contact once you screw the back of the phone back on. I had this issue once, but found that simply tightening the screws as much as possible without stripping them did the trick. Others who had this issue resolved it by slightly bending the pins higher so they make contact easier.
If you are 100% certain they are making contact, I have no idea what would cause it, considering all of the diagnostic steps you have already taken. If GPS status shows satellites but 0 are fixed, I'm 99% certain it's the pins not making complete contact.
I hope that helps. Good luck, and let me know how it goes.
PS: Make sure the ROMs you are testing with are confirmed to be working with GPS. If you want to rule out custom ROMs as a cause, use a stock ROM.
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Well me getting same problem.. still not figured out issue.
Sent from my ONEPLUS A3003 using Tapatalk
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Hastaloego said:
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Click to expand...
Click to collapse
Hahaa ;p
well, smart lock is not active in my phone...
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
thebcooper said:
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
Click to expand...
Click to collapse
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
MagDag said:
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
Click to expand...
Click to collapse
Just be more wary of the screen being knocked/bumped!
Yeah that handles hardware as far as I know (might also be under other processes if they use it too though)
Alright, thanks for your quick feedback.
I guess i will reset my phone now...
I'm pretty sure it's the fingerprint sensor. Really sad to see that OP3 has this issue too, this started happening to me on OP2 too after the marshmallow update. They made the fingerprint scanner much more sensitive, greatly improving it's speed but this started happening. The workaround is to keep the phone in your pocket screen facing outwards...
I have the same problem. It should be fixable via system update to not activate the fingerprint sensor while the proximity sensor detects something.
Or am i missing something here?
Same issue here
Same issue. It's kind sad that OP can't handle this to prevent waking up using proximity sensor like it happens with duoble tap. I hope that they will release an update soon.
Is there anything in settings called "pocket mode"?? a friend has a THL phone that has pocket mode which stops the phone from doing anything when it detects its in a pocket
Nope, I've searched whole settings and there no option like 'pocket mode'.
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
I've created an e-mail to support with issue describe. Will update thread while getting reply.
Yes this is a bad bug which OP need to fix asap.
So what's the solution to the problem, finally?
MagDag said:
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
ArjunRanaOO7 said:
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
Click to expand...
Click to collapse
You would think that priority would be given to the proximity sensor. If triggered it would disable the finger print input.
So, I recently installed Lineage OS on my n7 and noticed auto rotate wasn't working. Then flashed it back to stock thinking the lineage rom was bugged, still no auto rotate, it used to work last time I used the tablet around 3-4 months ago, so im wondering did the gyroscope get fried or something?
Anyway which board contains the gyroscope, the motherboard or daughterboard, anyone know? Recently replaced the daughterboard so im thinking that may control the gyroscope? I want to replace whichever board contains the gyroscope as it doesn't even show it moving in check my android app, don't really want to waste money on the wrong board if possible, so if anyone knows for certain it'd be a huge help!
chrisg4493 said:
So, I recently installed Lineage OS on my n7 and noticed auto rotate wasn't working. Then flashed it back to stock thinking the lineage rom was bugged, still no auto rotate, it used to work last time I used the tablet around 3-4 months ago, so im wondering did the gyroscope get fried or something?
Anyway which board contains the gyroscope, the motherboard or daughterboard, anyone know? Recently replaced the daughterboard so im thinking that may control the gyroscope? I want to replace whichever board contains the gyroscope as it doesn't even show it moving in check my android app, don't really want to waste money on the wrong board if possible, so if anyone knows for certain it'd be a huge help!
Click to expand...
Click to collapse
The gyro is on the daughterboard but it never fails. Connection of the wide silver cable between the boards is the problem - see my earlier post https://forum.xda-developers.com/showpost.php?p=66952073&postcount=3
k23m said:
The gyro is on the daughterboard but it never fails. Connection of the wide silver cable between the boards is the problem - see my earlier post https://forum.xda-developers.com/showpost.php?p=66952073&postcount=3
Click to expand...
Click to collapse
But then wouldn't the gyroscope show as moving in apps that can test it? It shows up as stuck, and on the twitch app it acts as if i am shaking the tablet cause it just keeps going from dark mode to light mode because twitch app has a feature that allows you to shake to enable dark mode/light mode.
Anyway I have tried re-seating the ribbon cable about 20 times now and still nothing shows up on gyroscope, even tried 2 different cables
chrisg4493 said:
Anyway I have tried re-seating the ribbon cable about 20 times now and still nothing shows up on gyroscope, even tried 2 different cables
Click to expand...
Click to collapse
The gyro and compass sensors share the same I2C data line connecting the two N7 PCBs. Please check with a sensor test app if the compass works - if yes, then the gyro has failed indeed.
Some apps will show you the sensors names - N7 has:
gyro Invensense MPU-6500
compass AKM AK8963
:good:
k23m said:
The gyro and compass sensors share the same I2C data line connecting the two N7 PCBs. Please check with a sensor test app if the compass works - if yes, then the gyro has failed indeed.
Some apps will show you the sensors names - N7 has:
gyro Invensense MPU-6500
compass AKM AK8963
:good:
Click to expand...
Click to collapse
Hmm, the compass seems frozen as well I don't understand though the ribbon cable seems to be fine no matter how many times I disconnect / reconnect it nothing seems to change... Very odd
I have same issue, I use rotate app to manually rotate and also automatically rotate some apps. Eg auto rotate YouTube and media player to landscape.
https://play.google.com/store/apps/details?id=jp.snowlife01.android.rotationcontrolpro
With the silver ribbon cable connected at one end try and get it tightly moulded around the battery hold it there and connect the other end. I found this out recently after a battery swap it helps to push the connecters in a bit more those few microns matter. I was having screen rotation problems after a recent battery swap after doing this everything's perfect again.
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.