Develop Bugs

POLL: How is Oreo working for you now that it's released?

Just curious to see how people are finding the new Oreo for the S7/S7 edge. For me, it's great. Definitely I do see an improvement in performance. Sluggishness is definitely reduced from what I was experiencing in Nougat. Battery life appears to be the same, if not a bit better, but it's hard to tell.
Only issue I've seen is some apps I have are not Oreo ready (such as the previous Power Amp beta, but there is an Alpha out right now that works but is very incomplete in things such as Playlists).
I have noticed that some apps no longer give notifications at all (mainly games with in-app notifications). Not sure if it's because they're not up-to-snuff with Oreo, but the important apps (such as Messenger+) do work just fine in regards to notifications.
Overall, I'm very pleased with this release which in all honesty will probably be the last upgrade for this phone. I still love my S7 and hope it lasts a long time for me.

This update is fantastic as far as I'm concerned. My phone seems to be more responsive and doesn't lag as much as it did on Nougat. Battery life has been better since the update. Somehow my fingerprint scan to unlock is 1,000 times better. Was always having issue with it before this update. I am also getting slightly better reception. I get slightly better reception in my office area where I previously had little to no reception. I like how some of the items in the pull down notification shade are compacted like your Wi-Fi connection, so they don't take up as much room. Feels like I have a new phone, and I also hope this last major update we will get will help my S7 last for a long time.

I agree, much snappier. I not having to keep putting down apps and restarting to keep it that way either. It makes my s7 a keeper for another year at least. None of the new features really apply to the way I use my device, so no difference there for me.
Sent from my SM-G930V using Tapatalk

Adaptive icons suck. Had to download an icon pack to return all of the Google apps to "normal". Bright white circles in my dark theme....
Other than that, I'll have to mess around more before I see if there's been much change. Haven't really noticed more responsiveness.

one word. HORRIBLE! Battery life has literally been cut by 40-60% with the exact same use as before even with power saver on, weird lag issues when I'm trying to multitask, incoming calls wont take precedence over whatever else is currently on screen, screen wont light up on incoming calls when idle, VZW caller id no longer works on unknown calls, fingerprint unlock no longer works just keeps saying "wipe home key and try again", while talking on the phone if the other person gets another call i now hear it ringing on my side and this is just after 2 days...... worst update ever to what was a flawlessly performing device. Wondering if I need to do a factory reset and start fresh

zachjf said:
one word. HORRIBLE! Battery life has literally been cut by 40-60% with the exact same use as before even with power saver on, weird lag issues when I'm trying to multitask, incoming calls wont take precedence over whatever else is currently on screen, screen wont light up on incoming calls when idle, VZW caller id no longer works on unknown calls, fingerprint unlock no longer works just keeps saying "wipe home key and try again", while talking on the phone if the other person gets another call i now hear it ringing on my side and this is just after 2 days...... worst update ever to what was a flawlessly performing device. Wondering if I need to do a factory reset and start fresh
Click to expand...
Click to collapse
A factory reset would be a good place to start, especially after a major update.

I did the full reset with the Odin package and it is very smooth with better battery life, even with battery saver off.

tylerhole said:
A factory reset would be a good place to start, especially after a major update.
Click to expand...
Click to collapse
it took 5 tries but I was finally able to get it to wipe/reset, kept giving me a "system update failed, no recovery package found" error. Resetting it seems to have cured the battery, heat and lag issues and is running smoothly again, only issue I still have is a slight delay in waking the phone on incoming calls but I can live with that

zachjf said:
it took 5 tries but I was finally able to get it to wipe/reset, kept giving me a "system update failed, no recovery package found" error. Resetting it seems to have cured the battery, heat and lag issues and is running smoothly again, only issue I still have is a slight delay in waking the phone on incoming calls but I can live with that
Click to expand...
Click to collapse
Glad to hear it worked. not sure what you can do about the lag when waking, maybe it'll work itself out in time.
Sent from my SM-G935V using Tapatalk

