this post was submitted on 13 Sep 2023
11 points (100.0% liked)

Google Pixel

5852 readers
1 users here now

The World's Google Pixel community!

This community is for lemmings to gather and discuss all things related to the Google Pixel phone and other related hardware. Feel free to ask questions, seek advice, and engage in discussions around the Pixel and its ecosystem.

We ask you to be polite when addressing others and respect Lemmy.world's rules.

NSFW content is not allowed and will immediately get you banned.

It also goes without saying that self-promotion of any nature and referral links are not allowed. When in doubt, contact the mod team first.

Also, please, no politics.

For more general Android discussions, see [email protected].

This community is not in any way affiliated with Google. If you are looking for customer support regarding your Pixel phone, look here instead: https://support.google.com/pixelphone/

founded 1 year ago
MODERATORS
 

Lately (last few weeks or so) my Pixel 6 Pro has developed an incredibly frustrating contactless payments problem.

Out of the blue it will become really, really slow to respond to tapping for a payment, taking 5 -20 seconds to actually open the Google Wallet/Pay app and do it's thing. If I tap and it's not immediately opened I've tried to open the app via the quick tile but the button is non-responsive. Eventually it'll open and then I can pay.

Once it's acting like this it'll do it indefinitely, but I can fix it by restarting the phone. Then payments (and opening the app) are near instant as they should be.

Anyone else seen anything like this? Any solutions?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 1 year ago (1 children)

I don't ever open Google pay or whatever it's called these days.

I just hold it to the contract point and it asks for my fingerprint instantly.

[โ€“] [email protected] 3 points 1 year ago

This bug was happening doing that. I never usually open the app either. I was having to because of this bug to try fix it.