yashsingh1/xdaforums huggingface dataset:
[Huawei Watch] TheSt33v:
Sounds like you might need to factory reset. The method I put in the OP has you disabling the package before the watch connects to the internet. I tried that and it worked perfectly.
[Huawei Watch] cherjr:
I've tried it your way (did factory reset, did all that "pm disable" things before connecting the watch to my phone, erasing data of google play services in the same time (before connecting as well)) - nothing seems to help now: in several hours there's that f...g notification again...
[Huawei Watch] danbest82:
Woke up to the notification again. You might be right. I'll try disabling WiFi then trying the disable. I personally don't feel like factory resetting it unless I reeeally have to and if I do, I might as well try 2.0. How is 2.0? Did any updates help fix the issue with notifications not popping up when received?
[Huawei Watch] TheSt33v:
I never had that issue on 2.0 so I'm not sure. It seemed to be an app-specific issue. I get all notifications just fine.
[Huawei Watch] TheSt33v:
Erasing the data in Google play services may have reset the permission you disabled. Don't do that. Try it my way exactly. If you try it that way exactly and you still see it, get me a logcat. I'm not sure why this is only working for me, but I will fix this.
[Huawei Watch] danbest82:
Maybe that's my issue too. I'll run all the pm disable commands again. My other thought is to just keep WiFi off until need to file transfer from phone.
[Huawei Watch] TheSt33v:
Keeping wifi off won't do any good. It can still get the update through your phone via bluetooth like it did before wifi on watches was a thing.
[Huawei Watch] danbest82:
Ah dammit. Good point. Too bad Google play services does everything on the watch and can't just disable it. Haha.
[Huawei Watch] HenryLolsen:
update notification came back for me as well.

I did everything according to the first post (apart from unsu), will report if the the notification comes back again...
[Huawei Watch] HenryLolsen:
...and it's back!

logcat shows me the following:

[ 02-04 13:50:29.009 2164: 4812 I/CmaSystemUpdateService ] showing system update notification

here is the full dump: https://1drv.ms/t/s!Ap1FALPFyxNigugJZJwcejn56ZU6yg
[Huawei Watch] TheSt33v:
Alright [MENTION=2523916]danbest82[/MENTION] and [MENTION=7128152]HenryLolsen[/MENTION], it's time to go nuclear on this sonofabitch. Try the following:

1. Factory reset.

2. Root if needed.

adb shell

su

pm disable com.google.android.gms/.update.SystemUpdateServiceSecretCodeReceiver

pm disable com.google.android.gms/.update.SystemUpdateServiceActiveReceiver

pm disable com.google.android.gms/.update.SystemUpdateServiceOtaPolicyReceiver

pm disable com.google.android.gms/.update.SystemUpdateService

pm disable com.google.android.gms/.update.SystemUpdateWearableActivity

pm disable com.google.android.gms/.update.SystemUpdateServiceReceiver

3. Reboot

4. Set up watch.

After doing that, whenever I select System Updates in Settings I get "Could not launch app," so it seems pretty dead to me. I decompiled the google play services apk and that's officially every service it contains that has a reference to system updates.
[Huawei Watch] JimBobMcSLim:
Hey all,

FYI I've been on 1.5 for a few months and it has been great. I've just started getting the update notification so looking to resolve as well. I have disabled

pm disable com.google.android.gms/.update.SystemUpdateService

pm disable com.google.android.gsf/.update.SystemUpdateService

removed the data/data/com.google.android.gms/app_download/update.zip file and then disabled -

pm disable com.google.android.gms/.update.SystemUpdateServiceActiveReceiver

Now stuck on the "System Update Paused - To continue, charge your battery" notification despite numerous reboots.

About to try disabling the remaining services mentioned in first and one of the more recent posts
[Huawei Watch] danbest82:
Thanks man! I'll try these later today when I get to my computer. I'm thinking that a main issue is that all the services we disable get enabled again after Google play services updates so we'd have to do thus each time. I'll report back in a few days.
[Huawei Watch] TheSt33v:
I was hoping it didn't work that way, but that would be a good explanation for why things work for a while and then suddenly the update reappears. I'll make a batch file that people can use to quickly re-disable those permissions and remove the update if it's there. It's not the best solution but it might be the best we can do.

