Related
Device
nexus 7 16gb wifi 2013 fullhd (from amazon).
My device rooted now, but it had this issue from stock.
Have no chance now to give it back to shop, because of my current location.
Issue
In different situations the touch screen may stop responding or it will working with a large response time. (some area of screen works fine, some not all).
How to i tested it
I downloaded all the famous multitouch sensor test applications, and at usual time it's works fine without any issue.
How can i "get" the issue
For example: Today I unlocked the device from the sleep (it slept for a 3-5 hours), waited some minutes in browser, google play app, and the issue is come. Sometimes it can come when i use the device in various applications (browser, settings, install new app etc). (not only after unlock from sleep).
The current solution of issue
Simple device reboot solve the problem.
Another solution: lock device to sleep, wait for 30 sec, and turn it on. After this actions the problem is gone.
But it may return in any time
The question:
What is it? Hardware or software issue and how to solve it? Any others have this issue like me?
P.S. I like my new nexus 7, have no other problems with it.. Hope we will find the solution to solve it in near future.
Should i try to use custom rom, custom kernel to fix it?
For example: ElementalX 0.10 KERNEL and ParanoidAndroid 3.91 ROM.
as i understand, my problem the same as write here: productforums.google.com/forum/?hl=en#!topic/mobile/W0Hfkq8hf-c%5B1-25-false%5D
I will wait answer from google, hope it can be fix as software issue.
This might help.
http://forum.xda-developers.com/showthread.php?t=2402307
Sent from Nexus 7 (2013) using Tapatalk 4
If someone helps, PLEASE use the THANKS button.
If you're having reboot problems please post here - if there are problem apps or bad devices out there it would be good to know!
Got a new Nexus 5X yesterday for my partner. Plugged it in and charged all day (oh what patience). 10pm started setup and added account to it. Phone immediately did an update which succeeded. Then it started to install the saved apps from the Google account, about 50 in all. After all the apps were installed I handed it over to her to play and log into all those apps with logins. Tedious.
Within about 30 minutes she tried to take a photo and it rebooted. Then a bit later she was using it and it rebooted again. Before going to be it rebooted a few more times. Then again this morning. There wasn't one particular app or other that was in use when these crashes happened. During the day she saw a message about "Google needs to restart". Also the camera often comes up with an all black screen and can't be used.
I called Google tech support and they wanted to do a factory reset and maybe a cache partition wipe. They would also like to investigate if a rogue app is causing the crashes by using it without any apps installed. Because reinstalling apps is so tedious I decided to have her do a cache partition reset I'm awaiting news. I'm hoping we don't have to do the other... I can't imagine how a bad app could be causing such repeated crashes (well I can, but it just shouldn't happen). That's lame...
It would really help if it was easy to get a crash log and find out the cause - unfortunately unless you're rooted this doesn't seem to be easy, and may well be impossible.
I've been having a lot of similar-sounding issues with my 5X. It's never rebooted while I was using it, but once or twice a day I'll pull it out of my pocket and it will be off, awaiting the unlock pattern to boot up.
The camera has been atrocious as well. I've seen the black screen you describe, tons of rotation lag, hanging, etc. Not just in Camera, but in other apps using the camera (such as when attaching a photo to a Hangout). Hoping this is something software-related and not a hardware problem.
I've had mine spontaneously reboot twice so far, both times I've pulled it out of my pocket and it required the PIN to unlock, then it booted up. I'm a bit concerned, as I have no idea when this happened, and, since it's encrypted a reboot essentially puts me offline until I notice it.
I just now had mine reboot during active use for the first time. I was long-pressing a wifi network in order to forget it (which is another 5x problem I keep having—wifi turns itself off or connects to the wrong networks).
My 5x was working fine and the crashing started happening yesterday...
they only app that i recently installed before the crashes started was firefox... are you guys using firefox by any chance???
Mine is still working fine, I do not have Firefox.
Same problem for me when using Firefox. The phone seems to crash and reboot when loading news websites containing photos and videos.
Not seen the issue when not using Firefox.
I've had my nexus 5x since mid/late November 2015. I've had the problem described below happen prior to today, and more than once.
Today, I cant turn my phone off - it seems to be in the middle of a reboot... the four coloured circles (google logo?) with colours going round and round. I powered it off cos it had started going slow... thought a reboot might fix the problem... but now its not starting and I cant even turn it off or do anything with it.. I've tried pressing the power button, I've tried holding the power button down, and I've tried different combinations... nothing seems to make a difference... (has been in that state of un-useablity for at least 30 mins now)
Anyone else also having wi-fi issues where facebook has an error and "cant connect" ?
I had the same thing happen and returned the phone, it's the only solution I found. I factory reset multiple times, called up Google and they told me to safe boot. Right.. I was completely stock and it rebooted multiple times / day and I know what I'm doing too, for the most part anyway. Got a replacement device and it has not once rebooted no matter what I do. Camera, Chrome random apps caused a reboot, it's not that. It's a defective device and you need to get it replaced period.
I have the same thing and can't sent it back to google because I live outside the US.
I believe it is a manufacture defect as I tried everything with no success really annoying.
Stuck with a brick...
Sent from my Nexus 5X using Tapatalk
I used my phone completely stock for weeks and had zero issues, whereas I have a friend who ordered and received the phone at the exact same time (likely same mfg batch) and had issues. Difference between us two is that I'm a minimalist and only have about 50 apps installed, and he has a ton that he rarely uses and restores them every time.
I know it seems ridiculous, but having an android phone gives you more customization and your apps more power of the phone, so it's completely feasible for ONE rogue app to destroy performance and/or battery.
You guys might all want to try uninstalling apps one by one and figuring out which apps are killing performance. In particular, check out the running services (developer options -> running services) and see which apps are constantly running, since those are more likely to be the ones causing issues.
For example, I've used firefox (for adblocked browsing) for weeks recently, and can definitely say it's a pretty slow app, so if you're having issues on it, you may want to just use chrome or lightning browser.
I just ordered a replacement as well. Mine would reboot about 1 to 2 times a week right after the fingerprint unlock. Annoying as hell today because I was in the middle of a conf call.
Sent from my Nexus 5X using Tapatalk
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!
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.
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.