Related
Since yesterday evening I did encounter the following problem.
Plugging my earphones wouldn't send any audio to them, speakers always active.
Microphone nevers works, not in calls, not in apps, not while recording a video.
I did perform a factory reset and installed paranoid android, still the same problem. I am restoring OxygenOS last version right now...
It's been a very frequent problem since the beginning of october, did anyone encounter this issue recently?
This sounds like a hardware issue to me. Were there any potentially problematic events (drops, moisture ...) in past 2 months?
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
This sounds like a hardware issue to me. Were there any potentially problematic events (drops, moisture ...) in past 2 months?
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Not really, no, I did also notice that I can't save videos at all.
EDIT: after a HARDRESET (using MSM downloader) to Marshmallow, updating with OTA, everything works again... WTF?
EDIT2: I have been able to record a whatsapp audio, working fine. Did try to make a phone call, doesn't work anymore
this has been occurring to me also when using iphone earphones. but using other earphones works well. try using different brand
chanchan126 said:
this has been occurring to me also when using iphone earphones. but using other earphones works well. try using different brand
Click to expand...
Click to collapse
Not earphones issue... I had to simply clean the connector, the female jack on the phone, there was some cotton on the end!
Edit: the mic and the earphones works for few minutes, but after a while they completely stop, only a phone reboot solves the problem (just temporarily!)
I did install the Android Mic Fix Magisk module... My phone seems to be working correctly since few hours now.
Update: not even Android Mic Fix solves this... the only temporary solution I have is to Reboot the device
frankdd89, have you found the solution? RN i have the same problem, I have flashed my and everything was solved but, like 3 days after again just stooped working well. I have a doubt whether is a hardware issue due to the mic works well during several days, let me know what did you at the end..
I have the same problem! I'm going Mad!
any updates guys ? i've the same problem on my OP3
Mic issues with my oneplus 3
MustfaAiedAli said:
any updates guys ? i've the same problem on my OP3
Click to expand...
Click to collapse
ive been having the same issue with my oneplus 3 for last 8 months. I have tried resetting, restoring, turning off google voice and have replaced the mic/charge port twice but nothing seems to solve the problem. Would really like to find a solution to this problem as i tend to think it's software related because i started having the problem after an update. At first was sporadic but mic is completely out now.
Hi all, i have the same problem with microphoned earphone
I have tried many type of earphone but the problem is the same (at the first connection and use, the microphone doesn't work , at the second try (record voice or call) without disconnection of earphone the phone change the icon in the status bar, from the icon of earphone with microphone to the icon of earphone without microphone and start to use the integrated microphone in the phone) i attach image of the status bar icon
- I have tried the same earphone into another OnePlus 3 of my friend and he doesn't have the issue
- The internal microphone work good
- I'm using a CTIA earphone (in this case i use Samsung original earphone with microfone founded into an original Samsung device box)
- I have tried to factory reset the phone, clean from dust the earphone hole but nothing as changed
now i think to send phone in warranty assistance to OnePlus ...
seandfw said:
ive been having the same issue with my oneplus 3 for last 8 months. I have tried resetting, restoring, turning off google voice and have replaced the mic/charge port twice but nothing seems to solve the problem. Would really like to find a solution to this problem as i tend to think it's software related because i started having the problem after an update. At first was sporadic but mic is completely out now.
Click to expand...
Click to collapse
I have the same issue, i try everything. Factory reset, change to a custom rom, etc. etc.
But nothing help. It works after a reboot for some minutes but that´s it.
Have any one found a solution for this issue?
Similar problems
I have similar problems. It started six weeks ago with the headphones that could not be detected. Then calling stopped working. Back then I rooted my phone and all the problems where gone. Until last Sunday my phone app crashed. Now all the problems are back again. I tried wiping all my data (also internal storage) and installing a custom ROM. This did not help. Does anyone have any suggestions? I really like the phone and it is still in mint condition.
Thanks in advance
Hi,
My girlfriend's Nexus proximity senor seems to be broken and her screen is black all the time when she's calling someone.
Is there an easy way (root or not, I don't care) to easily disable the sensor all the time or in Caller app ?
She's on latest stock Oreo 8.1.
Thank you
Experiencing this as well. From what I have read, it is an issue with 8.1 specifically and the 5X.
Google haven't really acknowledged the problem yet, which sucks.
Related reddit thread
For calls, pressing the power button twice seems to bring the screen back for use again - doing this too quickly starts the camera, if you have that enabled.
This probably won't help for other use cases, like whatsapp.
I can understand that it's a bug for WhatsApp (she has that bug too), but for the dialer too ?
I don't experience such issues. My prox sensor is working like it should. Though I have a friend who has some minor problems with it, but he has a glass screen protector on top of it. Mine has a cutout for the sensors
Sebacestmoi said:
Hi,
My girlfriend's Nexus proximity senor seems to be broken and her screen is black all the time when she's calling someone.
Is there an easy way (root or not, I don't care) to easily disable the sensor all the time or in Caller app ?
She's on latest stock Oreo 8.1.
Thank you
Click to expand...
Click to collapse
My old original Nexus 5 had this problem and I got around it with an Xposed Module called Disable Proximity Sensor. That module has since evolved to something called Sensor Disabler (Link: https://forum.xda-developers.com/xposed/modules/mod-disable-proximity-t2798887). It doesn't say that it has been tested on the Nexus 5x, but it might still work. I am not sure how compatible it is with the new Oreo version of Xposed. Installing Xposed might be a bit overkill, but if it fixes the problem, it might be worth it.
I know how frustrating and annoying a busted proximity sensor can be, so I hope you can find a solution.
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. ? I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
quan2032 said:
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
Click to expand...
Click to collapse
Mine is I can't hear them but they can bear me. What the hell is going on. Hahaha! If all else fails I'm going to get a new top receiver speaker put in at a shop close by. It does appear that many Xiaomi devices have had sound issues and have had speakers replaced. If you search on YouTube Xiaomi no sound on call or speaker replacement you'll see MANY videos on "how to." Quite a few videos specifically for mi mix 2. They should let us upgrade at least to the mix 2s for free.
I'll try 3.0 havoc but I've flashed around on Android 10 and 9 and problem hasn't gone away. Still zero sound on my end on calls but all speakers work doing anything else. Appreciate the recommendation. Thanks for commenting. Later today's ill flash 3.0 and see what's up. Then I may pull a few kernels from other roms and switch em out with whatever I'm on and see if I can't get something going that way.
I will also post a log of me on the phone talking and maybe someone can see something that's wrong... Hope so anyway..
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Sinchanwa said:
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Click to expand...
Click to collapse
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
flash713 said:
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hey there just want to know is your problem solved?
Sinchanwa said:
Hey there just want to know is your problem solved?
Click to expand...
Click to collapse
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
flash713 said:
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Sinchanwa said:
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Click to expand...
Click to collapse
I never thought that my sound issue was related to havoc in any way I am almost positive its a broken speaker. Looks as though that type of thing happens often on this device and other xiaomi devices. Google search receiver speaker replacement really fast and watch how many things show up about it. Its all over. I'm going to get a replacement. Using my moto g7 power rn as my main phone so I can have conversations and hear on my end. I always clean flash everything I flash. I never fail to wipe data, system, cache, delik cache on any install.
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
r_nally said:
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
Click to expand...
Click to collapse
This is just too strange. So maybe my issue does have something to do with installing Havoc 3.1. That was the first rom I flashed after I unlocked my bootloader and speaker worked fine on latest MIUI Global rom before... I wonder if it's possible to break a speaker due to a rom installation? I've never heard of that before. I thought surely it was just the rom and was a bug or a firmware problem. I flashed all kinda firmwares afterwards in latest twrp and also sideloaded a few to see if maybe something wasn't right with recovery and like you say it did not change anything at all. I still get zero sound on my receiver speaker while on a call.
I'm going to try a few more things and see if it does anything. If I find a fix or something that allows me to hear anything at all out of my end on receiver speaker I'll most definitely add it here in a post and to the op. Seems like there would be more people than us if it had something to do with Havoc... Idk. Appreciate your information. I hope we can get this fixed soon. I never even hardly used my phone when the speaker worked. ? I bought it used off swappa and about two weeks later unlocked and flashed Havoc and no sound during calls on my end.
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
r_nally said:
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
Click to expand...
Click to collapse
I used an app off Google play store to test speakers and my receiver speaker works but refuses to work during a call on my end. It did have sound come through loud and clear when I ran the tests I did when it first happened. I've flashed using magisk stable, canary, formatted data, used different firmwares, everything know to mankind and searched around and tried several things online and nothing. I've been trying to boot the Android 10 GSIs to see if that makes any difference but have had no luck using the same vendor and boot everyone used on pie GSIs so I snatched some from different roms and still no luck on GSIs that are Android 10. Lemme find link to test all i used and I'll return and post a link. Brb
Sent from my OnePlus5 using XDA Labs
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
r_nally said:
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
Click to expand...
Click to collapse
I doubt it and I did make a post there a while back about it. There are many others there ok that thread who reported sound issues and I wanted to confirm what for sure caused it before I put the blame all on a rom... The speakers on this device have had issues MANY times based on all the reports i read all over the internet. But if I can confirm exactly what it is I'll dang sure be very open about it online and let the world know in hopes that if it was something I did maybe someone else won't and I can somehow prevent it. But I did make a post there when it occurred. Search my username on the thread and you'll see it.
When you set a ringtone does sound come from your top speaker? On my device it does. Just curious. See if you can hear any sound selecting different ringtones. ?
Sent from my Mi MIX 2 using XDA Labs
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
I'm going to clean flash now after I do a backup and I'll install havoc and NanoDroid which eliminates Googles hold on all our devices. Once I get all setup I'll run some tests and see if maybe this solves it.
NanoDroid: https://forum.xda-developers.com/showthread.php?t=3584928
[MODULE/SYSTEM] NanoDroid 22.5.1.20200102 (microG, pseudo-debloat, F-Droid + apps)
No difference
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
On my other device , Moto G7 Power see the 8th post here: https://forum.xda-developers.com/g7-power/development/rom-havoc-os-3-2-t4058987
This time I haven't had it occur on G7 Power but when I saw that guys post I had a flash back. :/
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread.
[edit 17Jul20]
OK, it happened again today. No sound from top speaker when making or receiving calls. Had to switch to speaker phone. Then I cleared the 'Contact and dialer' app cache memory. (And for good measure the other caller and dailer apps also. TOP SPEAKER CAME ALIVE AGAIN!! So I am pretty sure its a bug/memory issue.
What I did: Long press the dailer icon - tap on App info - press 'Clear data' icon and select to clear chache memory.
ToBadX2 said:
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread. - Christo
Click to expand...
Click to collapse
What's crazy is this happened on my device just after I wiped data, system cache and flashed HAVOC which was the first rom that I flashed when I got this device. And I flashed my firmware and it did nothing at all. I'm getting a another speaker from eBay this week. They're only like $3 US. Gonna replace it and see what happens. ?
I'm facing hardware problems in my Pixel XL.
From time to time (a few times everyday) my Microphone just doesn't work.
I can't call, send WhatsApp messages, record audio on videos, etc.
And when failing, even not using it forces me to reboot.
Any solution?
I've tried so far to do a factory reset, reinstall from ADB the latest official ROM and not installing any app or similar to see if that could be part of the problem. But everything fails.
One of the early pixels perhaps ? They are known for having a defect on the audio codec related to a cold solder.
daedric said:
One of the early pixels perhaps ? They are known for having a defect on the audio codec related to a cold solder.
Click to expand...
Click to collapse
Yes, early pixel.
Is there any solution for that?
desvariando said:
Yes, early pixel.
Is there any solution for that?
Click to expand...
Click to collapse
Opening the device and attempting to reflux the solders, not a easy task. I still have a Pixel in the same situation.
I have the same problems, mic doesn't work, need to reboot one, even twice to finally fix it temporally. I have a pixel XL from Verizon, i need to unlock the bootloader but i can't because verizon greyed out the OEM unlock, so i basically have a phone that can't call or send whatsapp voice notes.
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.