EMUI 9.0 Fingerprint lockscreen issue - Huawei P10 Plus Questions & Answers

Hello all. I have Huawei P10 Plus, EMUI 9.0 with root by Magisk Manager 7.3.4 and Magisk 19.3. And I've found one issue with lockscreen. It doesn't reproduse when there is no root on phone. So I think it related to root.
It reproduces only when I use fingerprint lockscreen.
What I mean:
Fo example I've registered only 1 finger. And I've set phone brightness to min level. When I use correct finger to unlock my phone all works fine. But when I use other finger or some part of my hand - backlight of screen turns on, lockscreen stucks and phone brightness has max level. It continues about 2-3 seconds and after that backlight of screen is turns off. After that if I use correct finger I will unlock my phone as well. But if I use other finger I will see the same bug. It looks like root broke the logic of fingerprint unlocking.
Does someone know how I can fix this issues ??

because you have Rooted always issues
i never root
only stock firmware final EMUI 9.1 not issues all

Related

Moto g5 plus Fingerprint problem.

I am having this slight delay in the fingerprint unlock when the device is off. There is a momentarily black screen. It is fine when I use the fingerprint to unlock the device when it is on. Please gimme some solution to this problem.
It makes sense to have a moment delay. I'd your phone is asleep, the device needs to recognize the touch, wake up the sensor, then wake up some of the CPU to compare the read vs. stored fingerprint, as well as get the stored from memory. There will be a short delay in there.

No custom roms for mate 9 pro ?

