Yeah, the aw2.0 obviously has some flaw in regards of bluetooth connection. At least here on gwr. Just like you said, there are 2 connections now that wear "works" with and I think it is the base of all problems
Andorid wear 2.0
- Thread starter giorgior.r
- Start date
Altho I'd like to feedback that if you so happen to have lost BT connection to your GWR and can't seem to reconnect, you have a better chance of reconnecting the BT when it's connected to a wifi hotspot too.
Don't ask me why, but I've noticed it twice and purposely did it a third time to see if it's a fluke or not
Failed install: LeeDroid 3.1 --> Wear 2.0
Hi everyone
this is my first comment so sorry in advance for the noob stuff.
My g watch r is running leedroid 3.1 and since wear 2.0 came out I wanted install it manually (Leedroid wont update to wear2.0 by itself). So I did what any other kid would do and got the cookbook. I have experience with nexus, one plus, etc... But any way I tried when plugging the watch to my PC I always get the device listed under USB devices named as "unknown usb device (device descriptor request failed)"
I did go into research and did a lot of tries, but no success. I'm running Win 10 64bit, android studio with drivers installed. I even installed the LG driver. When I try my one plus two, from the command prompt adb devices lists it, but the watch is never in the list. Even tried other USB cables but nothing changed. I assume ADB is not the blame, but for some reason the dirver is not willing to work.
Any assistance is appreciated. Thanks in advance!
Hi everyone
this is my first comment so sorry in advance for the noob stuff.
My g watch r is running leedroid 3.1 and since wear 2.0 came out I wanted install it manually (Leedroid wont update to wear2.0 by itself). So I did what any other kid would do and got the cookbook. I have experience with nexus, one plus, etc... But any way I tried when plugging the watch to my PC I always get the device listed under USB devices named as "unknown usb device (device descriptor request failed)"
I did go into research and did a lot of tries, but no success. I'm running Win 10 64bit, android studio with drivers installed. I even installed the LG driver. When I try my one plus two, from the command prompt adb devices lists it, but the watch is never in the list. Even tried other USB cables but nothing changed. I assume ADB is not the blame, but for some reason the dirver is not willing to work.
Any assistance is appreciated. Thanks in advance!
How did you get the leedroid (whatever that is) onto watch?
Make sure you have all Google usb drivers. Also, try different adb / usb drivers for watch. In the device manager, choose to update driver, choose manual, look up from list. Try to find other adb drivers, may be present. Or find and install motorola adb drivers. That helped me to connect huawei watch.
In addition: Win 10 is sometimes a bit reluctant to install drivers. If you google disable driver signature enforcement you can easily find how to properly install such drivers.
Thank you for the feedback 
Leedroid is a LG Urbane watch port for the G watch r. Install can be found here:
https://forum.xda-developers.com/g-...edroid-r-urbane-port-v1-0-0-june-6th-t3128850
The thing is that the bootloader and the "adb devices" command worked back then. Same windows system.
I did everything in test mode as well, but no success. DRiver install from several manufacturers. I'll try the motorola driver later but I'm not sure if it leads in the correct direction.
If anything else comes into mind, please let me know!
Leedroid is a LG Urbane watch port for the G watch r. Install can be found here:
https://forum.xda-developers.com/g-...edroid-r-urbane-port-v1-0-0-june-6th-t3128850
The thing is that the bootloader and the "adb devices" command worked back then. Same windows system.
I did everything in test mode as well, but no success. DRiver install from several manufacturers. I'll try the motorola driver later but I'm not sure if it leads in the correct direction.
If anything else comes into mind, please let me know!
Today I tried with the naked and universal usb drivers but in terst and not test mode of win 10, but no success. I'm really thinking of throwing the watch into the garbage
Today I revived OTA update to my AW 2.0 (first update after the release of 2.0) - it's:
Android Wear 2.0.0.156099718
Android OS 7.1.1
Security patch level 1 may 2017
Build NXH19X
Works smooth but I don't know how to check working CPU core count.
Android Wear 2.0.0.156099718
Android OS 7.1.1
Security patch level 1 may 2017
Build NXH19X
Works smooth but I don't know how to check working CPU core count.
Last edited:
My g watch R is.....since 2.0
It freezes often and its very slow.
It freezes often and its very slow.
You should try to flash modified boot image with intercative governor and 2 cores...
My watch was slow as hell and barelly usable but since I flashed this "patch" it's a new watch and work very very good with equal or less battery consumption
PS : my watch prompted me with the update this afternoon but I have to check if I need to go back to original boot.img prior OTA
OK did the update and flash some incompatible boot.img...
Can someone get me OTA url so I can sideload it because I cant sideload previous one got error at 47%
Last edited:
Can someone please elaborate on this or point me to a guide? Ever since I upgraded to 2.0 watch is simply unusable. Lags, stalls, nothing works. "okay google" triggers a black screen, and after 15 seconds or so appears the google assistant. I really miss my watch. How can i check if two cores are enabled or whatever? Thanks!
You can go on dedicated thread in Android development
Envoyé de mon Nexus 6P en utilisant Tapatalk
Envoyé de mon Nexus 6P en utilisant Tapatalk
Thank you,
I did a fasboot oem unlock
fastboot flash boot boot.img
fastboot boot boot.img
I am now in a bootloop. Is there anyway i can boot back to fastboot and flash the original boot? Or does it take a super long time to boot? (i reset all data when oem unlocked)
Did you apply latest android update yesterday or today?
You can always flash original boot back to get it booting
Envoyé de mon Nexus 6P en utilisant Tapatalk
You can always flash original boot back to get it booting
Envoyé de mon Nexus 6P en utilisant Tapatalk
yes, i did the update today, then the rest of the steps i described. Can you help me boot back in fastboot? or should i see adb while its still booting? Thanks!
LE: i managed to boot back to fastboot by swping from 10 to 30 on the watch why LG logo was showing. reverting back to stock boot img. Is there some extra prep i need to do before flashing the custom boot img since i updated today? thanks!
Last edited:
I think (it had to be confirmed) that there is incompatibility between latest update and boot.img
Envoyé de mon Nexus 6P en utilisant Tapatalk
---------- Post added at 22:09 ---------- Previous post was at 22:08 ----------
I am waiting for a confirmation from devs and also ota url to get a compatible unmodified boot.img
Envoyé de mon Nexus 6P en utilisant Tapatalk
Envoyé de mon Nexus 6P en utilisant Tapatalk
---------- Post added at 22:09 ---------- Previous post was at 22:08 ----------
I am waiting for a confirmation from devs and also ota url to get a compatible unmodified boot.img
Envoyé de mon Nexus 6P en utilisant Tapatalk
do you have a link for the original firmware prior to the latest patch? I installed the original bootloader from the thread but it still won't boot so I would like to flash the prior patch and then the boot img. Thanks!
It's on redit search watch r ota url
Envoyé de mon Nexus 6P en utilisant Tapatalk
Envoyé de mon Nexus 6P en utilisant Tapatalk
found it, I'm sidloading as we speak. I will check which build version it is i might be able to flash the modified boot img afterwards. thx!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone