Related
Here is another update to M6E69B
https://android.googleapis.com/pack.../ea3f22cafa01264ded185bdec71b42821cec2c59.zip
I have no idea what it fixes / enhances / solves. I just got the update notice on my watch and grabbed it.
edit - I cannot see anything new other than the version. Sounds, watchfaces, installed apps, all the same. Let's hope the bugs are fixed, especially bluetooth drops.
Updated to it too. Can't spot any diffrences.
Someone on Reddit says it is a security update. Nothing else shows on Google Search.
https://www.reddit.com/r/hwatch/comments/4w9sxa/system_update_85/
Pkt_Lnt said:
Someone on Reddit says it is a security update. Nothing else shows on Google Search.
https://www.reddit.com/r/hwatch/comments/4w9sxa/system_update_85/
Click to expand...
Click to collapse
Quick glancing the patch tells me that bluetooth, wifi and clockwork were updated. More stuff and security, but mostly those.
justasalekna said:
Updated to it too. Can't spot any diffrences.
Click to expand...
Click to collapse
How to flash the zip, or unpack ?
Sent from my A168-L09 using XDA-Developers mobile app
Fauert said:
How to flash the zip, or unpack ?
Sent from my A168-L09 using XDA-Developers mobile app
Click to expand...
Click to collapse
You need to adb sideload it in recovery.
negamann303 said:
Quick glancing the patch tells me that bluetooth, wifi and clockwork were updated. More stuff and security, but mostly those.
Click to expand...
Click to collapse
Was hoping this update fixed the pairing issue on Nexus 4 phones, so I installed your latest ROM update, but it still fails to pair.
Received the update and installed automatically instantly. Haven't noticed anything different and I still can't seem to answer whatsapp calls anymore over bluetooth.
This was working before the last 1.5 update.
I have not gotten any update. Does it really take this long?
Sent from my ASUS_Z00AD using Tapatalk
Langgam84 said:
I have not gotten any update. Does it really take this long?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Tell me about it!!!! I'm still on "June" update, since I got the watch in July. I've been waiting for the OTA and it never comes. Is there a trick? I go to about>check for updates and its always "up to date". I have my "wifi" going to sleep after 3hrs. The thing always on the puck/charger overnight at 100% battery. But these OTA never happen. Looks like I've already missed the "July" update, and will probably have to get that before the "august" update....
What are you guys doing ??? Other than sideloading via adb....
mk69 said:
Tell me about it!!!! I'm still on "June" update, since I got the watch in July. I've been waiting for the OTA and it never comes. Is there a trick? I go to about>check for updates and its always "up to date". I have my "wifi" going to sleep after 3hrs. The thing always on the puck/charger overnight at 100% battery. But these OTA never happen. Looks like I've already missed the "July" update, and will probably have to get that before the "august" update....
What are you guys doing ??? Other than sideloading via adb....
Click to expand...
Click to collapse
i'm am also still at june update but got the notification of the update so when I am at home, I will charge my watch above 40% and hopefully it will be the august update.
Done the update: it now mentions july but no august yet
1.5 update can no longer make calls, battery life terrible!
I just updated last night and now I can no longer make calls, and the battery life is terrible!
"Voice Calling Info. Service not available, please try again later."
If the call does go through I can't hear the other person and they can't hear me?
Langgam84 said:
I have not gotten any update. Does it really take this long?
Click to expand...
Click to collapse
yes, it takes a while. I received mine just a view minutes ago.
That is why I posted this in the spirit of "share on XDA", so you don't have to wait. :highfive:
zdubin1 said:
I just updated last night and now I can no longer make calls, and the battery life is terrible!
"Voice Calling Info. Service not available, please try again later."
If the call does go through I can't hear the other person and they can't hear me?
Click to expand...
Click to collapse
I applied the update last night. The battery life seems about the same to me and the making/receiving calls on the watch still works.
Liquid Li0n said:
i'm am also still at june update but got the notification of the update so when I am at home, I will charge my watch above 40% and hopefully it will be the august update.
Done the update: it now mentions july but no august yet
Click to expand...
Click to collapse
No where has I seen that Huawei does monthly updates on any device. This was a patch for bluetooth, wifi, and security from comments I have found and searching. Older versions never even mentioned the security patch data. I do see better BT range and few BT dropouts, battery is the same. I don't do calls on the watch but use my BT headset for that.
Got the update today. Yep, it looks like it doesn't come at the same time for everyone. Thanks guys.
Sent from my ASUS_Z00AD using Tapatalk
Pkt_Lnt said:
No where has I seen that Huawei does monthly updates on any device. This was a patch for bluetooth, wifi, and security from comments I have found and searching. Older versions never even mentioned the security patch data. I do see better BT range and few BT dropouts, battery is the same. I don't do calls on the watch but use my BT headset for that.
Click to expand...
Click to collapse
I got my update earlier today and hope this helps my BT dropouts too! I have suspected that my BT headset dropouts might be related to my watch, so we shall see.
bbygfy said:
I applied the update last night. The battery life seems about the same to me and the making/receiving calls on the watch still works.
Click to expand...
Click to collapse
I think I may have found the issue. My Google play services looks to be way out of date. I've updated it on my phone, but it doesn't transfer to my watch? I tried updating it from the watch directly
about > version> google play services it says "checking for updates" but doesn't update it? Help!
zdubin1 said:
I think I may have found the issue. My Google play services looks to be way out of date. I've updated it on my phone, but it doesn't transfer to my watch? I tried updating it from the watch directly
about > version> google play services it says "checking for updates" but doesn't update it? Help!
Click to expand...
Click to collapse
Definitely old version. Other than the recync apps in the AW phone app or just an complete install, I have no idea, sorry
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
beezar said:
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
Click to expand...
Click to collapse
Yes it does. Feels good to have it back
Feels back to normal...
beezar said:
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
Click to expand...
Click to collapse
BTW this wasn't an issue, it was intentional from Google.
Sent from my Pixel 2 XL using XDA Labs
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
jrg67 said:
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
Click to expand...
Click to collapse
As soon as I clicked it, then I received the 54.7 MB OTA.
galaxys said:
As soon as I clicked it, then I received the 54.7 MB OTA.
Click to expand...
Click to collapse
I just looked around some more online and found others complaining of the same thing. Perhaps it's working for some but definitely not all. Just hit it again, still nothing.
Hate to hijack the thread, but this is as good a place as any to ask this really simple question of mine:
How do I update to the latest July patch if I'm still on stock May, but rooted with Magisk & Xposed enabled? I'm assuming I can just flash the full factory image zip with fastboot (disabling -w to avoid wipe) and just making sure to remove Magisk/Xposed before hand.
Latiken said:
Hate to hijack the thread, but this is as good a place as any to ask this really simple question of mine:
How do I update to the latest July patch if I'm still on stock May, but rooted with Magisk & Xposed enabled? I'm assuming I can just flash the full factory image zip with fastboot (disabling -w to avoid wipe) and just making sure to remove Magisk/Xposed before hand.
Click to expand...
Click to collapse
Yeah you can for sure do that when you flash the factory image it will remove magisk and xposed for u.
mac796 said:
Yeah you can for sure do that when you flash the factory image it will remove magisk and xposed for u.
Click to expand...
Click to collapse
Thank you for the confirmation. I assumed it would do that, but I'll probably do it myself to make sure nothing goes wrong in the flashing process.
Still slow after July update.
Sent from my [device_name] using XDA-Developers Legacy app
jrg67 said:
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
Click to expand...
Click to collapse
My work pixel 2 got the OTA yesterday. My pixel 2 xl still not seeing it.
Travisdroidx2 said:
My work pixel 2 got the OTA yesterday. My pixel 2 xl still not seeing it.
Click to expand...
Click to collapse
I tried to report the issue to google chat support but those people are useless outside of processing RMAs. 2 different reps told me the update isn't out yet bc it's dated the 5th and had no idea hitting the check for updates button overrides the staged rollout. Ugh.. I reported the issue on the pixel community board so let's see if that gets any traction.
jrg67 said:
I just looked around some more online and found others complaining of the same thing. Perhaps it's working for some but definitely not all. Just hit it again, still nothing.
Click to expand...
Click to collapse
I side loaded it using ADB. For some reason, it takes several days for the update to get to me in June (when prior updates worked after running "check for update").
I think delay is still present in july build as confimred by some users, so i will stay with May Build till now(waiting for fix).
I am still waiting for the July updates....
still haven't recieved July security update OTA for my Pixel 2 XL.
FPSRocketeer said:
still haven't recieved July security update OTA for my Pixel 2 XL.
Click to expand...
Click to collapse
Same.
For me June's OTA showed up instantly, but also still waiting for July security update.....
Sent from my Pixel 2 XL using XDA-Developers Legacy app
grgana said:
For me June's OTA showed up instantly, but also still waiting for July security update.....
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly the same here, thats so odd.. I wonder what is the cause of this, cuz some people got it pretty much instantly when Google released the update.
There are a couple of threads on this already here:
https://forum.xda-developers.com/pixel-2-xl/help/experiencing-random-restarts-t3895706
and here:
https://forum.xda-developers.com/pixel-2-xl/help/soft-rebooting-multiple-times-day-t3887222
but I felt that the issue needed a thread title which clearly spelled out the problem as it seems a lot of us are affected. Thanks to the original posters, I was able to solve my own problem but only after a useless RMA.
The good news is that Google is aware of the problem and Issue Tracker has it flagged as fixed. Hopefully it will be included in Monday's Feb update, but no ETA is listed in the Tracker thread.
https://issuetracker.google.com/issues/122141885
And, unfortunately, I can confirm that the problem was not fixed with the February update.
Good idea to create this thread
So far so good using Adguard with the March update. Almost 5 hours and no reboots.
Anyone else? Hopefully it was addressed with today's update.
Pig Vomit said:
So far so good using Adguard with the March update. Almost 5 hours and no reboots.
Anyone else? Hopefully it was addressed with today's update.
Click to expand...
Click to collapse
Not so good here, tried adguard private dns today and had the soft reboot within 2 hours.
Noticed the same on my Pixel 2 XL, but not on my Note 9 with AdGuard's DNS. Looks like a Pixel-specific issue to me, not an Android 9 issue
I continue to have had no soft or hard reboots since the March update. Adguard is working just fine for me.
And now I just had a soft reboot. I'm attributing it to AdGuard, as I never had a soft reboot before altering Private DNS settings. But it does seem much better. We'll see what the next few days hold.
*****EDIT**** And another one overnight. Problem definitely still there. I'm turning AdGuard back off.
Ugh, so this still hasn't been fixed on Pixel devices, I guess.
Still not fixed with April update, but that's Google for you...
boojay said:
Still not fixed with April update, but that's Google for you...
Click to expand...
Click to collapse
Wonder if it's fixed in Android Q
Anyway, a company that make most of it's money selling ads, I'm not surprise they take their time to fix this.
Still not fixed with April update on Pie.
Can anyone with Q give it a try and report back?
Try DNS66 instead. Same functionality, no issues.
Been running with private DNS set to AdGuard for about a week now......and no reboots. So I think it's been fixed.
If anyone on the May update is still having problems, please post back.
Pig Vomit said:
Been running with private DNS set to AdGuard for about a week now......and no reboots. So I think it's been fixed.
If anyone on the May update is still having problems, please post back.
Click to expand...
Click to collapse
Was fine since the May update until today, at which point it rebooted twice within 15 minutes.
Pig Vomit said:
Been running with private DNS set to AdGuard for about a week now......and no reboots. So I think it's been fixed.
If anyone on the May update is still having problems, please post back.
Click to expand...
Click to collapse
Just posting to confirm your findings. Been using AdGuard DNS for about a week now as my private DNS, and have had no reboots.
Sent from my Google Pixel 2 XL using XDA Labs
Well, no sooner had I changed the title and said it was fixed than Cliff posted about his reboots......and I thought, OK, isolated.....then tonight I had two reboots myself. Thus the title changed back to *NOT* fixed.
But I will say at least it seems to be WAY better, at least tolerable while weighing benefits vs. reboots. But I couldn't fit *KINDA* fixed in the title.
After the June update, unfortunately a reboot within an hour.
I thought it was just me , I rooted and moved to using ad-away
Moved to Android Q beta 4 a good week ago, AdGuard private dns enabled, works fine. No reboots.
Hello brother
I hope everyone is good,
I have been having a problem for the past two months. I'm getting all kinds of updates of the phone very late, updates to any problems with the Google Play Store, and OTA Security Update.
I do not understand why this is happening, is there any solution?
If there is a solution, sharing is very beneficial.
Thanks in advance
Saeed
*Note : Device Not Rooted
A.saeed said:
Hello brother
I hope everyone is good,
I have been having a problem for the past two months. I'm getting all kinds of updates of the phone very late, updates to any problems with the Google Play Store, and OTA Security Update.
I do not understand why this is happening, is there any solution?
If there is a solution, sharing is very beneficial.
Thanks in advance
Saeed
*Note : Device Not Rooted
Click to expand...
Click to collapse
What do you mean too late? Delayed or the fixes to the problems are taking too long?
Your post is not specific enough. Give examples to reproduce.
I know there were a bunch of topics on this earlier in the year but I have yet to find a solution and here's the weird thing...
I have a P6 Pro (Android 12.1) coworker has a P6 (Android 13) and both of us when at home (different homes lol) will have the Wi-Fi turn off, and a few seconds later turn back on again.
The problem for both of us started about a month ago. This is way too coincidental. Neither of us had this problem before and since we are on two separate but similar phones running two different versions of Android could this be a Google connectivity related app that is causing this problem? Maybe a bad update to something?
Btw I've tried all the fixes mentioned in previous posts. Everything but a factory reset and nothing has worked. It only happens once or two a day but it's annoying
I noticed that as well during the last couple of weeks. This wasn't happening before for sure. Still no idea what's causing it.
arvylas said:
I noticed that as well during the last couple of weeks. This wasn't happening before for sure. Still no idea what's causing it.
Click to expand...
Click to collapse
Thank you. The Google Connectivity Service app that helps manage Wi-Fi was updated about a month ago.
Since we all have different versions I'm thinking this has to be app related. Nothing else makes sense
I had the same issue back on 12.1 on my P4a...and oh man did it annoy the sht outta me! I too assumed it was prolly app related. I spent ages trying to chase it down. Then google offered me $300 trade-in plus a pair of Pixel Buds for a P6a...suddenly I just stopped looking.
Hand76 said:
Thank you. The Google Connectivity Service app that helps manage Wi-Fi was updated about a month ago.
Since we all have different versions I'm thinking this has to be app related. Nothing else makes sense
Click to expand...
Click to collapse
Did you try disabling the Google connectivity from app info?
arvylas said:
Did you try disabling the Google connectivity from app info?
Click to expand...
Click to collapse
Not yet but may that later tonight
For now I tried rolling back to v53 of Google connectivity service to check if that's the culprit.
arvylas said:
For now I tried rolling back to v53 of Google connectivity service to check if that's the culprit.
Click to expand...
Click to collapse
Since it also happens with GrapheneOS which doesn't have that, its not the culprit.
I'm using the modem from qpr beta. Is anyone else with the problem using this one?
arvylas said:
I'm using the modem from qpr beta. Is anyone else with the problem using this one?
Click to expand...
Click to collapse
Modem firmware isn't relevant to wifi.
I don't want to jinx it but after happening to me every day for a few weeks it stopped. Been a week now with no changes made on my end.
This had to be a Google app. They are always getting updated and not always for the better