Related
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)
First off, I disabled adaptive battery in Android P. Ever since the upgrade from 8 to 9, I noticed that notifications are right around 5 minutes late. I have a couple time-sensitive apps that I need notifications right away. Gmail and another app for my home automation. In Android 8, the were flawless. However, ever since going to 9, not so much.
I also noticed that when I delete messages in the gmail app for gmail and an IMAP email server I have it does nothing with the messages on the server. I login to webmail from a computer and the messages are still in the Inbox.
Anyone have any ideas? I am going to try a wipe again to see if it resolves the issues, but I am out of ideas. I had the above issues in Android 9 beta as well. I would downgrade and it fixed them.
I have the same thing and it turns out it is a common issue with Pie. I have not found a solution yet. I have read all kinds of things people have tried and nothing seems to help. Sorry that I can't be more positive. Hopefully Google will figure something out and fix in an update.
Here is a two page post I started about the issue but there are also many others online describing the same thing:
https://forums.androidcentral.com/android-pie/904647-notifications-delayed-stopped.html
My thought is that the delayed notifications are due to Android Pies implementation of adaptive battery. Maybe try excluding the apps you want to receive notifications from in a timely manner?
Sent from my Pixel 2 XL using XDA Labs
You don't happen to have data saver in the quick tiles turned on by accident do you? That does prevent notifications from getting pushed. Both my parents had this on and a bunch of notifications came through after turning it off. I made sure to remove it from even being an available option.
Sent from my Pixel 2 XL using Tapatalk
been fighting with this issue as well, but it only seems to be gmail, and a couple other apps, my sms notifications seem to come through fine, at least as far as I can tell. I've turned off adaptive battery etc, nothing seems to make a difference. sometimes i can turn my screen on and all the notifications will come flooding in, other times they come through 10ish min later.
yes i have also these issue
and i opened thread on these https://forum.xda-developers.com/pixel-2-xl/help/gmail-sync-problems-pie-t3839357
also i tried many apps, but instead of gmail but yet i didn't find any solution
Triscuit said:
My thought is that the delayed notifications are due to Android Pies implementation of adaptive battery. Maybe try excluding the apps you want to receive notifications from in a timely manner?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion but that is one of the first things I tried. No difference.
EeZeEpEe said:
You don't happen to have data saver in the quick tiles turned on by accident do you? That does prevent notifications from getting pushed.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Made sure it was off early on. No change.
The best way to describe my issue is that once the screen times out and has been off for at least about 5 minutes, notification sounds are delayed. It is sort of like the phone goes into a deeper sleep or something and then the problem arises. As soon as I use my fingerprint to wake the phone, all notifications blast through.
The delay can vary. Sometimes it is only 15 minutes or so, but often it is much longer. It is almost like once in a while an app wants to call home or something and to do so wakes up the phone just enough to allow some notifications through.
There also seem to be some issues with individual apps and notifications that may be fixed when a developer updates their app for Pie. For example, most apps notify immediately when the screen is on or within that first 5 minutes or so after the screen goes off. But since installing Pie, Kuna always has a delay of 5 to 10 minutes before notifying. Kuna does this 100% of the time. In fact if I have the phone awake, looking at the screen when walking out the front door, when the motion sensor is triggered, immediately there is a notification icon. But the sound notification is always delayed. This seems like an issue with Kuna and they are well know for being very slow with updates and fixes but eventually they do fix things. But the notification sound delays described in this thread do indeed seem like a system issue with Pie. Hopefully enough people will have the issue that Google will figure it out and fix.
I am having same issues after updating to Android P. At first, notifications came late about 5 min, but then they started to vary some coming in 15-30 minutes later. Can't figure out what is causing the time difference but either way I can't find a fix. I spoke with Google support and they had no fix as well.
sammys8 said:
I spoke with Google support and they had no fix as well.
Click to expand...
Click to collapse
Did Google give you any indication they were aware of the issue and trying to fix?
Will_T said:
Did Google give you any indication they were aware of the issue and trying to fix?
Click to expand...
Click to collapse
Nope, they didn't mention anything about existing issues or being aware of the issue.
Any one found any solutions or fixes? I feel like my notifications are becoming even more delayed now and have also realized I'm not getting a lot of various notifications at all (through many different apps).
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
3yoders said:
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
Click to expand...
Click to collapse
Just updated some settings, now we wait and see if these buried settings fix my delays.. here's to hoping! :good:
3yoders said:
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
Click to expand...
Click to collapse
One of the first things I tried was giving full useage, (no battery optimization) for all apps that I want notifications from. Did not help. Many other apps are still being optimized. I thought I had previously found a way to turn off all battery optimization but because I do have many apps in that list that are being optimized, I obviously did not. Right now I can't find a global setting to turn off battery optimization even though I thought I did before?
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand. Even after going through all the battery save features and making sure this app is exempt from them, it still happens if the screen is off, or my phone is off the charger. super annoying. wish there was a fix for this already!
pvtjoker42 said:
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand. Even after going through all the battery save features and making sure this app is exempt from them, it still happens if the screen is off, or my phone is off the charger. super annoying. wish there was a fix for this already!
Click to expand...
Click to collapse
Verizon sent me a replacement because of this problem. I was apprehensive, but got a very nice re-furb. Still have the same problem, but I got a phone that is indicated as Verizon on the LG site. In developer mode, the bootloader unlock button works. I guess everything isn't bad. I sure hope Google straightens this out soon.
pvtjoker42 said:
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand.
Click to expand...
Click to collapse
This happens only with Gmail on my phone - WhatsApp and Messages send instant notifications. Messages isn't optimized, the other apps are.
I can live with that, no big deal. Perhaps disabling battery optimization for Gmail would fix this, though.
Interesting note: I was talking to YouMail support today about something else but I asked about an issue where I get an email and transcript of a new voicemail but when I go to the YouMail app that voicemail is not shown until I drag down from the top of the screen to refresh the list. Support told me they are aware of this but can not do anything because it is a problem with the "latest Android version causing delay". So it is becoming a more widely known issue and hopefully Google will fix soon.
Thanks for all the feedback. Speaking of delay, I think I have tried just about every fix here and then some and still no luck. Wiping the phone did nothing as well. At this point, I would almost like to revert back to v8 to get this fixed.
I tried this supposed fix, (reply #51). https://forums.androidcentral.com/a...ifications-delayed-stopped-3.html#post6355714
No idea if it worked for me as when you restart the phone you need to do it again and less than 30 minutes after I went through the steps, my Pixel2 got the October update for Pie and required a restart!
Hi Guys,
I've been having a real hard time with this phone, I am sitting on the MIUI 10 stable global rom at the moment and I was wondering if you guys turn off MIUI optimization at all (in the developer settings) I'm not entirely sure what it does, but toggling it wipes out alot of permissions.
I've got 2 big issues with this phone. the Video Chat mic bug (Which I have seemed to get around by using WhatsApp for video chats)
The other being Android Auto not connecting all the time. I was wondering if maybe because this MIUI optimization is like a task killer that keeps killing stuff in the background?
When I need Android Auto to work, all I have to do is toggle USB Debugging and it fires up right away. Very strange, but it works for now.
Side Note for Xiaomi, Why do you need to lock down the phones like this? Android memory management works great, please don't mess with it. I just don't understand why we have these extra layers of security and permissions. It really messes with any third party apps, what an ordeal it is to get notifications working for example on any third part texting app. I have to go into like 3 different areas and then only sometimes it works. Please leave android alone, it works fine the way it is
I just turned them off. I guess we'll see how it goes.
I recently installed Lineage OS 17.1 on my Essential PH-1 (mata). I'm loving it besides this increasingly annoying issue. It seems that notifications are delayed while the phone is locked (screen off). Usually the delay is only a few minutes (3-5), but sometimes if my phone has been locked for a long time (1+ hours) the notifications will also be about an hour delayed. The apps I primarily notice this in are the included messages app and BlueMail. I think it probably affects all apps, but I don't really get notifications from other apps often enough to notice. I've tried updating to version 20200615 but I get the same result.
Any ideas? Thanks.
megustamata said:
I recently installed Lineage OS 17.1 on my Essential PH-1 (mata). I'm loving it besides this increasingly annoying issue. It seems that notifications are delayed while the phone is locked (screen off). Usually the delay is only a few minutes (3-5), but sometimes if my phone has been locked for a long time (1+ hours) the notifications will also be about an hour delayed. The apps I primarily notice this in are the included messages app and BlueMail. I think it probably affects all apps, but I don't really get notifications from other apps often enough to notice. I've tried updating to version 20200615 but I get the same result.
Any ideas? Thanks.
Click to expand...
Click to collapse
You can try to disable battery optimisation for the apps you expect notifications
kurtn said:
You can try to disable battery optimisation for the apps you expect notifications
Click to expand...
Click to collapse
Just disabled it for messaging services (it wasn't available for messaging), but I still get delayed notifications.
Same problem here. Tried disabling battery optimization. Tried PNF fixer. No email or SMS notification unless I unlock my phone. Using a OnePlus 3T.
Just found this XDA thread after searching for a solution for this issue on my Essential PH-1 running LineageOS 17.1 20201207-nightly. The fix that worked for me was found over in this Reddit post. In short, enter a command using ADB and reboot the phone. I've had success with this workaround. Hope it helps somebody with the delayed notification issue.
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.