In case you missed it, the official help forum for Android Wear has gone live. There are many places to go online to get help with using your new smartwatch, but this Google Group is the place the company would probably prefer you go. It's also a location where you have a reasonable chance of getting an answer. We try to answer many of the questions that you pitch to us in the comments, but we don't see everything.
Late yesterday, Google began rolling out an update to the Android Wear companion app. Despite a sudden growth of over 2 MB in size, the app only seemed to change the text of a warning, and there were no visible changes on our watches. We knew there had to be something great hidden under the covers, and we were right. The companion app certainly has some interesting changes of its own, but it also acts as the delivery mechanism for a Wear-customized version of Google Play services, and there's a bit to talk about in there, too.
Excitement over products like the Ouya, nVidia's Shield line, and even numerous gamepads proves that gaming on Android has entered the mainstream. Developers have been jumping at the opportunity to build games that work across many of the different operating systems; and thanks to the Cross-Platform SDK, they're able to integrate most of the Play Games services into their products on Windows, Mac, and Linux. Until now, this SDK has lagged behind the SDKs for Android and iOS on one specific feature: real-time multiplayer support.
Google has been wrestling with a series of strange and not too uncommon bugs with a part of the camera subsystem on the Nexus 5 called mm-qcamera-daemon. Without this component, the camera on this device won't function, but sometimes it goes wonky and drains the battery. A Googler has just marked this issue as "future release" in the AOSP issue tracker, meaning it should be fixed when Android L rolls out.
One of Samsung's claims to fame is a feature meant to improve productivity on mobile devices. One that users of stock Android and manufacturer skins alike have been yearning for for a while. That feature is multi-window, which allows users to run two apps on the screen at once, dragging and dropping between the two.
The problem is no one has been able to get it right yet. A company in the mobile space - in this writer's opinion - has yet to perfect the balance between utility and intuition when it comes to multi-window functionality on tablets (or phones, though I haven't used the Note 4 yet), but a post to Android Internals in March confirmed that Google had been working on the programmatic side of multi-window in stock Android.
With a big OTA expected to hit Android Wear devices starting around October 15th, Google has just published what might be a preparatory update for the Android Wear companion app. Taking the app up to version 1.0.2, the update adds about 3MB to the APK's file size. Google hasn't published a change log quite yet, but we can already tell from a cursory teardown that the new version brings with it an update to Google Play Services for Wearables (a package sent to the watch from the app) - version 6.1.11 (up from 5.0.91).
If you keep tabs on Android Wear, you've probably heard of Facer. It's the leading app for making and sharing custom watch faces for Android Wear. The lack of an official API has not deterred developers, and Facer isn't the only app offering new watch faces. Face for Wear has been in beta for a while now, but it's finally ready for everyone to check out.
Normally the kind of customer who buys a "rugged" phone like the Hydro VIBE isn't all that concerned with having the latest and greatest in software - or at least that seems to be the attitude of the carriers and manufacturers, who don't seem very concerned themselves. Perhaps that's why Sprint and Kyocera launched the phone with Android 4.3 back in May, despite the fact that 4.4 had already been available for seven months.
Android L is probably just a few weeks away, but Google's partners already have the code to begin designing updates. That's why SamMobile was able to get a hold of a nearly complete build of Android L on the Galaxy S5. It looks pretty much like you'd expect a Samsung ROM to look, but there's definitely some L influence.