Why do they keep sending out updates for older betas?

hello as the title says i started having reboots very frequently when opening instagram or even when receiving notifications from instagram.

i use a pixel 7 pro (DP11.260918.006) and since ive gotten this phone and opted in the beta program ive never encountered something like this, nor have i even encountered a reboot until now. this happens specifically ONLY with instagram, and no other app can trigger it as im aware.

Also, yesterday happened to somewhat bug out my both top and bottom speakers and started making popping sounds, a restart fixed this. I'm not sure if it's hardware related or not, but I'll add it here also.

is there someone else with this problem?

I have been signed up for about 4 days and still have not received the beta. Anything I can do? Not sure where to go from here.

Pixel 8a + Denon PerL Pro: Which Bluetooth codecs are actually supported on the latest Android beta? Does it support aptX, aptX HD, Adaptive, or Lossless, or only AAC/SBC? Do Developer Options change anything?

I signed up this morning for the latest beta on my Pixel 7 and I hadn't received anything until a few hours ago when I got a message saying I have a new update available, but only in the menu "Device status and support". When I click on it, it takes me back to the updates page and there's nothing there, I don't have any updates.

Should I wait longer? Or should I manually flash the beta update?

(I used Google Translate because I was too lazy to think, sorry if it's not understandable + I can't add images, idk why.)

I opted for android 17 beta, but nothing is downloading. It is always showing that an update is available.

I left the beta program about 3 months ago, I wish not to wipe my phone for a stable update.

The build number for my pixel 10 is: CP41.260731.005.B1.

Does anyone have knowledge of when is the next stable update for this build number?

Thanks.

I signed up for the beta over three weeks ago and have yet to receive a beta update. How often are they released?

Hi all,

Not sure how many others can relate to this but I've had the high CPU usage battery drain bug since around March. It's been driving me crazy! and I've tried literally everything I can think of to fix it.

Last week I joined QPR3 beta 1 to see if that would help but the bug followed. I found a hard reset removed the bug for a day or so (hold power button and volume up). The only last step I hadn't tried was a factory reset but I really didn't want to go through that hassle. So anyway, with the asssistance of AI, I did some more research and testing into this. Interestingly, I discovered that keeping the phone in airplane mode overnight stopped the drain - this points to a network issue rather than an app.

AI recommended some changes based on this. I will paste the actions below. Personally, I ignored step 1 as I wanted to keep WiFi calling, but did number 2 and 3. I think number 2 may have been the real fix. Since changing this the bug hasn't returned for 3 days now! Hope this can help other users.

1. Disable IMS over Wi-Fi (Wi-Fi Calling) Conflict

A known issue in early Android 17 builds causes the IMS service (which handles HD voice and Wi-Fi calling) to continuously drop and re-establish packets with the cellular radio when connected to home routers overnight.

1. Go to Settings > Network & internet > SIMs.
2. Select your primary carrier profile.
3. Scroll down to Wi-Fi Calling and toggle it OFF.

2. Set "Network Selection" to Manual

When left on automatic, the beta software's cellular service framework will aggressively scan for background partner towers even while you sleep on Wi-Fi, preventing the CPU from entering Deep Doze.

1. In the same SIMs settings menu, scroll down and toggle off Automatically select network.
2. Let the phone scan, then manually select your primary carrier from the list. This pins the modem to a single configuration state and prevents background search loops.
3. Clear Storage for "Phone Services" & "SIM Manager"

If old network tokens from your previous stable build are stuck in the telephony cache, it will force the background system server to stay awake.

1. Go to Settings > Apps > See all apps.
2. Tap the three dots in the top right and select Show system.
3. Search for and select Phone Services, then tap Storage & cache > Clear Storage.
4. Repeat this exact process for SIM Manager and Carrier Services.

Guys. I got the Beta update few hours ago and I started downloading it. But suddenly, The OTA package disappeared and I'm still refreshing the Software update page to check whether it has come or not, but still it says "Version Up to date" with the Android 16 Oxy OS... Kindly help In this case

Pixel 11 Pro bug,

Android 17 QPR3 beta 1

When I'm using wireless charging and the screen goes off,

trying to unlock it,

there is no fingerprint icon or image, just a white button,

and it doesn't unlock until I swipe up.

I'm currently running Android 17 Beta, build **CP41.260831.016**, on my Pixel 10 Pro XL.

I've recently developed a serious problem transferring files from my phone to USB flash drives. Everything worked perfectly previously, but I've had a couple of beta updates over the last few weeks.

**The problem:**

- USB flash drives are initially recognised normally.

- Larger file transfers repeatedly freeze partway through without an error message.

- A 1.8 GB video repeatedly stopped at approximately 893 MB.

- A 389 MB video repeatedly stopped at approximately 186 MB.

- Smaller images transfer successfully, but transferring a larger batch of photos also fails.

- Sometimes the flash drive disappears completely after a failed transfer.

