Related
Hi,
Every few hours my Compass and Inclinometer completely stops working. It only comes back after a reboot. Not a major issue but I was wondering if anyone else saw this.
Thanks!
Define completely stop working. Are the directions wrong? Are there no indication of direction whatsoever? Or are there any error messages?
If the directions are wrong, do a figure of eight.
mix1987 said:
Define completely stop working. Are the directions wrong? Are there no indication of direction whatsoever? Or are there any error messages?
If the directions are wrong, do a figure of eight.
Click to expand...
Click to collapse
As in the Compass and Inclinometer stopped noticing that the orientation of the phone changed in any way. With a bubble level app, the bubble never changed with orientation and with the compass app (or Google Maps) the arrow disappeared completely. Power cycle resolved but this is a bit annoying.
Go to phone and type *#0*#. Test out the sensor when your compass and inclinometer fails. If the test shows that the sensor is faulty, it means it's a hardware issue and get it changed.
If it's still working alright in the test, do a factory reset.
mix1987 said:
Go to phone and type *#0*#. Test out the sensor when your compass and inclinometer fails. If the test shows that the sensor is faulty, it means it's a hardware issue and get it changed.
If it's still working alright in the test, do a factory reset.
Click to expand...
Click to collapse
Sadly, it's Verizon and that code does not work. I did Factory reset and it still happens.
Now, to add to my joy, the Iris sensor is acting up too (See Google Photo Link)Iris not working
Going to be a fun call to VZ...
Get a one for one exchange.
mix1987 said:
Get a one for one exchange.
Click to expand...
Click to collapse
Yep, got off the phone with them and got the exchange sorted out.
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Lord_Maumad said:
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Click to expand...
Click to collapse
Hey, you can use the APP that comes with your phone to check if the proximity sensor fails.
How to open it: HiCare-Service-Smart diagnosis-Auto
Good luck
Thanks, But everything's fine with the sensor as Hicare. I don't believe it's a hardware problem, but I don't know what I can do about the system.
Lord_Maumad said:
Thanks, But everything's fine with the sensor as Hicare. I don't believe it's a hardware problem, but I don't know what I can do about the system.
Click to expand...
Click to collapse
Do you have a black screen when you are talking?
When the sensor is locked, no. Sometimes the screen turns black immediately when I get the phone call. That is, the sensor is locked. Passing the finger over the sensor a few times, it unlocks and goes back to work.
Having the same issue. I thought it was because of Drupe (am using it instead of default dialer). Weirdly, proximity sensor activates even before attending the call sometimes and am not able to do anything. Just let the call ring it out and then have to call back as even locking/unlocking doesnt work.
have upgraded to version 184 and the problem continues. I don't know what to do. Disappointment with Huawei
cashif said:
Having the same issue. I thought it was because of Drupe (am using it instead of default dialer). Weirdly, proximity sensor activates even before attending the call sometimes and am not able to do anything. Just let the call ring it out and then have to call back as even locking/unlocking doesnt work.
Click to expand...
Click to collapse
Hi, did you solve the problem? I downgraded and it worked again, so I decided to upgrade and it stopped again
Lord_Maumad said:
Hi, did you solve the problem? I downgraded and it worked again, so I decided to upgrade and it stopped again
Click to expand...
Click to collapse
Problem stopped after updating to latest firmware 184 version
Lord_Maumad said:
After the update I'm having trouble with the proximity sensor. It stops suddenly. Usually when I put the smartphone in the pocket. It was perfect before 172 firmware. Anybody notice anything? Any tips? I have the EVRL29. I also made a factory reset.
Click to expand...
Click to collapse
Are you using full cover tempered glass screen protector?
Unfortunately I'm not ?
I don't know if it is updated firmware bug or hardware failure. My friend's phone has this problem too, and even worse when dialing or listening to voice SMS in FB messenger, the screen was off until the voice finished. I thought it was full cover screen protector; however, it was not after I suggested him to take off the screen protector, and the problem still persisted. Anyway he told me there was not any problem before updating.
Lord_Maumad said:
Unfortunately I'm not
Click to expand...
Click to collapse
Are you using full cover tempered glass screen protector?In addition, can you check whether the position of your sensor is clean.
I'm not, and it's clean. It works until I put it in my pocket, then it gets stuck.
Today I realized one thing, if I touch the screen where the sensor is for more than 2 seconds, it hangs. If I stay near, it works ?
Lord_Maumad said:
Today I realized one thing, if I touch the screen where the sensor is for more than 2 seconds, it hangs. If I stay near, it works ?
Click to expand...
Click to collapse
My friend just sold his mate 20x with proximity sensor error and bought a new one with the same firmware version 9.0.0.184. The new one worked functionally with its proximity sensor. I think that his previous mate 20x had proximity sensor hardware's problem, not dead but not functional.
Ich have the same issue with a P30 Pro New Edition. I hope it's a hardware issue and the replacement unit will be fine.
Hello. I have this phone Mi 11 Lite 4g version. After i did software update to MIUI 13.0.7 Global Stable, fingerprint option gone in settings, and sometimes i have to click power button twice to turn off the screen. Any here have similar issues?
I have the same problem. After a while it showed up randomly in settings. So it rarely works. I hope it will be fixed with the next update. MIUI 13.0.7
This is a hardware problem. You should repair it in a workshop.
I had the same exact problem, turns out to be a hardware problem. As it was under warranty, I send it back and it was repaired. Good luck!
Same problem with me too, fingerprint sensor replaced by Xiaomi.
This is weird. I once woke up on a non-working fingerprint sensor. Although the option was still available in phone settings (I had 2 registered fingerprints), I couldn't register any new fingerprint.
That was like a nightmare to me, later on, I discovered it was caused by the missing property line:
Code:
ro.vendor.extension_library=libqti-perfd-client.so
Adding that line and rebooting fixed my situation.
Mohamedkam000 said:
This is weird. I once woke up on a non-working fingerprint sensor. Although the option was still available in phone settings (I had 2 registered fingerprints), I couldn't register any new fingerprint.
That was like a nightmare to me, later on, I discovered it was caused by the missing property line:
Code:
ro.vendor.extension_library=libqti-perfd-client.so
Adding that line and rebooting fixed my situation.
Click to expand...
Click to collapse
Not, is it working fine?
Thanks for sharing
Mohamedkam000 said:
This is weird. I once woke up on a non-working fingerprint sensor. Although the option was still available in phone settings (I had 2 registered fingerprints), I couldn't register any new fingerprint.
That was like a nightmare to me, later on, I discovered it was caused by the missing property line:
Code:
ro.vendor.extension_library=libqti-perfd-client.so
Adding that line and rebooting fixed my situation
Click to expand...
Click to collapse
Where should this line be added?
p1lo said:
Not, is it working fine?
Thanks for sharing
Click to expand...
Click to collapse
Ever since, it is working just fine.
Hadi7546 said:
Where should this line be added?
Click to expand...
Click to collapse
/vendor/build.prop is where I found it. I am on A12.1 GSI, 12.1 DotOS vendor, latest Vantom Kernel.
Mohamedkam000 said:
Ever since, it is working just fine.
/vendor/build.prop is where I found it. I am on A12.1 GSI, 12.1 DotOS vendor, latest Vantom Kernel.
Click to expand...
Click to collapse
root access needed?
Hadi7546 said:
root access needed?
Click to expand...
Click to collapse
Yes. You probably need to go to a service center.
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.
S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.