Pretty awesome that the sync API auto syncs once the wear app gets installed. So no need to wait for the wear app to install before trying to sync.
styofa doing anything
noise dept.
ojovivo
i don't do bad sauce passes
TVSTRANGERTHINGS
Misplaced Lens Cap
trying on a metaphor

Product Placement
KIROKAZE

tannertan36

@theartofmadeline

#extradirty

pixel skylines
dirt enthusiast
hello vonnie
he wasn't even looking at me and he found me
AnasAbdin

No title available
Sweet Seals For You, Always
cherry valley forever
seen from Portugal

seen from Singapore
seen from United States

seen from Egypt
seen from United States
seen from Jamaica

seen from United Kingdom
seen from Türkiye

seen from Germany
seen from Malaysia

seen from Bangladesh
seen from Germany

seen from Austria
seen from Portugal

seen from Malaysia
seen from Germany

seen from Netherlands
seen from India

seen from United States

seen from Malaysia
@hellomikedg
Pretty awesome that the sync API auto syncs once the wear app gets installed. So no need to wait for the wear app to install before trying to sync.
Watch faces are possible with no API
Deploying a Wear app to the play store?
When packahging your Wear app inside another APK, make sure to
Turn off Asset Compression
Many build tools automatically compress any files added to the assets/ directory of an Android app. Because the wearable APK is already zipped, these tools re-compress the wearable APK and the wearable app installer can no longer read the wearable app.
When this happens, the installation fails. On the handheld app, the PackageUpdateService logs the following error: "this file cannot be opened as a file descriptor; it is probably compressed."
To prevent this error in Android Studio, update your handheld app's build.gradle file with the following declaration:
android { aaptOptions { noCompress "apk" } }
http://developer.android.com/training/wearables/apps/packaging.html
Looks like the ambient watch faces are Dreams.
07-01 16:10:24.321 459-492/? I/PowerManagerService﹕ Going to sleep by user request...
07-01 16:10:24.331 459-489/? I/PowerManagerService﹕ Dozing...
07-01 16:10:24.331 459-479/? I/DreamController﹕ Starting dream: name=ComponentInfo{com.google.android.wearable.app/com.google.android.clockwork.home.AmbientMode}, isTest=false, canDoze=true, userId=0
Ripples
Universal icon set for all platforms coming this summer
Let your app icon guide your primary and accent colors
So much too short
I’ve been seeing about 12 hour battery life. Battery life is too short.
I can’t leave my phone in the living room and go up stairs without losing connectivity. BT range is too short.
You are now a developer!
How do we enable developer mode on Android Wear devices? It's pretty much identical to how we do it on phones.
Say "Ok Google, Settings" to get to the settings screen.
Scroll to the About option and select it.
Scroll to Build number, then tap on it about a dozen times and it will show a Toast saying that "You are now a developer"
Back out of this screen and you should see "Developer options" below "About"
Bluetooth debugging is awful
It seems really slow to deploy, which is making it near useless.
Setting up a G-Watch on windows
As usual new devices are a pain in the ass to use via ADB on Windows. OSx and Linux have it easy.
Turn off driver signature enforcement.
Go into the USB driver extras directory on your Android SDK. Something like C:\Users\Michael\AppData\Local\Android\android-studio\sdk\extras\google\usb_driver
Copy that entire folder somewhere safe.
Open android_winusb.inf in a text editor
Toss the next two lines under [Google.NTx86] and [Google.NTamd64] ;Wear GWatch %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01
The above lines basically say to use this driver for your GWatch.
Now go into device manager, you should see a GWatch with a yellow sign next to it complaining about the drivers.
Double click that and select update driver.
Point if to the directory you just copied and modified.
It should complain about the driver signature being incorrect, that's fine though.
Once that's installed, your device should be usable via ADB