zachjf said:
it took 5 tries but I was finally able to get it to wipe/reset, kept giving me a "system update failed, no recovery package found" error. Resetting it seems to have cured the battery, heat and lag issues and is running smoothly again, only issue I still have is a slight delay in waking the phone on incoming calls but I can live with that
Click to expand...
Click to collapse
Glad it's working now. Were you rooted and/or modified any of the default system apps? That can cause issues as well. I haven't rooted the S7 ever since I first got it over 1.5 years ago because I never had the need to. It's always been pretty good and stable except Nougat. It started out fine, but as time went on it got progressively worse. I didn't have to do a factory reset and so far, Oreo has been a dream come true.
People's mileage will vary depending on their use and any mods they may have done to their phones. Also, remember that not all apps are written to Oreo specs. Whenever there is a major upgrade, certain APIs and other programming techniques that might have worked (or been allowed to happen) under older versions of Android may now be no longer allowed. That can result in apps misbehaving under Oreo and thereby causing the symptoms you see (battery drain, sluggishness, etc). That's why it's always best to see if any apps you have installed have been updated to work correctly with Oreo.
Another option would have been to uninstall apps one by one to see if things improved after they were removed. At that point, you have found your culprit.
I usually do an update of all apps before doing an upgrade because a lot of devs will push out updates to make their apps conform to the next Android version's standards. That has usually allowed me to avoid any issues. Problem is, not all apps are kept up-to-date because the developer has moved on to other things, etc. But, if any apps that haven't been updated in a long time are still on after I upgrade, I usually would remove those first and that usually cured my ills. But, it is rare that I have the problem because I usually don't keep old, stale apps around. I'm a stickler for that for some reason.
In any case, glad you got it working!

iBolski said:
Just curious to see how people are finding the new Oreo for the S7/S7 edge. For me, it's great. Definitely I do see an improvement in performance. Sluggishness is definitely reduced from what I was experiencing in Nougat. Battery life appears to be the same, if not a bit better, but it's hard to tell.
Only issue I've seen is some apps I have are not Oreo ready (such as the previous Power Amp beta, but there is an Alpha out right now that works but is very incomplete in things such as Playlists).
I have noticed that some apps no longer give notifications at all (mainly games with in-app notifications). Not sure if it's because they're not up-to-snuff with Oreo, but the important apps (such as Messenger+) do work just fine in regards to notifications.
Overall, I'm very pleased with this release which in all honesty will probably be the last upgrade for this phone. I still love my S7 and hope it lasts a long time for me.
Click to expand...
Click to collapse
I had no problem at all updating. Went real smooth. My battery has better life and the heat/battery/lag/slow boot are so much betterer. The only things I miss is dolby and viper for sound quality being non rooted. I listen to a lot of music and now have to use an old rooted S5 for my music. Thank you for the release. I've only had it installed for a day and if I notice any issues I will post

samg1958 said:
I had no problem at all updating. Went real smooth. My battery has better life and the heat/battery/lag/slow boot are so much betterer. The only things I miss is dolby and viper for sound quality being non rooted. I listen to a lot of music and now have to use an old rooted S5 for my music. Thank you for the release. I've only had it installed for a day and if I notice any issues I will post
Click to expand...
Click to collapse
Hey mate, did you know that root for Oreo was released recently?
https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Bless jkruse, been using his roms / tools since my One+ 1

Awful, but to be fair, the phone has been horrible for several months now. Did the update to Oreo first, but phone was slow. Decided to do a factory data reset and start fresh with Oreo. It was a little bit better, but not great. Then I installed the g930vvrs4crg2 update and it got worse. Last try before smashing this phone is to Odin back to fresh Oreo, then install the latest update. Hopefully that helps.

woodardhsd said:
Awful, but to be fair, the phone has been horrible for several months now. Did the update to Oreo first, but phone was slow. Decided to do a factory data reset and start fresh with Oreo. It was a little bit better, but not great. Then I installed the g930vvrs4crg2 update and it got worse. Last try before smashing this phone is to Odin back to fresh Oreo, then install the latest update. Hopefully that helps.
Click to expand...
Click to collapse
The Verizon firmware is awful. Flashing the unlocked firmware (930U) is miles better. Very little bloat (most can be disabled or uninstalled)

Pixel 3XL still choppy and laggy after March update

I'm sure everyone has their gripes with this phone, but my main one has to deal with the overall smoothness of the device. Since day 1 it has been, at most times, horrendous. Animations are choppy at best, pulling down the notification shade is choppy, and opening apps is like watching someone stutter. Of course, doing a factory reset and rebooting every time your phone starts to slow down works, but who wants to do that every 30 minutes? Not me. But that's been my experience.
One other thing I've noticed is that any time I have a pending notification from Poke'mon Go, the phone's general smoothness comes to a choppy halt. As as soon as I dismiss the notification everything speeds up to normal -- for a short time.
I don't know what else to do. I've started really decreasing what I have and what I've put on my phone for the sake of having a smooth experience, but that's ridiculous. My phone has dwindled down to just that -- a phone. I feel like I can't do anything on it without the lags and stutters coming back to haunt my eyes. I know this phone only has 4GB of RAM, but damn. Something needs to be optimized. I can't play a game while listening to music, check an email really quick without one of the three, -- if not all -- of my apps being killed due to low RAM.
How is everyone else after the March update?

