It appears that after about 2-3 days of being rebooted, I lose the option of using a fingerprint reader to log onto my phone. I don't get the under screen display and have to use my pin number. A reboot cures it.
Has anyone else seen this or does anyone have a solution?
My phone is running the latest offical version of Android 12 and is not rooted.
cheers
Alan
Related
Hi. Since I upgraded to the Mate 7 - LT-10 Model to the new EMUI 3.1 and Android 5.1. The fingerprint does not seem to be working. It is not working like this, I setup the fingerprint reader in the settings like usual, after finishing the setup, the finger print does not seemed to be recognized. Never had this problem before. Any help? I do not want to reset my phone.
I've got some very strange issues happening since the latest T-Mobile update to baseband G930TUVU2APC8.
The phone is a T-Mobile Galaxy S7 with a Sandisk 200GB micro SD card installed
Whenever I'm on a phone call through a my Jawbone Era (and charging; I haven't tried it unplugged) the phone will behave as if it did a reboot, without actually rebooting, every few minutes. The phone will stop responding for about 20 seconds, then show just the wallpaper for about 5 seconds, then go back to the lock screen. At this lock screen it requires me to enter my password instead of using fingerprint as if it had just powered up. The phone call does not drop through all of this.
The next issue is that some pictures taken from the quick launch are sometimes not saved. I'm not 100% sure that this only happens after the reboot issue above, but I think it does. I have secure startup disabled .
I tried a factory reset which did not fix the issue, contacted t-mobile and was sent a replacement device that still has the problem. None of this was happening prior to the latest update.
Has anyone else experienced these issues? Also, is it possible to downgrade the firmware version?
Thank you,
Matthew
techy101 said:
I've got some very strange issues happening since the latest T-Mobile update to baseband G930TUVU2APC8.
The phone is a T-Mobile Galaxy S7 with a Sandisk 200GB micro SD card installed
Whenever I'm on a phone call through a my Jawbone Era (and charging; I haven't tried it unplugged) the phone will behave as if it did a reboot, without actually rebooting, every few minutes. The phone will stop responding for about 20 seconds, then show just the wallpaper for about 5 seconds, then go back to the lock screen. At this lock screen it requires me to enter my password instead of using fingerprint as if it had just powered up. The phone call does not drop through all of this.
The next issue is that some pictures taken from the quick launch are sometimes not saved. I'm not 100% sure that this only happens after the reboot issue above, but I think it does. I have secure startup disabled .
I tried a factory reset which did not fix the issue, contacted t-mobile and was sent a replacement device that still has the problem. None of this was happening prior to the latest update.
Has anyone else experienced these issues? Also, is it possible to downgrade the firmware version?
Thank you,
Matthew
Click to expand...
Click to collapse
The problem started in PB8 firmware, PC8 firmware has constant wifi dropout issues, you might find even that at 3G connection performing better than fiber optic wifi internet.
Easiest is to update facebook to latest version and see how many "can not connect right now" errors.
Random reboots is normal never mind how many times your factory reset or do a full firmware PB8 flash.
T Mo is not the brightest tools in the shed, it takes 5 visits to their T Mo offices to get the accounts and products purchased + refunds for items payed in cash or freebies refunded etc etc etc.....
Hi all, did a quick search but couldn't find what I was looking for. Feel free to point me in the right direction if I missed it...
Quick setup: Drowned my original S6 so bought a replacement second-hand, in really good condition. IMEI and such checks out as legit so no concerns about it being a fake.
Fingerprint scanner would NOT work reliably for the first couple of months - would accept new fingerprints OK but just wouldn't recognise them 80% of the time so I went with basic swipe for a while.
Then an update came through and ever since the fp scanner has worked flawlessly.
My issue is, whenever I restart the phone, it asks for my password to unlock instead of fp. That's fine, I know my password HOWEVER it will not accept it.
EVERY single time I restart my phone, I have to use Samsung's FindMyPhone on a nearby PC to unlock the phone. After which, I can reset the fingerprints and password and we're all good until the next time I have to restart (something I do VERY rarely now, because of this issue - if I'm not near a computer at the time, my phone is useless).
Has anyone else encountered this issue/know of a fix?
*Running stock Android 6.0.1. Optus (Australia) firmware, kernel 3.10.61-8829014
I dont know exactly the fix for this bug but if you did a backup, you can try a factory reset.
Hello guys, my fingerprint reader is not always working as it is intended. If it is working unlocking my phone isn't a problem, it is as fast as it should be. Also guestures on the fingerprint reader are working fine - then sometimes the fingerprint reader doesn't recognize that I put a finger on it. No vibration and no unlocked phone (obiviously) and I have to enter my pin to enter my phone.
Reboot doesn't resolve this issue, as it comes back a few minutes after restart. Phone is about a month old and on the latest Emui firmware. Any suggestions beside full wipe and returning to service center?
Thanks in advance!
The weird thing is that it doesn't even vibrate as to show that it didn't recognized the fingerprint, but it just doesn't show signs of life... And neither a reboot solve the issue instantaneously? So strange. Tell me something more, did you updated OTA, or with Firmware Finder? You have something like Greenify installes? Other?
RedSkull23 said:
The weird thing is that it doesn't even vibrate as to show that it didn't recognized the fingerprint, but it just doesn't show signs of life... And neither a reboot solve the issue instantaneously? So strange. Tell me something more, did you updated OTA, or with Firmware Finder? You have something like Greenify installes? Other?
Click to expand...
Click to collapse
No a reboot doesn't change anything - there is no app installed for battery optimization or a taskkiller or something similar. I've got the phone a month ago, everything else works flawless. I did the first update to android 7 via sd card and received another ota update some days ago. Every update was an official update from Huwaei/Honor, i have a c432 BLN-L21 device with no carrier lock or branding. Build: BLN-L21C432B365, Security patches from 1st August.
Just checked my build, man, and... we're exactly on the same, identical build. I only have to download the update and apply it because I'm still on B360, thing that I'll do probably tomorrow (even if I'd like to download the full package of 2,45GB and not only the upgrade of 547M, I'd like to keep the package for future eventualities since that Huawei removed firmwares from their site). Don't know if the first update via SD card could be responsible somehow or not of this, you remember if the update made by SD was the correct version of firmware that was matching with your initial build?
Does it happen mostly after you take out your phone from pocket and try to unlock with FP? Or some other behaviour while unlocking normally
shashank1320 said:
Does it happen mostly after you take out your phone from pocket and try to unlock with FP? Or some other behaviour while unlocking normally
Click to expand...
Click to collapse
It makes no difference if I take it out of the pocket or it is just lying around before trying to unlock it. No other faulty behaviour beside the unlocking problem.
@RedSkull23 I'm pretty sure I had the right firmware and that it was matching the product exactly.
gent0r said:
@RedSkull23 I'm pretty sure I had the right firmware and that it was matching the product exactly.
Click to expand...
Click to collapse
Well this tightens the circle of possible causes of this, did your phone ever dropped? I'm starting to think at an hardware problem now...
Try performing a hard factory reset but wipe the Cache Partition first. Be sure to back up all your data before you do this. That should help with any software conflicts.
RedSkull23 said:
Well this tightens the circle of possible causes of this, did your phone ever dropped? I'm starting to think at an hardware problem now...
Click to expand...
Click to collapse
Seems more of a hardware issue or may be a factory reset can help him here
Even I had the same problem. So the solution is to delete your previous finger print and than enable a new one. Hope this helps....
Hi, since updating to the new Android 11 update for OP6 I am having issues with Gpay - tap to pay.
I open up the goat app and hold my phone to the payment terminal and it does not work. However, if I reboot my phone it will work for a short time before once again not working.
OnePlus have not been that helpful, so I was wondering if anyone on the forum has the same issues and knows if it is a big or whether a fix existst?
Thanks
I, too, recognized that GPay didn't work since I updated to 11.
However, I have another app to pay by NFC from another bank, and that one works.
I haven't been able to test, yet, whether a reboot would fix that. Only appeard to me twice while I was standing at the cash-register in the supermarket.
I have this problem too.
After update to 11 version, in random time i cant pay in google pay.
Need OFF/ON NFC on phone and then works perfect.
Need wait some fix for NFC...
I have this problem also. After updating to A11 the Google Pay behavior becomes a little rare. When I try to add a new card the process start as it must be but after introducing the card data and press the button to go on, the next screen is completely white and nothing is seen and nothing happens, so I can`t continue with the process. I open a bug to OnePlus, I sent some screenshots and bug logs by no luck for the moment. So I am afraid I will roll back to A10.