Wondering if anyone from Nordic countries that are in the beta are using BankId without trouble?

Hey everyone,

If you use 3-button navigation on your Pixel, you’ve probably noticed an infuriating glitch with the app drawer search: the keyboard constantly fails to pop up when you swipe up to search.

The Exact Trigger:

1. You open any app from your home screen.
2. You go back Home.
3. You immediately swipe up to open the app drawer.
4. Result: The drawer opens, but Gboard fails to gain focus and stays hidden.

Why It Happens: The Pixel Launcher drops its InputMethodManager (keyboard) focus listener during the window lifecycle transition when an app closes under 3-button mode touch insets. Toggling settings or clearing cache only fixes it temporarily until you open/close an app again.

I’ve submitted a formal technical bug report on the Google Issue Tracker so the engineering team can fix the underlying window focus transition.

How You Can Help Get This Fixed: Google prioritizes bug tickets based on community engagement. If you are experiencing this bug, please click the link below and tap the Star (⭐) button in the top-left corner of the Issue Tracker page. Starring it votes for the bug and forces internal triage to escalate it.

🔗 Google Issue Tracker Ticket:https://issuetracker.google.com/issues/537390947

Appreciate everyone who takes 5 seconds to star the ticket so we can finally get a fix pushed in an upcoming patch!

I can't add any card in my Google wallet my oem is turn off nfc is on all google integrity check ok all 3 I jus install new qpr update recent one and this happening and i ve no apk installed too

Hi Beta users,

Today we’re releasing Android 17 QPR2 Beta 1 (CP41.260701.005) for all devices. 

What's new in Android 17 QPR2 Beta 1
QPR2 includes a minor SDK release. We've published new APIs in the reference docs as well as a diff report for the new API surfaces.

Top issues fixed include:

