Develop Bugs

USA 5.0 Discussion.. Who in The US has got the 5.0.1 update?

So I know there are a few other threads but I could not quite figure out who in the US has actually got the update and it seems most of the ones I see and look are outside the US and the ones saying they have not got it are in the US. Is there confirmation that people in the US are getting the update? I have tried the reset trick uninstalling android wear and moto connect and clearing Bluetooth but I have had no luck and I see others freaking out about it so I thought if we had a more clear answers Who and where they live that got that update? I know some have said on the wear roll outs it seems to not matter the region but it seems to or at least for US and Non US.

I guess the option "Did not get the 5.0.1 update, do not live in the US" was left out?

I guess I should have added it and i tried to delete the thread to add it. I was making a US thread because I had seen others for other areas so I guess I just didn't think to put it. my bad.

I got the update on Thursday during the day. I am in Florida, bought the watch from Best Buy. I did not need to reset the watch to see the update, but I did upgrade the Android Wear app to the latest version.

I live in AZ and am still anxiously awaiting to see the update. I did get the Android Wear update, but nothing for the watch .

I live in the Boston Mass area and i got the update on like Tuesday.
my real passion is to hack this baby up but i was having a b1tch of a time getting my usb interface i built to work.

Los Angeles, CA
got both the same day on thursday. did not even know there were updates as i dont keep up with these forums. i DID come here once I saw the update to see what it was about....

Well maybe they are doing big cities and moving there way in Ugh I wish they would just get to it or I could get this thing to mount via USB I have never had so much trouble with a cord.

New Jersey, update for android wear on Thursday - No update for my watch yet.

I don't think it has anything to do with cities. It's all about your Google account and what position it's in to receive the update. I'm in Pasadena (literally right next to Los Angeles) and i have yet to receive an update. This is without resetting the watch, or doing any other ridiculous tricks just to get it.

freeza said:
I don't think it has anything to do with cities. It's all about your Google account and what position it's in to receive the update. I'm in Pasadena (literally right next to Los Angeles) and i have yet to receive an update. This is without resetting the watch, or doing any other ridiculous tricks just to get it.
Click to expand...
Click to collapse
Im in Fall River,MA and i am still waiting for the update. I do have the updated Android Wear app. My girls G watch recieved the update yesterday. and i have reset this mother like fifteen times since my girl got hers, lmao

I got it but I had to force it.
Try this, it has worked for 3 other people.
1: Make sure your Google Play Services and Android Wear apps are updated to the latest versions using apkmirror.com (NOT the play store)
2: Remove BT pairing, "Forget device" from within the Wear app, wipe Wear apps data
3: Reset the watch
4: once booted and paired immediately go to settings/update and check for it. Within the first 3 times it should download it.
Again its not completely proven, but I've seen it work 3 times before including myself.

altimax98 said:
I got it but I had to force it.
Try this, it has worked for 3 other people.
1: Make sure your Google Play Services and Android Wear apps are updated to the latest versions using apkmirror.com (NOT the play store)
2: Remove BT pairing, "Forget device" from within the Wear app, wipe Wear apps data
3: Reset the watch
4: once booted and paired immediately go to settings/update and check for it. Within the first 3 times it should download it.
Again its not completely proven, but I've seen it work 3 times before including myself.
Click to expand...
Click to collapse
Did this. No luck.

gtg465x said:
Did this. No luck.
Click to expand...
Click to collapse
Clear data from Android wear and Moto connect. Uninstall both apps. Reset Moto 360. Install wear and connect. Pair watch. Check update and should get it.
That's what I did. I'm in Orlando, Florida. Have had the update for about 3days

altimax98 said:
I got it but I had to force it.
Try this, it has worked for 3 other people.
1: Make sure your Google Play Services and Android Wear apps are updated to the latest versions using apkmirror.com (NOT the play store)
2: Remove BT pairing, "Forget device" from within the Wear app, wipe Wear apps data
3: Reset the watch
4: once booted and paired immediately go to settings/update and check for it. Within the first 3 times it should download it.
Again its not completely proven, but I've seen it work 3 times before including myself.
Click to expand...
Click to collapse
I did it 4 times. Didn't work.
I think I'm done with the tricks.

I am not from USA (I live in EU), but i bought my watch in USA and recieved update on Thursday.
Sent from my SM-910c using Tapatalk

I tried the tricks too with no luck. I don't care anymore I'll get it when I get it.

Qbancelli said:
I did it 4 times. Didn't work.
I think I'm done with the tricks.
Click to expand...
Click to collapse
I did it like 40+ times with no luck so I made a usb cord to mount the watch and forced the update via shell side loading

tlxxxsracer said:
Clear data from Android wear and Moto connect. Uninstall both apps. Reset Moto 360. Install wear and connect. Pair watch. Check update and should get it.
That's what I did. I'm in Orlando, Florida. Have had the update for about 3days
Click to expand...
Click to collapse
Like I said before, I did all of that. Twice. Didn't get the update. It still requires some luck apparently.

Moto 360 won't update 4.4w.2

Just got a moto 360 in today and I cannot get it to update android wear. I've done everything I can think of. Rebooting it, resetting it, letting it sit, I've cleared app cache on Android wear and even uninstalled it.. I don't know what else to do. It gets to about 25% complete everytime and then it disconnects from my phone and says "unfortunately Google services has stopped working". And in order to get it to let me reattempt the download I have to reset my device completely. Anyone else have any thoughts??

Exact same thing has been happening to me! I just got the Moto 360 yesterday.
Help would be much appreciated.

I'm thinking about just returning it and waiting for the second gen to come out..

Imh4lfdead said:
I'm thinking about just returning it and waiting for the second gen to come out..
Click to expand...
Click to collapse
Look at the reviews of the Android Wear app. Many, many people seem to be having this problem with the latest update. I think I'll just wait it out until the app fixes these issues.

I just got my replacement Moto 360 today and had this problem. I thought Motorola sent me a defective replacement and was frustrated as hell for a couple hours lol. I was able to solve it by using a previous version of Android Wear app (I had a titanium backup saved from the end of June) and I was able to update the watch normally again. I reset the watch after restoring the old version of the app then checked for updates and this time it downloaded the entire thing and updated then after updating I updated the app to the newest version and all is well!

bsktballstar3131 said:
I just got my replacement Moto 360 today and had this problem. I thought Motorola sent me a defective replacement and was frustrated as hell for a couple hours lol. I was able to solve it by using a previous version of Android Wear app (I had a titanium backup saved from the end of June) and I was able to update the watch normally again. I reset the watch after restoring the old version of the app then checked for updates and this time it downloaded the entire thing and updated then after updating I updated the app to the newest version and all is well!
Click to expand...
Click to collapse
I just bought my Moto 360 all excited to get my Android Fanboyism to the next level.
The first thing I did was try to update my Android Wear version.
And This is when I start getting the error..
It keeps saying google play services crashed.
google apps crashed..
Someone help..