When I get home tonight I'll test that theory. I'll put my watch back on 1.5, disable everything, and manually update to the latest google play services and see what happens. Maybe I can figure out how to make a script that runs at boot to automatically disable those services and remove the update if it's there. That way if you ever see the update notification you could just reboot it away.

UPDATE: I think I found something important. The latest version of Google Play Services has a service called com.google.android.gms.update.SystemUpdateGcmTaskService. This is not in the previous versions. Not only that, but a few of the services we've been disabling don't even exist in the latest version. Looks like somewhere down the line, Google changed how it handles OTAs. Next time you try everything we've discussed previously and the update comes back, try giving it a pm disable com.google.android.gms/.update.SystemUpdateGcmTaskService, followed by a rm /data/data/com.google.android.gms/app_download/update.zip. Let me know how that goes.

New theory: new versions of the app don't re-enable the previously disabled services as evidenced by the previous post indicating that he has been update-free for several months. The reason why the updates are reappearing is because the latest GPS changed how it handles updates. So to disable updates, it makes the most sense to factory reset, update GPS manually and disable relevant services in latest GPS. That way, we're good to go until Google decides to shuffle things around again. Unfortunately we might have to keep finding and disabling new services as they appear, but this shouldn't happen too often and if we're lucky, it won't happen at all. I'll test this tonight.
[Huawei Watch] TheSt33v:
Okay everyone, new test time. Do the following from adb shell su:

pm disable com.google.android.gms/.update.SystemUpdateServiceActiveReceiver

pm disable com.google.android.gms/.update.SystemUpdateService

pm disable com.google.android.gms/.update.SystemUpdateGcmTaskService

pm disable com.google.android.gms/.update.SystemUpdateWearableActivity

Delete the update if it's there. If you can't get a notification to go away, factory reset, install the latest Google Play services (see OP for instructions on how) and then perform those four commands again. Report back with the results.
[Huawei Watch] danbest82:
OK, I've tried disabling everything in the previous post and found that the 3 you removed from this post were also not on my watch. I added the GcmTaskService to my disabling fun. Just rebooted. I will enable WiFi again and see what happens by the morning. BTW, I'm being stubborn and have not factory reset but will not post any issues if they arise until I do actually factory reset and try everything you've said. Thanks a lot for looking into this stuff even though you don't even use 1.5 anymore. You've been a great help to us.
[Huawei Watch] TheSt33v:
That's fine. Factory resetting is only necessary to remove any existing update notifications that you can't get rid of any other way. If you can get rid of it by other means then it shouldn't affect anything. And no problem. I needed a project. Also, let me know what happens when you go to System Update in settings.
[Huawei Watch] danbest82:
"Could not launch app"! Fingers crossed.
[Huawei Watch] TheSt33v:
Uhhggg. I'm getting a "Failed to install system update" notification. It goes away for a while after a reboot, but it comes back. Almost got it...
[Huawei Watch] danbest82:
I woke up to "charge watch to install update". Weird thing is that it was on the charger all night. I also didn't factory reset so we'll see what others get.
[Huawei Watch] TheSt33v:
I got that too. I managed to catch it before I went to bed, so I went logcat-diving. I found a likely culprit, com.google.android.gms/.chimera.GmsIntentOperationService. I disabled that, rebooted and went to bed. This morning, no notifications. Try that.

UPDATE: 3:22 PM and still no update notifications. Could it be that we finally beat this thing? God I hope so.
[Huawei Watch] cherjr:
Can you confirm everything's fine? If so - what exactly is the final list to pm-disable?

Thanks in advance
[Huawei Watch] HenryLolsen:
I had the normal update notification ("swipe right to install") showing up and did the following yesterday in adb shell su:

pm disable com.google.android.gms/.update.SystemUpdateServiceActiveReceiver

pm disable com.google.android.gms/.update.SystemUpdateService

pm disable com.google.android.gms/.update.SystemUpdateGcmTaskService

pm disable com.google.android.gms/.update.SystemUpdateWearableActivity

pm disable com.google.android.gms/.chimera.GmsIntentOperationService

