BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

dersie · Jul 26, 2017 at 7:11 PM

bcw0612x1 said:
Now I'm just trying to figure out a way to get rid of the persistent 2.0 software notification card prompting me to update. That's another issue altogether.

My ZW2 is still in 1.5 and I hope I can always avoid the upgrade 2 message

(not happen until now) Hopefully I since have my Sony SW3 wich is not 2.0 compatible

My LG-R was updated month ago but I do not like the lost of double and triple click for Theater and max brightness

AlniteK · Jul 25, 2017 3 0 0

Update notification back again this morning

Hi,

I had followed this guide and was happy again with my LG Watch R back to 1.5 for at least 20 days, when this morning, the update notification has come back !!!

Of course, if I try to make the update, it fails.
Due to TWRP in the bootloader, I presume.

Any idea ?

Rafal L · Aug 10, 2017 at 11:50 AM

AlniteK said:
I had followed this guide and was happy again with my LG Watch R back to 1.5 for at least 20 days, when this morning, the update notification has come back !!!

Exactly the same today morning happened to me. Maybe it is because updated Google services?

nagi603 · Aug 10, 2017

+1, update notification came for my watch too. Dam you, Google!

the commands
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gsf/.update.SystemUpdateService
are no longer enough unfortunately.

Weird thing is that I can't remember when I updated Google services last time. Definitely at least weeks ago.

...Just what I needed, a potentilly unusable watch right before a long holiday. Google has the best presents....

Seriously, I'd love it if google just wouldn't mess with it for 5-10 years?
(I looked at installing custom ROMs, the one I found basically started with "install linux". Sorry, can't and won't.)

edit: tried
cd /data/data/com.google.android.gms/app_download/
echo "" > update.zip
chattr +i update.zip

but still no cookie.

edit 2: tried the shotgun approach:
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

aaand while these helped in the past, they don't help now.

Edit 3: tried grepping the full file list for update.zip. *.zip, *.img, not one hit besides those I put there or the immutable update.zip.

ninjeratu · Aug 11, 2017 at 9:00 AM

Same here. So it would seem it's pushed from the AW app to the watch instead of pulled from the update services on the watch?

I tested reflashing the M1D65H images (and adding TWRP and superSU) and that worked. Over night. But now the notification is back.

carnagecjb · Aug 11, 2017

If that's the case, I'm kinda confused. The last update my wear app had was a full two weeks ago. So there has to be some method of pushing updates without updating the app...

[Edit]
I'm at work without my cradle, so I can't test, but anybody have any idea if this would work?
https://forum.xda-developers.com/showthread.php?t=2249350

dieselbuddeh · Aug 11, 2017 at 4:11 PM

nagi603 said:
+1, update notification came for my watch too. Dam you, Google!

the commands
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gsf/.update.SystemUpdateService
are no longer enough unfortunately.

Weird thing is that I can't remember when I updated Google services last time. Definitely at least weeks ago.

...Just what I needed, a potentilly unusable watch right before a long holiday. Google has the best presents....

Seriously, I'd love it if google just wouldn't mess with it for 5-10 years?
(I looked at installing custom ROMs, the one I found basically started with "install linux". Sorry, can't and won't.)

edit: tried
cd /data/data/com.google.android.gms/app_download/
echo "" > update.zip
chattr +i update.zip

but still no cookie.

edit 2: tried the shotgun approach:
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

aaand while these helped in the past, they don't help now.

Edit 3: tried grepping the full file list for update.zip. *.zip, *.img, not one hit besides those I put there or the immutable update.zip.

Code:

[ 08-11 11:08:29.846   964:  964 W/StreamLayout ]
Desired peek height 146.000000 does not fit in the range [15, 132]

[ 08-11 11:08:29.867   692:17996 I/ActivityManager ]
START u0 {act=android.settings.SYSTEM_UPDATE_SETTINGS pkg=com.google.android.gms} from uid 10012 on display 0

[ 08-11 11:08:31.150   692: 1510 I/ActivityManager ]
START u0 {act=android.settings.SYSTEM_UPDATE_SETTINGS pkg=com.google.android.gms} from uid 10004 on display 0

[ 08-11 11:08:31.152   964:  964 W/ActionFactory ]
activity not found.
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.SYSTEM_UPDATE_SETTINGS pkg=com.google.android.gms }
	at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1798)
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1512)
	at android.app.Activity.startActivityForResult(Activity.java:3930)
	at android.app.Activity.startActivityForResult(Activity.java:3890)
	at android.app.Activity.startActivity(Activity.java:4213)
	at com.google.android.clockwork.home.apps.AppIntentUtil.startActivityFromUserAction(AppIntentUtil.java:45)
	at com.google.android.clockwork.home.apps.AppIntentUtil.startActivityFromUserAction(AppIntentUtil.java:25)
	at com.google.android.clockwork.home.stream.factory.ActionFactory$2$1.postExecute(ActionFactory.java:160)
	at com.google.android.clockwork.home.voiceactions.SendIntentWithPermissionCheckAsyncTask.onPostExecute(SendIntentWithPermissionCheckAsyncTask.java:55)
	at com.google.android.clockwork.home.voiceactions.SendIntentWithPermissionCheckAsyncTask.onPostExecute(SendIntentWithPermissionCheckAsyncTask.java:10)
	at android.os.AsyncTask.finish(AsyncTask.java:651)
	at android.os.AsyncTask.-wrap1(AsyncTask.java)
	at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:668)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:148)
	at android.app.ActivityThread.main(ActivityThread.java:5422)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