I Can Help!!!
I can help you guys out. Just three days ago I bought my moto 360 at your SW version and had this EXACT issue. Here is how I fixed it.
First off, do yourself a favor and delete the lastest version of Android Wear on your phone. While you're at it, be sure to get rid of Moto Connect as well if you have installed it. Basically, what is happening, is android wear 4.4 doesn't seem to be compatible with the latest version of Android Wear for Phones, so as your phone is attempting to update your watch from 4.4 to 5.1.1, it throws this error.
Step two, disconnect your Moto 360 from your phone in the Android wear menu on your phone. Factory reset your Moto 360.
Step three, go to Here on your phone and download that APK to a location you can find it. This is an older version of android wear.
Step four, install this APK. Reboot your phone for good measure, and connect your Moto to your phone using the version of Android wear on your phone. MAKE SURE TO NOT ALLOW ANDROID WEAR ON YOUR PHONE TO UPDATE IN THE GOOGLE PLAY STORE.
Step Five, once everything is connected, on YOUR WATCH, go to settings --> about --> software updates. This step takes a LONG TIME, around 10-20 minutes, and your watch must be over 80% to complete this. When it finishes (the green circle wraps all the way around the X) it will ask if you want to upgrade. Tell it yes. When the watch finishes and reboot, FACTORY RESET IT AGAIN.
Step Six, With the watch reset, remove android wear from your phone, and do a fresh install on the play store. Now connect your phone to your watch. You should no longer have any issues. Your watch is now running Wear 5.1.1 and your phone is running the latest AW App. Go ahead, install Motorola connect and any other apps you want to have, and most importantly, ENJOY YOUR NEW WATCH!
To any mods out there watching, I'd recommend sticking this post or something. This is an error that is going to come up a LOT until google figures out why that happens. To my knowledge, this is the ONLY way to get a 4.4w2 Moto 360 running on the latest android wear release.
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Check out my post just below yours. I fixed mine this way. Post #7.

wydra91 said:
I can help you guys out. Just three days ago I bought my moto 360 at your SW version and had this EXACT issue. Here is how I fixed it.
First off, do yourself a favor and delete the lastest version of Android Wear on your phone. While you're at it, be sure to get rid of Moto Connect as well if you have installed it. Basically, what is happening, is android wear 4.4 doesn't seem to be compatible with the latest version of Android Wear for Phones, so as your phone is attempting to update your watch from 4.4 to 5.1.1, it throws this error.
Step two, disconnect your Moto 360 from your phone in the Android wear menu on your phone. Factory reset your Moto 360.
Step three, go to on your phone and download that APK to a location you can find it. This is an older version of android wear.
Step four, install this APK. Reboot your phone for good measure, and connect your Moto to your phone using the version of Android wear on your phone. MAKE SURE TO NOT ALLOW ANDROID WEAR ON YOUR PHONE TO UPDATE IN THE GOOGLE PLAY STORE.
Step Five, once everything is connected, on YOUR WATCH, go to settings --> about --> software updates. This step takes a LONG TIME, around 10-20 minutes, and your watch must be over 80% to complete this. When it finishes (the green circle wraps all the way around the X) it will ask if you want to upgrade. Tell it yes. When the watch finishes and reboot, FACTORY RESET IT AGAIN.
Step Six, With the watch reset, remove android wear from your phone, and do a fresh install on the play store. Now connect your phone to your watch. You should no longer have any issues. Your watch is now running Wear 5.1.1 and your phone is running the latest AW App. Go ahead, install Motorola connect and any other apps you want to have, and most importantly, ENJOY YOUR NEW WATCH!
To any mods out there watching, I'd recommend sticking this post or something. This is an error that is going to come up a LOT until google figures out why that happens. To my knowledge, this is the ONLY way to get a 4.4w2 Moto 360 running on the latest android wear release.
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Check out my post just below yours. I fixed mine this way. Post #7.
Click to expand...
Click to collapse
Thank you... It worked. <3

Finally, I found a solution that works! Thanks a lot!

wydra91 said:
I can help you guys out.
Click to expand...
Click to collapse
Bruh. Eternally gracious.

Please someone help, i tried exactly above instrucciones and nothing, im in centro america, i dont know if that its blocking the update or something
Enviado desde mi SM-N920I mediante Tapatalk

[POSSIBLE FIX] Android Wear 1.4 - Google Play Stopped Working

[POSSIBLE FIX] Disable Google Fit app on Moto 360. Working so far...
Thanks to several users on google support and reddit
I received my OTA update for Android Wear 1.4 this morning.
Running a Moto 360 V2 and a stock Nexus 6 with MRA48N.
Now my watch keeps giving Google Play Services has stopped working error on screen.
I've tried factory reset and older version of Android Wear... Nothing works.
PLEASE HELP

