r/android_beta

1. When I try to swipe away notifications, it more often expands them (as if I swiped down on it) unless I intentionally swipe slightly up
2. Swiping down to expand the notification pane intermittently doesn't work

just curious if anybody else is experiencing similar things

Finally, it's working after 24 hours of struggle with the latest version of Intune - 5.0.6983.0.

Issues encountered after the recent update: System UI Lag: The overall system UI is lagging and stuttering. Navigation Gesture Issue: When swiping up to return to the home screen, the required swipe distance or trigger mechanism seems to have changed. It feels very unnatural and hard to use. App Instability: Certain games and applications frequently crash or freeze. Overheating: The phone suffers from unexplained overheating even during casual use. Battery Drain: Battery life has significantly worsened. Camera Lag: The camera preview window stutters and lags heavily. Context Menu Changes: The layout of the long-press app menu has changed, and the font size has become smaller, making it much less user-friendly.

I have loved the update, but have had a lag issue. When I am in an app and select the notification for Snapchat or Facebook Messenger, there is a weird holdup. Then, when I try to slide the auto brightness slider in the notification shade, it won't do anything for a few seconds. Anyone else getting this?

Google still haven't fixed this bug (https://issuetracker.google.com/issues/502262230)? I updated, no change, this bug will soon be a whole quarter old. My Pixel 10 Pro's battery life is terrible, it overheats like crazy, and the background battery drains like crazy. I hate this company, I'd rather buy a normal phone than a Pixel.

As everyone knows Outlook and Teams isnt working and while I can use Chrome to check my emails I guess Chrome is not compatible for Teams. Is there a workaround until this get fixed?

Meaning what can I use to interact with Teams?

In the quick panel, the clock when it's in 24hr format, gets cut off especially at like 20:00 and 00:00

I assume it's the auto switching between cameras and aperture.

I'm currently on Android 17 beta (not qpr1), on my daily driver pixel 8, do you guys think I should opt back into the beta and install qpr1 beta 3? Or just go back to stable? Also.. does shizuku work properly in the qpr1 beta?

Lock screen shortcuts. Finally, it requires a long press to work. After it was working just by touch, this issue has been frustrating me on both beta and the stable. But thankfully it's fixed by QPR1 Beta 3.

Hi. Just installed the latest may 19th QPR beta 3 and noticed instantly that microsoft teams and outlook are crashing right away and not opening

Any solutions so far?

So far I haven’t noticed any lags or microstutters. HWUI rendering also feels way calmer and touch response seems more instant again.

Anyone else feel like QPR1 Beta 3 is smoother than QPR1 Beta 2 overall?

I just installed Android 17 qpr1 beta 3 on my pixel 7, I saw in videos that they added the blur effects to more elements of the pixel launcher (folders, long press menu), as well as the volume panel, I got the pixel launcher blur but the volume panel and other UI elements still look the same, is this intentional due to the older hardware of the pixel 7 or is it a bug?

With yesterday's update, they seem to have raised the touch target to swipe into the Multitasking screen (along with adding more feedback with haptics) that is really messing with my muscle memory. Anyone else experiencing the same? P10Pro

My battery seems to be getting hotter in this beta build, anyone else having this ? I'm on pixel 8 pro

Hi Beta users,

Today we’re sending you an Android 17 QPR1 Beta 3 CP31.260508.005.A1 for Pixel 6/Pro/a Pixel 7/Pro and CP31.260508.005 for all other devices.

Top issues fixed include:

• A recurring system error in ContextHubClientManager that caused excessive logcat noise when attempting to send messages to unregistered clients. (Issue #289721806)
• Clicking on the date on at a glance prompts to open the terminal (Issue #506101970)
• Wi-Fi unexpectedly disconnects due to erroneous low-quality detection despite strong signal strength. (Issue #494670350)
• Users experienced frequent crackling or distorted audio during media playback from any source. (Issue #482749744, Issue #471865281, Issue #485701794, Issue #489062503, Issue #494050912, Issue #494901502, Issue #493915745, Issue #458363923)
• UI elements are partially cut off or positioned off-screen when apps are expanded to full-screen mode. (Issue #476830614, Issue #489452085)
• Home screen widgets would disappear or become unavailable in the widget picker after a device reboot. (Issue #488125748, Issue #505117543, Issue #505671079, Issue #497140330, Issue #506685943, Issue #510967059)
• The mobile data icon incorrectly remains active in the Quick Settings panel after Airplane Mode is enabled. (Issue #501368569, Issue #505757076)

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 3?

You can get started with Android 17 QPR1 Beta 3 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 3 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, you can do so without wiping your device by opting out and not installing today’s QPR1 Beta 3 update. If you opt-out of the program after installing Beta 3 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.

 

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!

I'm on QPR1 beta, now 3. On a Pixel 9 Pro.

I have a lot of Issues with the fingerprint biometric reader.

When it works, it works fine. But most of the time it does work.

I get the error "Can't process fingerprint. Try again." and I can't unlock.

In daylight, face recognition works to unlock. But in the dark I have to rely on pattern unlock.

Even worse, sometimes the fingerprint reader is not seen at all by Android. Like it was disabled. In the security settings for unlock, I have only pin, pattern or face.

Sometimes a reboot reenables it, sometimes no.

I know there are risks with running a beta version but it's seriously impacting the use of my Pixel 9 Pro.

Do other people have this issue?

Is anyone else having lag or buggy app switching? Especially when I click on let's say an Instagram chat notification, for me personally it takes approximately 3.8 seconds to go to the chat, or will put me on the screen of inbox and then take a few seconds to go to the designated chat. it seems app switching in general has been buggy this update. Any one relating to it?

Not sure if it's just an issue with Intune portal or Microsoft apps in general but they all crash on start up, even Microsoft Launcher.

Anyone else have this before I post a bug report?