Annoying Pop-Up each time I use fingerprint to unlock my phone. - P8 Lite (2017) Discussion

Hello,
As the title says, I get the pop-up attached to this post each time I use the fingerprint to unlock my device. It appeared one hour after I installed an app called light flow. It doesn't happen when I unlock it with my pin, it only happens with my fingerprint AND when my WiFi is off. I Did a virus scan and of course it came up with nothing. I need help cause it is annoying the hell out of me.
Thanks.

Ok so I came across this:
https://forums.androidcentral.com/g...8-annoying-wifi-scanning-popup-wont-stop.html
Which basically says that disabling WiFi+ will work until Huawei and Google fix the Google play services bug.
Thanks for nothing:highfive:

Related

NFC unlock

Ever since upgrading to Lollipop 5.1 on my Moto X (2013), I get the message: "vnd.android.nfc://ext/motorola.com:xring", every time that the screen unlocks with the Motorola NFC Skip. Is there a way to prevent the message from showing?
Thanks
Pat
I get that message as well, the Skip doesn't really work consistently for me anymore though. Maybe the first day I set it up it kind of worked, now it doesn't do a damn thing. Anyone on 5.1 with 2013 able to get it to work reliably? I may do a factory reset if so.
If i remember correctly, Motorola posted that skip wont work anymore with 5.1
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
ohmimpotence said:
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
Click to expand...
Click to collapse
Does it still give the message or is it gone now?
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
ohmimpotence said:
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
Click to expand...
Click to collapse
I think that it has to do with SmartLock locks up the phone after 4 hours of inactivity.
The weird thing is it doesn't unlock with the Skip if it's locked due to inactivity.
Anyone ever get any satisfaction here? I just got the 5.1 update for me Verizon moto x, it's made my NFC ring practically unbearable. It unlocks the phone fine, but then it continually scans my ring and pops up every time the ring moves out of range and back in range of the NFC reader.
Sent from my XT1060 using XDA Free mobile app

Facial recognition issues anyone?

Anyone else getting face unlock issues? It works fine then suddenly stops working. Says it can't recognize a face. If I try to delete and re program the facial recognition, an error shows up saying the feature isn't working and the phone needs to be restarted. After restart, it works fine again. Happens now once daily.
twistanesh said:
Anyone else getting face unlock issues? It works fine then suddenly stops working. Says it can't recognize a face. If I try to delete and re program the facial recognition, an error shows up saying the feature isn't working and the phone needs to be restarted. After restart, it works fine again. Happens now once daily.
Click to expand...
Click to collapse
yes, I am having the same issue though it's perhaps once every three weeks.
I tried clearing the cache and data in the App manager but did nothing.
I am thinking it might be the app that scans for apps and it they are not used within three days it puts them to sleep. But that shouldn't cause it not to even run.
I think this is why Samsung put an option in the settings to auto restart your phone weekly or what not.
Mine acts up once in a while, so just switched back to IRIS. Anyone notice that there is no Preview Screen now? Just text at the top of the screen with instructions. (I like it better without the preview screen, thought it was tacky).
Have had this problem intermittently from day one, on this and another note. It's not so reliable. Fingerprint still the fastest.
Seriously facial recognition is garbage
Sent from my SM-N950F using XDA-Developers Legacy app
there is a setting which lets you make a less secure faster facial recognition. I use this with no problem...

Face unlock with Google Assistant

I have face unlock set up on my phone but if I want to set my alarm for example by saying 'ok Google set an alarm' the phone asks for me to show my face which isn't practical. I've looked in the settings but nothing seems to work.
Can anyone see something im missing?
Cheers
I have this problem as well. I use the Google Assistant quite a bit whilst driving, so it is really annoying that i have to then unlock the phone
Yep, same problem. 'Unlock with voice' doesn't really work. I've found this on other phones too. Be great if anyone has a solution.
Bluetooth unlock with the car set as the linked device?
Did anyone find a fix for this? It is annoying as hell.

[Q] Keeps requiring password/pin

Ever since the update to Oreo I've been constantly having this issue and it's extremely irritating and can't figure out how to stop it from happening. Basically at least once a day now, sometimes more than once it refuses to use the fingerprint scanner and wants me to enter my password or now my PIN since I switched to the less secure pin just to make it less of a pain everytime this happens and I just want it to go back to working properly so I can have the password again, does anyone know how to fix this issue? It's an unlocked note 8 and it's not rooted or anything, just a stock phone.
It's probably because you're phone has restarted and requires a pin after a restart before it'll use biometrics - It's a problem on Oreo, it's basically just a completely cr*p update that's broken so many things.
Samsung as usual, don't seem to give a stuff!
Nope, it's not a restart that's causing it, that's an entirely different message, especially since the phone's encrypted so the phone won't even start up on a reboot till the encryption password is entered. This is just a it randomly won't accept the fingerprint to unlock, I've turned the phone off then turned it right back on to unlock it and this has happened, 100% certain it had nothing to do with rebooting.
I've read some people saying they had an app that force locked the phone and that causes this and removing it fixed the problem, but I don't have any app that does that.
I have an unlocked note 8 too, I only use iris validation (finger print does not reliably work for me because of my eczema), the only time i have ever encountered this was when the phone went to lock screen while trying to access bio-metric validation (banking app, only ever happened once, i disabled fingerprint after due to unreliability relating to eczema as previously mentioned)
Maybe not the same issue but fingerprint unlock never works for me reliably. I get that message when my fingerprint can't be recognized. I have working hands so often my fingers get knicked, scratched, etc or even just wet causing my fingerprint not register. If I reregister fingerprint with out a perfect fingerprint, after my fingers heal, can't be recognized again. Happened on my Note 5 as well so I stopped using fingerprint to unlock.
Don't think that's the issue for me, I never have any issues with the fingerprint reader normally, it always works great when it actually lets me use it.

Question Face recognition/unlock stopped to work after last update

Hello! After the last update that I've received a couple of days ago (current OS version: 31.1010.0410.61) I can't unlock my phone using the camera, I need always to use the fingerprint. I've tried to re-setup the face recognition but nothing, I can't unlock the phone using the camera. Any idea how to fix it? I've noticed also that before during the unlock there was the green camera icon on top right, now there is just a green dot. I don't know if it can be relevant.
Any suggestion is appreciated.
Thanks!
Try to - delete your face from phone. Then in apps find Asus Face Unlock Service - force stop, then clear internal memory. Restart phone - register face and boom - works like charm, at least for now. You can also clear cache files system-wide and reboot your device.
Thanks for the suggestion but at the end I've solved in another way. When I went to "Security & Lock screen" section to remove the face recognition. I've noticed that there was a "Google Play system update" pending.
I've launched it and it fixed it
Good to know. But it may be temporary fix. I reported this bug of Asus official forum and - one of mods reply that they fix this in next FOTA. This must be something more serious.
The problem came back, after about a day later. Now everything is updated but the unlock doesn't work anymore. I wanted to try your method, but I don't find any "Asus Face Unlock Service" app. In the meanwhile I'll hope in a fix in the next FOTA
herod2k said:
The problem came back, after about a day later. Now everything is updated but the unlock doesn't work anymore. I wanted to try your method, but I don't find any "Asus Face Unlock Service" app. In the meanwhile I'll hope in a fix in the next FOTA
Click to expand...
Click to collapse
When you enter all apps menu press three dots and select show system apps. Then you find Asus face app.
Edit.
For me this solution is working for a out 2 days. After app crashes and you need repeat whole process.
I've just noticed that if you restart the phone it also "fixes" the problem, but I suppose that it won't last long. I really hope that they fix it asap

Categories

Resources