Same issue here. I tried the old fix of unpairing, deleting Android Wear from phone and installing and older APK. Factory reset watch and ran through the set up...all seemed to work fine until the Android Wear app updated, then back to same issue.

RickyGC said:
I received my OTA update for Android Wear 1.4 this morning.
Running a Moto 360 V2 and a stock Nexus 6 with MRA48N.
Now my watch keeps giving Google Play Services has stopped working error on screen.
I've tried factory reset and older version of Android Wear... Nothing works.
PLEASE HELP
Click to expand...
Click to collapse
I did this as well with the same results hope they come out with a fix soon.

Same issue here, hope google fix it quick
I had brougth my moto 360 v2 two days ago

I fixed it here is what I did
Uninstall Android Wear make sure to clear data and cache first
Download the previous APK http://www.apkmirror.com/apk/google...-wear-1-4-0-2392391-gms-android-apk-download/ and install
Factory reset watch and pair
A pain in the neck but it worked just dont update to the newer version till they get it right.
Nope that didn't do it either error came back after about 15 minutes.

Same Problem here with Moto 360 2nd Gen
I am also experiencing the same issue on my Moto 360 2nd Gen.
I have an open ticket with Google.... I was told this has been escalated to their Advanced support team.... still waiting for updates.
I have wiped cache within Google play services and downgraded to stock Google play services.. re-updated.. Wiped and cleared cache of Android wear and installed previous versions.. still same errors:
Moto 360 2nd Gen
Android Wear:1.3.0.2230669
Android OS: 5.1.1
Build: LLA44S
Google Play Services: 8.1.07 (2229520-534)
Errors:
-Google Play Services error Unknown issue with Google Play Services
-Unfortunately, Google play services has stopped.
Phone:
LG G4 running Android 5.1

I had this issue with my v2 today and I uninstalled google fit and it solved the issue. Did this before I knew it was a known issue to lol.
Sent from my Nexus 6 using Tapatalk

I found a solution, worked for me with moto 360 v2 and stock Galaxy S6
-Unpair watch from android wear app
-Factory reset watch
-Unistall Android wear (data and cache clead first)
-Clear data and cache from Google Play Services
-Reboot phone
-Fresh install Android Wear APP from google play store
-Pair the watch
Rock Solid :good:

I was able to resolve the issue by unpairing the watch from Android wear on my phone, Factory Resetting the Watch and then pairing it up to a Nexus 7 Tablet running Android 6.0 and the latest version of Android Wear. The watch synched to the tablet, was able to receive notifications. Once i confirmed there was no more "Unfortunately, Google Play services has stopped error", i then unpaired from the Tablet Android Wear, Factory reset the watch and re-paired to the same original phone running the latest Android Wear.
It has been almost 9 Hours since this was completed and this appears to have resolved the issue for me.

