Develop Bugs

GPS usage crashes phone.

I applied the OTA update and every time an app tries to use GPS my phone restarts. The GPS icon blinks about 3 times then the phone turns off. I disabled GPS and still have 'find by WiFi' on and Google Maps gets pretty close. I also did a master reset and formatted my SD card. Last ditch effort I updated my PRL and profile. No dice.
Other thoughts: Amazing phone and I want 2.2.
Sent from my PC36100 using XDA App

I believe (using the GPS for 2 days with no crash) I was able to fix it by going into the bootloader [power button and volume down] and selecting "clear storage". My guess is that doing a master reset from withing the phone didn't clear everything.

Exchange your phone
I have had the same problem. A week ago monday after Sprint pushed OTA update phone worked even better than when I first purchased. For two days that was, I recieved a gmail, opened through notifications and from that moment on my phone has become a nice musical lit-up papper weight. I had a Hero before and NEVER had a crash or reboot. My Touch Pro was another story. I have done now 3 hard resets. After number two I only installed updates to Sprints bloatware(sprint nav) and google branded apps. Two days later I recieved a google-talk message and uppon opening it, it all started over again. I can reproduce this rebooting by launching any gps software with gps set to on. Sprint nav not only causes reboot but wipes credentials that you enter when you first launch app. I can launch gps programs if the GPS settings are ALL turned off(both switches). Of course I have to log into Sprint Nav again after every crash. I thought this was fixed after my last hard reset, I have not downloaded anything (no root)or installed any apps since my last reset. I just got past my 30 day but I am going to RAISE HELL later today, obvously this is unacceptable in a new phone(flagship), SPRINT and HTC were notified last week. They did take notes but they are going to try to get me to submit a claim rather than exchange. Neither Sprint or HTC seem to know shi* about this rebooting issue. Obvousily nobody checks sprint user forums. I urge anyone with crashing/rebooting to take back for exchange. Do not waste time trying to fix yourself. I fixed myself 3 times only for the random rebooting to come back within 48 hours. No 3rd party apps other than Sprint(I was afraid to download anymore). I won't even talk about the screen splitting from the base of the phone, I doubt they know anything about this issue either. So my state-of-the-art smartphone is now a 4g less, crappy 3g service, non functional gps, musical (splash screen) papperweight. This was the only phone that I have waited very impatient for and this whole experience has left a VERY bad taste in my mouth. They even screwed the launch of this device. Best Buy and Radio Shack were the only ones taking preorders and Sprint screwed the activation and provisioning up the day of launch as well. I wish I could hate this phone, I would terminate service with Sprint after this experience.

im runing OMJ 1.6 which inclues lastest OTA and and last night i opened maps it asked me to turn on gps and when i did i had constant force closes had to take the battery out to make it stop, couldnt do anything because everytime i did force close it reloaded the system but force close again.

I have had this issue since I got my phone June 5, anything that requires the gps shuts down the phone. I have been waiting for a replacement phone from Radioshack for 3 weeks. I have tried resets, updates with no luck. A local Sprint tech looked at it and told me he thought it was a hardware problem with my phone.

UPDATE
This morn I took to a Sprint repair center. After looking at the device she said that there was water damage and that the stickers had turned red. She also said she found the GPS reciever loose and soldered it back. Funny thing is is that me EVO has never been dropped or near water except for the spray that was used for my invisasheild. I was extremely careful about the aplication, in fact I screwed up because the first application wasn't wet enough. Also I have a PRO2 and Hero as well and as you prob know the batteries are interchangeable. As a result I am constantly swapping batteries because my EVO loves to kill batteries pretty quickly. I think I wold have caught the stickers turning. Also with all the problems I know I have looked to see if there was water damage. Of coure she never produced the stickers and they have now been removed. As I right this right now I am waiting for my EVO to reboot again. NOW I HAVE NO SOUND AND HAD TO HARD RESET MY PHONE! Oh and the repair person said I had too many Apps as well. I brought the phone in this morning with its default settings and apps. If there are too many apps than thats your fault not mine. I am soooo pissed about this whole experience, it's got to the point that I am actualy starting to laugh because Sprint seems so incompetent.

This afternoon I was showing my phone to a client and I launched the normal GPS apps, Google maps, Navigation, GPS Status and CarLocator. As soon as I enabled geotagging on my phone crashed/rebooted. To fix it I went to the bootloder and cleared the storage so that everything would go to stock settings. So far I haven't had a crash yet. I can handle not having geotagging as long as everything else works. Though it is a great feature to have .

