• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Android Pay Issue

LarrDeb

Lurker
Is anyone else experiencing a problem with Android Pay?

I tap, it asks me for my pin to unlock, it then asks me to re-tap, and then asks me for my pin.....

This happens in an endless loop that goes absolutely no where.

I've checked all my settings are correct to have the app installed.

My device is rooted (as far as my noob experience with such a thing).

I don't know why it stopped working after doing so well on the previous OS.
 
Just got this email:

Hi,
It looks like the recent Android 7.0 update may have impacted Android Pay on your DROID Turbo 2. As a result, when you try to pay with Android Pay, you may be asked to unlock your phone repeatedly and the transaction might not go through.
We’re sorry for any inconvenience this may have caused. We’re working to resolve this as quickly as possible and will be releasing a new version of Android Pay in April that will fix the issue.
How to fix it immediately
To fix the issue immediately, you can clear all data stored in Google Play services, then add your credit and debit cards to Android Pay again. Keep in mind, if you have an Android Wear device paired with your DROID Turbo 2, you’ll need to factory reset it and pair it again after you clear all data.
  1. Open your phone settings
  2. Go to Apps > Google Play services > Storage > Manage space
  3. Tap on Clear all data
  4. Open the Android Pay app and add your credit and debit cards again
 
You must mean that you are NOT rooted. I believe that rooted phones are not allowed to use Android Pay.

But, it will be fixed in APRIL? That's a long time for an important fix! It's good that there is a workaround, though.
 
Well, after 2 updates the App continues the endless cycle of asking for a pin to unlock my device, re-tap, and back to square one. So done with this app at this point.
 
It won't work on rooted phones.

If you have a connected device/watch try disconnecting that first, then use Android Pay. I have to do that with my watch, it will sometimes get caught in a loop if I don't.
 
It won't work on rooted phones.

If you have a connected device/watch try disconnecting that first, then use Android Pay. I have to do that with my watch, it will sometimes get caught in a loop if I don't.

My device isn't rooted (I confirmed that). Android Pay was working find on the previous OS before 7.0. I have looked through every fix it helper, I have uninstalled and reinstalled, I make sure I have no connected devices via Bluetooth (I turn it off before using it), I just have no idea what I could do other than factory resetting my phone (which I'd rather just keep swiping my CC before I resort to that).
 
Greetings.
So when the Verizon Droid Turbo 2 Android pay was broken for me in May, even the clearing full steps did not resolve the problem. (Not rooted either.) I got tired of having to reset my Moto 360 watch from those steps, and asking the bank to reactivate my Android Pay Request.

It was a sad time.

After several updates, resets, and retries now and then last month it started working again.... sort of.

Now when I activate the Tap & Pay, it requests to unlock my phone, then another tap request, and it works perfectly. This is a rather annoying step as I am sure cashiers are frustrated with people trying to figure out how to use their tap & pay services and do not know what they are doing, so when I activate mine... Then have to wait and enter my lock pattern, then try again... It is not as efficient as it should be.
Sometimes a few tap and pay terminals will cancel the request immediately after the first tap request and their register has to be told to re-request a charge transaction which is frustrating to ask for. Some terminals will make multiple rapid tap request (like 3 per second..Firehouse Subs) which if you hold it there will keep prompting for the passcode over and over causing delays as the prompt opens like 5 times.

Thinking perhaps Android Pay was unhappy with my alternate security options, I disabled voice to unlock (which never worked), keep unlocked at location ( was testing using at home), and device dependant keep unlocked ( Bluetooth device in the car), so the only security allowed was the approved unlock pattern. Still is taking a tap/unlock/tap action combination to complete.

Any other ideas? ☺️

Thank you,
Zwergin
Chris Claxton
 
Back
Top Bottom