I pulled this with logcat. Maybe it will help the community.

DarkDvr · Aug 11, 2017 at 5:37 PM

Same issue, "charge watch to install update" notification is back. Disabling update services doesn't help. "update.zip" file is still in /cache/, and cannot be touched, even under SU.

Not sure what else to try.

nagi603 · Aug 11, 2017

DarkDvr said:
Same issue, "charge watch to install update" notification is back. Disabling update services doesn't help. "update.zip" file is still in /cache/, and cannot be touched, even under SU.

Not sure what else to try.

Weird, I had no such file there, besides my own 1 byte update.zip

edit:
disabled com.google.android.gms/.chimera.GmsIntentOperationService and it might have solved the issue.... at least the notification disappeared immediately.

I noticed it calling an update in logcat:
08-11 19:19:49.031 1287 1593 I SystemUpdate: [Execution,InstallationEventIntentOperation] Received intent (Intent { act=com.google.android.gms.update.INSTALLATION_EVENT cat=[targeted_intent_op_prefix:.update.execution.InstallationEventIntentOperation] cmp=com.google.android.gms/.chimera.GmsIntentOperationService (has extras) }) with event 200.

now restarting and hoping for no update...

edit 2: no update notification yet, ad it should have already appeared. Though I have no idea what else I might have broken in the process. We'll see

command to run is:
adb shell su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
(absolutely no warranties it works for you and/or doesn't break things. It might burn your house down, raise zombies, start voting for Trump Jr, etc...)

carnagecjb · Aug 11, 2017 at 6:52 PM

I'll give it a shot tonight when I get home, and report my results!

AlniteK · Jul 25, 2017 3 0 0

nagi603 said:
adb shell su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService

I

Done...
No notification yet, after 5 minutes...

Seems like you find it.
You're great !
Thx,

paggps · Aug 11, 2017 at 10:33 PM

I have had this same problem today, and this solution works !
Thank you very much for sharing it !

nagi603 said:
command to run is:
adb shell su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService

carnagecjb · Aug 12, 2017 at 8:55 PM

Applied the fix last night, been working great for the last 15 hours or so...

kkazakov · Aug 14, 2017 at 1:53 PM

What is the reason for 'su' command just hanging the shell? Just ... nothing happens. Sometimes "SuperSu has crashed" or sth like that appear.

majinvegeta3886 · Aug 14, 2017 at 2:13 PM

after pm disable com.google.android.gms/.chimera.GmsIntentOperationService
i had to pm disable com.google.android.gms
then pm enable com.google.android.gms to get the notification off the screen.

FloW_Hamburg · Dec 14, 2014 3 0 0

su crashes for me too

I experienced the crashing of su too.
I'm able to connect my watch and start the adb shell but when entering any su command either the cmd window freezes or I get a su crashed message on my watch.

kkazakov · Aug 15, 2017 at 5:52 AM

FloW_Hamburg said:
I experienced the crashing of su too.
I'm able to connect my watch and start the adb shell but when entering any su command either the cmd window freezes or I get a su crashed message on my watch.

I tried everything ... reflashing the image, re-flashing the SuperSU, different versions, but the result is the same - it crashes or freezes. Help!

ninjeratu · Aug 15, 2017 at 8:38 AM

kkazakov said:
I tried everything ... reflashing the image, re-flashing the SuperSU, different versions, but the result is the same - it crashes or freezes. Help!

Stupid question: What if you don't pipe commands through the su command, and instead just spawn a su shell and THEN enter the commands?
[email protected]:/ $ su
[email protected]:/ #
[email protected]:/ # pm list packages
...

kkazakov · Aug 15, 2017 at 10:09 AM

ninjeratu said:
Stupid question: What if you don't pipe commands through the su command, and instead just spawn a su shell and THEN enter the commands?
[email protected]:/ $ su
[email protected]:/ #
[email protected]:/ # pm list packages
...

It hangs on 'su' command.

So I don't get the row after 'su'. For the record - this was working a week ago. I already patched it after one of the factory resets of the watch.

One of my other options would be to go with custom rom ... but that's so not "User-friendly", Google ...

ninjeratu · Aug 15, 2017

kkazakov said:
It hangs on 'su' command.

So I don't get the row after 'su'. For the record - this was working a week ago. I already patched it after one of the factory resets of the watch.

One of my other options would be to go with custom rom ... but that's so not "User-friendly", Google ...

Then I'd wager that you're on a "wrong" SuperSU.
It's quite possible that the flash went OK, but if superSU were properly installed it would work.
You would probably need a systemless SuperSU and TWRP with squashfs
SuperSU 2.79
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
TWRP with squashfs
http://www.mediafire.com/file/rhfr5ps2c8ssxx5/twrp-3.0.0-0-lenok+squashfs.img
Factory reset, flash/boot twrp then flash superSU. ANd look out for errors.

I assume you're on a Lenok, not Dory.

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Senior Member

New member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Member

New member

Senior Member

Senior Member

Senior Member

Senior Member