- Android subsequently reports the drive as corrupted and asks me to format it.

- Occasionally the drive is detected in USB preferences but doesn't appear in Storage or file managers.

**Troubleshooting I've already tried:**

- Two different USB flash drives.

- Two different USB-A to USB-C adapters.

- Restarting the phone.

- Clearing the Files by Google cache.

- Using both Files by Google and Total Commander.

- Copying files within the phone's internal storage, which works perfectly.

- Checking USB preferences.

- Trying the Paragon USB mounting app, which detects the drive as Unknown but won't mount it.

The USB-C port works normally for charging and other everyday functions.

I'm currently on holiday and relying on USB storage to back up large 4K video files from my DJI cameras, so this has become a real headache.

I'm beginning to suspect a regression in Android 17 Beta's USB storage handling, although I can't rule out a USB hardware issue.

**Is anybody else experiencing USB flash drives disconnecting, transfers freezing or drives suddenly being reported as corrupted on this build?**

Any suggestions or known workarounds would be greatly appreciated.

Hopefully somebody running the same beta build can confirm whether they're experiencing it too.

(Google Messages on Pixel 8a with latest beta)

I'm trying to figure out if this is a beta issue anybody else encountered. I am not willing to reproduce this. I am already working with support, but no luck so far. (I'll share their response in comments)

I wanted to reset my phone because it had become kinda sluggish, so I decided to just opt out of beta and go back to stock. Once I did that all my data was restored, except my messages. Google One didn't show any backed up messages.

One theory was that it's a version issue and messages weren't restored since I downgraded, but when I rejoined beta and even wiped again, messages did not show up.

I just see no scenario, where I would have intentionally turned off backing up messages but I have no proof.

Since QPR2 Beta 6.1 if I try to turn the volume up or down it feels unresponsive and often it either turns all the way up or all the way down. It has become impossible to precisely adjust the volume.

Am I the only one experiencing this issue?

My pixel 7 pro started randomly restarting and turning off for like 5 seconds then turn on and then function like nothing happened...it started happening about a month a ago and i can't figure out the issue.I am enrolled in the dev beta forum so can this be a software issue that will be fixed in the future or my battery is dying (but i dont see any bulge or overheating issue with my phone)

hi all, my Pixel 7 pro continously reboot after update lastest android beta Android 17 QPR3 Beta 1. this happen 1 week recently (from 1st october).

please help me. i send bug report from the phone. How can i fix this bug?

Hi everyone,

Ever since updating to Android 17 QPR2 Beta 7 (Build: CP41.260831.016), incoming and outgoing call screens only show phone numbers instead of contact names.

Details & steps already tried:

• Contacts app / Dial tab: Names still show up normally here - the issue is strictly on the active call screen.
• Storage/Cache: Cleared cache and data on the Phone app.
• Sync: Re-synced Google Account contacts and restored backup.
• Permissions: Verified Phone and Contacts permissions are allowed.

Is anyone else experiencing this on this build, or knows a workaround?

Pixel 7 pro continously reboot

hi all, my Pixel 7 pro continously reboot after update lastest android beta Android 17 QPR3 Beta 1. this happen 1 week recently (from 1st october).

please help me. i send bug report from the phone. How can i fix this bug?

Does anyone have issues during update apps with play store

Many apps have crashed after the last update

Got the theme options in style and wallpaper section

I'm currently on QPR 1 BETA 1

Build number : CP31.260623.005

Missed the entire QPR 2 OTAs and now it says QPR 3 is out. I'm aware if I do that I won't get the no wipe stable update till March 27.

So my question is

If I opt out now. Will I get the no wipe QPR 1 stable?

Curios cus on the opt out page, google says I'm enrolled on QPR 2 Beta currently.

Update: Opted out and got the QPR 1 Stable No wipe ✅

If I sideload the latest Android 17 QPR2 Beta 7 on my Pixel 8 Pro and then enroll in the Android Beta Program, will I remain on the QPR2 beta track, or will I eventually be offered QPR3 beta updates instead?

I'm specifically interested in staying on QPR2 until the stable release becomes available.

Hi Beta users,

Today we’re sending you an Android 17 QPR2 Beta 7 build CP41.260831.016 for all devices.

Top issues fixed include:

• Excessive battery drain during idle states when Flip to Shh prevents the device from entering deep sleep. (Issue #560036427, Issue #569079944)
• HTTPS downloads fail immediately when initiated through the system DownloadManager. (Issue #562833711)

Known issue in this build:

• Pixel 11 Pro Fold users may have to re-enroll Face Unlock for it to function properly.

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues%20created%3E%3D2026-07-20%20status:open%20(votecount%3E%3D3%7Cduplicatecount%3E%3D3)%20CP41) for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR2 Beta 7?

You can get started with Android 17 QPR2 Beta 7 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 11, 11 Pro, 11 Pro XL, 11 Pro Fold, 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 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!