Now my phone restarts even though geotagging is off. Anyone know of I can reflash my Evo though the HTC rom manager on a computer? I think putting the default rom would narrow it down to hardware or software.

I did hard-reset on Friday morning and installed all of my apps and then some, but did not install wheatherbug elite which worked fine on my Hero and worked fine on EVO for three weeks prior to Sprints OTA. So far so good,wil post results in fuure. No reboots so far and its been over 38 hours. I read on another forum that WB does not release GPS even after uninstall. Will post results in a day or two.If this is the fix by sprint/htc than give me back my phone with no updates!

???????
Ok, right after I posted my last post I recieved a phone call, durring wich the battery died. I replaced battery with a fresh one, powered on, launched sprint nav, and it rebooted. **** so much for the weatherbug idea..... After reboot I launched google maps, again reboot. I have not installed any apps since noon friday. I have played around non stop with ALL the apps and settings and have not changed anything since friday afternoon. Its 1:15 Sunday morning and nothing has changed on my phone for around 36 hours! Is this a software problem or hardware problem? Software problem means I will wait untll sprint fixes their update wich seems to me caused all this or is it a hardware issue that I need to figure some way to replace even though no EVO's can be found?

Spoke to HTC this morn, htc says that this is a known issue affecting some of their customers and that the carrier (Sprint) should have replaced it already. Even though I bought at Radio Shack. Because sprint has acted so unbelievably incompetent HTC is going to send a new unit in 4-5 days. So anyone having GPS problems and did the OTA should have their phone replaced. Those are not my words but HTC's. Also she explained that my first call for help should be HTC not Sprint. She claims she could trouble shoot better than Sprint. Also advised that Sprint tecs are worthless. I could have told her that.

Evo reboot fixed
-------SOLUTION FOUND-----------EVO REBOOT---------------GPS REBOOT-----------
Step one, call Sprint and get your msl code (unlock code).
Step two open the phone dialer and press “##GPSCLRX#
Step three input the code given to you from sprint (phone will reboot in 20 seconds)
Then launch your GPS programs and you will notice they work (at least for moment)
I will keep my codes on hand for the more than likely event that after 24 hours of use it probably will reoccur all over again.
I am on my second EVO now and I have painstaking already gone through all the hard resets and troubleshooting apps. Repair store and service calls to both Sprint and HTC as well. This is the first time I have gotten the phone to work after the GPS reboots without a hard reset.

-------SOLUTION FOUND-----------EVO REBOOT---------------GPS REBOOT-----------
Step one, call Sprint and get your msl code (unlock code).
Step two open the phone dialer and press “##GPSCLRX#
Step three input the code given to you from sprint (phone will reboot in 20 seconds)
Then launch your GPS programs and you will notice they work (at least for moment)
I will keep my codes on hand for the more than likely event that after 24 hours of use it probably will reoccur all over again.
I am on my second EVO now and I have painstaking already gone through all the hard resets and troubleshooting apps. Repair store and service calls to both Sprint and HTC as well. This is the first time I have gotten the phone to work after the GPS reboots without a hard reset.

Updated to 1.28 on Three UK

I was running the stock 1.26 version and it was perfect. No flickering, very smooth, but the phone kept bugging me for the update, so I updated it. Update went smooth, but now I have that terrible screen flicker, it's by far not as smooth... so if you have no problems with 1.26, don't update. I'll revert to 1.26 and hope that it goes back to being as flawless as it was before.
Edit: Just noticed that wireless connections are much worse as well with this update. At the moment I can only use WiFi and even that doesn't work properly for some reason (i.e. can surf but can't get to beta.swype.com - but I can get there on my desktop using the same WLAN). All borked...

You are one of the only people who has said this about the 1.28 update. Also you can't revert unless you get a new phone with 1.26 as your HBOOT was updated when you installed this update.

Yes, I just noticed that . So until 3 come up with a better update, I'm stuck with this junk Should have stuck to my usual motto: Don't fix it if it ain't broke.

Updated mine on the day I got the phone not noticed any screen flicker at all and I have been looking for it. Dont use Wifi as the 3's 3G is plenty fast enough and I have all you can eat data so can't comment on that. Data connection is FAR more stable than on the ONE S which I swapped it for.

