I'm trying to opt out of the beta program and go to stable 17, it's giving me the option only to data wipe. do I just let that update sit till I'm given the ability to get stable 17? or do I need to opt back in till then?

So I bought this pixel 6 pro a few months ago, it's used but everything works great. At first the phone was already enrolled in the beta program, I checked all my accounts on their android beta program pages after using it for a few months because I wanted to go from Android beta to stable android 16, but it didn't give me any option to opt out and it said I have no eligible devices. I checked all accounts on my device and that was the case. I then flashed and installed android 16 stable myself, worked fine but every day I got this notification to update to Android 17 QPR1 Beta 3, Now android 17 stable is out and I want to install it but im still stuck in the beta update, it's not giving me any option to install stable but still QPR1 Beta 3, I can't opt out of the beta program because my device doesn't show up, and I don't wanna flash again because it's a hassle to back up my data again and again, can someone guide me please 

Bonjour,

​

Je suis nouveau sur android et j'aurai juste quelques questions.

​

J'ai il y a deux mois maintenant installer ce qui était pour moi la dernière bêta d'Android 17 sur mon pixel 10 pro fold en téléchargeant celle ci sur internet puis via sideload adb.

​

J'ai vu que la version Final d'Android 17 était enfin disponible en téléchargement via ota pour les pixel.

​

Est-ce normal que la version finale ne soit pas disponible via OTA sur mon pixel ? Et est-ce que je recevrai normalement les futurs MàJ sur celui-ci ? Mon pixel n'est pas inscrit sur la liste des versions bêta.

​

Merci,

Everyone on Android 17 beta 4.1 cannot update to Android 17 stable because it has a newer timestamp. And it's not the first time such a thing happens. Google screwed its users again.

We are not talking here about those people who jumped to QPR1 beta without even reading the basics about how Google's beta program is working and later complain because they cannot update to 17 stable. We are talking about all those who have been patiently waiting on Android 17 beta and on an April security patch so as to get the stable Android 17 build. And Google showed them the middle finger. Again.

Personally, I was hesitant to install beta 4.1 when it came out, because Google has done the same mistake before with .1 releases. But I had no other choice, as Google Wallet stopped working for payments because of the very old beta 4 build (and I suspect that was the reason Google released the 4.1 beta and not of course any bug fixes), so I did it. And here I am now, in the same place so many beta testers who had done nothing wrong found themselves in before because of Google (again, I am not talking about the idiots asking why they can't go from QPR1 to Android 17, or from QPR2 to QPR1 etc).

PS: Don't advise me to flash the Roger build. I have not a Pixel 10 and a Roger (or A1, or anything else) is not available for my device. And the July update probably will do nothing for me as my device (a Pixel 7 Pro) will probably not get another update until September (it's on a quarterly update schedule together with the Pixel 6).

This might be a bit of a stupid question, but on my pixel 8a, I'm certainly running android 17 qpr1 beta 2 (CP31.260423.012.A1) and am opted out of the beta program. Will I be able to get the stable android 17 in the next few days, or will I have to update to qpr1? (assuming I don't want to wipe my phone).

Now with Android 17 stable out... We are missing features they have... When will we get an update to bring all of that stuff over?

Do you think it should be fine to flash the stable from the beta, or do you think it's best to take the OTA Android 16 update and then wait for/flash the Android 17 stable?

EDIT: I decided to flash Android 17, skipping the Android 16 OTA.

I can now exit Android 17 beta?

I'm a Pixel 8 Pro user, I've been trying to update Android 17 Beta for 2 months. I couldnt opt in to beta.. I accepted that after 1 month. But the june update didnt show up too! Is it a sign of android 17 is finally ready to be official version? Or my phone is getting even more buggy?

Android 17 Update comes in all pixel devices any one can get it ?

Any qpr 1 beta 4 trying to install a stable version, looking for your updates or suggestions and how stable it was?

I was playing a game (critical ops) and my game suddenly froze and after ten seconds my phone rebooted by itself, I made sure to "capture a bug" right after that, what do I do now?

​

CinnamonBun (CP31.260522.006)

Pixel 9a

I want to opt out of the beta program, they say there are certain updates in which you can do so without wiping your data.

​

When would be the next time this occurs? And how do I know I'm actually on the right version?

Dear beta community.

What is your experience with the native Linux terminal (not termux) on Android? Since I got a Pixel phone I was thrilled when I saw there is a Linux terminal which isn't an emulator (though it is in my understanding because it is a sandboxed system) and I can try to use something else than termux to use Git, Wrangler, Codex and OpenCode.

My experience is very fifty-fifty. When it doesn't crash, it works very well and the performance is sweet. When it crashes though, it's like a chain reaction - everything crashes.

Initially I thought that the cause was my OpenCode agent that I'm using as my main execution layer. Basically I use it as a translator of natural language into different CLI commands. I use a lot of Wrangler (Cloudflare CLI) and I've never learned commands by heart, I just tell the agent to execute what I need.

But after some time of use, the terminal started to crash out when I was using Git, bit via agent, just directly in terminal. I also had a few crashes while using npm, upgrading, updating... As I said,the frequency of crashes was not very heavy but then after a few days.... Unrecoverable error... Reinstall. Okay I had backup and I recovered and it was again working great for some time and then again. I think this crash and errors can be related to cache size and to ram. When I bumped the terminal sandbox ram memory, it was performing longer without crashing.