Maybe you should consider asking for a replacement cause it shouldn't be such a problem.

brand0nYates said:
...How is everyone else after the March update?
Click to expand...
Click to collapse
Before you request a RMA, I would suggest Installing the March 2019 factory image 'wipe data'.
This guide will help: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Do #4 'wipe data' then #7 or #8 to root.
Note: Use twrp-3.2.3-3 not twrp-3.2.3-4 that has problems.
Why am I recommend you wipe your phone and re-setting up your phone? Your problem might be that one of the Apps or Mods you have installed are not compatible.
Edit: After reading your response, this does not apply. rotflmao

Homeboy76 said:
Before you request a RMA, I would suggest Installing the March 2019 factory image 'wipe data'.
This guide will help: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Do #4 'wipe data' then #7 or #8 to root.
Note: Use twrp-3.2.3-3 not twrp-3.2.3-4 that has problems.
Why am I recommend you wipe your phone and re-setting up your phone? Your problem might be that one of the Apps or Mods you have installed are not compatible.
Click to expand...
Click to collapse
Unfortunately rooting my phone isn't an option right now since mine came from Verizon. At least I know my issue doesn't stem from mods though,right? :crying:

brand0nYates said:
Unfortunately rooting my phone isn't an option right now since mine came from Verizon. At least I know my issue doesn't stem from mods though,right? :crying:
Click to expand...
Click to collapse
My mistake in 'assuming' instead of asking if you had a Google Pixel3XL.
The fact you have a 'Verizon' Pixel3XL could have been mentioned in the OP. It would have helped screen your responses.

ive played with about a dozen pixel 3 and 3xls and the issue exists everywhere
some people are more sensitive to it than others.
i have literally shown people the "choppy-ness" and they dont see it, so it looks like you may be one of the ones who are more sensitive to these things.

Mine been good for the most part. After one of the updates it felt slow. To the point it was getting on my nerves. I even had to do a reset.
After March update, most is fixed. Feels like a good old pixel.
Still camera experience isn't the fastest but is better than before.
Initial turn on of app like sms, settings, phone takes time but that has always been there since day one.
I didn't notice any choppiness yet anywhere, even in Google feed.

I haven't noticed any major or unusual choppiness on mine. However, I think what apps you use has a lot you do with it. Some apps are just memory hogs and will show down your phone regardless of what it is. I have over 240 apps but none are social media nor games like Pokeman. My phone runs pretty smooth.
Sent from my Pixel 3 XL

I have a Pixel 3 and the camera still sucks after the March OTA. The camera would take forever to load the view finder. It would crash after going from camera to video mode. I have to restart the phone for the camera to work. Needless to say the March OTA did not resolve camera problems.

You are not alone my friend. The laggy-ness is unreal. This led me to want to root my phone and improve performance. I am researching all the things I can before I root. It looks doable but I'm afraid I might brick my phone.
It's a shame that your's is from Verizon. Hopefully, the April update fixes the issues.

Not only have I had this issue, but mine seems to be worse after the March update. It seems to lag the most right after I unlock it (not always), there are times I have to wait for 4+ seconds for it to become responsive. The camera still has some issues, but after using it for a while (the camera and the phone itself), it seems to get more responsive.
I've also noticed a bit of a battery drain. Now showing any apps that can be causing it. Can't say atm if this is due to the update or not as a few days I have used it more, and according to AccuBattery, my phones seems to have not fully charged last night.

This has bothered me since day one...I've come to the conclusion that chrome was a memory hog...been using opera mini , Nova launcher, disabled apps I don't use along with chrome, disabled all background activity, added home screen shortcuts instead of apps. People have blamed it on adaptive battery but now I get no choppiness even with adaptive battery on ... Worth a shot

Interesting. I've stayed on the January update because of this thread, however, I haven't had many issues with choppiness on my Google 3XL. The only time I've ever experienced any choppiness at all was when using certain custom kernels. But as of the January update, the stock kernel usually gets me at least 5 hours of intensive usage screen on time and so I haven't had the need to use a custom kernel.
And also, I'm super sensitive to choppiness as I'm a PC gamer and play everything at 165fps (and so anything under 60fps burns my eyes lol) - so it's definitely not that I'm just not seeing it.

