Skip to main content

Pixel users on Android 16 QPR1 Beta 3.1 facing Google Wallet, VPN issues

For some reason, not all Beta 3.1 users have received the stable release of Android 16 QPR1, and they are now facing Google Wallet/Pay and VPN issues. 

The Android 16 QPR1 “No Data Wipe” OTA started rolling out two weeks ago for some Beta 3.1 users.  However, it’s not yet available for all testers that opted out of the Beta Program (as they don’t want to be on QPR2 just yet). Our Pixel Tablet received said OTA, but it’s absent on a Pixel 8a.

Those still on Android 16 QPR1 Beta 3.1 are now getting a warning message with tap-to-pay. Opening Google Wallet reveals the “Device doesn’t meet security requirements” message: “This device may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info.”

Top comment by Thomas Moneyhon

Liked by 26 people

ABNER: I have to ask you to please look at facts.

NO USER ON 3.1 GOT AN UPDATE TO STABLE. ONLY 3.0 (those who did NOT UPDATE IN AUGUST)

Thus correct: "The Android 16 QPR1 “No Data Wipe” OTA started rolling out two weeks ago for some Beta 3.1 users."

and

"Our Pixel Tablet received said OTA, but it’s absent on a Pixel 8a."

Not true. Your pixel tablet was on 3.0 not 3.1. My pixel tablet is on 3.1 and has not got the ota to stable, thats how i know 💯 this is incorrect information you are sharing.

-Thank you.

View all comments

That said, after tapping “Got it,” everything functions normally for most users. For others, Google Pay does not work. 

Advertisement - scroll for more content

Meanwhile, we’re noticing an issue with the Pixel-only VPN by Google refusing to connect on Beta 3.1. It just shows the “isn’t available for this account” error.

The “No Data Wipe” update usually rolls out without issue after the stable release. It remains to be seen whether Google is waiting for the October 2025 security patch at this point.

A more immediate fix for those impacted is rejoining the Android Beta Program for QPR2 Beta 2. It’s pretty stable, but you might have an issue with the media player not appearing on the lockscreen. (Lockscreen widgets can be used as a workaround.)

FTC: We use income earning auto affiliate links. More.

You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel

Comments

Author

Avatar for Abner Li Abner Li

Editor-in-chief. Interested in the minutiae of Google and Alphabet. Tips/talk: abner@9to5g.com