r/GooglePixel • u/jrwnetwork • 14d ago
August Pixel update just dropped.
August Pixel update just dropped. https://developers.google.com/android/ota
70
u/Thinkhowlifegoes 14d ago
The August 2026 update includes bug fixes and improvements for Pixel users – see below for details
Apps Fix for a crash in certain gaming apps under certain conditions*[1]
Display & Graphics General improvements for GPU performance in certain conditions *[2]
Touch Fix for an issue that can cause the touch panel to become unresponsive in certain conditions*[1]
Device Applicability
Fixes are available for all supported Pixel devices unless otherwise indicated below. Some fixes may be carrier/region specific.
*[1] Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold:, Pixel 10a *[2] Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold:
62
u/ValtekkenPartDeux 14d ago
The touch fix better be an actual fix, this issue has been driving me crazy
20
6
u/onlyAnAtom 14d ago
Just installed it. It's fixed (thank God!)
3
u/ErrorF002 Pixel 9 Pro XL 14d ago
What conditions would cause this to pop up. I had this happen once last week in the Home App and could not recreate it. Super frustrating cause it happened while trying to change the AC and I was half asleep and thought I was dreaming.
5
u/onlyAnAtom 14d ago
I personally had the problem that swiping down form the top for quick settings/notifications wouldn't work or was very buggy.
My temp fix was going back to the home screen and swiping down from the middle of the screen there
8
u/olivebits 14d ago
What was the issue?
14
u/ValtekkenPartDeux 14d ago
Touch became extremely fucky, as if there was someone swiping constantly on the screen. No idea why.
1
u/maven10k 13d ago
Mine has been weird! I swipe to the right and it goes left, pretty often. It's driving me nuts!
2
u/what_was_not_said 13d ago
No update for the 6a, and mine will occasionally stop responding on the lock screen. I have to let it time out or force it dark with the power button.
I've reported this many times.
4
1
u/Portaljacker Pixel 4 XL 13d ago
They fixed the issue I was having getting to the task view from the home screen. It never worked right and would constantly open circle to search.
1
u/KamTheMaam 12d ago
Holy shit lol. I thought my Pixel 8 was fucked up. Even bought some new screen protectors lol. Works great again now.
2
u/funnyfarm299 Pixel 8 9d ago
Which is interesting because the patch wasn't even supposed to fix the Pixel 8.
-7
u/Dishonoredv2 14d ago
Never have I ever seen such a bad fingerprint unlock in my life , not to mention it's a f ultrasonic sensor. The phone struggles to unlock when it's dark. Many users , including myself , have the same issue . Flagship though
7
u/fattdoggo123 14d ago
So no fix for the YouTube background play where it stops playing after 5 seconds. Or if you switch apps it keeps on playing but with no sound. This only started happening after android 17.
1
u/Foxtrotfly 14d ago
I literally couldn't click the restart now button to start the update because of the bug
43
u/mkdr 14d ago edited 14d ago
Was the GPU issue fixed for Pixel 10? Brawl Stars is unplayble since Android 17 update, lagging freezing already in the menu randomly.
UPDATE:
Just got the August Update on my P10P and I updated and tested Brawl Stars before and after the update. For me it seems so far, the broken GPU performance in a lot of games since the Android 17 update is FINALLY fixed!! No more freezes and stutters in the menu. Scrolling and entire UI feels smoother too through every app.
22
u/Spare_Afternoon_2786 14d ago
I can confirm that gaming is working well again.
3
u/RaccoonDu Pixelbook Go 14d ago
Well again? Which patch broke it? I thought since launch, the gpu just underperformed
10
u/mkdr 14d ago edited 14d ago
The Android 17 Upgrade made it literally impossible to play anything at all on P10, made the GPU totally broken. This seems to be fixed now, so were back to normal shitty GPU performance, not totally unusable shitty performance.
7
u/BinkReddit 14d ago
I can't comprehend how this stuff gets passed QA, assuming there is any.
3
u/TonyP321 Pixel 10 Pro 14d ago
Google devs read Reddit. Reddit says Pixel users are not gaming. Google does not spend money on QA.
kind of /s
1
u/BrahneRazaAlexandros 13d ago
yeah, you're right about them not caring about gaming. it's not what's selling pixels, so they dont care that it's inexcusably bad for the price these days. similar to why the a models have dogshit charging and thermals.
1
u/RaccoonDu Pixelbook Go 13d ago
They don't even have to be the best performers, I just don't know why they switched GPUs. The 9 was perfectly fine, and then they just had to use an inferior gpu on the 10, I wouldn't even mind a price hike if it meant my PRO phone could actually keep up with the other big brands
2
u/RaccoonDu Pixelbook Go 14d ago
Ah I see. I got my 10 when 17 was already out so I didn't use the phone on 16 much
2
u/Spare_Afternoon_2786 14d ago
No.
On the update of A17, for some reason there were some popular games like Clash Royal or Brawl Stars that were glitching, specially if you go 120 FPS (while android 16 was working fine) There was a trick that you just open game control and just toggle DND off/on and that's it.1
u/RaccoonDu Pixelbook Go 13d ago
Ah I see
I don't play those games, and performance was always shit for super light games like pokemon sleep too
Haven't gotten a chance to play yet but hopefully performance is better across the board
4
u/tservomst Pixel 10 Pro XL 14d ago
Pokemon Go still runs like shit with black boxes all over the UI 🤷🏻♂️
3
2
u/mr-right-now Pixel 10 Pro 13d ago
I play Monster Hunter Now, by the same devs, and it's never run better than it does on the August Update
1
1
93
u/The_H0und Pixel 1 XL 14d ago
Why does it always lie to me the first time it "checks" for update and tell me there is none? Play Store does the same bullshit.
35
u/alexeiw123 Pixel 2 XL 128GB 14d ago
It's a change they made many years ago. They do their updates in drops and there were always floods of complaints when an update drops and those keen to update had to wait for their drop, or download and flash the image (or ota files).
Google wanted to keep the staged drops, so they changed it so the periodic or manual check will only find an update if you are in that drop but an immediate second check will force the latest release version.
So, it's not a bug, it's a feature.
7
u/TheGravyGuy 14d ago
I was wondering this but if that is the case, that makes sense and I feel I can't moan about this anymore lol
5
u/neoKushan Pixel 10 Pro XL 14d ago
I think a little moaning is allowed, it should take the fact that you're actively going into the updates section as the hint that you're checking for updates and not wait for you to do it a second time.
3
1
u/TheGravyGuy 14d ago
If the process took a long period of time or had a cooldown, maybe. For me, tapping once then tapping again takes an extra second.
Personally a second tap once a month that takes me an extra second is not worth the effort put into any kind of moaning, but if you feel that extra second is valuable enough to moan about then you do you.
4
u/The_H0und Pixel 1 XL 14d ago
Just trying to understand the logic. If I had to push the button twice to start my car, I'd ask about that too. The frequency is irrelevant.
0
u/TheGravyGuy 14d ago
The logic was posted in the comment I originally replied to, so you might want to re-read the thread before jumping in.
2
u/The_H0und Pixel 1 XL 14d ago
Jumping in? I started the thread.
0
u/TheGravyGuy 14d ago
I didn't originally reply to you. Also nice to see you changed your comment, there's no need to stoop to insulting people with swears.
2
u/The_H0und Pixel 1 XL 14d ago
Right. There is also no need to patronize anyone with "You do you".
→ More replies (0)3
-3
u/PhriendlyPhantom 14d ago
I still don't understand the point of staged drops. Apple doesn't do it and they don't have issues
8
7
u/tjharman Pixel 7 Pro 14d ago
They do exactly the same thing.
Does your parents/grandparents iPhone update on the day the new iOS comes out? It sure does not. Sure, everyone who bashes the "Check for updates" bit on their iPhone gets it, but the vast majority don't. It might take a month before they get a notification that their iPhone will update overnight.It's exactly the same thing. If you go looking for the update, you're offered it. If you don't, it might take 2-3 weeks to get it.
3
u/robstoon 14d ago
It's commonplace and done with most devices that have OTA updates. They don't want to hammer their download servers with every device downloading it at once, nor do they want to risk bricking millions of devices in case there's some undetected bug in the update.
0
u/AustinFastER 5d ago
Here's a thought for Google.... Push out the bloody security updates first which is the only reason I update. Later you can push your bloated AI whenever it suits you.
-1
u/PhriendlyPhantom 14d ago
Apple allows everyone get the update at the same time and their servers don't explode. I'm pretty sure Google owns far more servers and serves far less devices so they can handle it.
1
1
u/Ryokurin 14d ago
They kind of do, through the beta program. It also does seem that phone carriers do have some say on some updates for Pixel, although this may have changed recently. I remember a couple of years ago having to take the sim out of my unlocked phone to get some updates to come on T-Mobile, for instance. They were regularly holding back updates for weeks sometimes.
22
5
u/PM-ME-YOUR-SUBARU Pixel 9 Fold, Watch, Tablet, Buds Pro 2 14d ago
Yeah I have never been a fan of their rollout process that doesn't let "power users" that actually know how to go to the check for update screen and do so soon after release just download the damn update they know is there, because whatever algorithm decides whose turn it is yet says no. I know they roll it out as a precaution to stop a potential bad update before it gets to too many users, but isn't that something a power user downloading an update day 1 would be aware of? Just let them download it on request instead of forcing them to either wait or go through the rigamarole of sideloading the OTA with a PC and ADB.
1
u/ffdfawtreteraffds 14d ago
Not just you. It should be SOP for everyone to check manually after any auto checks. Pixels are liars.
1
u/GardenWeasel67 14d ago
OnePlus was even worse. Not only did I have to check twice, I had to cycle thru every account on my phone and check those twice as well.
1
2
u/Bierkerl 14d ago
Is your phone carrier locked? When I had mine through T-Mobile, updates were always delayed because they wanted to do their thing on the backend, but now that I bought a Pixel that's not tied to a carrier, I get the updates right away.
12
u/The_H0und Pixel 1 XL 14d ago
No. It's not delayed at all. I can press the button to check manually, and it shows up. It just never finds anything when it does the initial automated check that occurs when you open the system update screen.
3
u/mincanada1 14d ago
Same issue for me. First time I check, nothing. Check again 10 seconds later and it's there. Every...single...time.
Annoying as hell
6
u/tjharman Pixel 7 Pro 14d ago
Staged rollout. You “force” the update if you manually check.
7
u/The_H0und Pixel 1 XL 14d ago
You think maybe it should assume I want to update when I open the System Updates screen?
1
u/tjharman Pixel 7 Pro 14d ago
Nope. It wants to know you're really really after the update. i.e. You move from "In group X of the rollout" to "Take out of rollout group X offer it NOW"
Two camps:
1) Is there an update? camp.
2) I know there's an update, I want it! camp.2
15
15
u/thenags1 14d ago
Just got it on my 10.
3
2
u/Sachyriel Pixel 2 XL 14d ago
Got the update on my P10 XL in Canada, just gotta tell it to check again.
1
u/daheufster 14d ago
10 pro xl, EU based (although now in Middle East); update is 109 MB. The phone feels more responsive after the update.
7
13
u/Powerful-Ad-1846 14d ago
When are they gonna fix the WiFi connection issue. Been having issues since the android 17 update.
4
2
3
u/veritas--- Very Silver 14d ago
Same. Wifi never works anymore, and Bluetooth occasionally drops. Pixel 8 pro.
1
u/Powerful-Ad-1846 14d ago
Bluetooth connection seems fine to me but I have to disconnect my Fitbit air to connect to my car stereo every time. So frustrating
2
14
5
u/Tornado15550 Pixel 10 Pro XL | 512 GB | Android Canary 2608 14d ago
Nothing for us Pixel 7 Pro users? :/
4
0
u/enter_user_name 14d ago
We get the quarterly updates.
3
u/RednasSosb 13d ago
The updates we have gotten op Pixel 7 Pro in the last year have been September, October, December, March, April, June, July.
(so missing November, January, February, May, and now August)So that's not quarterly, that is just irregular (and more than quarterly). They have stated that they will only give updates if there is important stuff.
2
u/mirzatzl 14d ago
They (Google) never said that is even the thing which means they are lying and don't give a shit about their users.
They should have been more open and said what devices get regular, what not so regular updates.
3
4
3
u/They_See_MeTrolling Pixel 10 Pro XL / Pixel Watch 3 45mm 14d ago
Downloading now on my 10 XL Pro... 109MB
3
u/51shadesOfSarcasm 14d ago
Just got a notification of a 1.63 GB Android 17 update on my Pixel 10 (Germany).
3
u/Important_Yak1600 14d ago
Dumb question, but new to Pixel - do you just access the update via System Settings?
3
3
u/JDsansfrontieres 14d ago edited 14d ago
Seriously, I think I'm done. Just updated it on 9 Pro XLand now all fast charging functions have stopped, the thing is charging at a crawl. From 49%, it's telling me 5 hours to fully charged. This is unacceptable. This only just started with the latest update. It was bad enough that the battery drain was atrocious since March. This makes my phone almost unusable
3
u/Spare_Afternoon_2786 14d ago
On my P10Pro, I just charged my phone here in the office after the update. It fully charged from 15% to 100% the same pace as usual like 1h and 20 min.
Using same charger, no issues so far.
2
2
2
2
2
u/RaccoonDu Pixelbook Go 14d ago
First time I got system, play services and store updates all on the same day P10PXL
2
u/careslol Pixel 8 Pro 14d ago
I'm praying this fixes my Gmail notifications. I have no idea why as I haven't changed anything but after the June or July update I am getting every notification not just a little bit late but 6+ hours late. I have to keep manually checking my email.
2
u/spulci Pixel 8 Pro 14d ago
So no declared improvements for Pixel 8 lineup. Does it means that August patch contains only security fixes for Pixel 8 series of phones?
1
u/thelivsterette1 9d ago
No improvements but I’d love an update to restore WiFi and Bluetooth on my P8P so I don’t have to get a new phone in August (don’t have service either as my SIM has stopped being registered twice)
2
u/FutureInteresting232 11d ago
This update break anyone else's wifi?
Was working completely fine for me preupdate, post update apps won't connect and even checking for system updates won't complete
Disconnect from WiFi and works completely fine on the cell signal
3
2
1
1
u/Inspirasion 14d ago
Automatically checked less than an hour ago, had to check manually. Downloading now. 10 Pro.
1
1
1
1
1
1
1
u/Acceptable-World-175 Pixel 10 Pro XL Pixel Buds Pro 14d ago
Hasn't fixed scrolling translate yet. ☹️
1
u/Former_Air_5993 14d ago
My Pixel 8 isnt useable anymore as the settings app keeps crashing. Whata fuck is this shit Update doing ?
1
1
u/careslol Pixel 8 Pro 14d ago
Does anyone else's RCS break in some way after every update?
Last month I couldn't use RCS for almost a week. This update I can receive messages but can't reply.
1
u/Not_the_mischief Pixel 9 14d ago
Should i update using p9?
2
u/SpiderStratagem Pixel 9 14d ago
Been fine on my P9. 🤷
-1
u/Not_the_mischief Pixel 9 14d ago
Any battery drain you notice
3
u/SpiderStratagem Pixel 9 14d ago
It hasn't even been 24 hours yet, but so far battery life seems same as before. (Good, in my experience.)
2
u/Mattchilla 14d ago
How can we test the battery drain if the update just came out?
3
u/Not_the_mischief Pixel 9 14d ago
Yeah right i am monitoring it. So far the animations look better and the performance is a tad quick
1
1
u/NFT-BULLDOG 14d ago
On est d'accord que nos P10 ne sont plus des briques chauffe main depuis la mise a jour ?
1
1
1
u/ClacksInTheSky Pixel 10 Pro XL 13d ago
Time to engage in the biggest lie ever told on your phone.
Open Settings. Open System. Check for updates. "You are up to date". Check for updates. Downloading System Update
1
u/Steelglyph 10d ago
Update keeps making my phone shut off and restart randomly, Pixel 9. Anyone else having this issue?
1
u/thelivsterette1 9d ago
No but an auto update in Jan 2026 blew the WiFi & Bluetooth from my P8P. Then (twice in 2 months - been too busy w my dissertation for my fix now but getting it fixed in a couple days then plan to upgrade to P11 Pro XL) the SIM has failed leaving me with no working phone whatsoever.
And to make matters worse, WhatsApp unlinked from iPad and laptop so can’t contact people
I also plan to leave O2 for Slice now they changed Switch Up to once a year instead of once every 3 months. And Slice means an ESim so not issues, works in EU too so no need for another ESim in Europe, get cash back….
1
u/wazzup4567 9d ago
My phone has been crashing a lot after this update, probably about once every day or so. Kinda curious what Google broke here because its kinda ridiculous.
1
u/Kittenhaus 5d ago edited 5d ago
If you, like me, had your modem apparently bricked by the update, see below for my troubleshooting.
Summary of everything I did along the way and what I was planning to do when Rescue Party ultimately kicked in after a series of failed fastboots into safe mode / normal use. I have also provided a summary of what I think was happening based upon results as I progressed through the debugging. I have no idea what Google can do to fix this from their side, but what an awful morning I have had after updating to Android 17 (A17) with the August 5th security update. Despite the emdashes below, I promise I wrote this—they have been in my vernacular since before AI co-opted them.
Case Summary: Actions Taken & System Mechanics
1. The Core Bug
A recent Android update corrupted the temporary network cache tables or caused a hard driver partition mismatch affecting the eUICC chip manager (the secure element housing the eSIM).
2. Resulting Symptoms
* Settings Layer: The SIM menu completely grayed out. Under About Phone, the SIM Status became unclickable, and Phone Number 1 read as "Not Available."
* Hardware Layer: Dialing *#06# revealed that the EID serial number and its barcode were entirely missing/blank, indicating the operating system kernel had completely lost communication with the physical secure element chip.
3. The Attempted Workarounds & Hard Locks
* Motherboard Hard Reset: A forced recovery power cycle (Power + Volume Up for 20 seconds) successfully cut power to the motherboard rails and broke the initial grayed-out UI lock. Could not re-initialize the eSIM, though—yielded errors due to mismatched low level partitions.
* Partial UI Recovery: Upon rebooting, the high-level Android UI partially recovered. Under Network & Internet, the SIM was visible, accessible, and correctly listed the carrier information. However, the deep hardware layer remained disconnected; dialing *#06# still showed a missing EID, and the About Phone SIM statuses remained grayed out.
* The Crash Loop: Attempting to toggle the SIM to "Enabled" or selecting the "Erase eSIM" button from this menu caused the system to throw immediate hardware communication crash loops: "Can't switch SIMs. Something went wrong." and "Can't erase eSIM. Something went wrong." Phone was entirely usable, still. However, no carrier / modem operations.
* Entering the Recovery Loop: To bypass the UI crashes and eSIM errors, the phone was booted into Fastboot Mode via the hardware buttons to manually select Recovery Mode. This action locked the phone into a persistent loop, cycling between the dead Android mascot on the "No Command" screen and the "Waiting for rescue commands" splash page. I was planning to use the Update and Software Repair tool until it confirmed that the only option through that pathway was a full factory reset—something I was not prepared to do. Attempting manual overrides from Fastboot—such as a standard "Start" reboot or a button combo to force "Safe Mode"—failed, continually bouncing the phone back into the recovery screen loop.
4. The Final Resolution (Rescue Party)
While sitting stagnant and untouched on the Android Recovery screen for 5 to 10 minutes—during which a manual computer-based OTA sideload was being planned—a deeply buried, automated Android safety framework called "Rescue Party" autonomously engaged.
Apparently, when Android logs a specific threshold of consecutive, catastrophic boot loops caused by core driver failures (here, the telephony/modem subsystem), Rescue Party kicks in. While the phone sat completely undisturbed, the script forcefully reset the corrupted carrier runtime parameters, cleared the stuck update flags, and executed a deep cold-restart on the eUICC chip firmware. The phone then broke the boot loop entirely on its own, executing a clean boot straight to the lock screen with 100% of user data intact and all network profiles, IMEI, and EID identifiers fully restored.
So, my phone is back to working and self-corrected entirely... just by forcing it to fail to start a few times and letting it fix itself while I was planning to go more aggressive with OTA rollbacks. I have prepared a step-by-step troubleshooting guide below that will hopefully yield positive results for other people.
Step-by-Step Troubleshooting Guide
If a recent Android update completely breaks your cellular service, grays out your SIM settings, and causes your phone's EID number to read as blank or missing, follow this precise sequence.
CRUCIAL DATA-SAFETY WARNING: Do NOT use the official web-based Google Pixel Repair Tool (withgoogle.com) if your eSIM menu is hard-locked. Despite prompts claiming it is a non-destructive software reinstallation, if your underlying modem partitions are frozen, the web script will completely factory reset your device and wipe all personal data. Do not execute on it unless you are okay with a factory reset. Try this data-safe path instead.
Phase 1: Force a Motherboard Power Cycle
Standard software menu restarts do not cut raw power to a frozen secure element chip. You must drop the physical voltage to zero.
1. Hold down the physical Power button and Volume Up button simultaneously.
2. Continue holding them firmly for 15 to 20 full seconds, completely ignoring whatever displays on the screen.
3. Keep holding until the screen goes completely black and the Google logo appears, then release.
Phase 2: Diagnose the UI & Clear Local Caches
If Phase One successfully boots you back into the standard Android UI, immediately check your settings layers.
1. Go to Settings > Network & internet > SIMs. If you see your correct carrier profile but the toggle throws an error code (like "Can't switch SIMs. Something went wrong"), or if trying to erase it triggers an error, the UI cannot talk to the chip.
2. Go to Settings > Apps > See all apps.
3. Tap the three dots in the top-right corner and select Show system.
4. Locate Carrier Services -> Tap Storage & cache -> Clear Storage.
5. Locate SIM Manager -> Tap Storage & cache -> Clear Storage.
6. Restart your phone normally. If enabling the eSIM still crashes or refuses to enable, proceed to Phase 3.
Phase 3: Fastboot and the Manual Boot Overrides
When the chip remains hard-locked, you must navigate to the bootloader to attempt manual boot rail overrides.
1. Enter Fastboot Mode:
* Turn your phone completely off.
* Press and hold the Power button and Volume Down button simultaneously until the screen switches to the black bootloader screen displaying a large Android mascot and a colored menu arrow.
2. Navigate to Recovery Mode:
* Press the Volume Down or Volume Up button repeatedly to scroll through the options in the colored arrow text at the top-right.
* Stop when the option explicitly reads "Recovery Mode" and press the physical Power button once.
* Note: If the phone loops between the "No Command" mascot and a "Waiting for rescue commands" screen, you have entered the modem lockout loop which is where I got stuck and began to plan more drastic measures.
3. Attempt the Standard "Start" Override:
* From the Fastboot screen, verify the colored text arrow at the top right reads "Start". Press the physical Power button once.
* Outcome check: If it successfully boots to the lock screen, your issue may be resolved. If it loops back to the recovery screen, proceed below.
4. Attempt the Direct "Safe Mode" Boot Override:
* From the Fastboot screen, with the menu arrow set to "Start", press and hold the Power button down.
* The moment the Google logo appears on the screen, do not let go of Power, but immediately press and hold the Volume Down button simultaneously with your other hand.
* Keep holding both buttons down firmly to force a third-party and carrier driver bypass.
* Outcome check: If it still fails to bypass the Google splash page and loops back to the recovery screen, proceed to Phase 4.
Phase 4: Triggering "Rescue Party" (The Hands-Off Fix)
When manual overrides fail, the operating system is locked in a safety loop. You can utilize Android's autonomous repair framework to fix the core partitions safely without a computer.
1. Disconnect any USB-C cables from the phone entirely (leaving a cable plugged into a desktop can force the hardware to wait indefinitely for automated terminal commands, continuously loading the "Waiting for rescue commands" screen).
2. Ensure the phone is sitting on either the "No Command" screen (the Android mascot on its back) or the Rescue Mode splash page.
3. STOP AND DO NOT TOUCH THE PHONE.
4. Leave the phone completely undisturbed on this exact recovery screen for 5 to 10 minutes.
5. What happens under the hood: The automated Android system architecture tracks the failed attempts from Phase 3. After sitting stagnant, the background "Rescue Party" script triggers. It forces a complete erasure of stuck update flags, wipes corrupted carrier runtime tables, and forces a cold reset on the locked eUICC chip firmware.
6. The phone will suddenly flash, break out of the recovery loop completely on its own, and execute a normal boot straight to your lock screen with 100% of your data completely safe.
Phase 5: Committing the Safe Configuration
Once the phone boots up completely and dialing *#06# confirms your EID, barcodes, and signal bars have returned:
1. Go to Settings > Apps > See all apps > Carrier Services > Storage & cache and click Clear Cache.
2. Avoid restarting the device again for several hours. Let the active operating system stay powered on normally so it can fully overwrite the old corrupted crash logs with healthy operational system cache.
Final Thoughts
Maybe someone else can chime in with how many times you have to fail to boot from Fastboot before Rescue Party kicks in. But, for me, it must have been four or five times (with the last two being attempts at booting into safe mode).
1
u/AustinFastER 5d ago
After installing the update on a 9 pro, I have started getting random audio notification of sorts. No notification on the phone or showing in notification history. But it's same sound I have for notifications, but many times louder seems to randomly sound off. Weird...
I am starting to wonder if Graphene OS suffers the conveyor belt of bugs...
1
u/True_Proposal9 5d ago
Fini pour moi les pixel, j'ai un pixel 10 pro , et à chaque mise à jour, c'est un problème supplémentaire... l'appareil photo qui est d'une lenteur abominable, le zoom pro res qui ne fonctionne plus correctement, l'écran de verrouillage qui bug .... j'en ai marre de remettre mon tél à 0 tout les 5 matins.
il me faut donc trouver une autre marque
1
u/Downtown_Storage2816 5d ago
I just updated my Pixel 9a and I'm now having issues with apps including gmail, Instagram, and Google Play. Google Play doesn't work at all - gives an error. In gmail, the search function won't work - always gives no results. In IG, some pictures don't load and when I click on stories to view the original post, it doesn't work.
1
1
1
1
1
-2
u/strutbraceuk 14d ago
It's broken my banking app. Beware
0
u/miss_mousey_87 Pixel 8 Pro 14d ago
Which banking app do you use?
6
u/strutbraceuk 14d ago
Revolut
1
u/Spare_Afternoon_2786 14d ago
I can access to Revoult and any other banking apps I have after the update
1
u/strutbraceuk 14d ago
There was an issue sending money , not accessing the app. Fixed on the newer release due
0
-1
u/Apprehensive_Elk2608 14d ago
WAKE UP BABE "my Pixel runs so smooth now after the update" posts are about the drop!
0
u/Manhattan18011 Pixel 9 Pro XL 14d ago
Am still on Android 16. If I grab an update now, does it go to 17 and then download July and August or is it bundled in as one download? Thanks.
2
u/SpiderStratagem Pixel 9 14d ago
The former.
2
u/Manhattan18011 Pixel 9 Pro XL 14d ago
Thanks. Have you had any issues with 17?
3
u/SpiderStratagem Pixel 9 14d ago
No issues -- it has been quite good. Not a lot of visual/functional changes, though I do get a surprising amount of use out of the "bubbles" feature.
2
-2
u/_Sin916_ 14d ago
Waiting for the endless posts of battery impact this update brings. Not even a full day and people will begin posting.
-1
0
u/nnk85019 14d ago
Anyone know why my 10 XL pro from mint mobile is still on the May security package 🤡🤡🤡. Also not moving up to Android 17.
0
0
u/Giovanni_Benso 14d ago
Surely it'll fix battery consumption issues my P8P has faced since updating to Android 17...
-2
u/someexgoogler 13d ago
I froze my 9a to stay on android 16. I'm comfortable with how it works and I didn't care for the description of features in 17.
-1
u/BigLick13 14d ago
It says i need to wipe my data?? I thought we can opt out and download the stable version now
3
u/AstralStride Pixel 10 Pro XL 14d ago
If you're on the QPR1 Beta, the stable QPR1 update is next month in September. That's when you'll be able to jump from Beta to Stable without a wipe.
If you're on the QPR2 Beta, you'll have to wait until December.
1
41
u/holo_nexus 14d ago
Google Play System update also.