I have also searched through the mate 9 rom forum but never seen explicit mention of "LON-L29..." ROMs, so all seem to be mate 9 (MHA-L...).
Hopefully i am overlooking something ;-(
There are regularly updated KangVip roms for the Al00 variant (China Mainland dual sim) with the latest oreo builds, magisk root and xposed. But you have to register real name identification with a mainland huawei account to get them.
I linked one in the roms and android development part of the forum
https://forum.xda-developers.com/mate-9-pro/development/kangvip-rom-b354-mate-9-pro-links-t3790605
jalk44 said:
There are regularly updated KangVip roms for the Al00 variant (China Mainland dual sim) with the latest oreo builds, magisk root and xposed. But you have to register real name identification with a mainland huawei account to get them.
I linked one in the roms and android development part of the forum
https://forum.xda-developers.com/mate-9-pro/development/kangvip-rom-b354-mate-9-pro-links-t3790605
Click to expand...
Click to collapse
Hello,
I tried to flash the European version LON-L29 but no longer sees the sims. What do I do now?
Good news for the custom ROMS addicts (like me): OpenKirin Team
Kurinkita said:
Good news for the custom ROMS addicts (like me): OpenKirin Team
Click to expand...
Click to collapse
Has anyone dared to even go so far as to try installing one of the ROMs on the LON-L29? If so, I would love to return to resurrection remix ROM.
H10N3 said:
Has anyone dared to even go so far as to try installing one of the ROMs on the LON-L29? If so, I would love to return to resurrection remix ROM.
Click to expand...
Click to collapse
Yes, I have installed Resurrection Remix (LON-L29 owner also) . Works pretty well but there are some issues:
- The capacitive buttons don't light up (but work) and the fingerprint sensor does not act as the home button (I need to use a third party app to do that).
- When adaptive brightness is turned on, it stays mainly on the highest brightness setting.
- While having the Ambient display turned on and unlocking the phone via fingerprint, the screen does not turn on. You have to push the power button.
- Some lag with Myfitnesspal when adding items (irelevant for many, but can be annoying)
- Making a call via Google Assistant via voice, sometimes it takes even 30 seconds to initiate the call.
There may be more but these are the ones that I encountered.
Also tried a few hours the LineageOS ROM, but the camera (Huawei Camera app) kept crashing and restarting. The capacitive button lights worked well and the fingerprint sensor acted as the home button.
Kurinkita said:
Yes, I have installed Resurrection Remix (LON-L29 owner also) . Works pretty well but there are some issues:
- The capacitive buttons don't light up (but work) and the fingerprint sensor does not act as the home button (I need to use a third party app to do that).
- When adaptive brightness is turned on, it stays mainly on the highest brightness setting.
- While having the Ambient display turned on and unlocking the phone via fingerprint, the screen does not turn on. You have to push the power button.
- Some lag with Myfitnesspal when adding items (irelevant for many, but can be annoying)
- Making a call via Google Assistant via voice, sometimes it takes even 30 seconds to initiate the call.
There may be more but these are the ones that I encountered.
Also tried a few hours the LineageOS ROM, but the camera (Huawei Camera app) kept crashing and restarting. The capacitive button lights worked well and the fingerprint sensor acted as the home button.
Click to expand...
Click to collapse
You are a brave soul. I'm very averse to "beta status" of ROMs. Please keep us updated when you install new releases. Would love to switch when they iron out the bugs.
I'm an custom ROMs addict for more than 5 years now. I remember the days when a "fully" functional custom ROM was barely usable as a daily driver .
I'll keep updating, I hope a new update to the RR ROM comes soon for our devices,
Kurinkita said:
Yes, I have installed Resurrection Remix (LON-L29 owner also) . Works pretty well but there are some issues:
- The capacitive buttons don't light up (but work) and the fingerprint sensor does not act as the home button (I need to use a third party app to do that).
- When adaptive brightness is turned on, it stays mainly on the highest brightness setting.
- While having the Ambient display turned on and unlocking the phone via fingerprint, the screen does not turn on. You have to push the power button.
- Some lag with Myfitnesspal when adding items (irelevant for many, but can be annoying)
- Making a call via Google Assistant via voice, sometimes it takes even 30 seconds to initiate the call.
There may be more but these are the ones that I encountered.
Also tried a few hours the LineageOS ROM, but the camera (Huawei Camera app) kept crashing and restarting. The capacitive button lights worked well and the fingerprint sensor acted as the home button.
Click to expand...
Click to collapse
Any problems using Bluetooth? I'm experiencing some problems when listening to Spotify over Bluetooth, when connected to either of my cars or our Bluetooth speaker. Android Auto doesn't work, if connected to the car's head unit, are you able if Android Auto works on AOSP?
With Bluetooth I had no problems for what I use it for (BT headphones and A2DP connection to the car infotainment mostly).
Spotify works well, on both headset and car infotainment. About Android Auto, I don't use it so I have no idea.
I had issues with Waze on RR, as most of the time it couldn't connect to the GPS, but on Carbon ROM it worked flawlessly.

Fingerprint issue with Work Profile

I have been using fingerprint sensor on my Oneplus6T from the beginning. I have a work profile setup on my phone and I have added fingerprint to unlock work profile apps too.
I have always felt that the fingerprint sensor does not work well with work profile. It takes atleast 6-7 tries and sometimes does not work at all. I recently found out the reason.
The fingerprint icon for work profile does not show the animation!!! Since there is no animation, the area is not lit up and hence the fingerprint does not work. This is very strange.
I checked all the settings and could not find anything. As far as I know there is now way of turning on/off the animation as it is always required for fingerprint identification.
So I am wondering why the animation is missing when it comes to work profile unlock. Have any one else faced this issue?
Fingerprint animation works perfectly fine for phone lock, app lock etc. It only fails in case of work profile
PS: I am using Oxygen OS 9.0.14

Biometric sensors are sleeping?

Hello, I'm very disappointed with the fingerprint sensor and the face unlock:
when I try to unlock my device after some time, the fingerprint is very slow, also the camera is revealing after 1 or 2 secs after the swipe. But if I unlock - lock - unlock again both methods are fast like they should be.
I think there is something putting them in stand-by to prevend battery drain, but is very very very very annoying and frustrating.
Is there any way to fix this?
Thanks!

[SOLVED] H872 - Updated HavocOS & now proximity sensor broke

Solution in post #4.
I have a H872. I had been running Havoc OS v3.1 10/01/2020 without any issues. This past weekend I decided to update to Havoc OS v3.4 21/04/2020 (clean flash) and everything was great until I realized that the proximity sensor wasn’t working. When I received a call the screen stayed black. Swiping down from the notification bar let me answer the call but the proximity sensor didn't work - screen stayed black. I couldn't even hang up - had to wait for the other caller to hang up. Same issue when I initiated the call.
I then tried Havoc OS v3.4 18/04/2020 (clean flash again) and the same calling/proximity sensor issue remained PLUS I could not send/receive MMS even though APN was set up exactly the same as my original configuration (I had taken screenshots of my original setup). I attempted Havoc OS v3.4 21/04/2020 once again and MMS stopped working too! As well as the proximity sensor issue.
I then restored my original nandroid of Havoc OS v3.1 10/01/2020. While it restored successfully in TWRP, it never booted into the system. It just hung on the last frame of the boot animation. I am at a complete loss as to how to fix this phone now. I have just installed MSM Xtended and the proximity sensor is still non-functioning. I have since switched my sim to my Xiaomi backup but really want to get back to my G6.
It worked perfectly…I attempted a simple upgrade and all hell has broken loose! Any tips? Please.
Update:
I completely restored the phone to stock with H872 20g kdz/LGUP and was able to send MMS but the proximity sensor was still not functioning. Can the sensor just suddenly go bad like that? It was working perfectly until I updated Havoc.
Anyway, I have re-rooted and reinstalled the latest havoc. I am hopeful that I will get MMS to work, however, am not sure the proximity sensor will. I have found here that Android 10 allows for all sensors to be disabled with a Quick Settings Tile. This would work for when I initiate a call (can use the power button to turn the screen off/on). But would not be able to activate it once a call comes in. Is there a way to automate the sensor to turn on/off automatically when a call comes in? Or better yet, just disable the proximity sensor, and only the proximity sensor, completely? Been Googling all morning but haven't found much aside from this toggle, and an Xposed mod that may not even work with Riru Xposed...not to mention I want to avoid Xposed if I can.
Still looking for advice if you have any.
Thanks!
Update 2:
I am now running the latest Havoc with working MMS but still the proximity sensor issue persists. I am getting around it by using the Quick Settings Tile/toggle that is activated in Developer Options. This turns off the proximity sensor, as well as compass, accelerometer, & gyroscope. So I have to remember to disable it after a call.
I have searched to no end for a way to disable the proximity sensor permanently but there is very little on the subject. I've tried some apps that claim to turn it off, but they have not worked for me. It seems to me it should be an easy thing to do...but no!
My request:
Someone that can explain how to disable the proximity sensor on Havoc, or someone that could maybe recompile the dialer.apk to not utilize the proximity sensor.
Thanks again!
Final update: Solved!
I decided to install EdXposed and Sensor Disabler. After a lot of experimenting I found settings that work. In Sensor Disabler I selected:
LGE Virtual Proximity Sensor & selected "Remove Sensor" and Saved
Proximity (There are 2 listed - I set both the same) & selected Mock Sensor Values & set them to the highest setting possible and Saved.
Now I can make & receive calls and have access to the Accept/Reject/Message functions, as well as the keypad to input if needed and can end calls. The power button is easily accessible on the back and turns the screen off & on during a call, so I can keep it off the whole time I'm talking.
Not the most ideal situation but works for me considering the proximity sensor is completely useless now. Hope this helps anyone else in the same predicament.
EDIT - Sensor Disabler doesn't appear to be the most reliable. After a reboot it's hit or miss if it will work. It seems that after rebooting it takes a couple minutes for the app to "kick" in and function...but then it only seems to work more for incoming calls. Ultimately I am still using the Quick Settings tile to turn off all sensors during calls.

Categories

Resources