xJuicex said:
I was able to resolve the issue by unpairing the watch from Android wear on my phone, Factory Resetting the Watch and then pairing it up to a Nexus 7 Tablet running Android 6.0 and the latest version of Android Wear. The watch synched to the tablet, was able to receive notifications. Once i confirmed there was no more "Unfortunately, Google Play services has stopped error", i then unpaired from the Tablet Android Wear, Factory reset the watch and re-paired to the same original phone running the latest Android Wear.
It has been almost 9 Hours since this was completed and this appears to have resolved the issue for me.
Click to expand...
Click to collapse
This worked for me too. It appears to be Google's recommended path... and I've yet to have it let me down. On my fifth (ugh, don't ask) Android Wear watch... this basic strategy has (painstakenly) worked each time. Especially when I get a watch that has been in cold storage, and still has Android Wear 1.0W on it.

My watch disconnects whenever i install any wear enhanced app / watchface. I have to restart the watch to reconnect it. It happens on installing any app/face! Plz help.
PS: tried reseting the watch and the phone too. I have it paired to a Moto X2014 running 5.1 stock unrooted.

its end of januari 2016 and still have the same problems. I read people who factory reset and install the wear app back and its fixed. but its not. if the watch gets disconnected a few times for being to far away from Phone then after a while whatsapp messages stop working to show up. I also get the message that i need to installe google play services. on my Phone. wich is installed and on latest version...
Only thin working right now is using the android wear app 1.1 wich works perfectly. But in the play store the update keeps popping up so i need to watch out that i dont press update all. because then it will be reinstalling the latest version wich is a *****.
Cant wait until 1.5 is released.... hope it will be fixed then.
is there a way to report this to google or Motorola somehow. everyone seems to have the same issue here. why isnt this fixed sooner?

Apps Not Automatically Updating

I'm not sure if this is an issue with the Pixel 2 XL or an Android OS bug but it's happening on my Pixel 2 XL so I'm adding here.
I have the Google Play Store app set to automatically update apps when connected to WiFi but apps are not updating. I've been connected to my home wifi for several hours and there are still apps waiting to update.
Anyone else having this issue?

jimv1983 said:
I'm not sure if this is an issue with the Pixel 2 XL or an Android OS bug but it's happening on my Pixel 2 XL so I'm adding here.
I have the Google Play Store app set to automatically update apps when connected to WiFi but apps are not updating. I've been connected to my home wifi for several hours and there are still apps waiting to update.
Anyone else having this issue?
Click to expand...
Click to collapse
I feel like it automatically downloads when on WiFi and connected to power even though there's no setting for power connected.
Sent from my Pixel 2 XL using Tapatalk

I'm having this issue too....mine doesn't auto update...even when connected to power and wifi.

I have the same problem. I've literally tried everything I could think of.

Yes! Bump! I've actually been having this problem as far back as February (at least that's around when I noticed) and had been meaning to make a thread, but hadn't gotten to it 'til now; and XDA showed this thread when I was creating so, I'll be pleading here...
I, too, FOR THE LIFE of me can't correct this...!
My setup: running Oreo 8.1 May update, rooted, Flash kernel, TWRP 3.2.1-2 custom recovery, a few Magisk modules (see sig).
Troubleshooting: rebooted, plugged phone in, allowed all permissions and ability to modify system settings, I've changed it to auto-update apps "at any time" (both mobile data & wi-fi), when updating to May patch I wiped the System partition and flashed the May Full Factory image, cleared Play Store app cache, cleared Play Store app data, uninstalled Play Store updates, Disabled Play Store - then Enabled, uninstalled Google Play Services updates / reset to factory version, and finally manually updated Google Play Services.
Anyone, any thoughts/ideas/advice?! I had hoped the last 3 months' security patch updates might fix this, but since it hasn't, my last hope is here...! :begging:
P.S. I am hoping that flashing a full factory image with the -w intact/included is not the last and only option...

simplepinoi177 said:
Yes! Bump! I've actually been having this problem as far back as February (at least that's around when I noticed) and had been meaning to make a thread, but hadn't gotten to it 'til now; and XDA showed this thread when I was creating so, I'll be pleading here...
I, too, FOR THE LIFE of me can't correct this...!
My setup: running Oreo 8.1 May update, rooted, Flash kernel, TWRP 3.2.1-2 custom recovery, a few Magisk modules (see sig).
Troubleshooting: rebooted, allowed all permissions and ability to modify system settings, I've changed it to auto-update apps "at any time" (both mobile data & wi-fi), when updating to May patch I wiped the System partition and flashed the May Full Factory image, cleared Play Store app cache, cleared Play Store app data, uninstalled Play Store updates, Disabled Play Store - then Enabled, uninstalled Google Play Services updates / reset to factory version, and finally manually updated Google Play Services.
Anyone, any thoughts/ideas/advice?! I had hoped the last 3 months' security patch updates might fix this, but since it hasn't, my last hope is here...! :begging:
P.S. I am hoping that flashing a full factory image with the -w intact/included is not the last and only option...
Click to expand...
Click to collapse
I've said it before that, for me at least, I've noticed it only auto updates when plugged in even if I have plenty of battery like greater than 50%. I'm set to auto update on WiFi only. I'll go into the app store and see I have a handful of update, plug in, and see them to start downloading.
Sent from my Pixel 2 XL using Tapatalk

