Develop Bugs

[Q] Wrong Time Showing up

I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.

restart
humpty123 said:
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
Click to expand...
Click to collapse
I had the same problem and restarted my device. At first it displayed the same (incorrect) time, but then it quickly changed to the correct time. Mine was about 20mins ahead.

not fixed...
melscheld said:
I had the same problem and restarted my device. At first it displayed the same (incorrect) time, but then it quickly changed to the correct time. Mine was about 20mins ahead.
Click to expand...
Click to collapse
A few hours post-restart and it looks like the time is off again. It seems to be a cumulative effect...

Fix
humpty123 said:
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
Click to expand...
Click to collapse
I had the same issue - got mine a few days ago - after reading the post here I did a full device reset and set it up again with my phone. Been going for about a day and no issues. I wonder if it was an issues with having the new update right out of the box. Who knows. But if your having this issue a quick reset and setup and no issues. Will repost if something changes.

Moto 360: consistently wrong time now
alandashby said:
I had the same issue - got mine a few days ago - after reading the post here I did a full device reset and set it up again with my phone. Been going for about a day and no issues. I wonder if it was an issues with having the new update right out of the box. Who knows. But if your having this issue a quick reset and setup and no issues. Will repost if something changes.
Click to expand...
Click to collapse
I've had my Moto 360 for over a week now ... love it, recommend it to everyone I know
But I'm having the same problem now. My watch just won't keep time, and it's getting worse and worse (i.e. farther off of the real time). Everything else seems fine - I still get notifications so I know the watch is paired to my phone correctly, my phone's time is set by the carrier and remains correct throughout the day, etc. But now my Moto 360 will "slip" forwards in time by over 20 minutes! I have to double-check the time on my phone every time I check on my watch now, which needless to say is not a very good feature in a watch.
Restarting the watch and reconnecting in Android Wear does fix the time syncronization, but having to reboot my watch a couple times a day is not very desirable obviously. I've reset my watch (Reset device in settings) twice now, rebooted my phone, wiped Android Wear's settings on my phone and uninstalled then reinstalled it - same thing, incorrect time on my watch after anywhere from 1 to 6 hours.
It was perfectly fine when I first got it, and perfectly fine (even better!) after the update. It would be marginally less awful if I could re-sync the time without having to restart my watch, but disconnecting via Android Wear and/or turning Bluetooth off then on again, un-pairing the watch then re-pairing it, etc., all have no effect for me. Super lame :crying:
If I could manually set the time, I could deal with that.

I have time problems as well, but only....
chimpster said:
I've had my Moto 360 for over a week now ... love it, recommend it to everyone I know
But I'm having the same problem now. My watch just won't keep time, and it's getting worse and worse (i.e. farther off of the real time). Everything else seems fine - I still get notifications so I know the watch is paired to my phone correctly, my phone's time is set by the carrier and remains correct throughout the day, etc. But now my Moto 360 will "slip" forwards in time by over 20 minutes! I have to double-check the time on my phone every time I check on my watch now, which needless to say is not a very good feature in a watch.
Restarting the watch and reconnecting in Android Wear does fix the time syncronization, but having to reboot my watch a couple times a day is not very desirable obviously. I've reset my watch (Reset device in settings) twice now, rebooted my phone, wiped Android Wear's settings on my phone and uninstalled then reinstalled it - same thing, incorrect time on my watch after anywhere from 1 to 6 hours.
It was perfectly fine when I first got it, and perfectly fine (even better!) after the update. It would be marginally less awful if I could re-sync the time without having to restart my watch, but disconnecting via Android Wear and/or turning Bluetooth off then on again, un-pairing the watch then re-pairing it, etc., all have no effect for me. Super lame :crying:
If I could manually set the time, I could deal with that.
Click to expand...
Click to collapse
My time-problems comes only when I load any of the clockfaces from "Facer", then it goes a whole hour off.

