[Asus ZenWatch 3] Misterjunky:
re: Android Wear 2.0 and 1.5

[MENTION=883085]tomcatoggo[/MENTION]

I wish you would check your build.prop and let me and everyone here know exactly

what you added or changed in it so we can all try it out.

As far as the ADB not working, in your case it has nothing to do with the watch.

If you cannot see any ADB dialogue when you type "adb devices" and or you

cannot see the very long ADB dialogue when you simply type "ADB" in your

window's computer after opening the DOS command/cmd window it means

that there is no communications between the ADB app and your computer.

Try this,,, create a new folder on your computer's C: called ADB and install the

ADB software into that folder then copy all the IMG (image files), Android Wear 2.0

and android wear 1.5 files including all the kernels, twrp and root files into the same

ADB folder then open a command/cmd prompt on your computer and change the

path to the ADB folder by typing CD/ADB and press enter in the black command

prompt window. After that you can use the adb commands without any issues.

Also, after a few days when I updated to the new android wear 2.0 I tried changing something in the build.prop too,

forgot exactly what it was though. But I do recall seeing a post someplace saying that if we change anything in the

build.prop file it will automatically revert to the stock build.prop after we reboot the watch.

I also read that unless we have root access the build.prop cannot be altered because of it reverting back to stock..

Whatever it was what I tried adding or changing in the build.prop did not work for me.

The easiest way to find out if your build.prop edit is working for you is to install "AIDA64" on your watch from the

playstore and check your free memory (internal free space ). After you install and open it on your watch click the

top option "SYSTEM" and scroll down til you see "internal free space", it should be at least 1.2GB, if not it means

that whether or not your build.prop edit stops all the notifications the watch is still is downloading the AW 2.0 install

file or files so when you click on "update" the AW 2.0 is ready to install.

The location of the installation file or files are in root /cache folder which we cannot delete due to no root access.

The AW 2.0 installation file is close to 350MB.

(I am using the official stock Android Wear 2.0 in my watch due to the notifications & auto downloading of AW 2.0 files.)

Also here is something that is very interesting that most likely no one will believe...

Three or Four days ago I saw an update called "Google Play Services" at the play store so I went ahead and installed

it on my phone and noticed that my watch also had the update waiting to be installed.

I did not think too much about it because I have gotten many updates similar to that many times already.

But after that happened I decided to reboot the watch just like I usually do when I get any updates and surprisingly

I noticed that the watch was working super fast compared to how it was before this playstore update.

The slowest app to load in android wear 2.0 is always the "playstore", it used to take forever for it to load, it was so slow

that many times the screen timed out before the playstore fully opened, but since the "google play services" got updated

the playstore opens in approx. 3-4 seconds and all the other apps in the watch open and load even faster and I tested all

the apps in the watch and it was truly amazing, they were all fast, I think even faster than android wear 1.5. Also I do not

notice lag or sluggishness now.

You might want to look into this yourself and let me know your results.

Good luck, have a great day!