EeZeEpEe said:
I've said it before that, for my at least, I've noticed it only auto updates when plugged in even if I have plenty of battery like greater than 50%. I'm set to auto update on WiFi only. I'll go into the app store and see I have a handful of update, plug in, and see them to start downloading.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I eventually noticed as well that it only updates when plugged in. I'm not sure if it has anything to do with how charged the battery is but I haven't looked too closely at that.

....yea...I've also plugged in as well, i'll edit to reflect that...
...BUT I think I'm onto something...does anyone/everyone that has this problem have Titanium Backup installed and running btw???

Same, only auto updates when plugged in...
I always have Titanium which is running normally... Awesome app!

Yea...I get that apps are really only automatically updating when plugged in. But assuming even that isn't allowing apps to automatically update....
i'm more wondering if @upperbladez and @smokeythebear3 have Titanium Backup installed; as that's what was stopping the updating the apps automatically....

simplepinoi177 said:
Yea...I get that apps are really only automatically updating when plugged in. But assuming even that isn't allowing apps to automatically update....
i'm more wondering if @upperbladez and @smokeythebear3 have Titanium Backup installed; as that's what was stopping the updating the apps automatically....
Click to expand...
Click to collapse
I do not have Titanium Backup Installed...I don't have any power saver apps either. It's really agitating

upperbladez said:
I do not have Titanium Backup Installed...I don't have any power saver apps either. It's really agitating
Click to expand...
Click to collapse
Yeah...I had really high hopes earlier as well, but found that it wasn't TB. Because there is a setting in the preferences that deals with auto-updating and it seems that, by default, it sets it to Disabled, but even after Enabling it, it hasn't gotten auto-update to work.
I had inadvertently thought it worked because, at the same time as the TB discovery, I reset to factory settings both Google Play Store and Google Play Services (as I have many times before). This seems to have the auto-update work once, but I can't get it to replicate or do it again after this first initial time. Also, it's hard to debug, troubleshoot, and test because I have to wait some time for a number of apps to need updating before I can see if it truly works or not.
I hope someone has an idea or thought that might explain why or help reach an explanation...

simplepinoi177 said:
Yeah...I had really high hopes earlier as well, but found that it wasn't TB. Because there is a setting in the preferences that deals with auto-updating and it seems that, by default, it sets it to Disabled, but even after Enabling it, it hasn't gotten auto-update to work.
I had inadvertently thought it worked because, at the same time as the TB discovery, I reset to factory settings both Google Play Store and Google Play Services (as I have many times before). This seems to have the auto-update work once, but I can't get it to replicate or do it again after this first initial time. Also, it's hard to debug, troubleshoot, and test because I have to wait some time for a number of apps to need updating before I can see if it truly works or not.
I hope someone has an idea or thought that might explain why or help reach an explanation...
Click to expand...
Click to collapse
Yeah it's so agitating?