rm /data/data/com.google.android.gms/app_download/update.zip

reboot

Since then I charged once to 100% and have yet to see the notification pop up again. So it seems to work for now.

Thx [MENTION=5901115]TheSt33v[/MENTION] for all the effort!
[Huawei Watch] danbest82:
Thanks! Just disabled it and rebooted last night. No notification by the morning....We might be good!?

The list that [MENTION=7128152]HenryLolsen[/MENTION] posted is pretty much what I did over a few days. I'm sure [MENTION=5901115]TheSt33v[/MENTION] will update the OP.
[Huawei Watch] TheSt33v:
Seems to be. See OP.
[Huawei Watch] PureXTC:
I've seen quite a lot of activity in this thread lately and thought I may chime in as well.

I had this same issue many months ago (back in October) and have compiled my own set of commands that has eliminated any OTA/update or notification from appearing on my watch since. I'm currently using stock AW 1.5.

The only niggle I've found is that I don't get a confirmation when sending a text through "OK, Google" although it still works just fine . I just see the error "Try again on your phone".

The two final commands are possibly "key" as I've write-protected the actual directory the update downloads to. Therefore, with no update.zip being saved there is no notice to update.

I should note there was no clearing of Play Services, no factory reset, just a simple reboot of my watch after these commands.

adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
adb shell su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService

adb shell su -c rm /data/data/com.google.android.gms/app_download/update.zip
adb shell su -c chattr +i /data/data/com.google.android.gms/app_download
[Huawei Watch] TheSt33v:
Thanks. A few of the services you are disabling in gms no longer exist in the latest version, and there is at least one new update-related service that you are not disabling. I decided not to attack it from a gsf angle. It just seemed to me since I was getting such a variability in what worked and what didn't among different devices that gms had a larger role in the process than gsf since that one is updated so much more frequently. But yes, that .chimera service was definitely the missing piece of the puzzle. I considered making the download folder read-only like you did, but I decided not to because I didn't want a situation where the download requests were being constantly made and denied forever, which could potentially be a huge battery/resource drain. I never tested this theory though so maybe that wouldn't happen, but my thinking was if update.zip gets downloaded, that eliminates the need for additional requests and isn't an issue if we kill the rest of the players involved.

As for factory resetting and wiping data, that's actually not strictly necessary in my method either. I've just been telling people that for testing purposes to eliminate unknown variables, and I kept that in the guide for the same reason. I want to be as noob friendly as possible.
[Huawei Watch] PureXTC:
The blocking of write requests to the download folder hasn't impacted my battery at all. I average about 2.5%/hr on my watch (going since October since running my commands) so I can attest that there is no problem setting it to read-only.

This has definitely been a pain trying to narrow things down as to the main instigator and I commend your efforts! Sorry I didn't see things sooner or I'd have pointed you towards chimera.

I haven't torn apart Play Services in a while so I don't exactly know what isn't relevant any more with my command set (if it ain't broke :) ).

I'll guarantee this is what keeps those dang notifications from appearing unless Google makes a large change to how Play Services works. Been update notification free for 4+ months now!
[Huawei Watch] TheSt33v:
Well I suspect in your case it's not affecting your battery because the services you have disabled have disabled the update requests. Or maybe not. Who knows. I suspect that chimera service is the most important one because before my investigation, someone dug up a list that was almost identical to yours minus that service and it didn't work. Or rather it did work on a fresh, factory version of AW 1.5, only for the update to reappear sometime later (presumably after gms gets updated).

In any case, problem solved. If/when it reappears again, I'll be glad to take it on.
[Huawei Watch] jdsm:
Please please do you have any video tutorial to explain how to do that

It is very complicated to me and i can't do it

---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------

Please please do you have any video tutorial to explain how to do that

It is very complicated to me and i can't do it
[Huawei Watch] inteks:
No sorry . No Video... But you can ask if something isnt clear.

Gesendet von meinem SM-G935F mit Tapatalk
[Huawei Watch] jdsm:
Thank you for your respond

Unfortunately all is not clear for

I made the downgrade to 1.5 following a video on you tube + the method on xda