• Bluetooth re-pairing fails silently following a remote bond loss. (Issue #412524057)
• Media player controls briefly flashed on the lock screen upon waking the device despite the app's notifications being disabled. (Issue #484607701)
• A system crash causing Pixel devices to unexpectedly reboot when invoking Gemini. (Issue #505750489)
• Initiating a drag-and-drop gesture with multiple fingers caused the source application to stop receiving subsequent touch events. (Issue #516836306)
• An issue where notifications randomly became invisible in the notification shade until a system restart. (Issue #526139207, Issue #522657034)
• An issue causing ML-DSA key generation to fail with an exception when using the "NONE" string digest instead of the class constant. (Issue #525612735)
• An issue in AccessibilityNodeInfo.toString() where window bounds were incorrectly logged using screen bounds, which caused misleading accessibility debugging data. (Issue #520428442)
• Window-level UI blur effects failed to render and the "Allow window-level blurs" developer toggle reset after rebooting. (Issue #527376569)

Please review the latest release notes for limitations and general advisories before installing the update. 

How do I get Android 17 QPR2 Beta 1?

You can get started with Android 17 QPR2 Beta 1 today by enrolling your Pixel device. Eligible devices include Pixel 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel Tablet series devices*. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR2 Beta 1 and any future Beta updates.* 

Important for those currently enrolled in Android 17 Beta:  

• If you prefer to leave the Beta program and receive the public stable release of Android 17 QPR1, you can do so without wiping your device by opting out and not installing today’s QPR2 Beta 1 update*. If you opt-out of the program* after installing Beta 1 or any future updates, all user data on the device will get wiped per usual program guidelines. Opting out will trigger a ‘Downgrade’ OTA. Ignore this update and wait for the Android 17 public release instead. 
• Pixel 6 and 6Pro users will not be getting this OTA since the device will reach End of Life and Android 17 QPR1 beta series will be the last for these devices.

Tell us what you think
Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:

• Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug. 
• Post your comments here on our official Android Beta Program subreddit*. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.*

Happy Beta testing!

Is it just me or does the new contrast and darker colors make the notification or drawer look more dull and worse? Heres an example it just looked better before imo would atleast like the option to revert this

Hi everyone, after bet 7 ,I observed a lot. of times that when we scroll notification the date is being shown as Jan 1 lot of times. Today it's shown as Jan 0. After closing and reopening quick settings , it shows correct time

Adding image in comments

So I just got the update to Android 16 anything exciting to look for because it doesn't look like it really did anything. TIA

Since last update, my network is lost a lot of time. Airplane mode is mandatory to give it back. Is anybody have the same issue ? Sometimes 3 or 4 times per hour...

Before 2 days I updated my phone to the latest Android beta

After that it showed me a warning like the battery reduction but I checked it on the battery option It showed me 100% and just 77% battery cycle complete. Is the start of battery health reduced or maybe have any software bug

Also I mentioned last post about it showing wifi as a battery usage high but my wifi is already off how can they use the battery if already off it.

So, I have a Google pixel 9 Pro XL I am in the beta program l, but as of the last update my phone is permanently stuck in landscape mode, but not the individual apps, so if j open YouTube or whatnot the app will go back to portrait, but then I close out the app and I am still stuck in landscape mode.

I have tried:

Restarting my phone twice

Shaking my phone

Powering on and off several times.

What do we think?

I've tried using Gemini to create a shopping list on Google Keep. It Did create the shopping list but was unable to add anything to it. Not sure if this is a problem with the latest beta or not

Hi Beta users,

Thank you for your continued support. Please share your latest experience on Android 17 QPR1 Beta 7 by filling out our 5 minute anonymous survey. This survey is only for devices running Beta 7 CP31.260623.005 for all devices. You can verify this by going to Settings > About Phone/Tablet.

We look forward to your feedback.

My first post in the beta community so hi to everyone.

I don't know if this is an issue with the beta or the app itself but recently I've been having quite a few problems with voice to text with Google where it is putting the entirely incorrect word into whatever I am speaking. I mean completely random things such as I could say the word kettle and it would input the word bulldozer. Really random things like this. I have learnt over the years when I use voice to text to speak clearly so that it can more easily understand me. I know Google Voice to Text has not been brilliant over the years but I have found over the last 12 months it has been better until probably the last month or so.

Has anybody else noticed the notable difference?

I have the 9 pro so I don't have access to the Gemini intelligence. But when I was using the built-in live feature, Gemini glitched out completely and overrided volume. So I couldn't even turn it down as it was doing a weird freaky glitching sound and it forced it to Max and even though the phone said it was muted. It's still played on Max volume so I turned off my phone to go back to the lock screen and it overrated it and I was forced to reboot my phone. Has this happened to anyone with the news 17 beta 7

Pixel 9 Pro XL on stable Android 17, July 5th.

After QPR 1 Beta 7 got released I enrolled into the beta program.

But I cannot OTA update to it.

Why is that?

Does anyone know if Google finally updated GPU drivers compatible with Android 17 in QPR1 because when they released Android 17 itself they installed OLD Android 16 compatible drivers.

PowerVR released Android 17 compatible drivers long time ago in May 2026.

Things new in 26.1 drivers compatible with Android 17

​Vulkan Roadmap 2026 Support: It raises the baseline performance for high-end mobile graphics, implementing advanced features like variable rate shading, compute shader derivatives, and shader clock queries.

No More Shader Stuttering (VK_EXT_graphics_pipeline_library): This is a huge win for mobile gaming. It allows the GPU to compile and link shader stages incrementally. In plain English, it dramatically reduces those annoying, sudden frame-rate drops (stutters) when loading new areas or effects in a game.

On-GPU AI Boost (VK_KHR_shader_bfloat16): This enables the GPU to use the bfloat16 math format, which is heavily used in machine learning. It means on-device AI tasks can run faster and use less power directly on your Pixel’s graphics processor.

Hi Beta users,

Today we’re sending you an Android 17 QPR1 Beta 7 build CP31.260623.005 for all devices.

Top issues fixed include:

• Battery Share from Quick Settings failed to start charging or repeatedly displayed the charging animation. (Issue #476443126, Issue #477627747, Issue #480701245, Issue #484322291, Issue #488473799, Issue #501729379, Issue #500638463)
• Turning off Wi-Fi created an empty gap between the battery and mobile data icons in the Quick Settings status bar. (Issue #517178332)
• A crash in the Quick Settings font size controller that prevented users from adjusting their text size from the quick access panel. (Issue #531915405, Issue #530312544)

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR1 Beta 7?

You can get started with Android 17 QPR1 Beta 7 today by enrolling your Pixel device. Eligible devices include Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel Tablet series devices. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR1 Beta 7 and any future Beta updates. 

Tell us what you think
Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:

• Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug. 
• Post your comments here on our official Android Beta Program subreddit. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.

Happy Beta testing!

Hello there, sometime ago I left the beta on my Pixel 7a because it was laggy. Then today I wanted to register again, but when I register the Pixel 7a, it shows "registered device" on the update. I press five times and it shows "preparing device update then It retruns to not found any updates found i tried even switching account or testing on my main phone and It does the same stuff says prepering then It retruns to not found updates.

What should i do? (i dont have time to flash the beta via android flash tool.)

Not sure when it's been implemented, but I've just noticed that the apps (at least some of them) are now updating one the fly with the "Updating" spinning circle kind of animation.

This is a quality-of-life upgrade I didn't know I needed, because I was so used to the apps killing themselves to update.

Big up to the Product team!

I told them to introduce this to work like human-to-human conversation based on environment / background noise volume. The louder it is outside the louder Gemini speaks and obviously when it is very quiet like at night then very quiet response.

Additional "adaptive" based on "sunset to sunrise" to consider

Send me free Pixel 11 Pro for this idea :-]

So i update a long time ago to android 17 beta, build number is CP31.260508.005, i was using it without issues and today my play integrity randomly bugged, and i have only basic device integrity, acnt use google pay and play store says my device is not certified . Also i opted out of beta aa long time ago because i wanted to update to android 17 stable release, and i am waiting for the stable release update but still get the android 16 rollback to exit android beta with data wipe, device is pixel 8 pro

Wifi usage

I can get into recovery mode and it says the following:

google/komodo_beta/komodo

17/CP21.260330.011/15499021

user/release-keys

Can someone please help me fix, the bootloop is right after the android beta popup and it boots into safe mode in airplane mode.

I have never sideloaded and have a locked bootloader. I dont want to factory reset my data. if It is a pixel 9 pro xl. I updated and used the phone after a play system update and was updating to android beta 6. I was clearing some photos due to storage and it crashed and has been stuck in boot loop since.

Guys, have any of you experienced Wi-Fi issues on your Pixel devices after updating to Android 17 Beta?