I don’t think this is a pixel issue , more of an android one. I’m very sensitive to Jank. Hopefully android Q will help but I won’t hold my breath.

Note 10+ - No sound from ear speaker

I've tried all kinds of stuff at this point, %100 know it's software, as I did the cache wipe and it worked for about 10 seconds during a call, then stops. Speaker phone works fine, but it's literally 0 audio otherwise. Tried even the google phone app as well thinking the samsung default phone app might be the issue, but I'm seeing this is happening to others in this thread:
https://r2.community.samsung.com/t5...android-11-update-in-galaxy-a10s/td-p/9197711
This started 2 days ago. This is a major headache for me.
Anyone have any ideas on a fix? or anyone else having these issues?

I wouldn't have upgraded to 11. Samsung uses specific little apks to navigate around Android 10's buggy OS. Over 100 were added to 10 aa compared to 9 to tame 10 down and make it usable. It's even more for 11, no doubt. It may be one of those added on apks that's the issue. Almost impossible to find unless you know which ones specifically to target. In 10 I was impressed by that little nightmare. Samsung is trying very hard, but they have a crapware Android 11's framework and Google's rules to navigate to do this.
Have you updated anything before this happened, if so go back to the factory load version.
Have you installed/uninstalled any apps?
Does it work in safe mode?
Try a network reset.
Try a factory reset if you get desperate, but it's likely to reoccur if you don't find the root cause.
You can use a package disabler to troubleshoot it by disabling apks one at a time, but there are literally hundreds. It will also completely clean apk data leaving no marks; clearing data in settings doesn't always and all it takes is one to screw up some system apps... been there, done that.
Unless you're in wuv with 11, I recommend rolling back to 10 if doable. It would probably save you a lot of time and trouble. Pie is for easier to troubleshoot than 10. I have two N10+'s, one running on 9, one on 10. They will never be upgraded to 11... that's how strongly I feel about it. I'm still getting to know the Android 10 variant's characteristics, so far no major issues.
The one running on 9 is fast and very stable, current load is over 1.5 years old.

blackhawk said:
I wouldn't have upgraded to 11. Samsung uses specific little apks to navigate around Android 10's buggy OS. Over 100 were added to 10 aa compared to 9 to tame 10 down and make it usable. It's even more for 11, no doubt. It may be one of those added on apks that's the issue. Almost impossible to find unless you know which ones specifically to target. In 10 I was impressed by that little nightmare. Samsung is trying very hard, but they have a crapware Android 11's framework and Google's rules to navigate to do this.
Click to expand...
Click to collapse
Well that sucks, I bought the phone used with 11 on it already I guess I need to figure out how to roll it back.
blackhawk said:
Have you updated anything before this happened, if so go back to the factory load version.
Have you installed/uninstalled any apps?
Does it work in safe mode?
Click to expand...
Click to collapse
I haven't installed anything for over a month when it started happening. Doesn't work in safe mode, only works for 1 call after I wipe the cache.
blackhawk said:
Try a network reset.
Click to expand...
Click to collapse
Well, this actually worked, hopefully I can just do the reset if it happens again. It's working on 2 test calls so far so, here's to hoping it lasts. Really appreciate this!
blackhawk said:
Try a factory reset if you get desperate, but it's likely to reoccur if you don't find the root cause.
You can use a package disabler to troubleshoot it by disabling apks one at a time, but there are literally hundreds. It will also completely clean apk data leaving no marks; clearing data in settings doesn't always and all it takes is one to screw up some system apps... been there, done that.
Unless you're in wuv with 11, I recommend rolling back to 10 if doable. It would probably save you a lot of time and trouble. Pie is for easier to troubleshoot than 10. I have two N10+'s, one running on 9, one on 10. They will never be upgraded to 11... that's how strongly I feel about it. I'm still getting to know the Android 10 variant's characteristics, so far no major issues.
The one running on 9 is fast and very stable, current load is over 1.5 years old.
Click to expand...
Click to collapse
The upgrade from 10 to 11 didn't make much a deal to me, they aren't so different that it matters. I do think I'll look into how to downgrade to 10 though.
Appreciate the help!

Yay!
It was just a hidden settings issue. That purge should keep for a while. Occasionally I need to do it for bt on mine as well but never for the phone. Just a semi annoying glitch but not a big deal once you know the trick.
Rollback is likely impossible if it's a factory load because of the bootloader version. Typical of Samsung; I can't roll back my Q variant to Pie.
It depends on the bootloader version vs the rom version. The significant digit is the 5th one from the end. If the rom's 5th digit is the same or higher, you can flash it. If lower than the bootloader's 5th significant digit, no go.
In my case the value is 2.
I'm curious what are your impressions of 11?

