Related
Almost every Samsung android phone I've own has this problem after using it for a period of time. I've had the note 10+ since launch and the dreaded issue has return.
For some apps, I would tap the notification for the app. It would take a few minutes before the app will open.
Anyone has this issue?
I've had it on my note8, Note9 and now the note10+.
Hard reset will fix it but I don't want to reset and start again..
Continuation from note 8 thread: https://forum.xda-developers.com/galaxy-note-8/help/app-lag-clicking-notification-t3781356/page2
I don't have this issue.
Some people prefer to perform an hard reset as soon as they got the phone, before starting using it for the first time ; maybe they had some issues like yours at first, then wanted to avoid them.
Personally I didn't got any at first run.
That's odd, I have not experienced what you say in any of my samsung devices dating from my beloved S3 to this note10+
Yes..i am so confuse why it happens.. When the phone is new or just had a hard reset.. I don't have the issue.. Over time I always get it.
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Is it all apps or certain apps only? Are you running stock or rooted? Exynos or Snapdragon? I haven't seen this issue shown up in a while, but have had it happen on Android devices in general in the past.
aarick said:
Almost every Samsung android phone I've own has this problem after using it for a period of time. I've had the note 10+ since launch and the dreaded issue has return.
For some apps, I would tap the notification for the app. It would take a few minutes before the app will open.
Anyone has this issue?
I've had it on my note8, Note9 and now the note10+.
Hard reset will fix it but I don't want to reset and start again..
Continuation from note 8 thread: https://forum.xda-developers.com/galaxy-note-8/help/app-lag-clicking-notification-t3781356/page2
Click to expand...
Click to collapse
Aaron J said:
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Click to expand...
Click to collapse
I don't have this issue, but as @dhorgas, more info would be helpful if it's a problem that can easily be fixed.
Two have the issue here, It could be a common app both of you are running.
lennie said:
I don't have this issue, but as @dhorgas, more info would be helpful if it's a problem that can easily be fixed.
Two have the issue here, It could be a common app both of you are running.
Click to expand...
Click to collapse
It seems to be related to pendingIntent type notifications as if I tap a notifications that is a collapsed version of all the notifications, the app will load instantly. Have a look at this video I created:
(I didn’t include the tap showing on screen unfortunately, will attempt to do another video next time)
Initial tap was when the notification is collapsed for reolink and that will just open up the app. Happens instantly.
I close the app, expanded the notification and click on specific notification
The app doesn’t open until 8 minutes + later towards the end of the video.
Issue is happening across a fair few apps so I doubt it's common app..
I also have the issue of delayed notifications as discussed here:
https://eu.community.samsung.com/t5...ue-affecting-all-range-of-Samsung/td-p/738070
dhorgas said:
Is it all apps or certain apps only? Are you running stock or rooted? Exynos or Snapdragon? I haven't seen this issue shown up in a while, but have had it happen on Android devices in general in the past.
Click to expand...
Click to collapse
Stock on exynos
Aaron J said:
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Click to expand...
Click to collapse
Have the same issue with the play store. One way to speed it up is to force close play store... Then reopen it..
The app will redownload and should install this time.. Not always..
Quick update: Got fed up and did a factory reset and restored everything. Everything's working fine now. Obviously that's a last resort, but so far it's the only solution I've seen.
aarick said:
It seems to be related to pendingIntent type notifications as if I tap a notifications that is a collapsed version of all the notifications, the app will load instantly. Have a look at this video I created:
(I didn’t include the tap showing on screen unfortunately, will attempt to do another video next time)
Initial tap was when the notification is collapsed for reolink and that will just open up the app. Happens instantly.
I close the app, expanded the notification and click on specific notification
The app doesn’t open until 8 minutes + later towards the end of the video.
Issue is happening across a fair few apps so I doubt it's common app..
I also have the issue of delayed notifications as discussed here:
https://eu.community.samsung.com/t5...ue-affecting-all-range-of-Samsung/td-p/738070
Click to expand...
Click to collapse
Wow. That would drive me crazy. Try backup, hard reset and restore like @Aaron J did and see if that fixes the issue.
lennie said:
Wow. That would drive me crazy. Try backup, hard reset and restore like @Aaron J did and see if that fixes the issue.
Click to expand...
Click to collapse
Yes.. It will fix it.. But it's temporary..
The issue won't happen straight away.. It takes a few weeks/months and will return.. It has happened to me from the note 8, note 9 and now note 10+.
Initially everything will be good and fast.. Then eventually issue will return..
So need to try to get to the root of it..
Aaron J said:
Quick update: Got fed up and did a factory reset and restored everything. Everything's working fine now. Obviously that's a last resort, but so far it's the only solution I've seen.
Click to expand...
Click to collapse
Hope the issue doesn't return for you.. It always returns for me..
I have been dealing with 3 issues in my phone:
-delayed notifications
-slow app opening when tapping notifications
-apps installation through play store delayed after download
So recent development, I have been following this thread on Samsung forums regarding delayed notifications
https://eu.community.samsung.com/t5...ting-all-range-of-Samsung/td-p/738070/page/28
Have tried all the fixes which has given minor relief..
But the last suggestion to disable dynamic lock on windows 10 seems to have fixed the issue for me. Early days but all 3 issues have not reoccured yet today.. Usually my Samsung reminders will not show until I reboot. But today been good so far.
Apps install instantly and apps open from notifications straight away..
Will report back in a few days if anything changes..
aarick said:
I have been dealing with 3 issues in my phone:
-delayed notifications
-slow app opening when tapping notifications
-apps installation through play store delayed after download
So recent development, I have been following this thread on Samsung forums regarding delayed notifications
https://eu.community.samsung.com/t5...ting-all-range-of-Samsung/td-p/738070/page/28
Have tried all the fixes which has given minor relief..
But the last suggestion to disable dynamic lock on windows 10 seems to have fixed the issue for me. Early days but all 3 issues have not reoccured yet today.. Usually my Samsung reminders will not show until I reboot. But today been good so far.
Apps install instantly and apps open from notifications straight away..
Will report back in a few days if anything changes..
Click to expand...
Click to collapse
So ... did this do it? I've been dealing with this for a LONG time. My Note 8 started this crap after the 9 'upgrade', motivated me to get a new Note 10. A few months later, the SAME exact problem is cropping up.
Slow notification reactions, stuck installs, notifications coming in repeatedly, notifications coming in late all at once.
If this isn't resolved soon, my next phone will definitely not be a Samsung.
nokster said:
So ... did this do it? I've been dealing with this for a LONG time. My Note 8 started this crap after the 9 'upgrade', motivated me to get a new Note 10. A few months later, the SAME exact problem is cropping up.
Slow notification reactions, stuck installs, notifications coming in repeatedly, notifications coming in late all at once.
If this isn't resolved soon, my next phone will definitely not be a Samsung.
Click to expand...
Click to collapse
Yes, my issue is gone now. Try removing windows dynamic lock and unpair your phone from your laptop if you have this setup.
If not, try slowly removing other Bluetooth devices.
For me, a Bluetooth yeelock also caused the delay to return..I have to reboot each time after using the lock to get it back to normal.
I also think a plantronics desktop headset was also causing the issue as I was getting the lag everytime I reach home since removing windows dynamic lock. I have since unplugged it and unpaired. So far been good for a few weeks now.
I heard this issue wasn't specific to Samsung but might be an Android issue..i think it started with Android 9.0 as you have mentioned as I never had this issue when I was using the note 8 before one ui.. But note 9 and 10+ both had issues..
Similar issue mentioned on pixel phone support:
https://support.google.com/pixelphone/thread/5024453?hl=en
aarick said:
Yes, my issue is gone now. Try removing windows dynamic lock and unpair your phone from your laptop if you have this setup.
If not, try slowly removing other Bluetooth devices.
For me, a Bluetooth yeelock also caused the delay to return..I have to reboot each time after using the lock to get it back to normal.
I also think a plantronics desktop headset was also causing the issue as I was getting the lag everytime I reach home since removing windows dynamic lock. I have since unplugged it and unpaired. So far been good for a few weeks now.
I heard this issue wasn't specific to Samsung but might be an Android issue..i think it started with Android 9.0 as you have mentioned as I never had this issue when I was using the note 8 before one ui.. But note 9 and 10+ both had issues..
Similar issue mentioned on pixel phone support:
https://support.google.com/pixelphone/thread/5024453?hl=en
Click to expand...
Click to collapse
I don't have Dynamic Lock set up, nor do any of my computers have bluetooth enabled. BUT I do have this cursed Plantronics PLT W8200 series headset that has been nothing but buggy since I got it. Not surprised if this is the cause. I just unpaired it - fingers crossed.
I hope that's it because otherwise, it's just 2 other pretty crucial devices I have paired.
nokster said:
I don't have Dynamic Lock set up, nor do any of my computers have bluetooth enabled. BUT I do have this cursed Plantronics PLT W8200 series headset that has been nothing but buggy since I got it. Not surprised if this is the cause. I just unpaired it - fingers crossed.
I hope that's it because otherwise, it's just 2 other pretty crucial devices I have paired.
Click to expand...
Click to collapse
Would be good to hear if this fixes your issue. Please make sure you reboot after unpairing too and if possible completely unplug the plantronics as I think it might try to connect to your phone still (but fail) and potentially still bring the issue back as my yeelock doesn't even show up as a paired device, the app just sends msg to it via bluetooth and I still have delays after using it.
Keep us updated...
aarick said:
Would be good to hear if this fixes your issue. Please make sure you reboot after unpairing too and if possible completely unplug the plantronics as I think it might try to connect to your phone still (but fail) and potentially still bring the issue back as my yeelock doesn't even show up as a paired device, the app just sends msg to it via bluetooth and I still have delays after using it.
Keep us updated...
Click to expand...
Click to collapse
So after the weekend of having the Plantronics headset un-paired, it *seems* better. Hopefully it stays that way.
Does anyone else have this issue where you are swiping and it will suddenly freeze and you have to wait for it to unfreeze, maybe Gboard needs updating for Android 12
Shipoftheline said:
Does anyone else have this issue where you are swiping and it will suddenly freeze and you have to wait for it to unfreeze, maybe Gboard needs updating for Android 12
Click to expand...
Click to collapse
Not specifically Gboard, but quite literally only just today I've been getting some little lags on my Pixel 6 Pro and experience the same freeze on SwiftKey.
Running Kirisakura and all has been well with no new apps installed recently, but indeed today been getting some weird brief lags....
Unsure what the cause could be, but thought I'd share my experience nonetheless
I had a ton of Android 12 issues that were tangentially related to Gboard: minimize arrow persisting even when the keyboard wasn't visible, mysterious System UI ANRs after using the keyboard, etc. At some point I had opted in to the Gboard beta and opting out to the production release build fixed all of my issues.
Yes. Sporadically
I've been having intermittent issues with both Gboard and Swiftkey. There's been a few times when the keyboard doesn't display when I'm trying to message or send an email. I have to restart the phone. A bit of a pain in the butt. BTW, I have not received the December update.
xSDMx said:
I had a ton of Android 12 issues that were tangentially related to Gboard: minimize arrow persisting even when the keyboard wasn't visible, mysterious System UI ANRs after using the keyboard, etc. At some point I had opted in to the Gboard beta and opting out to the production release build fixed all of my issues.
Click to expand...
Click to collapse
Trying the beta version now to see if that fixes it
I do also encounter some lag when typing. Already contacted google support about it. You can either wipe your phone, if the problem isn't gone you are able to send it in for warranty.
I assume it is a software problem, so I won't do anything for now.
But glad to see there are more people who have the same problem.
MacLaughlin said:
I do also encounter some lag when typing. Already contacted google support about it. You can either wipe your phone, if the problem isn't gone you are able to send it in for warranty.
I assume it is a software problem, so I won't do anything for now.
But glad to see there are more people who have the same problem.
Click to expand...
Click to collapse
As you worked out seems pointless wiping the phone when its most likely a software issue, the Gboard beta is so far ok for me
I've switched from beta to stable
I do also encounter lagging when browsing in chrome or switching between recent apps. Not a huge deal breaker, but it should be fixed
Maybe this is the cause
https://www.reddit.com/r/GooglePixel/comments/rpokg3
Shipoftheline said:
Maybe this is the cause
https://www.reddit.com/r/GooglePixel/comments/rpokg3
Click to expand...
Click to collapse
Oh I'm glad this is being recognised! As whilst I don't use Gboard (SwiftKey instead) I have the lags, which aren't just typing but also when scrolling and so this lag explanation of occurring when the battery percent drops makes sense as it is very much intermittent.
Will hope to see a fix soon.
This is getting worse for me, was out typing before when it just locked and then after a few seconds a load of gibberish came out
I wonder if this is the cause of some entire screen lock-ups for some of us until we turn the screen off and back on?
zetsumeikuro said:
I wonder if this is the cause of some entire screen lock-ups for some of us until we turn the screen off and back on?
Click to expand...
Click to collapse
I had one where the screen was 100% locked, couldn't turn the screen off or the phone itself for 5 minutes................no way of a hard reset etc so I was worried about screen burn, lucky it reset itself after 5 minutes
Shipoftheline said:
I had one where the screen was 100% locked, couldn't turn the screen off or the phone itself for 5 minutes................no way of a hard reset etc so I was worried about screen burn, lucky it reset itself after 5 minutes
Click to expand...
Click to collapse
Damn, that's pretty bad and I haven't experienced a lock-up of that level. Have you experienced the lesser lock-ups as well? The one that I described in addition to your five minute lock-up?
zetsumeikuro said:
Damn, that's pretty bad and I haven't experienced a lock-up of that level. Have you experienced the lesser lock-ups as well? The one that I described in addition to your five minute lock-up?
Click to expand...
Click to collapse
The small ones while typing
Shipoftheline said:
The small ones while typing
Click to expand...
Click to collapse
If it is the Accessibility Services issue plaguing others, it's pretty crazy how extreme the issue is for some. Vs the small delays/hithces that I've read, the majority are suffering. Hopefully Google fixes this soon as I don't want to play device lottery with a refurb.
zetsumeikuro said:
If it is the Accessibility Services issue plaguing others, it's pretty crazy how extreme the issue is for some. Vs the small delays/hithces that I've read, the majority are suffering. Hopefully Google fixes this soon as I don't want to play device lottery with a refurb.
Click to expand...
Click to collapse
The only real Accessibility setting I used was dark mode either way this has been going on since October so I'm going to try this new patch from (Jan) Google but if it hasn't fixed it I'm gone and will never buy a Google device again, I found not being able to swipe text etc without freezing for all this time is just pushed me to far now
Shipoftheline said:
The only real Accessibility setting I used was dark mode either way this has been going on since October so I'm going to try this new patch from (Jan) Google but if it hasn't fixed it I'm gone and will never buy a Google device again, I found not being able to swipe text etc without freezing for all this time is just pushed me to far now
Click to expand...
Click to collapse
I just had it happen once on a fresh install of the Jan build when I was scrolling through Discord. Haven't updated the apps yet so that could of been why. I also ran the Pixel repair tool and I'll see if it happens again. It is pretty annoying when it happens and having to stop what you're doing to turn the screen off and on again. Don't really want to deal with Google during a time where their support is non-existent and end up getting a scratched up, dinged up refurb replacement. That or get a replacement and the same crap happens.
The freeze looks like this: https://i.imgur.com/jelcWFR.mp4
If your device freeze like that, it's probably the same bug.
I've seen this issue discussed multiple times on reddit.com/r/GooglePixel but no one found the root cause of the issue: here, here2, and other threads.
How to temporary fix the bug
Disable all accessibility features from Settings -> Accessibility.
Disable Voice Access, Accessibility shortcut, and all the other accessibility apps, features or services. System or downloaded apps, doesn't matter, disable all of them.
How to fix the bug
Unfortunately, this can be done only by Google. The bug is inside the Google Android 12 for Pixel 6/6 Pro.
Star this issue: https://issuetracker.google.com/issues/212049949 to increase the chance of Google fixing it.
How to reproduce the bug
The touch input (looks like the screen) will freeze for 1-2 seconds each time the battery drops 1% when there is an accessibility service enabled with "canPerformGesture" permission.
Steps:
Enable any Accessibility Service/Feature that has "canPerformGesture" permission (an accessibility service that can tap on the screen on behalf of user).
You can try this dummy app that does nothing, it only triggers the bug: pixel_6_accessibility_service_freeze_bug_v1.apk
Use your device normally and when the battery drops 1% the touch input will freeze for 1-2 seconds and then will unfreeze and do rapidly all the touches registered in the freeze period.
Dummy App to reproduce the bug
The Dummy app I created it is available here: https://github.com/micku7zu/PixelAccessibilityLag
APK available here: pixel_6_accessibility_service_freeze_bug_v1.apk
It does absolutely nothing with the accessibility service, just requests the permission to trigger the bug. You can check the accessibility service code here: https://github.com/micku7zu/PixelAc...cessibilitylag/PixelAccessibilityService.java
Disclaimer
I don't own a Google Pixel 6 or 6 Pro. I'm a developer of an app that needs accessibility services to work and a user reported this strange issue to me when he has my app enabled in Accessibility settings. We've worked together and found the root cause of the issue and created the issue on Google Issue Tracker.
Thanks @Burrro - Xda for reporting the bug and helping with investigation to find the root cause
Star the issue if you have the bug: https://issuetracker.google.com/issues/212049949
Thank you for this! Apparently it was KDE Connect forcing me to run into towers in Wild Rift. Thought it was just the phone lagging a bit this whole time
Good news: 138 people have starred this issue and the bug was assigned to product and engineering team. Hopefully they will fix the issue now.
Hey, I just registered to come here and say thank you! This was driving me crazy. My old Pixel 3 XL was also lagging and I thought that it would just be a bit old and bloated. When I switched to my Pixel 6 Pro and had lags again, I was very disappointed and thought that it really would have something to do with my specific setup, so I uninstalled heavy apps like MacroDroid and Gravity Screen, but it didn't help. As I said, at this point it was really driving me crazy and I just lived with it. To see the explanation of the bug and that it happens every time the battery percentage drops was just such a relief! It all makes sense now. I will have to live with it until Google fixes it, cause I really need all my apps that have accessibility services. Again, thanks so much!
Edit: Disabled my apps for a quick test. Indeed, the phone does not lag anymore when the battery drops. I enabled just your test app and it lags again on battery drop. This is so weird. It's being said that Google fix many bugs in the January update, I hope this is one of them. That would be really quick tho, so I guess it will be in the February update?
Kitt3120 said:
Hey, I just registered to come here and say thank you! This was driving me crazy. My old Pixel 3 XL was also lagging and I thought that it would just be a bit old and bloated. When I switched to my Pixel 6 Pro and had lags again, I was very disappointed and thought that it really would have something to do with my specific setup, so I uninstalled heavy apps like MacroDroid and Gravity Screen, but it didn't help. As I said, at this point it was really driving me crazy and I just lived with it. To see the explanation of the bug and that it happens every time the battery percentage drops was just such a relief! It all makes sense now. I will have to live with it until Google fixes it, cause I really need all my apps that have accessibility services. Again, thanks so much!
Click to expand...
Click to collapse
I'm glad it helped you, and hopefully all this publicity will make Google fix the issue.
Aaaand another bug, just had it when typing this message.
This phone has been released without proper tests, this is really annoying.
Is this the same issue or something new/unrelated?
XDA article: [Update: A fix is coming] Google Pixel 6 owners are facing an annoying screen freezing issue
January 25, 2022 9:37am Kishan Vyas
[Update: A fix is coming] Google Pixel 6 owners are facing an annoying screen freezing issueUpdate 1 (01/25/2022 @ 09:37 ET): Google says the issue will be patched in a future update. Scroll to the bottom for more information. The article as published on December 30, 2021, is preserved below.
The Pixel 6 and Pixel 6 Pro are some of the best flagships available on the market right now. From powerful cameras and in-house Tensor chipset to thoughtful software experience, Google’s latest flagships phones have everything you would want from a modern-day flagship. While the Pixel 6 series has received positive reviews from critics, it seems end-users aren’t having a stellar experience with Google’s newest phones so far. The new phones have been subject to numerous bugs and issues as of late, with users complaining about the slower fingerprint scanner, ghost dialing, connectivity issues, and more. Lately, many Pixel 6 owners have noticed an annoying issue where the device completely freezes up for a few seconds.
Google Pixel 6 Pro Review: Fantastic everyday phone with an undeniable Exynos inspiration
The freezing touch-input issue seems to trigger on Pixel 6/Pro units that have an Accessibility Service running with canPerformGesture permission enabled. When this permission is enabled, the whole system freezes for 1-2 seconds every time the battery drops by 1%. If you own a Pixel 6 or Pixel 6 Pro and are affected by this bug, there’s a temporary workaround to resolve the issue. It requires disabling all Accessibility features. To do so, go to Settings > Accessbitliy on your Pixel 6 and turn off every accessibility service you find in there, including Voice Access, Accessibility Menu, Switch Access, and others.
Google says it’s currently investigating the issue and has assigned the bug to the relevant product and engineering team. The company hasn’t provided any timeline as to when we can expect the software fix to be ready. We’ll keep an eye out and let you know as soon as we learn more details about the screen freezing bug.
Update: A fix is comingGoogle has marked the screen freezing bug as fixed and has confirmed a software fix is coming to Pixel 6 and Pixel 6 units in a future update. It’s likely the fix will arrive as part of the February 2022 update.
Click to expand...
Click to collapse
roirraW edor ehT said:
Is this the same issue or something new/unrelated?
XDA article: [Update: A fix is coming] Google Pixel 6 owners are facing an annoying screen freezing issue
Click to expand...
Click to collapse
It's the same, it was just updated with the latest comment from Google:
[email protected]<[email protected]> #95Jan 25, 2022 06:32AM
Marked as fixed.
06:32AM
The development team has fixed the issue that you have reported and it will be available in a future build.
Click to expand...
Click to collapse
Google said that the issue will be fixed in the next update.
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.
Had the fold since the 22nd and really loving it. Few things bugging me. Anyone else experiencing UI Glitches from time to time? Examples are the app tray displaying blank which I had to restart the phone to resolve. Outlook app the mail box panel empty even after a closed the app fully was still blank. Scrolling through twitter and often the display flickers at the bottom? Any other users finding things like this? Hoping for a early update from Samsung to flush any ealry bugs
I am holding it since 23rd and it has absolutely been a godsent device
No issues. No hiccups. 256 gb version.
Maybe an update will resolve the issue for you.
Can't say that I'm experiencing these issues.
A hear most to a fresh install not using smart switch which I did. Maybe the time saving was not worth it? do you still use a backup or literally re install everything
I did use Smart Switch and no glitches. It works flawlessly for me.
There is a OneUI update in the Samsung store I noticed.
YellowGTO said:
There is a OneUI update in the Samsung store I noticed.
Click to expand...
Click to collapse
Checked the galaxy store just says installed no update
Haven't experienced the issues you've mentioned at all. I've had the ZF4 since Aug. 23.
Chrome beta has a glitch on the tabs, mentioned it right from the start. Sure its just teathing issues with the new chipset. USA have had a firmware (pre launch, not checked if its ahead or in line with European launch firmware) so sure something will be along soon, as the security updates are over a month old too.