Some watch faces do not move the hour hand until the second hand advances thru the full hour. Could that be the case?

I got the same problem!!
It was 15 mins ahead and all the sudden the time was corrected by itself...

humpty123 said:
I just got moto 360 and the time is wrong on the watch how can i get it to the correct time its currently 8 mins off.
Click to expand...
Click to collapse
Just restart the watch. Once it pairs again, the time will be set correctly.

sreymj said:
Just restart the watch. Once it pairs again, the time will be set correctly.
Click to expand...
Click to collapse
This is not a solution?? You can't look at the watch and not be able to trust the time, without checking your phone to see if it's right?? then sync again. It's a watch!!! It's it's core job. It should be able to be trusted to be right!!!
Mine has been out between 5 and 15 mins 3 times in the last 2 days, always fast. So not a refresh of screen issue.
I use Facer too, but even when I swipe to a standard watch face they are out too, until I do some sysnc with the phone.
I'm going to keep on a standard watch face today, and see what happens. Can't it really be facer? surly it just report the time on the device, will not change anything??
i have reported to Moto too, they know of no issue. Suggest everyone does the same.
On moto forum too;
https://forums.motorola.com/posts/75d3867b9d
Reads like it's a bug in latest firmware. Anyone got confirmation from Moto of this?

I just read on Android Forums that this may be related to wifi router software being out of date. YMMV.

Android Wear new version Feb 26th, with it new problems

I am getting tired of starting posts with the new problems each version of firmware etc brings but here it goes anyway.
I received an update to Android Wear on my phone(2014 Moto X) Feb 26 which also updated the Android Wear on my Moto 360. Notifications have been working since however my watch has clearly been losing connection to my phone as my Smart Lock/trusted device feature has failed to operate three times so far. Instead of the phone auto unlocking I have had to put my pin in. The watch and phone have never been more then 4 or 5 feet apart. This very very rarely occurred with previous versions.
Sigh, why does each version get worse, and does google test this stuff at all???

Try resetting the watch and uninstall/reinstalling the app.

Working great here without problems

Haven't noticed any problems myself. Granted, something similar did happen when I migrated ROMs. But a reset and app reinstall fixed it.

I have had better luck with it today after rebooting both the phone and watch. Hopefully it stays this way.

no issues here.

throwing my hat in the "no problems" ring...
stock not rooted. no issues at all. using a nex 6 stock and sometimes i pair it with the stock nex 9 lte...

Watch constantly flashing while charging on cradle. Even after restart and theater mode and what not. Annoying issue especially during the night

I did uninstall all Wear apps and did a reset to factory default but still fails to install 5.0.2.
Asked for support in Android Wear and Moto360 forum.

The bright to dim flashing while on charger is caused by watchmaker v 3.3.2 ,the beata i am testing 3.3.3 fixes the isue. Use a stock face temporarily
.
Sent from my SM-T800 using Tapatalk

mbaseball3 said:
Watch constantly flashing while charging on cradle. Even after restart and theater mode and what not. Annoying issue especially during the night
Click to expand...
Click to collapse
if you use watchmaker update it to latest version . it solves the problem

nechmadi said:
if you use watchmaker update it to latest version . it solves the problem
Click to expand...
Click to collapse
Yeah I realized that. Thanks. Really didn't think it had anything to do with watchmaker and thought for sure it was the new update. Ugh just so many issues lately I can't keep up lol. Its either lollipop on the M8 that sucks or issues with the watch

Slow app opening when tapping notifications

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.

No Sleep data on Huawei Health App

Since the turn of the year, the sleep tracking of the Huawei Watch GT2 is no longer shown in the Huawei Health App, although the data are available on the watch. Is there a proposed solution?

ThinkD said:
Since the turn of the year, the sleep tracking of the Huawei Watch GT2 is no longer shown in the Huawei Health App, although the data are available on the watch. Is there a proposed solution?
Click to expand...
Click to collapse
Huawei have replied to the issue on the official support forum... Accessible via HiCare. They're on it now trying to fix.
Sent from my CLT-L29 using Tapatalk

