Following these steps to resolve fingerprint unlock issue after Android 10 update:
1. Delete all existing fingerprints.
2. Turn off 'Always On' from Display Settings
2. Set Screen Lock(Security Settings) to 'None'
3. Set Battery Optimisation to 'Don't optimise' for 'In-Display Fingerprint' app.
4. Force stop 'In-Display Fingerprint' app, and remove cache and data for this app.
5. Restart your phone.
6. Select Fingerprint option from Security menu and add your fingerprint, make sure raise to wake up toggle is set to ON in fingerprint menu.
That's it.
If fingerprint icon does not appear on raising the phone, tap the screen twice for it appear.
P.S. : You will have to follow these steps again if you restart the phone after all the steps.
After all this Fingerprint still breaks after,
1. Clicking Notification from lock screen
2. Picking up call from lock screen
Maybe step 3 and 4 are not necessary, But still added it to be safe.
paragkharche said:
Following these steps to resolve fingerprint unlock issue after Android 10 update:
1. Delete all existing fingerprints.
2. Turn off 'Always On' from Display Settings
2. Set Screen Lock(Security Settings) to 'None'
3. Set Battery Optimisation to 'Don't optimise' for 'In-Display Fingerprint' app.
4. Force stop 'In-Display Fingerprint' app, and remove cache and data for this app.
5. Restart your phone.
6. Select Fingerprint option from Security menu and add your fingerprint, make sure raise to wake up toggle is set to ON in fingerprint menu.
That's it.
If fingerprint icon does not appear on raising the phone, tap the screen twice for it appear.
P.S. : You will have to follow these steps again if you restart the phone after all the steps.
Click to expand...
Click to collapse
Thanks bro.. seems this is fixed the issue, my finger scanner is still active after 1 hour.. this is the longest time after 10 update. Will update if it stops working
---------- Post added at 05:39 PM ---------- Previous post was at 05:25 PM ----------
paragkharche said:
Maybe step 3 and 4 are not necessary, But still added it to be safe.
Click to expand...
Click to collapse
I think they are needed.. i did the remaining ateps multiple times but fingerprint stopped after 30 mins.. now it is working
Never mind,
It stopped working again..
Worked for a few minutes and stopped...
Like all the other solutions that were posted.i think we just have to wait for xiomi to kindly release an update to fix it,in addition to the rest issues.
i received only the february update without android 10 and i have same problem so its not from android 10
sathish43210 said:
Thanks bro.. seems this is fixed the issue, my finger scanner is still active after 1 hour.. this is the longest time after 10 update. Will update if it stops working
---------- Post added at 05:39 PM ---------- Previous post was at 05:25 PM ----------
I think they are needed.. i did the remaining ateps multiple times but fingerprint stopped after 30 mins.. now it is working
Never mind,
It stopped working again..
Click to expand...
Click to collapse
Teddybeat said:
Worked for a few minutes and stopped...
Like all the other solutions that were posted.i think we just have to wait for xiomi to kindly release an update to fix it,in addition to the rest issues.
Click to expand...
Click to collapse
Clicking on notifications from lock screen also breaks it like it does after a restart.
I am turning off notifications on lock screen until next update is available.
paragkharche said:
Following these steps to resolve fingerprint unlock issue after Android 10 update:
1. Delete all existing fingerprints.
2. Turn off 'Always On' from Display Settings
2. Set Screen Lock(Security Settings) to 'None'
3. Set Battery Optimisation to 'Don't optimise' for 'In-Display Fingerprint' app.
4. Force stop 'In-Display Fingerprint' app, and remove cache and data for this app.
5. Restart your phone.
6. Select Fingerprint option from Security menu and add your fingerprint, make sure raise to wake up toggle is set to ON in fingerprint menu.
That's it.
If fingerprint icon does not appear on raising the phone, tap the screen twice for it appear.
P.S. : You will have to follow these steps again if you restart the phone after all the steps.
Click to expand...
Click to collapse
paragkharche said:
Clicking on notifications from lock screen also breaks it like it does after a restart.
I am turning off notifications on lock screen until next update is available.
Click to expand...
Click to collapse
I don't use notifications on locked screen and it's working kind of flawless.... On Android 10 you still need to double tap to wake right
Sent from my Mi A3 using Tapatalk
fburgos said:
I don't use notifications on locked screen and it's working kind of flawless.... On Android 10 you still need to double tap to wake right
Sent from my Mi A3 using Tapatalk
Click to expand...
Click to collapse
Nope. T2W is not a feature.
---------- Post added at 06:22 PM ---------- Previous post was at 06:21 PM ----------
paragkharche said:
Clicking on notifications from lock screen also breaks it like it does after a restart.
I am turning off notifications on lock screen until next update is available.
Click to expand...
Click to collapse
I am guessing you are the same dude who posted this exact same thing in Reddit?
tereyaglidoner said:
Nope. T2W is not a feature.
---------- Post added at 06:22 PM ---------- Previous post was at 06:21 PM ----------
I am guessing you are the same dude who posted this exact same thing in Reddit?
Click to expand...
Click to collapse
Yeah bro
Anyone identified root cause of for fod disappearing in lock screen?
I identified few scenarios which are breaking fingerprint scanner on lock screen.
1.double press power button, while jump to camera is enabled on double press power button
2. Unlocking phone with any other unlocking methods like face recognition and pattern.
Please share your experience
Having absolutely zero issues here all works as normal and always has since the update.
What I did to get android 10 was completely flash the last stock android 9 using miflash.
Setup as normal and signed into all my accounts. Setup fingerprint and lock screen pattern.
Updated to android 10 through prompt.
Booted to a fully working os and then proceeded to unlock the bootloader and flash magisk patched boot.img through fastboot.
Been working perfectly ever since. No issues with fingerprint icon not being displayed or fod not working or any issues as a matter of fact.
Noticed a slight increase in battery for the first couple of days but that soon turned into a 10 hour average sot since so no issues there either.
I would urge anyone who has issues to take logs of every bug you find and send it to the xiaomi Dev team through the 'feedback app'.
I think they have most bugs sorted now but no harm in sending they might find other issues
I couldn't post it that's why posting it here.
Whenever I connect headphones to mobile and call anybody, it works fine. But if call and then connect the headphones, other person can't hear me at all. This has started after I updated to android 10. Anybody has same issues?
Thats wired headphones
sathish43210 said:
Anyone identified root cause of for fod disappearing in lock screen?
Click to expand...
Click to collapse
Its also when someone calls and the screen is locked, that brakes it for me
The fix is working.......?
I turned of the lock screen notifications .......?for now
Hope xiaomi will fix this soon.....
Related
I set two time profiles to control dnd setting automatically for the night.
First I set it to priority. Second profile then resets it to none as that removes the priority icon from toolbar. I realised that all sounds are gone after that.
If I set it to all, priority icon stays in status bar.
I tried also to do just a single profile with ending time, but that also left priority icon to the bar.
Is there a way to get priority mode to work with tasker?
What are you trying to achieve? If it's setting DnD for the night automatically, you don't need tasker for it. Have you tried using automatic rules in DnD settings?
See http://www.howtogeek.com/260506/how-to-set-automatic-quiet-times-in-android-with-do-no-disturb/
tropicanapure said:
What are you trying to achieve? If it's setting DnD for the night automatically, you don't need tasker for it. Have you tried using automatic rules in DnD settings?
See http://www.howtogeek.com/260506/how-to-set-automatic-quiet-times-in-android-with-do-no-disturb/
Click to expand...
Click to collapse
Very funny.. We have alert slider, so automatic rules gone. Back on trees.
---------- Post added at 05:21 PM ---------- Previous post was at 05:17 PM ----------
veepee78 said:
I set two time profiles to control dnd setting automatically for the night.
First I set it to priority. Second profile then resets it to none as that removes the priority icon from toolbar. I realised that all sounds are gone after that.
If I set it to all, priority icon stays in status bar.
I tried also to do just a single profile with ending time, but that also left priority icon to the bar.
Is there a way to get priority mode to work with tasker?
Click to expand...
Click to collapse
I have same issue and I can't find solution yet. I use set volume as workaround.
Oneplus seriously damaged DnD. Shame.
OUTbrain said:
Very funny.. We have alert slider, so automatic rules gone. Back on trees.
---------- Post added at 05:21 PM ---------- Previous post was at 05:17 PM ----------
I have same issue and I can't find solution yet. I use set volume as workaround.
Oneplus seriously damaged DnD. Shame.
Click to expand...
Click to collapse
Adjusting volume is not that good.. Nothing comes through with that. I'd like to be reachable by phone for known callers. I quess we have to wait cyanogen to fix the rom
I've had the same issue. Tasker will remove the 'priority' status but screws up the volumes. The only way round it at the moment is to leave slider in normal, use tasker to set priority when needed, then on return to 'normal' from tasker move slider to mid position then back to normal. This seems to reset volumes back to normal. Hopefully oneplus can sort out this DND issue and allow software to override the slider.
Sent from my ONEPLUS A3003 using Tapatalk
I've found a way. Leave slider in mid position (priority) and use the inbuilt priority settings to allow normal audio to be heard. I've got tasker to set DND to priority and volume to 3. When full DND is needed, set tasker DND to 'alarms'. This kills all audio except alarms. Use tasker to go back to DND 'priority' for normal use. This does leave a constant priority notification at the top but audio seems to work. By using tasker/audio/silent mode, you can create a vibrate only mode that stops audio but keeps vibrate notifications with respect to the priority mode settings at a system level.
Sent from my ONEPLUS A3003 using Tapatalk
Good catch! You can delete the constant priority notification through Customisation/ Status bar
Sent from my OnePlus 3
geovass said:
Good catch! You can delete the constant priority notification through Customisation/ Status bar
Sent from my OnePlus 3
Click to expand...
Click to collapse
Nice one! You can then add custom tasker notify icons to display silent or vibrate modes.
Sent from my OnePlus 3.
One thing I realised is that having the slider in the mid position i don't get any notifications (without activating DnD).
Any thoughts?
Sent from my OnePlus 3
geovass said:
One thing I realised is that having the slider in the mid position i don't get any notifications (without activating DnD).
Any thoughts?
Sent from my OnePlus 3
Click to expand...
Click to collapse
Mine seems to work. On the alert slider settings make sure you have calls and messages set to 'everyone' under the priority settings. For other apps like Gmail or WhatsApp, go to 'app notifications' under sound and notifications and set them to notify when in priority mode. This is a bit of a pain but gets over the software controlled notifications issue until oneplus can sort something out.
Sent from my OnePlus 3.
Aha! Key was to set all apps under "app notifications" to notify when in priority! Now i think its working!
Many thanks!
I know it's a kind of trolling but somebody may not realise this - by using CM13 you have the best of both worlds built in.
You have stock android DND (automatic) and you can also customise what the button does. [I don't use neither of these features but noticed them in CM settings panel while setting up my device]
Hey @yourmate
Anything else missing/not working properly beside Dash Charge on CM? I am waiting to make sure it is stable (one thing I cannot afford are random reboots). For example, I am not using them, but curious, are the Op3 gestures available or gone? (V and O to enable flashlight/Camera - CM's anywhere gesture was not great I thought)
Automated DnD is for me the main issue on Op3, and I also liked CM's auto-brightness/Night mode. Kind of feel going back several years haha
didyeah said:
Hey man,
Anything else missing/not working properly beside Dash Charge on CM? I am waiting to make sure it is stable (one thing I cannot afford are random reboots). For example, I am not using them, but curious, are the Op3 gestures available or gone? (V and O to enable flashlight/Camera - CM's anywhere gesture was not great I thought)
Automated DnD is for me the main issue on Op3, and I also liked CM's auto-brightness/Night mode. Kind of feel going back several years haha
Click to expand...
Click to collapse
Everything fine. Gestures works. No reboots so far. Instead dash charge and camera much better then oos. And camera will be ported very soon I think.
didyeah said:
Anything else missing/not working properly beside Dash Charge on CM?
Click to expand...
Click to collapse
None I came across.
didyeah said:
I am waiting to make sure it is stable (one thing I cannot afford are random reboots).
Click to expand...
Click to collapse
Rock solid I have NOT had any reboots or even a freeze
didyeah said:
are the Op3 gestures available or gone? (V and O to enable flashlight/Camera - CM's anywhere gesture was not great I thought)
Click to expand...
Click to collapse
They're available in a dedicated menu
TBH I haven't used OOS for a second so I cannot really compare the two but I've bought this phone only for two reasons anyway:
- dual SIM
- official CM support
Sorry for being a bit OT
Sounds great guys. I guess I'll just ditch OOS for CM this week end then and forget all that DnD shenanigans once and for all
didyeah said:
Sounds great guys. I guess I'll just ditch OOS for CM this week end then and forget all that DnD shenanigans once and for all
Click to expand...
Click to collapse
This guy does daily nightlies until official appears
With OOS 3.2.2 DND works correctly with tasker!
Sent from my ONEPLUS A3003 using Tapatalk
I can also confirm everything seems fixed in OOS 3.2.2. I can set the alert slider to any position and then run a tasker task to set vibrate only, all audio or silent mode. The slider can be used to override the tasker setting but tasker can be run again to re establish the desired sound profile.
Sent from my OnePlus 3.
I can confirm that this is resolved with OOS 3.2.2
Strange that my device couldn't find the 3.2.2 update. Installed it manually via TWRP without problem though.
I saw a lot of threads about the knockOn options and it turned on in my device.
The problem is after I lock the device with the button or double tap I can't unlock it using double tap also I can't open the clock with swipe down, I can unlock it using the button.
Dose anyone knows whats the problem?
Update:
1) The problem also exists in Safe Mode.
2) After I installed KnockOn - Tap to wake or lock App from Google Play, Double Tap to wake up works better still some delays probably because of the original knock on but still its some kind of workaround.
In my opinion its strange, its not working in safe mode so its suppose to be a hardware problem but on the other hand it works with a software. How can it be? Is it a software problem or hardware problem?
I also have the same problem the double touch does not wake the cell phone
@11alex11 @kamelot24
Swipe down and double tap do not work when the proximity sensor detects something close up such as when the phone is in your pocket.
Verify your proximity sensors are working properly using this app: https://play.google.com/store/apps/details?id=com.tigermonster.proxfinder
It should not say 0cm with nothing near the phone.
As I said in the first post, the double tap work to lock the device but it doesn't work to unlock it (sometimes it does). The proximity sensor works fine.
New progression with the problem solution, check out the main post.
htr5 said:
@11alex11 @kamelot24
Swipe down and double tap do not work when the proximity sensor detects something close up such as when the phone is in your pocket.
Verify your proximity sensors are working properly using this app: https://play.google.com/store/apps/details?id=com.tigermonster.proxfinder
It should not say 0cm with nothing near the phone.
Click to expand...
Click to collapse
not ,
It does not fix it at all. still the same
---------- Post added at 02:38 PM ---------- Previous post was at 02:34 PM ----------
The sensor is fine. The problem is just the double tap :llorando:
Anybody else having issues with the pixel screen not turning on? I get haptic feedback when I touch the screen but the screen doesn't come on. I have to hold down the power button to reboot. It only does it every now and then, I think it's the immersive mode that's causing it.
I am using double tap to lock (Nova Prime) and double tap to wake (settings > system > languages, inputs and gestures),
and once in a while, my double tap to wake (I presume during deep sleep) takes several taps to register.
I'm having the same issue too. Haven't found a solution yet.
Sent from my Pixel 2 XL using Tapatalk
Az Biker said:
I am using double tap to lock (Nova Prime) and double tap to wake (settings > system > languages, inputs and gestures), and once in a while, my double tap to wake (I presume during deep sleep) takes several taps to register.
Click to expand...
Click to collapse
mirwolf said:
I'm having the same issue too. Haven't found a solution yet.
Click to expand...
Click to collapse
I'm using Nova Prime too, but not the DTTL feature, and I'm not seeing this issue. I am using the DTTW in Settings (8.1). Have you tried toggling off DTTL in Nova for a while? Stranger things have happened.
v12xke said:
I'm using Nova Prime too, but not the DTTL feature, and I'm not seeing this issue. I am using the DTTW in Settings (8.1). Have you tried toggling off DTTL in Nova for a while? Stranger things have happened.
Click to expand...
Click to collapse
I'm not using Nova' DTTL, just DTTW in settings. Also using immersive move with system tuner. Not quite sure why i can't get it to wake when it happens. Ambient display turns off and its just a dark screen. Fingerprint reader registers because you can feel the vibration, but the display remains off. I tried flashing 8.1 again and reinstalled magisk, but the issue is still there. happens randomly.
mirwolf said:
I'm not using Nova' DTTL, just DTTW in settings. Also using immersive move with system tuner. Not quite sure why i can't get it to wake when it happens. Ambient display turns off and its just a dark screen. Fingerprint reader registers because you can feel the vibration, but the display remains off. I tried flashing 8.1 again and reinstalled magisk, but the issue is still there. happens randomly.
Click to expand...
Click to collapse
I believe there is a problem with Oreo and immersive mode. I had the same thing happen to me. Screen would go black if I pushed the power button but finger print scanner worked as you could feel the vibration. Also if you press lock again you get the screen lock sound.
Sent from my Pixel 2 XL using XDA Labs
Anyone found a solution to this issue. I'm having the same problem. Exactly as described.
Zetanator said:
Anyone found a solution to this issue. I'm having the same problem. Exactly as described.
Click to expand...
Click to collapse
Remove Magisk manager and remove Root entirely. Rooting is what caused it for me, I guess I had an older version of Magisk manager installed so I went to the official Magisk thread and downloaded and installed the latest Magisk manager app then flash the Magisk zip file via twrp and I haven't had a problem since
mackentosh said:
Remove Magisk manager and remove Root entirely. Rooting is what caused it for me, I guess I had an older version of Magisk manager installed so I went to the official Magisk thread and downloaded and installed the latest Magisk manager app then flash the Magisk zip file via twrp and I haven't had a problem since
Click to expand...
Click to collapse
Thanks I appreciate the help. I ended up going back to stock. The issue got progressively worse.
I too have this issue, I'm almost positive the phone does this when when the screen times out. If I press power button to turn it off I never have the issue. I only think that's what causes it but i think there's more to it, like having magisk and being rooted. Just assumptions. I also noticed that when this happens Android thinks the screens on, I have an app that lets me use active edge to turn on flashlight and it turns light on even though the screen isn't actually on. Even in battery settings it shows my sot being higher than it should.
I experienced the issue. I did have the immersive mode, rooted with magisk, edge sense, and was using substratum. After I installed an up to date module for edge sense in Magisk manager, I haven't seen it since. I think it's the previous outdated Magisk module that's doing it. Could be the base Magisk module as well.
Same issue here... very frustrating. I dropped $6 on this launcher primarily for just the tap to sleep / wake feature on my Pixel 2 XL and can't wake it. It's locked in a deep sleep. I'm forced to press the power button once and then it just wakes to ambient screen on double tap afterwards. THEN...double tap again to wake. Did I just waste my money? Anyone get a solution to this yet?
I just want to add that I have the same issue but I'm not rooted. Using an immersive mode app. Really hoping this isn't an issue on P.
robnhl said:
I just want to add that I have the same issue but I'm not rooted. Using an immersive mode app. Really hoping this isn't an issue on P.
Click to expand...
Click to collapse
I've solved this issue for me. I'm using Navigation Bar Hider from the Play Store to force immersive mode. I had to deselect the system UI-type apps from the NBH settings. Since I did that I haven't had any issues waking up the phone. I basically deselected all of the system apps then went back and selected things like Chrome, Calendar, etc.
Me too... With inmersive mode but only when have less of 10-15% of battery .....
Enviado desde mi Pixel 2 XL mediante Tapatalk
I have been having an issue for awhile that is driving me crazy. I have my screen lock set to swipe with Ambient Display set to on and Double Tap to check phone enabled. On occasion, I can double tap to wake the phone or push the power button when the Ambient Display is showing and the lock screen is bypassed and the Home Screen is displayed. I have tried to go to Settings/Security & location/Advanced and Clear Credentials, followed by a reboot. It solves the issue for awhile but then it returns. Sometimes it is several days and sometimes it is within several hours. Anyone else have this issue? If so did you figure out a fix? Thanks
bdcrim said:
I have been having an issue for awhile that is driving me crazy. I have my screen lock set to swipe with Ambient Display set to on and Double Tap to check phone enabled. On occasion, I can double tap to wake the phone or push the power button when the Ambient Display is showing and the lock screen is bypassed and the Home Screen is displayed. I have tried to go to Settings/Security & location/Advanced and Clear Credentials, followed by a reboot. It solves the issue for awhile but then it returns. Sometimes it is several days and sometimes it is within several hours. Anyone else have this issue? If so did you figure out a fix? Thanks
Click to expand...
Click to collapse
Do you have any Smart Lock options checked?
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Do you have any Smart Lock options checked?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Nope. That choice is grayed out when you choose swipe for Screen Lock. Thanks
bdcrim said:
Nope. That choice is grayed out when you choose swipe for Screen Lock. Thanks
Click to expand...
Click to collapse
When you choose "swipe", it disables your lock screen.
Try this: choose password/pin/pattern for your lockscreen. Add a fingerprint too. Then go back to settings and choose swipe. You'll get a warning that you are disabling device protection and removing security for it.
xunholyx said:
When you choose "swipe", it disables your lock screen.
Try this: choose password/pin/pattern for your lockscreen. Add a fingerprint too. Then go back to settings and choose swipe. You'll get a warning that you are disabling device protection and removing security for it.
Click to expand...
Click to collapse
Thanks. It looks like swipe is actually a choice for the lock screen . I have been using it for about a year. None is the choice if you want to bypass it. I did try what you suggested and it worked for a day, but then it reverted back to bypassing again. Thanks again
We all are aware that enabling faster animation under developer settings causes a glitch in the fingerprint reader in Always On Display where the fingerprint reader icon gets disabled.
Is there a fix for this yet?
lemonspeakerz said:
We all are aware that enabling faster animation under developer settings causes a glitch in the fingerprint reader in Always On Display where the fingerprint reader icon gets disabled.
Is there a fix for this yet?
Click to expand...
Click to collapse
No, we are not all ware. I do not have any problems with my fingerprint reader when making animations faster.
It seems to be a bug that only affects a certain number of people.
Yup, no issues here on .037.
I'm affected, no fix known to me.
gpvecchi said:
Yup, no issues here on .037.
Click to expand...
Click to collapse
I'm also on .037
I find this so strange. I've set my animation to anything other than 100 or 0, and afterwards, my AOD sometimes does not display the fingerprint logo for me to unlock the pixel 6 pro.
I'm then forced to press the power button to show the logo and proceed to unlock the phone.
lemonspeakerz said:
I'm also on .037
I find this so strange. I've set my animation to anything other than 100 or 0, and afterwards, my AOD sometimes does not display the fingerprint logo for me to unlock the pixel 6 pro.
I'm then forced to press the power button to show the logo and proceed to unlock the phone.
Click to expand...
Click to collapse
Same thing here.
I went back to x1.0 animations and now everything is ok with fingerprint and AOD. it used to disappear, and I had to power on the screen to unlock it with fingerprint.
If this phone had a better battery consumption and face unlock, I would keep it for 5 more years... but like this, I'm changing to Xiaomi 12 as soon as it gets released.
Has this been fixed with the December update?
mko000 said:
Has this been fixed with the December update?
Click to expand...
Click to collapse
Yes. It has. But I'm not a fan of it since the update. The animation is sometimes choppy and it's very noticeable. I'm annoyed with it. The animation was not an issue prior to the update.