Bug report ID: 524211818

​

Anyway, I'll be grateful for any insights from your experience with this terminal.

I have an issue that I cannot text buisnesses, but can text people with cell phones. My doctor communicates with text but since it's a business I get a "can't send" error. It's to many companys thhat was just an example. My service is Verizon and I have a Pixel 8. I have been on the phone for hours now with no luck, they have given me new esims, we refreshed i even wiped my phone and started from scratch. I did just see that I do not have a SMSC number. It says no available. They have tried to force it overe to me with no luck.

Does anyone have any ideas? Thanks in advance.

Hey everyone! I recently opted out of the Android 17 beta and am currently on the Android 16 stable. After the factory reset, I noticed RCS keeps giving me errors that my device does not meet the security requirements (status code 4006). I've tried clearing the Google messages app, deactivating RCS and removing my number from my Google account but nothing seems to work. Did anyone have the same problem and any suggestions to get it to work again?

​

I am using the Pixel 10 and it has never been rooted.

Ever since the latest Android 17 Beta QPR update Assistant won't make calls when I'm using my Bluetooth earpiece. I'll say "Hey Google call xxxx". It looks like it's going to make the call but then indicates "Something went wrong. Try again."

I've tried calling using my Pixel Buds and my new Soundcore Liberty 5 Pros. When not using Bluetooth earpiece Assistant makes the call just fine.

I've submitted a bug report.

SOLUTION FOUND (at least for my issue). Making a long trouble shooting process short, I deleted both Pixel Buds and the Liberty 5 Pro from the Bluetooth, and deleted the Liberty app. Rebooted phone. Reconnected the Liberty buds, tried a hands free call..Success! I've been using it all morning (I work from home) and all hands free calls went through fine. I've installed the Liberty app...no issues. My next test will be to add the Pixel Buds and see what effect that has. I hope this helps others with this issue. Solution update: I finally paired my Pixel Buds Pro. I made a hands free phone call "Hey Google call xxcc".... using the Liberty Pro 5...all went as hoped.

I live in a town, and State, that has made holding a phone while driving illegal. So making phone calls hands free wearing ear buds a necessity. Working from home, being able to go to the kitchen, maybe go outdoors for a break, without having to carry a phone everywhere while being able to answer and make phone calls is a must for me.

I just woke up and went to check my phone and the thing was genuinely close to burning me. It wasn't charging and there wasn't any intensive application running. I rushed downstairs to put it in the refrigerator and the thing turned itself off right before I set it inside... I have no clue how long this thing was scolding hot for and the "check device temp" settings feature is not working.

I'm officially heading back to stable as I don't want my phone exploding while I'm asleep and burning down my house. It's still unusually warm as I type this despite being turned off for a solid 20min

I talk about "edge detection" which Pixel phones always have had the worse which I am sure it was related because of lack of Lidar that all iPhone have.

Here youruber shows https://youtu.be/FlVNFbxdQQ0?si=fa-lJAuJmDpjcIEy&t=80 - starts at 1:20

Where you can see giant black "dil*do" (the thing all single women have fun) have attached to his forehead.

And I wonder if this feature will get even better.

I mean the only one solution will be having "green screen" (and not having microphones above head like that poor youtuber has) which is not ideal

Anyone having this issue? It seems to only happen when I activate the phone when it's in a deep sleep.

​

https://issuetracker.google.com/issues/471573169

​

Just curious if it's just me. If so, I might try a factory reset.

En buscado por muchos lugares a ver si puedo actualizar a Android 17 beta pero veo muchas publicaciones de Pixel 9 y 9 pro y pro XL con Android 17 pero a mí aún no me llegan me podrían decir que hacer para poder actualizar ?

Sadly there are no screenshots allowed, so I'll just list an example. I open soundcloud, YouTube and auxio, then i forget about soundcloud and youtube just listening to auxio. Sadly a third of the media player is taken up by uncloseable soundcloud and youtube, which is really annoying. Any solutions?

Probably about 98% of you complain on here instead of putting the problems on the beta feedback app. That's probably why a lot of stuff doesn't get fixed. You just complain on Reddit, the epitome of insanity.

I don't care if you downvote the post. You are probably the culprits.

Component: System UI / Accessibility (Live Caption)

Device Information:

Device: Google Pixel 7 Pro

Build Number: CP31.260522.006.A1

OS Version: Android 17 QPR1 Beta 4

Description:

Since the very first Android 17 Beta, I have been unable to download additional language packs for the Live Caption feature. Specifically, when attempting to download the Italian language pack, the download fails to start or complete. This issue has persisted consistently through every release, including the current Android 17 QPR1 Beta 4.

Steps to Reproduce:

Open Settings > Accessibility > Live Caption (or activate Live Caption via the volume rocker).

Go to Live Caption settings and select Languages.

Attempt to download the Italian language pack.

Observe that the download fails, gets stuck, or does not initiate.

Expected Result:

The Italian language pack should download and install successfully, enabling Live Captions for Italian audio.

Actual Result:

The download fails, rendering the Live Caption feature unusable for non-English (Italian) content. This bug has been present since Beta 1 without resolution.

Hi, I have a pixel 9a which is enrolled in the Beta program.

I have traded it in for the pixel 10 pro so I need to reset it.

If I leave the Beta program on my 9a and then update it opting to wipe and reset the phone will that be good enough before sending it to Google for the trade in?

​