Thanks same issue on m20pro and GT2
Tapatalk

Hi, it happens also to me since 2 days ago, written to Huawei for a fix. We shall se because at me only nap slep is synked to phone app even if all the night sleep is awailable on watch.

My GT Watch also stopped syncing sleep data on January 1st. Sounds like a year rollover issue or something close.
Let us know if you hear anything from Huawei.

Same problem here. after 10.0.3.018 update unable to sync sleep data, it starts syncing and at 78% it fails.
Watch GT and Mate 20 pro combo.

Huawei has fixed the bug with an update - great!

Huewei gt 2 watch sleep
log into the app and hit the update button they put up kicks in to fix the bug on the sleep app so now the sleep app works just update the app and it will work on your phone and your watch now
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
Update the app on the app store and it will now work they put a fix in for the bug

Nope... still not working for me...
... I have one 2 hr nap logged but no sleep data since year end. App is updated, manual sync button pushed (lots), Google Fit unlinked, watch and phone rebooted numerous times, watch recording sleep fine. All other data sync's no problem. So either the watch isn't pushing the data or the app isn't processing it. ?* Phone is a Xiaomi Mi9T Pro.
Any suggestions appreciated. Thx.

Same on Honor Magic, 78% and says abnormal data or no data available, since 31st December.

doesn't work on mi 9 and Huawei watch 2 which is amdriod wear
I have samw problem on watch 2 and xiaomi mi 9

Latest update (second this month) still hasn't fixed it. Still only getting naps recorded... I keep updated my review on Play Store and I've also emailed the link on the store page.

I have the same issue with Huawei W2 and Samsung Note9. No sleep data sync since the turn of the year. The watch has the information, I can scroll on it, but it is not synchronized with the app and my phone.

I faced the same problem of no sleep data sync,despite the fact that it was recorded on my Huawei watch gt..
My both phones LG V30 with oreo and LG G6 with Pie,could never sync these sleep data after 12/1/20.
I tried a lot of different versions of huawei health in both phones,but without result.
The final solution came after i factory resetted my watch,and now sleep data syncs perfectly,even with December 2019 huawei health version.
So if anybody is still facing this problem,factory resetting the watch is the solution.

No sleep data
Dennisthe said:
Same on Honor Magic, 78% and says abnormal data or no data available, since 31st December.
Click to expand...
Click to collapse
I am facing same problem with my honor magic watch2 and my phone galaxy s5. how did u manage to fix it.
also the app is not working properly so many times my watch become disconnected and giving the error that health has stopped.
help?

Hi - has this bug returned? Sleep data is on the watch, but at 78% of update on app, it stops and says no data available?

Hi guys.
I made this post https://forum.xda-developers.com/sm...onor-magic-watch-2-huawei-health-app-t4135869
But seeing that this one has a lot of activity, I ask you.
Have you found a way to edit your sleep data? (For the ones that have it syncing ok)
For example, I lay down at 10pm to watch a movie, but fell asleep at 1130pm. The watch will recognize I went to sleep at 10pm, but doesn´t have an edit function to tell it I actually went to sleep at 1130pm.
Samsung has that option and I got used to it while I was using my gear sport.
Cheers!

Hi guys,
I think mine after the latest update several months ago, it stop showing heartrate & sleep historical.
Lately, I’ve notice that sleep data has always been there. It only just stop showing data if you access it through home dashboard app screen. ( for some reason)
but if you go into my data> Health measurement > Sleep, it’s there. (Atleast for mine)
Hope this help, and Huawei, please fix this.

Question A13, another "Am I the only one?" Thread!

Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.

You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s

nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).

Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.

Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.

jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.

roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?

For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.

Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/

jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.

Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!

roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".

jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.

Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).

I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.

96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.

jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.

Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.

jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.

96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.