Can you please calrify the steps for me i am really can't use the watch because of this stupid notification
[Huawei Watch] jdsm:
Please help me
[Huawei Watch] inteks:
If you have downgraded allready. Next step is root.

Connect watch to computer and start commandline.

Then copy supersuwear.zip to sdcard with push

adb reboot bootloader

fastboot boot negalite-HW-TWRP-3.0.3-v1.5.img

Then install this zip in twrp on watch.

Reboot the watch.

Then in adb shell type "su" to get rootshell

Then you can execute the commands to disable the updateservice...

Gesendet von meinem SM-G935F mit Tapatalk
[Huawei Watch] paco3346:
You all are genius! Disabling chimera was the final step.

Side note- even without removing the update.zip the notification was gone after disabling chimera and a reboot. (I still removed the file to reclaim the space)
[Huawei Watch] pan_sattan:
it looks like maps dont work after disabling of this things...
[Huawei Watch] TheSt33v:
Can anyone else confirm this?
[Huawei Watch] JimBobMcSLim:
Step 1 needs some expansion for us noobs. Getting a file onto your unrooted watch is not exactly straightforward. St33v, consider editing the first post?

1. Transfer supersuwear.zip to a tmp folder on your watch:

adb shell mkdir /sdcard/tmp

adb push supersuwear.zip /sdcard/tmp/

:good:

---------- Post added at 11:26 AM ---------- Previous post was at 11:01 AM ----------

And I'm only just realising that the linked file near the top of the first post needs to be flashed in using TWRP or similar as well? I've just been through what I thought was the whole process in the first post and still stuck on Android 2.0. Too many assumptions made...
[Huawei Watch] JimBobMcSLim:
So I appear to now be cooking but not exactly with gas. Back on 1.5 again, rooted, etc but now I have "Unfortunately, Fit has stopped" message every 5 seconds. Slightly more annoying than the previous occasional Update the system or similar notification I was getting.

AW - 1.5.0.3594574

Google Play Services - 12.5.21

Android OS - 6.0.1

Security Patch Level - 1 January 2017 [Can we update the Sec patches but stay on AW1.5 or are they interrelated?)

---------- Post added at 12:47 PM ---------- Previous post was at 12:45 PM ----------

Oh yeah, and at some point my tilt-to-wake stopped working during all of this. I upgraded back to 2.0 and factory reset etc to no avail. Not sure if it's related to my self inflicted version yo-yo-ing or just bad timing.
[Huawei Watch] TheSt33v:
Meh. I feel like if you're going to be messing with stuff like this, you should probably know about these things or at least be willing to do the research to figure it out, as you commendably did. Also, my post is pretty old and has gotten this far without any requests for clarification, so I think I'll leave it as is. But if I get any requests like this in the future, I will refer them to your post.

Re: security patches, no. This is part of the firmware. No firmware update, no security update. However, unless you're a celebrity or an international spy, I wouldn't be too worried about someone trying to hack your watch. Since its primary portal to the world is your phone (especially on AW 1.5), they would have to get through that first, and if they could get to that then they wouldn't need to bother with your watch.

Re: tilt to wake, I'm not sure what would have broken that, but I would recommend waiting a few hours before concluding that something is broken. AW does a lot behind the scenes after the initial setup, and the performance hit is pretty massive while this is happening. If you need to take the nuclear option and start from super-scratch, here is the only known official factory image for the HW: https://www.androidfilehost.com/?fid=745425885120748838. Use fastboot to flash it, not TWRP.
[Huawei Watch] JimBobMcSLim:
Tilt to wake is most definitely broken as well as the Heart Rate Monitor at present. Odd as the HRM was busted on 2.0 and downgrading to 1.5 the first time around made it work again. I think I have botched my permissions somewhere and I suspect somethings related to Google Fit are contributing. Like, without the Fit app on the phone or with the App but some odd permissions settings, the sensors like HRM are crippled? I have read some odd stuff in other forums about Fit settings and permissions breaking the Tilt to wake.
[Huawei Watch] TheSt33v:
Then I would recommend flashing the factory image. That's about as reset as you can get. There should be a batch file in there that does all the flashing for you. All you have to do is boot the watch in fastboot mode and plug it in to a computer that has fastboot working. Make sure you extract all of the files in the factory image to the same folder that contains fastboot.exe, and make sure the watch's bootloader is unlocked. After you do that, boot it up and see if everything is working. If it is, get TWRP back on there and flash the "downgrade" (which will now be an upgrade) package to get on the most recent 1.5.
[Huawei Watch] sm00th4f3:
it worked once after doing this. You really have to have the newest gms apk for it to work.

