Develop Bugs

Phone Freezes Up When Pressing Back Button On Nav Bar in Strange Way

So, I got my new Pixel XL (128 GB, Quite Black, Google Store), and activated it with Project Fi a few days ago. Today, I noticed a bizarre issue. So far, I'm only able to get it to occur consistently in the Play Store. When pressing the back button on the navigation bar to return to the previous screen, the phone locks up, but not completely. The app and the back button both become completely unresponsive to touch, the volume buttons do not do anything, but the overview, home, and power button still function as normal. Navigating away from the app, or turning the screen off and back on fixes it, but it happens consistently enough to be very irritating. However, I can't get it to happen consistently enough to isolate a cause, or to capture a screen recording of it. It seems, though, to be more likely that it is app related, but that also seems strange given that it is the Play Store. The only other correlation I can find is to the Keyboard (which I'm using GBoard). Sometimes, it seems to occur after using the keyboard to search the store.
Does anyone have any suggestions/tips/etc. on a way to deal with it? Its hardly a fatal issue, but strange, and I'm curious if anyone knows what this could be.
Also, a side question: is it even worth unlocking/installing mods/etc.? I got 5+ hours of SOT with my first full charge cycle, curious if anyone has any input.

SonarMonkey said:
So, I got my new Pixel XL (128 GB, Quite Black, Google Store), and activated it with Project Fi a few days ago. Today, I noticed a bizarre issue. So far, I'm only able to get it to occur consistently in the Play Store. When pressing the back button on the navigation bar to return to the previous screen, the phone locks up, but not completely. The app and the back button both become completely unresponsive to touch, the volume buttons do not do anything, but the overview, home, and power button still function as normal. Navigating away from the app, or turning the screen off and back on fixes it, but it happens consistently enough to be very irritating. However, I can't get it to happen consistently enough to isolate a cause, or to capture a screen recording of it. It seems, though, to be more likely that it is app related, but that also seems strange given that it is the Play Store. The only other correlation I can find is to the Keyboard (which I'm using GBoard). Sometimes, it seems to occur after using the keyboard to search the store.
Does anyone have any suggestions/tips/etc. on a way to deal with it? Its hardly a fatal issue, but strange, and I'm curious if anyone knows what this could be.
Also, a side question: is it even worth unlocking/installing mods/etc.? I got 5+ hours of SOT with my first full charge cycle, curious if anyone has any input.
Click to expand...
Click to collapse
I recommend unlocking so at least if you ever have a bad ota update you can still fix you're device with a new factory image. As far as the lag issues. I had something similar when Gboard first came out. What is you're current build. You may need to update you're phone.

toknitup420 said:
I recommend unlocking so at least if you ever have a bad ota update you can still fix you're device with a new factory image. As far as the lag issues. I had something similar when Gboard first came out. What is you're current build. You may need to update you're phone.
Click to expand...
Click to collapse
I'm on the May image, and all my apps are up to date (aside from staggered update I may not have received, always possible). I'll wait for the June image to come out tomorrow and see if that fixes it. Thanks for the input on both fronts!
Although, if I unlock the bootloader I may fall all the way down the rabbit hole, haha.

SonarMonkey said:
I'm on the May image, and all my apps are up to date (aside from staggered update I may not have received, always possible). I'll wait for the June image to come out tomorrow and see if that fixes it. Thanks for the input on both fronts!
Although, if I unlock the bootloader I may fall all the way down the rabbit hole, haha.
Click to expand...
Click to collapse
Nothing wrong with falling down the rabbit hole lol. Personally I run stock system with my mod pack. Gives me incredible battery cuz it's stock system but I also get to have some custom tweaks. Best of both worlds.

toknitup420 said:
Nothing wrong with falling down the rabbit hole lol. Personally I run stock system with my mod pack. Gives me incredible battery cuz it's stock system but I also get to have some custom tweaks. Best of both worlds.
Click to expand...
Click to collapse
Any particular mods? I've been flashing/modding/etc since my Droid Razr M but reading around on the Pixel XL forums is the first time I've felt out of my depth again - all this A/B partition stuff, changes to the way root and GApps work, etc. seems so different.

Random Apps Opening after 8.0

Has anyone else been experiencing random applications opening on the device after the Oreo Update? I have the VZW Varient so i dont know if that makes a difference but im interested to know others feedback

I'm on T-Mobile variant as well as on oreo and have not had such an issue. Which applications have been doing such things?

i've got the similar issue for my z2f EU (xt1789-06) and i'n with 7.1.1
app: amazon, yahoo auction JP, chrome

Hmm..I did notice a couple apps do that..

FragmentedLogik said:
Has anyone else been experiencing random applications opening on the device after the Oreo Update? I have the VZW Varient so i dont know if that makes a difference but im interested to know others feedback
Click to expand...
Click to collapse
I've noticed it a few times. Nothing consistent. Probably just the Chinese government making tiny mistakes

Randon apps
Yes im experiencing the same problem with apps just opening over the top of what ever your doing. Apps that I haven't used in awhile. Would love to find out what is causing it

I don't have that issue. The application manager will opens temporarily when device reboots. The only bug I have found is that if I try to disable the amazon app my phone instantly reboots.
Sent from my Moto Z (2) using Tapatalk

I am on Sprint and have used this phone since Sept and never have experienced this, not even on Oreo since I updated on Tuesday.

just to add my two cents. I was having this problem. Turned off Moto voice security and I haven't seen this happen again.

I've got it too, can't figure it out. I'll have to try your suggestion JAWheat411, thanks!
Warning for those who are experiencing it: this bug has the capability to bypass screen locks. Opened up an app today that completely bypassed it. Interrupted my Spotify while at work and saw that app open instead. And I am sure that I locked my phone since I leave it on my toolbox, and don't want all my co-workers in my business.

I'm also having this very same problem. I will also try disabling Moto voice security and see if that rectifies the issue. I will report back in about 2 days.

3165dwayne said:
I'm also having this very same problem. I will also try disabling Moto voice security and see if that rectifies the issue. I will report back in about 2 days.
Click to expand...
Click to collapse
lol, I'm late. I still have the problem. It's very random and hasn't been happening as frequently but it still happens.

Same on my Note 8. Very frustrating.

rcbass said:
Yes im experiencing the same problem with apps just opening over the top of what ever your doing. Apps that I haven't used in awhile. Would love to find out what is causing it
Click to expand...
Click to collapse
This is exactly what is happening to my Galaxy S7 edge since the Oreo update. And it goes right past the lockscreen and my security. My phone is always locked, yet I find I've send a nonsense text, or pocket dialed someone, or that a gibberish email is half-composed, or that my calendar is open and a new nonsense event is half-entered. Somehow Oreo is doing all sorts of screen taps, or allowing my phone to wake up and let the pocket do that. And I have enabled the thing about disable touch when in pocket, and I've shut down smart unlock, but that hasn't made a bit of difference.

This problem is happening with my recently bought Moto Z2 Force. It started out random, but then became pretty consistent. I tried disabling the Moto actions (voice command, voice unlock and one button nav) but the problem kept happening afterwards too and became consistent.
It even opened outlook and managed to delete an important email from my boss that I hadn't read yet! Had I not been looking at my phone while it happened, I would have had one unhappy boss.
Even after unlocking the phone, it would just try random unlock codes for a while and eventually lock out the screen for 30 seconds, and then try again. Wouldn't even let me restart the phone. After struggling for more than 2 hours, I was finally able to restart in safe mode and the problem seemed to stop in safe mode. I disabled Moto actions app, deleted data from that app, and also just to be safe removed the HDR+ cam app that I ported. Planning to monitor for a couple of days and see what happens.
This sh!t is just bonkers!

Slow app opening when tapping notifications

Almost every Samsung android phone I've own has this problem after using it for a period of time. I've had the note 10+ since launch and the dreaded issue has return.
For some apps, I would tap the notification for the app. It would take a few minutes before the app will open.
Anyone has this issue?
I've had it on my note8, Note9 and now the note10+.
Hard reset will fix it but I don't want to reset and start again..
Continuation from note 8 thread: https://forum.xda-developers.com/galaxy-note-8/help/app-lag-clicking-notification-t3781356/page2

I don't have this issue.
Some people prefer to perform an hard reset as soon as they got the phone, before starting using it for the first time ; maybe they had some issues like yours at first, then wanted to avoid them.
Personally I didn't got any at first run.

That's odd, I have not experienced what you say in any of my samsung devices dating from my beloved S3 to this note10+

Yes..i am so confuse why it happens.. When the phone is new or just had a hard reset.. I don't have the issue.. Over time I always get it.

I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.

Is it all apps or certain apps only? Are you running stock or rooted? Exynos or Snapdragon? I haven't seen this issue shown up in a while, but have had it happen on Android devices in general in the past.

aarick said:
Almost every Samsung android phone I've own has this problem after using it for a period of time. I've had the note 10+ since launch and the dreaded issue has return.
For some apps, I would tap the notification for the app. It would take a few minutes before the app will open.
Anyone has this issue?
I've had it on my note8, Note9 and now the note10+.
Hard reset will fix it but I don't want to reset and start again..
Continuation from note 8 thread: https://forum.xda-developers.com/galaxy-note-8/help/app-lag-clicking-notification-t3781356/page2
Click to expand...
Click to collapse
Aaron J said:
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Click to expand...
Click to collapse
I don't have this issue, but as @dhorgas, more info would be helpful if it's a problem that can easily be fixed.
Two have the issue here, It could be a common app both of you are running.

lennie said:
I don't have this issue, but as @dhorgas, more info would be helpful if it's a problem that can easily be fixed.
Two have the issue here, It could be a common app both of you are running.
Click to expand...
Click to collapse
It seems to be related to pendingIntent type notifications as if I tap a notifications that is a collapsed version of all the notifications, the app will load instantly. Have a look at this video I created:
(I didn’t include the tap showing on screen unfortunately, will attempt to do another video next time)
Initial tap was when the notification is collapsed for reolink and that will just open up the app. Happens instantly.
I close the app, expanded the notification and click on specific notification
The app doesn’t open until 8 minutes + later towards the end of the video.
Issue is happening across a fair few apps so I doubt it's common app..
I also have the issue of delayed notifications as discussed here:
https://eu.community.samsung.com/t5...ue-affecting-all-range-of-Samsung/td-p/738070

dhorgas said:
Is it all apps or certain apps only? Are you running stock or rooted? Exynos or Snapdragon? I haven't seen this issue shown up in a while, but have had it happen on Android devices in general in the past.
Click to expand...
Click to collapse
Stock on exynos

Aaron J said:
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Click to expand...
Click to collapse
Have the same issue with the play store. One way to speed it up is to force close play store... Then reopen it..
The app will redownload and should install this time.. Not always..

Quick update: Got fed up and did a factory reset and restored everything. Everything's working fine now. Obviously that's a last resort, but so far it's the only solution I've seen.

aarick said:
It seems to be related to pendingIntent type notifications as if I tap a notifications that is a collapsed version of all the notifications, the app will load instantly. Have a look at this video I created:
(I didn’t include the tap showing on screen unfortunately, will attempt to do another video next time)
Initial tap was when the notification is collapsed for reolink and that will just open up the app. Happens instantly.
I close the app, expanded the notification and click on specific notification
The app doesn’t open until 8 minutes + later towards the end of the video.
Issue is happening across a fair few apps so I doubt it's common app..
I also have the issue of delayed notifications as discussed here:
https://eu.community.samsung.com/t5...ue-affecting-all-range-of-Samsung/td-p/738070
Click to expand...
Click to collapse
Wow. That would drive me crazy. Try backup, hard reset and restore like @Aaron J did and see if that fixes the issue.

lennie said:
Wow. That would drive me crazy. Try backup, hard reset and restore like @Aaron J did and see if that fixes the issue.
Click to expand...
Click to collapse
Yes.. It will fix it.. But it's temporary..
The issue won't happen straight away.. It takes a few weeks/months and will return.. It has happened to me from the note 8, note 9 and now note 10+.
Initially everything will be good and fast.. Then eventually issue will return..
So need to try to get to the root of it..

Aaron J said:
Quick update: Got fed up and did a factory reset and restored everything. Everything's working fine now. Obviously that's a last resort, but so far it's the only solution I've seen.
Click to expand...
Click to collapse
Hope the issue doesn't return for you.. It always returns for me..

I have been dealing with 3 issues in my phone:
-delayed notifications
-slow app opening when tapping notifications
-apps installation through play store delayed after download
So recent development, I have been following this thread on Samsung forums regarding delayed notifications
https://eu.community.samsung.com/t5...ting-all-range-of-Samsung/td-p/738070/page/28
Have tried all the fixes which has given minor relief..
But the last suggestion to disable dynamic lock on windows 10 seems to have fixed the issue for me. Early days but all 3 issues have not reoccured yet today.. Usually my Samsung reminders will not show until I reboot. But today been good so far.
Apps install instantly and apps open from notifications straight away..
Will report back in a few days if anything changes..

aarick said:
I have been dealing with 3 issues in my phone:
-delayed notifications
-slow app opening when tapping notifications
-apps installation through play store delayed after download
So recent development, I have been following this thread on Samsung forums regarding delayed notifications
https://eu.community.samsung.com/t5...ting-all-range-of-Samsung/td-p/738070/page/28
Have tried all the fixes which has given minor relief..
But the last suggestion to disable dynamic lock on windows 10 seems to have fixed the issue for me. Early days but all 3 issues have not reoccured yet today.. Usually my Samsung reminders will not show until I reboot. But today been good so far.
Apps install instantly and apps open from notifications straight away..
Will report back in a few days if anything changes..
Click to expand...
Click to collapse
So ... did this do it? I've been dealing with this for a LONG time. My Note 8 started this crap after the 9 'upgrade', motivated me to get a new Note 10. A few months later, the SAME exact problem is cropping up.
Slow notification reactions, stuck installs, notifications coming in repeatedly, notifications coming in late all at once.
If this isn't resolved soon, my next phone will definitely not be a Samsung.

nokster said:
So ... did this do it? I've been dealing with this for a LONG time. My Note 8 started this crap after the 9 'upgrade', motivated me to get a new Note 10. A few months later, the SAME exact problem is cropping up.
Slow notification reactions, stuck installs, notifications coming in repeatedly, notifications coming in late all at once.
If this isn't resolved soon, my next phone will definitely not be a Samsung.
Click to expand...
Click to collapse
Yes, my issue is gone now. Try removing windows dynamic lock and unpair your phone from your laptop if you have this setup.
If not, try slowly removing other Bluetooth devices.
For me, a Bluetooth yeelock also caused the delay to return..I have to reboot each time after using the lock to get it back to normal.
I also think a plantronics desktop headset was also causing the issue as I was getting the lag everytime I reach home since removing windows dynamic lock. I have since unplugged it and unpaired. So far been good for a few weeks now.
I heard this issue wasn't specific to Samsung but might be an Android issue..i think it started with Android 9.0 as you have mentioned as I never had this issue when I was using the note 8 before one ui.. But note 9 and 10+ both had issues..
Similar issue mentioned on pixel phone support:
https://support.google.com/pixelphone/thread/5024453?hl=en

aarick said:
Yes, my issue is gone now. Try removing windows dynamic lock and unpair your phone from your laptop if you have this setup.
If not, try slowly removing other Bluetooth devices.
For me, a Bluetooth yeelock also caused the delay to return..I have to reboot each time after using the lock to get it back to normal.
I also think a plantronics desktop headset was also causing the issue as I was getting the lag everytime I reach home since removing windows dynamic lock. I have since unplugged it and unpaired. So far been good for a few weeks now.
I heard this issue wasn't specific to Samsung but might be an Android issue..i think it started with Android 9.0 as you have mentioned as I never had this issue when I was using the note 8 before one ui.. But note 9 and 10+ both had issues..
Similar issue mentioned on pixel phone support:
https://support.google.com/pixelphone/thread/5024453?hl=en
Click to expand...
Click to collapse
I don't have Dynamic Lock set up, nor do any of my computers have bluetooth enabled. BUT I do have this cursed Plantronics PLT W8200 series headset that has been nothing but buggy since I got it. Not surprised if this is the cause. I just unpaired it - fingers crossed.
I hope that's it because otherwise, it's just 2 other pretty crucial devices I have paired.

nokster said:
I don't have Dynamic Lock set up, nor do any of my computers have bluetooth enabled. BUT I do have this cursed Plantronics PLT W8200 series headset that has been nothing but buggy since I got it. Not surprised if this is the cause. I just unpaired it - fingers crossed.
I hope that's it because otherwise, it's just 2 other pretty crucial devices I have paired.
Click to expand...
Click to collapse
Would be good to hear if this fixes your issue. Please make sure you reboot after unpairing too and if possible completely unplug the plantronics as I think it might try to connect to your phone still (but fail) and potentially still bring the issue back as my yeelock doesn't even show up as a paired device, the app just sends msg to it via bluetooth and I still have delays after using it.
Keep us updated...

aarick said:
Would be good to hear if this fixes your issue. Please make sure you reboot after unpairing too and if possible completely unplug the plantronics as I think it might try to connect to your phone still (but fail) and potentially still bring the issue back as my yeelock doesn't even show up as a paired device, the app just sends msg to it via bluetooth and I still have delays after using it.
Keep us updated...
Click to expand...
Click to collapse
So after the weekend of having the Plantronics headset un-paired, it *seems* better. Hopefully it stays that way.

Question Stuttering Scrolling In Some Apps?

Anyone noticed this? Telegram and Twitter for eg, the scrolling is pretty stuttery, it's like the CPU touch boost isn't working on them?

Not sure what you would call stuttering.
It is known that Telegram and Twitter have some optimizations issues with the new 120Hz panel, they revert back to 60hz (you can easily notice this when activating le "show refresh rate" in developer options). That should be easy to fix with a small software update. Even though (you might have noticed) it only effects Telegram when you are INSIDE a group/chat, if you scroll through the "list" of groups you are in, it uses 120hz.
Or do you really mean "stuttery" like playing a game with 15 FPS and you think you are inside lag-hausen?

Morgrain said:
Not sure what you would call stuttering.
It is known that Telegram and Twitter have some optimizations issues with the new 120Hz panel, they revert back to 60hz (you can easily notice this when activating le "show refresh rate" in developer options). That should be easy to fix with a small software update. Even though (you might have noticed) it only effects Telegram when you are INSIDE a group/chat, if you scroll through the "list" of groups you are in, it uses 120hz.
Or do you really mean "stuttery" like playing a game with 15 FPS and you think you are inside lag-hausen?
Click to expand...
Click to collapse
Morgrain said:
Not sure what you would call stuttering.
It is known that Telegram and Twitter have some optimizations issues with the new 120Hz panel, they revert back to 60hz (you can easily notice this when activating le "show refresh rate" in developer options). That should be easy to fix with a small software update. Even though (you might have noticed) it only effects Telegram when you are INSIDE a group/chat, if you scroll through the "list" of groups you are in, it uses 120hz.
Or do you really mean "stuttery" like playing a game with 15 FPS and you think you are inside lag-hausen?
Click to expand...
Click to collapse
Is this an A12 thing? The scrolling on my [email protected] for eg is a heck of a lot smoother in Twitter than on the P6P. Edit: Twitter is running at 120hz, so it can't be that.

Batfink33 said:
Is this an A12 thing? The scrolling on my [email protected] for eg is a heck of a lot smoother in Twitter than on the P6P.
Click to expand...
Click to collapse
We don't know at this point, since no other phones has A12 released yet. It might be A12 related, it might be P6 related. What is clear however, is that this should be easy to fix.

I have noticed this on P5 and a little less on this device. Android 11+12. I don't get why this happens on modern devices.

Golf c said:
I have noticed this on P5 and a little less on this device. Android 11+12. I don't get why this happens on modern devices.
Click to expand...
Click to collapse
Weird. Like I said, it doesn't happen on my s21U. It's obviously a software thing but i wonder what.

Batfink33 said:
Weird. Like I said, it doesn't happen on my s21U. It's obviously a software thing but i wonder what.
Click to expand...
Click to collapse
Did you copy your phones apps over from another device? Have you tried reinstalling your specific app? Maybe it's a glitch or bug that is caused by this. It's usually a wise idea to do a delete cache/data once you encounter problems with a certain app.

It happens on Twitter and Reddit apps for me also. It was mentioned on Verge review too.
Video:
https://imgur.com/a/WUGs0c7

Man, it's happening in more than a few apps for me. Scrolling down a page in Chrome will stutter! (And that's a system app — I can't try uninstalling and reinstalling it.) Yes, clearly a software issue, but it's not trivial. Hope they fix this; the phone is otherwise stellar.

It is not related with Software I guess because it works fluidly SD 888 from last year. I took a video about it Here is the link.
Both have android 12 and both have the same settings on Twitter app.

Lots of stutter in Chrome and the Google app for me. It's really annoying.

xantrk said:
It happens on Twitter and Reddit apps for me also. It was mentioned on Verge review too.
Video:
https://imgur.com/a/WUGs0c7
Click to expand...
Click to collapse
Which app for those graph overlay ?

I can verify that Twitter stutters for me as well

Batfink33 said:
Anyone noticed this? Telegram and Twitter for eg, the scrolling is pretty stuttery, it's like the CPU touch boost isn't working on them?
Click to expand...
Click to collapse
yep, I had this going on in my PayPal App, the display will flicker around almost violently, and I was typing so you wait a sec, it settles down type some more, etc. I made a decent feedback report on my end, with a great screen recording capture of the "seizure-like" display issue, LIVE! es

evnStevn said:
yep, I had this going on in my PayPal App, the display will flicker around almost violently, and I was typing so you wait a sec, it settles down type some more, etc. I made a decent feedback report on my end, with a great screen recording capture of the "seizure-like" display issue, LIVE! es
Click to expand...
Click to collapse
This used to happen to me from upgrading my phone too many times without doing a full wipe first (which I then started doing on the android flash site). Nowadays, I always do a full wipe with each update and I haven't experienced that stuttering since I began doing so.
It just stinks always having to setup your phone from scratch every month if you continuously update like I do lol.

NippleSauce said:
This used to happen to me from upgrading my phone too many times without doing a full wipe first (which I then started doing on the android flash site). Nowadays, I always do a full wipe with each update and I haven't experienced that stuttering since I began doing so.
It just stinks always having to setup your phone from scratch every month if you continuously update like I do lol.
Click to expand...
Click to collapse
Roger that.

NippleSauce said:
This used to happen to me from upgrading my phone too many times without doing a full wipe first (which I then started doing on the android flash site). Nowadays, I always do a full wipe with each update and I haven't experienced that stuttering since I began doing so.
It just stinks always having to setup your phone from scratch every month if you continuously update like I do lol.
Click to expand...
Click to collapse
No way you should have to do that.

awarman said:
No way you should have to do that.
Click to expand...
Click to collapse
I thought the same thing at first - as with my previous phones that had TWRP, this was never a problem. But honestly, I only just started believing in what I mentioned this past week. By February, I hadn't wiped me phone since I had gotten it in December and was experiencing the problems that you described. I thought it was a bad phone, however, after COMPLETELY wiping, then reflashing and setting everything up again the problem was resolved.
But just this week I updated my phone to the June Beta 2 / GPR3 Beta 2 (Build: S3B1.220318.003) and decided not to wipe it clean...and now I'm experiencing the annoying stuttering/temporary freeze issues yet again.
Granted, it's a beta... But I'm not too sure it would have these issues - the same issues that had occurred in the past when I wasn't doing full wipes on my phone when updating. So I suppose I'll have to wipe my phone and start over on QPR3B2 and report back with the results. I'll probably do this within the next few days.

Boom batishta said:
Which app for those graph overlay ?
Click to expand...
Click to collapse
System > Developer options > Profile HWUI Rendering > On screen as bars.

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.