As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
LubbocksFall said:
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
Click to expand...
Click to collapse
I have not had any issues with apps that rely on / give the option of fingerprint authentication. I also have Chase installed and I just tested it and it works fine. I also have Amex, Bank of America, alarm.com, ADT Pulse and fingerprint access seems to be working fine on all of them. I am also running stock 8.1 Oreo / March update- but I am unlocked and rooted with Magisk. One suggestion based on some Fingerprint related struggles I had recently (when TWRP couldn't decrypt and I had to remove Fingerprint/pattern security during the update process and then add back after updating/rooting)....I found that some apps that had already had Fingerprint access enabled, didn't behave well when Fingerprints were removed then added back on the phone. The best workaround I found in those cases was to uninstall the app completely, fully setup Fingerprint security on the phone, then install the apps again. This definitely was the case with Amex, Chase, and Bank of America. Just something to try...good luck.
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
LubbocksFall said:
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
Click to expand...
Click to collapse
Sideloading or taking the OTA natively doesn't typically wipe app data in my experience. Flashing the factory image (without removing the -w) would wipe your data (and most everything else)...but that creates alot of work in setting up your phone again. I found uninstalling the troublesome apps, setting up fingerprint security/pattern, then reinstalling and setting up the apps relying on fingerprints worked the best for me - but the situations are a bit different as my troubles always were related to adding new fingerprints to the phone and apps that had the "old" fingerprint information already....for me - uninstalling / reinstalling the apps solved my issue.. YMMV
Related
Flashed OTA to Oreo tonight, was 7.1.2 August Update, Unlocked, Google Phone on Verizon Network
Flashed this kernel:
https://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154
Rooted with Su, and Hidden with Suhide
After every restart, i get 2 app crashes of Gboard and Google App Services, the keyboard and everything seems to function normally after the crashes.
Attempted to clear data/caches on both apps, no change.
Has anyone experienced this or have any suggestions? Would prefer not to wipe completely.
Thank you
It might be a simple OTA issue, it probably bring some unneeded props from previous build (I adjusted nav bar in beta 3 so I can use pip but even after final release I still have it).
You can always flash factory ota image without wiping the phone. You need to edit a .bat file ofc, which is just removing a "-w" part.
But don't take my advice if you are not going to take a back up. It might get ugly also ?
Thank you for your thoughts. I spent too many hours trying to get it to work properly. I think I have it now. Hopefully this helps someone:
I found greenify was having issues and possibly locking apps/files after the update.
Uninstalled Greenify, and Pandora (which Greenify was complaining about)
Uninstalled Gboard
Removed device admin for Play Services
Uninstalled all updates for Play Services
Cleared all app preferences
Rebooted
Installed Play Services
Installed Gboard
Rebooted
Installed Greenify
Installed Pandora
Errors gone at this point. Will report back if something else comes up.
I have been rooted with SuperSu/Suhide since September and now am using Magisk 14.2 with the October security updates (flashed image and removed "-w" to retain data). I pass all of the safetynet checks from various apps under both conditions. I am having a problem adding cards to Android Pay. I add the card, verify the CVC, agree to the terms, and then get a popup saying that Google Play services has stopped. It does not finish verifying the card and clicking on the card results in the "Google Play services keeps stopping" error. This has happened since the September security update (did clear user data then) and I cannot find what may be causing it. I did edit the hosts file and build.prop when using SuperSu/Suhide, but now only the hosts file with Magisk. Anyone have a similar issues or know of solutions? Thanks.
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
Not sure if it's related, but I updated to September's Oreo build using fastboot flash of the factory image. I removed -w to save data. After this I was no longer able to purchase apps in the play store, always caused the play store to crash. Free downloads worked fine but paid transactions never went through. I ended up flashing the factory image and wiping data and all is well. I am unrooted.
mwalt2 said:
So no one else has experienced this? Does Android Pay and Magisk work fine?
:good:
Click to expand...
Click to collapse
I have the same issue can't buy apps. Get to the point of buying it and get FC. Doesn't matter if I'm rooted or not. Tried magisk and suhide
Not sure what could be the exact reason. I had google play services stopped problem on my Note 3, but it was not rooted. I followed a guide on Mobipicker, that worked for me. You can also refer, but not sure that will work for rooted devices.
I know this is old, but I found this thread because I had been having the same problem...I found the fix for my situation and figured I'd share in case anyone else came across the same issue... Everytime I tried to verify my card Google play services stopped...
I remembered that it checks that you have a secured lock screen when you set up at some point...I turned off smart lock location, on body detection, and face... Worked without any problems...
I'm at home, so I'm not sure if smart lock was preventing it from working just by being turned on, or if it thought I didn't have a secured lock screen because smart lock was triggered by me being at home...
I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Google Pay can be used under rooted device?
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
sb1893 said:
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Click to expand...
Click to collapse
JD_dadada said:
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
Click to expand...
Click to collapse
I've always been able to leverage the root hiding capabilities offered by the root providers I have used. Originally suhide for SuperSu...then when I moved to Magisk MagiskHide. Both have worked well for my root (and unlocked bootloader) hiding purposes. I've always been able to use Android/Google Pay, banking apps, alarm system apps, Netflix, etc...Occasionally, the cat and mouse game catches up with the root hiding solution, but the developers have been pretty quick to overcome any of the challenges encountered thus far.
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Zaczero said:
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Click to expand...
Click to collapse
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
javlada said:
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
Click to expand...
Click to collapse
Looks like I found the problem (at least in my case).
Some ROMs got issues with fingerprint scanner. I noticed that in my bank app after adding the fingerprint unlock it started to crash. Also in google play I couldn't add fingerprint as payment confirmation.
In Google Pay one of the steps of verifying cc is fingerprint check. I think that this fingerprint bug may cause the google pay to fail.
After installing a ROM with fingerprint scanner working properly (now I'm on LineageOS) the issue went away. Got my cc verified successfully with root and rom
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
davidrqli said:
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
Click to expand...
Click to collapse
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
sb1893 said:
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
Click to expand...
Click to collapse
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
davidrqli said:
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
Click to expand...
Click to collapse
Any progress on this? Were you able to get it working?
sb1893 said:
Any progress on this? Were you able to get it working?
Click to expand...
Click to collapse
Nope, still the exact same. Issues also persist in Safe Mode.
Had this issue with DP4. Had to do a factory reset. Sorry.
jaytv said:
Had this issue with DP4. Had to do a factory reset. Sorry.
Click to expand...
Click to collapse
Gotcha... thanks. Not in a position to do a factory reset now, but maybe in a week or so when I'm back from a trip. Anyone else have any luck fixing this without a factory reset?
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
davidrqli said:
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
Click to expand...
Click to collapse
Glad you got it sorted. That normally does the trick but it does suck if you don't have everything backed up.