It's quite stupid but, that's how it is.
[Huawei Watch] dave457:
Hi

Is there a stock image of Wear OS, i.e. a recent version 2, that could be used in a "flash-all.bat" type way. I have one for version 1.5 put to update back to the latest version is a real pain.

I am looking for this as an easy method to revert to latest stock, removing TWRP etc.

Anyone have a file or a link?

Thanks
[Huawei Watch] Mad07:
TWRP doesn't make trouble. You can still use the recovery with the latest Stock FW. It's working without any problems on my side
[Huawei Watch] d.brown:
+1
[Huawei Watch] jasonic8:
I have this problem - which indicates the ROM is not rooted right? But I flashed the supersuwear.zip - does that not root the ROM?

I'm confused - sorry.

Should it be a factory reset and then flash supersuwear.zip - so item 2 and then 1 from the first page?
[Tilt, TyTN II, MDA Vario III General] photon01:
Bump this, i have been thinking about this also, if it had 2 seperate headphone and mic plugs, the adaptors for say a guitar or bass would be basic, since the mic is mono and so are the insturments. If i had the tools for micro-miniature soldering, i'd be able to do it easily. but i dont, so if any1 wants to make a couple, i would purchase it in a heartbeat.

You can use meteor or any recorder on the handset, if you're in a quiet room the internal mic does record sound pretty good. if there was a way to do multi tracks at the same time(multiple leads) now that would be something.
[Tilt, TyTN II, MDA Vario III General] calebw:
Yep, big bump from me. MeTeor is fantastic, having a little recording studio anywhere is great. However, getting a line-in would just open up everything!

Caleb
[LG G5 Questions & Answers] uid_0:
We got a "water resistant" case for my wife's H860N which turned out not to be so water resistant. Now after letting the phone, battery, SIM, and memory card dry out when trying to power the device on it will not boot (at least nothing on screen) and will just sit there with the blue notification LED blinking. I've searched here and Google but can't seem to find a reference which describes this behavior. Does anybody know what the flashing LED with no screen response indicates? The SIM and the memory card seem to have survived the ordeal as they both work in another phone.
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] diazabdulm:
Greetings LeEco 2 Users!

This is a topic for developers to share their work concerning Nougat support for our device. I am currently working on making madOS work on the X620 but it's giving me bootloop. I will share the ZIP so anyone can help out!

HERE'S MY BUILD:

PLEASE TEST AND HELP OUT!

https://mega.nz/#!OVoxnCKS!PvxlclotIfQ3Z5GDUKwDrmO1XikrO8sqXr1BSPzQ6RI
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] senseijtitus:
Can this b port it for le2x526?
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] Palm Trees:
mad = MediatekAndroidDevelopers.
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] Paulietgm:
X620

Wow, finaly, I have been waiting so long for this, custom rom 7.1 for my le 2 x620. I will try this soon. Keep it up!

Tired to see custom roms 7.1 only for x52x variants.
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] CYB3R0ID694:
If possible..

Please make Source available..
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] matheustheus27:
Do you use a madOS of which device to do this?
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] SrdjanM:
As i can't find anywhere i nees to do it on this way. Is there anyone who know where to find 026s for Le 2 Pro x620?

I'm now on 023s and everything is great except battery life, there are pretty big problem, so im now looking for 026s for this model or if somebody knows how to solve this battery problem. Thanks in advance
[LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve] Palm Trees:
There are plenty of rom options here: http://www.leeco.re/forum/115-mtk-x20-rom/ . You can try flashing "ROM LeEco Le 2 X620 X626 5.9.26S06.141 r2.0 by_WoRFReD MULTI" http://www.leeco.re/topic/5330-rom-leeco-le-2-x620-x626-5926s06141-r20-by_worfred-multi/