I think I figured it out....[GUIDE] included!
I think I figured it out (at least in my case) -- but I think it's probably applicable to most any other(s) who are having the same issue...
First of all, if you have Titanium Backup, make sure to set Default auto-update app to Enabled
Go to Menu
Preferences
Go to Restoration Settings
You will find Default auto-update mode in the section; 4th on the list within that section
Go to Google Play Store App Info
Clear Cache (inside Storage)
Clear Data (also inside Storage)
Disable the app
Click OK when warned that it will "replace this app with the factory version..."
Go to Settings, Apps & Notifications, See all ### apps
At the top right, select the 3 verticle dots and select "Show system"
Find and select Google Play Services
Clear Cache
Go back to App Info (back arrow; arrow pointing left), at the top right, select the 3 vertical dots and select "Uninstall updates"
Click OK when warned that it will "replace with the factory version..."
Reboot
Download the latest Google Play Services
HERE'S one place you can find it and/or you can Google search to find other copies yourself...
Pick the newest latest version (beta if you wish to be on bleeding edge but stability not ensured)
Choose the Android 8.0+ variant
Download the "arm64 + arm" & "nodpi" one
Install the latest Google Play Services using the file you downloaded
Reboot
Go back to Google Play Services App Info (show all ### apps, show system, etc.)
Clear Cache (of Google Play Services)
Go back to "show all ### apps"
Select the drop-down menu and select Disabled
Select Google Play Store
Clear Cache and Data (of Google Play Store inside Storage)
Plug Phone to charger
Launch Google Play Store
Select the 3 stacked horizontal lines on the top left and go to Settings
Select and configure how you wish to auto-update apps
Click on Play Store version (all the way on the bottom)
After pressing OK (it'll most likely say Play Store will update soon), it may or may not begin downloading components for the Play Store. After a bit, it may or may not actually begin auto-updating...
In the few instances I've done this and on the 2 pixel 2's I have access to, the auto-updating may begin soon after (within 2 minutes), or eventually (sorry for vague description, but I had thought these steps didn't work and wasn't paying attention and after a while, I saw it auto-updating!).
Also, it still seems that it'll auto-update only while plugged in charging. That particular bug/requirement hasn't been resolved, but as this is specifically an auto-update troubleshooting thread.......
Hope this helps any/all who is having the same issue. I hope (but am doubtful) that this will work for everyone; but if it doesn't, I'd have to say that it might be something with your ROM (stock or custom), settings (system or another app interfering [As I found out TB actually might/does]), or some very unique bug because this is probably the most comprehensive app reset for Google Play. It's kind of overkill, but you might have some luck going the "last resort" route and flashing the Full Factory image in hopes it'll fix the system and app comparability issues (if that is indeed the reason...).
In the end, I hope this helps any who might be having this issue....:victory::highfive:

I have this same issue. I tried wiping Google Play cache/data and had a hell of a time getting it to show my installed apps after that. I don't have TB installed so I'm not really sure what's going on. It's a PITA having to manually update apps all the time.

corywf said:
I have this same issue. I tried wiping Google Play cache/data and had a hell of a time getting it to show my installed apps after that. I don't have TB installed so I'm not really sure what's going on. It's a PITA having to manually update apps all the time.
Click to expand...
Click to collapse
Yeah....but maybe uninstalling Google Play store (not just cache and data and actually reverting to an older version) and doing the same (sorta) towards Google Play Services is the critical difference (as shown in my guide)... Hopefully that sorts ya out...!:good:
Good luck to ya!

I'm set to auto update over WiFi, and I've never actually paid attention.. but my apps are always updated and I get the notification stating that 13 apps were updated... So it must be working on my end?
EDIT: Not sure if it would make a diff, but I am running latest DU...

Az Biker said:
I'm set to auto update over WiFi, and I've never actually paid attention.. but my apps are always updated and I get the notification stating that 13 apps were updated... So it must be working on my end?
Click to expand...
Click to collapse
Yes, that's "the dream" . For us/me, that wasn't happening -- for whatever reason; whether it was set to do it over WiFi or both mobile & WiFi.
I used to not pay attention either, until I went and checked and kept finding a list of 50+ apps needing to update and/or all these apps were outdated every 3 or so days! Then I realized I hadn't been getting that which you are experiencing... And, as @corywf as stated, it can get quite tedious and annoying having to manually "Update all" every few days just to keep all the apps up-to-date! (Curious note: I never realized how many times in a small number of days certain apps actually update; it's like every 2 days! Which is nice and good to say towards the app as the devs are continuously working on it -- Instagram, Nextdoor, and Chrome come to mind -- but certainly rather annoying when manually "keeping up") Especially when we've all experienced these things happening automatically and in the background...

I had this issue since the Feb or March update I think but since flashing the May update, apps are back to updating automatically

Tebor said:
I had this issue since the Feb or March update I think but since flashing the May update, apps are back to updating automatically
Click to expand...
Click to collapse
That's good! I believe it was around the same time I noticed the issue as well (although as said in my last post, this is usually something that is in the background and done automatically so I can only say it was around this point). I'm glad flashing the latest update worked -- I'm wondering, did you flash a Full Factory or an OTA? -- and hopefully it works for others. But, unfortunately, I had Full Factory flashed to the May update with no such luck. It took my guide (a little up above) to fix it on me and my gf's Pixel 2 (non-XL)...
Cheers! :highfive::victory::good:

General New Play System Update

Just had a new Play System Update 55mb. I'm now on Nov 1 instead of the August 1 after the last update.
https://imgur.com/a/yknsVGp

Same here.

Still on September. Won't find any update.
There is no way to force/sideload this, right?

@m1ckbr1t
Thanks for the heads up.
I have been checking a couple of times per week to update to the November patch, but I hadn't checked since Wednesday last week; I didn't realize the update was there until I saw your post

I went from Nov. 5 to Nov. 1

I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.

Bxrider117 said:
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Click to expand...
Click to collapse
Yes it did

Bxrider117 said:
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Click to expand...
Click to collapse
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.

MacGuy2006 said:
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
I've had none of these issues

MacGuy2006 said:
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
have you guys seen this page. I dunno what to think anymore. the hype around Pixels is such a weird thing. I get that there are bugs (and I've had a few glitches) but none of the bugs I've had are even listed here:
Google Pixel 6, 6 Pro, & 6a new updates, bugs, issues, problems tracker
A detailed & continuously updated round-up of everything related to Google Pixel 6, 6 Pro, & 6a updates, bugs, issues, & problems.
piunikaweb.com

MacGuy2006 said:
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
When the phone fails to read your Fingerprint (something along the lines of three or four times in a row), it automatically blocks/deactivates the FPS, until you unlock it with your TO KNOW security measure (in your case PIN).
I had it happen to me a couple of times over the course of this month, and it was a tad too annoying to shrug off. I definitely miss my old P4 Faceunlock, never bothered me (except when I wore masks, lel).

I had it as well ... was on Nov 1, update, reboot and still on Nov 1 ...
Note there are two things: (a) security update (Nov 5 in my case) and (b) Play-systemupdate (Nov 1 in my case).
See screenshot.

When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.

roirraW edor ehT said:
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
Click to expand...
Click to collapse
Damn that's huge for a play system update. You have an unlocked device or carrier?

roirraW edor ehT said:
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
Click to expand...
Click to collapse
You apparently ordered the supersize version at the drive-thru

pimpmaneaton said:
Damn that's huge for a play system update. You have an unlocked device or carrier?
Click to expand...
Click to collapse
Yes, I have the Unlocked (and rooted) 512 GB model, using on AT&T. Maybe it hadn't checked for any Play System updates since I rooted - since I waited to root (and disable verity and verification, and flash the stock firmware and wipe) until just a week and a half ago (I think).
I confirm it now says November 1. Thank goodness Settings has search and I'm also glad it remembers my last several searches in settings, even after a reboot.
Lughnasadh said:
You apparently ordered the supersize version at the drive-thru
Click to expand...
Click to collapse
LOL!!!!

Lughnasadh said:
I went from Nov. 5 to Nov. 1
Click to expand...
Click to collapse
You do realize that Google Play system update (Settings > About phone > Android version > Google Play system update) is different from the monthly security patch (Settings > System > System update), right?

snoopygum said:
You do realize that Google Play system update (Settings > About phone > Android version > Google Play system update) is different from the monthly security patch (Settings > System > System update), right?
Click to expand...
Click to collapse
Yes, of course.

Lughnasadh said:
Yes, of course.
Click to expand...
Click to collapse
Excellent, because judging by some of the posts here that's not quite universal.
In case anyone is still confused:
Monthly patch - Nov 5
Google Play system Update - Nov 1

any noticeable changes? I'm asked to reboot... but I rather not until the next system update