I don't know but this update has royally screwed my phone. Each time the alarm is supposed to go off, the phone reboots (no matter which alarm app I use). I also get reboots for random other apps.
For me it's just a real PITA and at the moment, I would consider the phone unreliable at best. I'll try flashing the 1.28 from Three again but I'm not holding my breath
Just wish I could go back to 1.26.
Edit: I just flashed Energy ROM and the phone still reboots when using Alarm Clock Extreme. It's just sooooooooo annoying!
Isn't there any way to go back to 1.26?
Edit2: After the phone just rebooted, it rebooted again when I was just looking at the notification screen.
Is it a problem with Three UK if the phone has been unlocked? I feel very much inclined to return the phone and get a replacement... phone is unsuable at the moment as a smartphone...
Edit 3: I can't even re-flash it... updater says "can't update this". Oh gosh, Three, please make it fast to the next update.

Anyone having issues with the May update?

My phone was working fine prior to the update. Now since installing it once my phone screen turns off it's basically unresponsive to the power button and fingerprint scanner for about 15-30 seconds before it finally becomes responsive again. Then once I'm in it's fine and the issue starts all over again once it goes to sleep.

Not here. Just flashed the may update. Unlocked, and rooted.

Wout2426 said:
Not here. Just flashed the may update. Unlocked, and rooted.
Click to expand...
Click to collapse
Damn. I'm bone stock and had no issues.. Immediately after the update my screen takes 15 seconds or so to come on after hitting the power button or unlocking with my finger.

Did you flash the update manually or install OTA?
I've experienced similarly weird issues in the past when installing new updates from Google OTA and have since started pushing all of my updates through manually.

NippleSauce said:
Did you flash the update manually or install OTA?
I've experienced similarly weird issues in the past when installing new updates from Google OTA and have since started pushing all of my updates through manually.
Click to expand...
Click to collapse
I installed OTA.
I did just notice the issue does not exist if the phone is plugged into the charger. Very weird.

Flashed May update manually, all good. I'd suggest full image flash (without -w flag) if you're facing issues.

So I factory reset my phone and side loaded the latest update. All has been good for days. All of a sudden this morning the issue is back.

having issues with finger print scanner and phone taking long time to unlock. Pixel line just ain't good!

mongolx said:
having issues with finger print scanner and phone taking long time to unlock. Pixel line just ain't good!
Click to expand...
Click to collapse
I must respectfully disagree. I've had my 3XL since day one, and have not had any issues at all. All OTA updates installed without issue, and this is the best phone I've ever had, and I've had more Android phones that I can list dating back to the Nexus One.

Awesome 4 ya. Reddit and other threads speak 4 them self....

Girlfriends Pixel 2 XL started doing it today after the update as well. Although it stopped after a few hours.

Did anyone receive the google play system update? ive got the main may update but google play system update is still march?. Pixel 3a received them both the same day. Im wondering if this is the cause and it was removed.

I'm having the exact same issue. It started happening in the morning. Unrooted stock. As soon as i lock my device it will turn off. Don't know how to fix that.
Update: chatted with google. And they are sending replacement device

I faced lag on my 2xl couple of weeks ago after the update it seems but i guess it was google doing something in the background perhaps regarding Covid app or something they were trying to do. The random lag stopped in a week or two. So i assume it was google doing something on our phones.

Question Every 3-4 days I must reboot

Ok, so like the title says, every 3-4 days I must reboot my phone.
When I play games, the game icon will show up in the lower right corner, I have everything for the game stuff turned off. I can click on the icon and it will ask me to turn on. I back out and it's gone for a few minutes. Mostly until I swipe back, then it will reappear. I can reboot the phone and it will work fine again for a another 3-4 days.
There are other instances that force me to reboot as well, one happened last night. I was scrolling through a local news app and the touch stopped working. I could not scroll up or down, and swiping back did not work. I had to lock the phone and just as the screen went dark, the phone scrolled in the directions I did and it backed out. This only happened when I hit the lock screen.
Is there a fix for this? Has anyone else experienced this?

My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.

thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Mine does not reboot or shutdown on it own, not once... I have to reboot every so often to keep it functional.

@thepersona My phone doesn't auto reboot either. I'd say do a backup and run https://flash.android.com/welcome to fully Factory Reset the phone and see if that helps (Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Like the OP I do have to reboot my phone about every 3-4 days, but I don't attribute that just to Google Android, coders have become lax on how tight they keep their code, and I say that because in Windows 10 and Windows 11 you have to reboot every few days as well or see an increase in weird issues.