blackhawk said:
Yay!
It was just a hidden settings issue. That purge should keep for a while. Occasionally I need to do it for bt on mine as well but never for the phone. Just a semi annoying glitch but not a big deal once you know the trick.
Click to expand...
Click to collapse
Well now it works on and off, very weird.
blackhawk said:
Rollback is likely impossible if it's a factory load because of the bootloader version. Typical of Samsung; I can't roll back my Q variant to Pie.
Click to expand...
Click to collapse
Ugg, that's annoying.
blackhawk said:
It depends on the bootloader version vs the rom version. The significant digit is the 5th one from the end. If the rom's 5th digit is the same or higher, you can flash it. If lower than the bootloader's 5th significant digit, no go.
Click to expand...
Click to collapse
Hmm, mine is a 7, so if I want to rom it I need to get a rom with 7 or higher? This doesn't seem good.
blackhawk said:
In my case the value is 2.
I'm curious what are your impressions of 11?
Click to expand...
Click to collapse
11 is fine, this is my 2nd note, originally had the Note 4 and really loved it. Now this one, while I like the phone has a ton of bloat on it. This Bixby crap is just awful and now this speaker issue is really making me sour to it. I honestly wish I could go to a base build of 10/11 without all the crap added, I dont use any of it because it's just flashy bells with 0 function.

It's not as bad as it looks once you sort it out.
There seems to be around 80 apks I don't want running including lame bixby.
I use this package disabler to take out the trash.
Avoid using power management and the optimization options as they cause trouble... oh yeah is that turned on?!!!
If so, that's probably the cause.
In Device Care>battery, there are a bunch of options, only toggle on fast charging. Use medium power option.
Developer options>standby apps, all buckets should show as active otherwise power management is enabled! That power management enable/disable setting can't be changed here though. If enabled you can change individual bucket settings, but it doesn't work right. Uses more battery and will cause erratic behavior. Android will run fine without it once optimized.
It's not all bloatware, some is useful. Most just sits there and does nothing unless called on.
Some like digitalwell being, kid's whatever, FB, etc are just crapware. Gone.
Starting in 10 there are around at least 100 more smaller apks showing then in 9. These are essential to tone down 10 and 11. The Samsung version of 10/11 are much better than say Pixel's variant of those OS's. They only run when needed and don't seem to cause excessive battery usage.
All cloud crap including Google Backup Transport eat battery. Google play Services and Playstore I keep disabled unless needed. Google, app and carrier feedback, turn off.
Turn off Google Firebase unless you use it.
See if you can find a adb edit to kill scoped storage on your 11 if you want. I think it exist.

What do you use on your Nexus 7 in 2022?

Just curious to see what people use this tablet for these days. I'm trying to find a good use for mine and am coming to the conclusion that if you want what has features its going to come with issues. But Lineage is quite fast just no features.
Curious on others opinions!

Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future

From here ... > ... The best
No need to look at a high Android!

erdar said:
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
Click to expand...
Click to collapse
CrDroid isn't broken but it does have an odd systemUi bug likely to the system partition and other things being so outdated. Whenever restarting the tablet it will continue to respring until it decides to boot the best way to handle this is just to leave it be I've found that more often then not it will eventually start up, other times it refuses to start at all and I will have to reboot again most times I try to refrain from turning it off. Unfortunately this seems like the only way to get good features for this tablet. Wishing someone would take interest like forkLineage or EvoX perhaps

Mr.Conkel said:
"CrDroid isn't broken but it does have an odd systemUi bug ....."
Click to expand...
Click to collapse
I agree, although I prefer pixel experience (and the like).
As for the CRDROID ... My problem was that the curtain does not open, and many programs were not launched, and there was an arrow in the bar, which is displayed only when the navigation bar is two Buttons, and I had gestures enabled) Very strange, actually. It's funny that it all started after the ROM crashed .. I still wanted to try at least lineage 18.1, but after reinstalling a12 I'm too lazy

Running unofficial LineageOS 17.1. I don't really use the tablet or anything really. My touch screen doesn't really work, along with the tilt sensor. It's really slow which is to be expected. I use my Fire 7 since it's faster and less frustrating to use.

I pulled my old nexus out from the cupboard a few weeks ago and was amazed that the battery still had decent life after yrs not being used. I managed to unlock bootloader and install twrp before the micro USB charging port stopped working. I now have DotOS android 9 installed and am using the nexus as my eReader, charging via Qi wireless

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.