Related
Hi
I've made the update Android Wear 2.0 on my LG G Watch R (through the Play Store).
However, i really do not like the new interface and how notifications are now displayed.
Is it possible de downgrade Android Wear to old version 1.5? How should I do that?
Thanks for your help, have a nice day.
nicodvt said:
Hi
I've made the update Android Wear 2.0 on my LG G Watch R (through the Play Store).
However, i really do not like the new interface and how notifications are now displayed.
Is it possible de downgrade Android Wear to old version 1.5? How should I do that?
Thanks for your help, have a nice day.
Click to expand...
Click to collapse
you can flash stock image via fastboot https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
After having downgraded, has anyone managed to get rid of the update message?
midafaya said:
After having downgraded, has anyone managed to get rid of the update message?
Click to expand...
Click to collapse
Yeap, I rebooted my watch and had no more the update message.
nicodvt said:
[*] That's finished, my watch was again on Android Wear 1.5 <3
[/LIST]
Click to expand...
Click to collapse
Hi Nicodvt. Thank you for this good summary.
Unfortunatly, our friends from Google have perhaps not performed a lot for the Android Wear 2.0 new features implementation but they are really good in the development of their OTA procedure!
After the downgrade to AW1.5, even after the installation of the Android Wear 1.5 apk smartphone application and settings in Playstore not to automatically update the applications, the "always on" notification on the watch to install the new version of Android Wear 2.0 appeared one day after the downgrade....
See post below to remove the notification.
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
adlx.xda said:
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
Click to expand...
Click to collapse
Ah, that seems to work (for now)!
It removed the notification (after applying and rebooting) and has not reappeared for 45 minutes even after a few reboots.
I confirm these 2 commands seem to remove the upgrade notification.
For information, the creation of an empty update.zip file in the /cache/ folder was not enough and the upgrade notification appeared spontaneously one day later.
Thanks
It's great, I also want to come back the ver 1.5, but i dont have an experience in this field. I have problem in step 2 and try to install the ADT,... but it doesnt work very well. Can I contact to you via facebook or skype? Thank you.
nicodvt said:
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
Click to expand...
Click to collapse
dungkr89 said:
It's great, I also want to come back the ver 1.5, but i dont have an experience in this field. I have problem in step 2 and try to install the ADT,... but it doesnt work very well. Can I contact to you via facebook or skype? Thank you.
Click to expand...
Click to collapse
Check your private message @dungkr89 if you want to reach me.
Hi,
If you have some difficulties, I made this memo for me.
Downgrade LG G Watch R and block OTA upgrades
---------------------------------------------
Prepare the PC
--------------
Install adb-setup-1.4.3.exe on the PC
Place in folder (C:/wear for example) all the necessary files :
- M1D65H_boot.img
- M1D65H_recovery.img
- M1D65H_boot_system.img
- SuperSU-v2.78_Lg-G-Watch-R.zip
- twrp-3.0.0-0-Lg-G-Watch-R.img
Prepare the watch and smartphone
--------------------------------
On the smartphone, dissociate and restore factory settings on the watch.
Remove ALL applications on the smartphone in relation with the wear watch (excepted Android wear). This is usefull to avoid a long installation with risk of applications not compatible with the Android Wear version which will be installed on the watch.
Reassociate the watch with the smartphone
On the watch :
Activate developper mode (click 7 times on the build number in version menu)
Then in the developper menu, activate adb degug
Connect the watch to the pc via usb
On the PC :
DOS commands invite
Change directory (cd) to point he folfer where are located the .img files.
Type:
adb devices
// The watch device is present and ready
// Switch the watch in fastboot mode
adb reboot bootloader
adb devices
// If the watch is seen oem locked you have to type:
fastboot oem unlock
// If the watch has not been restored (I recommend to do it before via the smartphone)
//fastboot format userdata
//fastboot format cache
//fastboot format system
Send the firmware to the watch
------------------------------------
fastboot flash boot M1D65H_boot.img
fastboot flash recovery M1D65H_recovery.img
fastboot flash system M1D65H_system.img
Restart the watch via the screen menu
ROOT the watch
--------------
adb reboot bootloader
fastboot flash recovery twrp_xxx.img
//fastboot boot twrp_xxx.img (if command below is rejected)
adb push SuperSU_xxx.zip /sdcard/
// From the watch screen, by typing on the screen and following instructions, move to sdcard folder and install from zip the SuperSU_xxx.zip application
Then, when the patch has been installed (quite long), the watch has restarted. Reconnect to the watch via the PC and adb commands
Deactivate OTA
--------------
adb reboot bootloader
adb devices //to make sure your watch is connected
adb shell
> su
> pm disable com.google.android.gms/.update.SystemUpdateService
> pm disable com.google.android.gsf/.update.SystemUpdateService
> exit
Before to reassociate the watch with the smartphone, eventually, remove the Android Wear application on the smartphone and reinstall the Android Wear V1.5.apk on the smartphone.
Reassociate the watch with the smartphone.
Thanks for this thread! I am having issue getting SU in cmd. I have installed 3 different TWRP and 3 different SuperSU.zip trying to get it to work. I can't seem to get any of them to execute su commands. When trying I get a FC on SuperSU on watch, and adb does nothing after
- adb shell
- su
- then nothing happens, and I eventually get SuperSU FC on watch.
Thanks in advance for the help.
Thanks both for the re-flash guide and the commands for disabling the update service. Had a problem not finding appropriate SU and TWRP images, but after finding them I'm finally free of the damn 2.0 and the update notification too.
SU: SuperSU-2.78-wear.zip
TWRP: twrp-3.0.0-0-lenok+squashfs.img
I did not check any other root-needing apps, and as far as I'm concerned, I'm done with updates for the lifetime of this watch...
nagi603 said:
Thanks both for the re-flash guide and the commands for disabling the update service. Had a problem not finding appropriate SU and TWRP images, but after finding them I'm finally free of the damn 2.0 and the update notification too.
SU: SuperSU-2.78-wear.zip
TWRP: twrp-3.0.0-0-lenok+squashfs.img
I did not check any other root-needing apps, and as far as I'm concerned, I'm done with updates for the lifetime of this watch...
Click to expand...
Click to collapse
That's the su and twrp I have installed on my watch at this time, I am not able to get su commands to execute. Is there something else that needs to be done after installing these? Thanks.
I want to get rid of the automatic upgrade to AW 2.0, so I want to apply the recipe you have kindly shared, but I don´t know how to do it because it is my first time with ADB commands.
I have already ADB installed and USB debugging enabled. I can type "adb devices" and my watch is listed.
The question is how to apply the (two?) commands you suggest.
- Should I type "laptop$ adb shell" ??
- At the $ prompt I have tryed to type "su" but get an error.
- Also: the two commands are "one single line" each, like "...systemUpdateService Component ....", or they are two lines each command?
- Should the watch be rooted to do this ?
Thank you very much.
PD: I have flashed my watch back to AW 1.5 with no problems, using the instructions given in this link:
https://forum.xda-developers.com/g-watch-r/general/andorid-wear-2-0-t3382032/page23
adlx.xda said:
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
Click to expand...
Click to collapse
[/COLOR]
paggps said:
I want to get rid of the automatic upgrade to AW 2.0, so I want to apply the recipe you have kindly shared, but I don´t know how to do it because it is my first time with ADB commands.
I have already ADB installed and USB debugging enabled. I can type "adb devices" and my watch is listed.
The question is how to apply the (two?) commands you suggest.
- Should I type "laptop$ adb shell" ??
- At the $ prompt I have tryed to type "su" but get an error.
- Also: the two commands are "one single line" each, like "...systemUpdateService Component ....", or they are two lines each command?
- Should the watch be rooted to do this ?
Thank you very much.
PD: I have flashed my watch back to AW 1.5 with no problems, using the instructions given in this link:
https://forum.xda-developers.com/g-watch-r/general/andorid-wear-2-0-t3382032/page23
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Click to expand...
Click to collapse
The commands are single lines, and it will require root. Make sure you use twrp listed above, and super su 2.78 for wear, also listed above.
It's clear that the downgrade to AW1.5 is quite easy. However, it's less obvious to block the OTA!
For that, it's mandatory to root the Watch and I didn't find a clear notice to do it. After many atempts, I did it without clearly understand how I made it!!!! But it's done, and the upgrade notification has disappeared.
I wrote my onwn notice (in case I want to try again in few months a new attempt to test for instance the next AW2.1...) here.
Somebody in this forum could write a full clean procedure for newbie with all the links to do the downgrade and OTA disabling in one shot with a 100% success.
nicodvt said:
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
Click to expand...
Click to collapse
Hi,
Using you guide to go back to 1.5 on g watch r but im stuck on step 6......
Only thing i can do in adb i type Y and nothing else?
Hi,
I try follow your steps, everything seems to be fine. But after last command 'fastboot reboot' I am still booting to fastboot. Please do you know what can be wrong here?
Thanks
Dear Sirs
It has been almost 2 years since I got my Nexus 6P, and I always disable the navigation bar for a better usage. Before Oreo I added 'qemu.hw.mainkeys = 1' on Build Pro file via root file explorer. But it no longer worked, If I did, the system will collapse and I have to reflash the system. So is there any new way to disable the navigation entirely on Oreo.
Many thanks.
Best Regards
ChaoChao
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
dratsablive said:
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
Click to expand...
Click to collapse
So sad. thanks for your help though.
dratsablive said:
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
Click to expand...
Click to collapse
Try issuing the command
adb shell settings list global
to see if that setting still exists.
stevemw said:
Try issuing the command
adb shell settings list global
to see if that setting still exists.
Click to expand...
Click to collapse
I was trying to execute the command
adb shell settings put global policy_control immersive.navigation=*
from a terminal on the phone, but executing this command on my laptop while connected to phone worked
Anyone can please help..!!!!
In android 8.0 (oreo),i am unable to hide soft keys using "qemu.hw.mainkeys=1".since after this my phone starts doing data factory reset,next time it boots.
I tried immersive mode but soft keys alwayas pops up while using keyboard.
Also tried themer.zip from some xda link,it does hide the soft keys but swipe at bottom where softkeys are seems laggy while performing swipe action in LMT launcher.
There's an app called custom navigation bar, you can try it out, after you did your setup you can even uninstall it.
i install custom navigation bar app,but it failed compatibilty test,what to do now???
I dont want to hide the nav bar. I want to completely disable it so it wont pop up at all anywhere. I'll be using swipe navigation.
lemonspeakers said:
I dont want to hide the nav bar. I want to completely disable it so it wont pop up at all anywhere. I'll be using swipe navigation.
Click to expand...
Click to collapse
I want to disable it as well. Pie Control is great.
Any solution yet to disable the navigation bar on Oreo 8.x?
phedoreanu said:
I want to disable it as well. Pie Control is great.
Any solution yet to disable the navigation bar on Oreo 8.x?
Click to expand...
Click to collapse
If you are rooted stock Feb update you can flash this. A restore zip should be created in a folder called ozop on your sdcard.
Hey folks!
I just bought 10.1 Android screen with GPS running Android version 7.1.2, processor type: Ultra Octa-T8
my question is:
How to split the screen (running two apps simultaneously )? Is there any app can do the split?
Thanks in advance,
Android7 supports split screen by default, so no special application is needed.
BUT Since T8's firmware has freeform mode enabled, you can not use split screen unless it is invalidated.
If you can use ADB, you can override freeform mode with the following syntax
adb shell delete global enable_freeform_support
But stock firmware will not be able to use ADB.
I would like to know if there is a good way...
warata said:
Android7 supports split screen by default, so no special application is needed.
BUT Since T8's firmware has freeform mode enabled, you can not use split screen unless it is invalidated.
If you can use ADB, you can override freeform mode with the following syntax
adb shell delete global enable_freeform_support
But stock firmware will not be able to use ADB.
I would like to know if there is a good way...
Click to expand...
Click to collapse
thanks for the reply,
How can I override freeform mode with the following syntax
adb shell delete global enable_freeform_support
Do you mean I have to root the screen?
would you please give more details I am new this world
MoMo131 said:
thanks for the reply,
How can I override freeform mode with the following syntax
adb shell delete global enable_freeform_support
Do you mean I have to root the screen?
would you please give more details I am new this world
Click to expand...
Click to collapse
Is this what you mean??:
https://www.youtube.com/watch?v=MRHyH9anr4c
MoMo131 said:
Is this what you mean??:
https://www.youtube.com/watch?v=MRHyH9anr4c
Click to expand...
Click to collapse
That's right buddy.In freeform mode you can use it immediately in stock ROM.
But its function is not quite useful in car stereos.
If you can disable free form mode it should be possible to use split mode.
But I am not a developer, nor is it familiar to Android.
I think that it is better for you to come to this thread for better advice.
https://forum.xda-developers.com/an...ecity-vw-allwinner-t8-2gb-32gb-7-1-2-t3704290
Now i use joneplus tools + oneplus mod dialer for call recording on Android 13.
I miss a spam call blocker...
Any solution to have the automatic call recording function AND spam call blocker with Android 13?
Thanks.
Try using the Google Dialer with the Pixelify Magisk Module.
ChIP_83 said:
Now i use joneplus tools + oneplus mod dialer for call recording on Android 13.
I miss a spam call blocker...
Any solution to have the automatic call recording function AND spam call blocker with Android 13?
Thanks.
Click to expand...
Click to collapse
Hey there, Can you please explain how did you managed to use call recording on Android 13? I have Oneplus 8 pro IN2025 and can't find solution to make Call Recording work after the upgrade to Android 13 from 12
yaniv.s said:
Hey there, Can you please explain how did you managed to use call recording on Android 13? I have Oneplus 8 pro IN2025 and can't find solution to make Call Recording work after the upgrade to Android 13 from 12
Click to expand...
Click to collapse
I solved it like this:
I installed joneplus tools (from the playstore I know that it doesn't work anymore so it must be installed from the apk - in reality I had already installed it)
set the permissions via ADB as required by the various guides (remember to enable Disable Permission Monitoring in developper options)
loaded the modified oneplus dialer
doing so everything works as before, with the difference that I no longer have the screen where I can change the recording options in the dialer, but the recordings still start automatically (I think it is due to the fact that the "modified dialer" goes to "modify " call screen only.
ChIP_83 said:
I solved it like this:
I installed joneplus tools (from the playstore I know that it doesn't work anymore so it must be installed from the apk - in reality I had already installed it)
set the permissions via ADB as required by the various guides
loaded the modified oneplus dialer
doing so everything works as before, with the difference that I no longer have the screen where I can change the recording options in the dialer, but the recordings still start automatically (I think it is due to the fact that the "modified dialer" goes to "modify " call screen only.
Click to expand...
Click to collapse
Thank you sooo much !!! The modified app was the part missing
ChIP_83 said:
I solved it like this:
I installed joneplus tools (from the playstore I know that it doesn't work anymore so it must be installed from the apk - in reality I had already installed it)
set the permissions via ADB as required by the various guides (remember to enable Disable Permission Monitoring in developper options)
loaded the modified oneplus dialer
doing so everything works as before, with the difference that I no longer have the screen where I can change the recording options in the dialer, but the recordings still start automatically (I think it is due to the fact that the "modified dialer" goes to "modify " call screen only.
Click to expand...
Click to collapse
hi ChiP_83,
about the ADB command in step #2, is it
"/adb shell settings put global op_voice_recording_supported_by_mcc 1"?
thanks in advance
This was working on android 11
ADB command with joneplus tools installed
adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
ADB command without installing joneplus tools
adb shell settings put global op_voice_recording_supported_by_mcc 1
Hi all. I just tied to set call recording, install joneplus tools, and granted write through adb, install modified dialer, but no luck, call recording not visible. If i try update my regular phone app, looks like it finished with success, but can't find same version number..
Well new android version IN2025_11_F62 and no call recorder again.. any solutions?
ANDROID:202211081700 (4G) 12 (fake 10)
MCU:MLO-mtk_C56_whe02d-aAaAaA_473X-CC568091-8A 20221221
Model: A007_C56_HA11_U859-EN-D_2022-11-08-1652
Octo 2.2Ghz 128GB+8GB 4G LTE on board.
Recently bought this headunit from Alli. It is a very quick unit although it comes with a lot of behind the scenes bloat and I have so far been unable to root and ADB does not work.
My main problem is an app called TXZ VOICE. It is interfering with android assistant. It is installed as a system app and I am unable to remove or disable it. As is the case with many of the other bloat apps.
I guess I'll have to wait for the community to pick it up. But what little information I have learned is the factory code 99992. A testing mode that appears to have an ADB shell, however it will not remove or disable apps.
Any insight would be greatly appreciated
If an ADB shell is provided, then check device's system file build.prop for the follwing entries
ro.build.type=userdebug
ro.debuggable=1
ro.secure=0
Click to expand...
Click to collapse
to check whether you can debloat Android or not.
jwoegerbauer said:
If an ADB shell is provided, then check device's system file build.prop for the follwing entries
to check whether you can debloat Android or not.
Click to expand...
Click to collapse
Thank you for the reply.
ro.build.type=userdebug
ro.debuggable=1
ro.secure=1
So I guess there's the answer.
The bootloader does seem to be unlocked however. I think there is a custom bootloader installed but I can't access it.
A device's bootloader ( Linux kernel ) and device's Android OS are totally different things.
If I understood it well then you want to debloat Android OS: this gets done via ADB ( read: Android Debug Bridge ).
Yeah. I was just adding any information I know about this headunit. My hope is perhaps it may be possible to flash new firmware in the future.