card13 said:
@thepersona Mine upgraded just fine, but my parents both failed the Dec update and had random issues requiring the use of the Android Flash Tool).
Click to expand...
Click to collapse
Just to clarify this, most carriers prevented the December update from releasing as Google has asked them to prevent it from going through, primarily due to an issue with calls dropping.
I always manually update my phone, however, I noticed the call dropping bug one day for about an hour straight.
But aside from this meaningless info, I agree with what you said: Attempt a factory reset and see what happens. I turn my phone off every night and charge it, so I don't notice any issues similar to what OP has mentioned.

thepersona said:
My phone is rebooted on two to three occasions a month. Others have it more frequently. I wouldn't even say rebooted. Mine just shuts down at random times like other users so I don't know if there's a fix for this. I'm hoping there will be one within an update soon.
Google's absolutely ****ty disregard for their customers and customer service. I'm not Keen on sending a brand new device over to get a refurbished one that isn't guaranteed to solve the issue and most likely guaranteed to come with different issues that my device doesn't have already.
Does it back up to combat this since I have alarms set for work? In case the phone turns off, I don't want to miss work. I use my Google Home Mini speakers, a backup alarm.
Click to expand...
Click to collapse
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!

wilpang said:
Yeah mine did that it would randomly restart once a week no matter what I was doing but I did a factory reset and it hasn't happened since!
Click to expand...
Click to collapse
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol

thepersona said:
In your case, was it just a restart? Because mine literally powers off It doesn't reboot again. It shuts down in the middle of the night and I wouldn't know until I wake up when using my phone to figure out it won't turn on. I almost missed work on several occasions because of this lol
Click to expand...
Click to collapse
Yeah I was lucky and it was only once a week which was tolerable!
Something is definitely not right, hopefully is not a dodgy app but that would be preferable than something unfixable.

Ok guys you are missing my point and question. I DO NOT have the random reboots most have, but I have other issues that no one seem to have. Example, I listen to Spotify over night, I fall asleep to music, but 2 days ago it would randomly pause. At first I thought it was do not disturb that I just turned on, on my watch. It was not. Then I thought I may have been hitting my watch, I took it off and it still paused. I rebooted my phone and it's been fine since, no random pauses. Another example is, I play a game but I have the game dashboard turned off, but there times where the icon will pop up in the lower right. When I go into the settings for it, it shows it's off. When I go back to the game the icon is gone for a few minutes then it reappears. The only way for me to get it to stop showing for a few days is to reboot my phone.
I know you shouldn't have to reboot your phone every few days, and by few I mean sometimes it's 3-4 times a week. That tells me something is wrong.

Are you on the November or December update?
If November, I would try the December one.
Rooted or not rooted?
Either way, I would try a factory refresh and don't restore your apps from backup. Manually install only your most critical apps and see if you have the problem. Even better would be not install any additional apps at all and see if the problem happens. If it doesn't happen, install another small group of your most important apps and test again for long enough. Etc.
If you try thre update and/or factory reset, you could try restoring your cloud backup as normal and see if you have any problems still, but if you do, be prepared to factory reset and try like I mentioned in the above paragraph.
Until you can narrow down if the phone has this problem on the December update before you even change settings and add your favorite apps, then you won't know if it's the phone itself (possibly hardware problem), an app you have installed, a problem particular to a combination of factors including if you're on the November update, or what.
Good luck! Please let us know what happens.

I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.

darbylonia said:
I can tell you that until I updated to the December update I had the kinds of issues you had, where my P6P would malfunction (scrolling, just freezing) and I had to reboot the device. That was the first 6 weeks of using it. But when I updated to the December build, the issues for the most part went away. Hopefully you are on November and can update to December or wait until the January update drops. But I can say that I almost considered returning the phone due to the bugs until the December update resolved everything and it was like a new phone!
Good luck.
Click to expand...
Click to collapse
Awesome!!! This is the kind of news I like to hear..... Just waiting for att to send it through. I checked this morning as my work Verizon Samsung phone got an update.

Question A13, another "Am I the only one?" Thread!

Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.

You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s

nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).

Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.

Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.

jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.

roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?

For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.

Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/

jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.

Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!

roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".

jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.

Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).

I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.

96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.

jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.

Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.

jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.

96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.