Related
Hello,
I've done lots of searching for answers to my questions here and elsewhere and come up empty-handed, so I apologize if I've missed something and this has been covered already.
My phone occasionally runs smoothly and fast, like it's supposed to. More often -- pretty much every time I need to interact with the phone and across all apps I use -- it freezes when I tap on something, whether it's to open an app or interact with an app that's already running. It will completely freeze up for anywhere from five to 15 seconds before reacting, and it's extremely frustrating at times. Sometimes, the screen will time out before I can enter my PIN to unlock it; sometimes when somebody calls and I tap "answer," the phone doesn't react fast enough to actually answer and I miss the call. As I said, very frustrating. It did this both before the update to Lollipop last week, and after.
Here's what I've tried: Hard reset; restarting; deleting or disabling all the apps (including Blinkfeed) I thought I safely could, usually just one or two at a time. I've run it in safe mode, and the phone works normally that way -- I just can't figure out what's making it freeze up. I've run a CPU monitor program, and haven't seen any huge spikes from any apps; and according to the app manager in settings, I typically have about 1G of RAM free.
I'm very hesitant to root the phone, mostly because this is a warranty replacement for a Verizon M7 I had rooted (and returned to stock), and none of the ROMs I tried with the previous phone worked well -- if at all -- with the security policies I am required to use to log in to my employer's Exchange server. Those policies include data encryption.
I'm running stock Lollipop 5.0.2 and Sense 6.0 on Build number 6.22.605.3, Baseband 1.13.41.1209.
If anybody has ideas for me to try, I'd greatly appreciate it. My upgrade date is late August of this year, but it's getting harder and harder to live with this phone, which I absolutely need for my work.
Thank you very much in advance.
It's been a month now since the Lollipop update. I have read through a few threads about performance issues in general after the update. I am going to assume that your phone too has become a victim of the update. I have NOT updated to Lollipop. Mainly because of my recent root and install of TWRP custom recovery, EX Kernel and ViperROM 7.0.2. If these issues aren't resolved, I will not update. Besides, KitKat is doing great for me. I would suspect certain services not running in safe mode that allow the phone to react normally as opposed to all services running in normal mode. Have you contacted VZN and/or HTC for possible t/sing solutions? I see that you have done what I would've done. After failing I would assume it is because of the Lollipop update
So far I never rooted or flash any rom manually. All OTA updates from Android 6. The phone is getting slow and laggy sometimes which really annoys me. Of course the number of apps installed might be an issue, but I don't have any games, no Facebook. All my apps are utilities like banks, smart homes, etc. I have hard reset a few times but it doesn't help. I believe the updates play some roles here as I didn't remember it being this laggy when I first bought the phone and it was on 6.0
So what should I do? I don't care if it's Android M or N, root or not. I just need a smooth phone. Does flashing back to 6.0 help? Or does rooting help? Thanks
Have you tried backing up your data and doing a factory reset?
Edit: Sorry, I guess that's the same thing as a hard reset. I don't have problems with my S7A being slow, and it's updated to almost the latest version (G1).
I am on BQH1 but I remember it happens in G1 as well. The most annoying thing is the fingerprint ready is not as responsive as before. A lot of time I can't unlock my phone with my finger.
yes , i have noticed after the new update take long time to wake etc , even after the factory reset , i am planning to go back marshmallow
but the interesting thing is that some times its OK no issues .
Slow Updates
Since upgrading to 7.0 Nougat my Play Store is slow as hell. Downloads are fast once it finally connects but it takes forever to start. I have factory reset phone.
Does anyone got a fix on this? The phone is just slow as hell, and I often find it's hard to unlock it, or just open an app...
lifehome said:
Does anyone got a fix on this? The phone is just slow as hell, and I often find it's hard to unlock it, or just open an app...
Click to expand...
Click to collapse
Disabling some system apps (AT&T and Samsung bloatware) should help, using Application Manager. Disable apps that have no business running in the background or connecting to the net. Also, run Device Manager from time to time.
To make the Home button significantly responsive, DO NOT map it's double-press action to anything. Make sure that S-Voice cannot use it: disable in S-Voice settings.
I am assuming that your device is non-rooted, just like mine.
I belive earlier updates of Nogat works much MUCH more smooth on this phone.
I'm gonna start over from the D4 verison- I was running stock D4 nogat and everything was amazing... I go to this latest L6 December security update... total trash.
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)
I have seen too many horror stories on here and on the internet with Android 10 and the pixel 2XL to think that I won't have at least one of them if I make the update. The biggest and most concerning complaint I see is crazy battery drain. There have been people having boot issues. There are complaints of root causing issues or not working. There is a whole thread of viper for Android being difficult to implement on Android 10. I have seen threads and articles about weird Wi-Fi connectivity issues. I'm sure there are some other major complaints that I haven't seen or I'm not thinking about this moment.
has the October update fixed any of these? I'd love to do a clean install when I go to Android 10. Since stuff is lost when you do clean installs- idc what ya say, the backups never get everything- I don't want to go to Android 10, have a bunch of issues, and just end up rolling back to Android 9. Then I'm just out a bunch of time and data. I don't want to go to 10 until these major issues are resolved.
I've been on 10 since the Q4 beta and haven't had any major issues - but I'm quite a narrow user, generally have everything switched off except wifi/mobile data, and basically only use it for web browsing/reddit mostly, with occasional pics and sometimes music in the car. But I tend to get 9 hours SOT daily as long as I have signal (I'm often out of signal and get 6.5 hours SOT in those days)
Asides from that it's been solid for my use, I couldn't go back now as I really like gestural navigation, and I haven't noticed any glitches/bugs - best thing I done for battery life was installing Blokada.
Battery is just as good as it was on Beta 4, I have no boot issues and Magisk rooted the phone just fine. The only problem I have is /system and /vendor not mounting but this wont be fixed for awhile according to John Wu because Google changed how they mount in Android 10. If you do install the October update do a fresh install not an upgrade, I bet most of the issues you are describing are due to people upgrading from Pie or the beta and not wiping the phone when they do said upgrade.
i have some issues after upgraded to android Q, i have boot issue which take a long time approximately 5-10 minutes to boot, also my device cannot connect to any wired things ( connect to pc, dongle jack etc). And latest update didn't fix this issues
Did you dirty or clean flash? What's about the rest of you guys who have had good experiences?
Schroeder09 said:
Did you dirty or clean flash? What's about the rest of you guys who have had good experiences?
Click to expand...
Click to collapse
I dirty flashed from 9 to 10. Then dirty flashed again to October update. I fastbooted into twrp, installed twrp 3.3.0-0 image to recovery ramdisk, rebooted to twrp, flashed magisk, then Ex kernel, rebooted, and all is well for me :good::good:
Schroeder09 said:
I have seen too many horror stories on here and on the internet with Android 10 and the pixel 2XL to think that
I won't have at least one of them if I make the update. The biggest and most concerning complaint I see is crazy battery drain. There have been people having boot issues. There are complaints of root causing issues or not working. There is a whole thread of viper for Android being difficult to implement on Android 10. I have seen threads and articles about weird Wi-Fi connectivity issues. I'm sure there are some other major complaints that I haven't seen or I'm not thinking about this moment.
has the October update fixed any of these? I'd love to do a clean install when I go to Android 10. Since stuff is lost when you do clean installs- idc what ya say, the backups never get everything- I don't want to go to Android 10, have a bunch of issues, and just end up rolling back to Android 9. Then I'm just out a bunch of time and data.
I don't want to go to 10 until these major issues are resolved.
Click to expand...
Click to collapse
Schroeder09 said:
Did you dirty or clean flash? What's about the rest of you guys who have had good experiences?
Click to expand...
Click to collapse
I know how you feel…I was pushing/pushed it off for as long as I could – til the very least TWRP having write access. But then I read/heard on how the October update specifically addresses some pretty serious security issues/threats!
I dirty flashed/updated to 10, but I made sure to remove any screen-lock and all my Magisk modules – but then found some issues later on where it would’ve been better to uninstall Magisk all together, rather than just the modules.
There are always little hitches that can (and do) come up, but it’s only actually experiencing them that you know whether it’s a worth it enough compromise or not. I say, update it, and if you have issues as big as booting, crashing, or rooting related things, then (as you say) you can always downgrade back to where you’re comfortable and “hitch-less”. But, if it’s Viper (or 1-or-2 apps specifically) just going a little wonky and/or you don’t really rely on, or even battery life (if you get [just] enough anyways), or dark-theme related, then those types of things you can learn to live with and/or “deal” with in the meantime – and it will merely be a bit of an annoyance for the beginning; which, with any kind of upgrade, is usually the case no matter at what point in its version life-cycle. Especially if it’s a “sort-of works” kind of situation. Also, if there are “workarounds” in place as well; then at least it’s not absolutely and totally impossible & incompatible. Then, as always, if it gets too much or too annoying, it’s not that you can’t downgrade and start-over.
I would say my experience is still a mixed bag; but feel I’m on the latter side of things where it’s “buggy”, but not critically and works juuuust enough that it’s not too impossible to get what I want to get done, done. My only real complaint is with the no-button “Gesture navigation”; how can Google NOT include a way to go to your primary homescreen?! It’s not as if the Home button really only had one function nor has it even been that way in the distant enough past to not know better. But at least that was easy enough to revert (as they gave the option)…
Just something to keep in mind…good luck!
Schroeder09 said:
Did you dirty or clean flash? What's about the rest of you guys who have had good experiences?
Click to expand...
Click to collapse
I did dirty flash, and now i really want to downgrade to android 9 but i can't because my device wont connect to my pc
My phone occasionally reboots. It has a bug related when you keep pressing back on apps, and there's a few others that I can't remember. It's been like this since beta 5. This android update is a joke and I'm amazed that it ever hit *stable*
There are several kinds of Android 10 bugs which generally users come across after update. Here I have listed some Android 10 bugs and with their solutions. No matter whatever types of bugs you are coming across in your phone after Android 10 update, here are the list of Android 10 bugs and their solutions.
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.