Big things are happening for the smallest of Android devices. Over the last month, we've seen several attempts to extend the capabilities of Android Wear, some have worked out, while others haven't fared so well. Most of the activity has come in the form of 3rd-party apps, so there hasn't been much action for dedicated modders. That is, until today. Team Win just posted its first official custom recovery for the LG G Watch (dory).
The Google Glass developers are at it again; they keep coming up with new ways to burn through that tiny battery. Today, the Glass Development Kit changelog was updated to detail the addition of USB webcam support for developers looking to add access to views outside of the standard forward-facing perspective. Webcams must be attached via On-The-Go (OTG) cable, and Plug 'n Play isn't supported, so Glass must be rebooted before the attached camera can be recognized.
If you've been dying to start poking around the Android Wear source code, now is the time! Google just posted 4.4W to AOSP. The active development branches are distributed throughout each project repository as kitkat-wear. This is the location where further patches and minor updates will appear. There is are also tags for android-4.4w_r1 (build KTU84Q), which represent the first official release of the platform.
There aren't any repositories for either Dory (LG G Watch) or Sprat (Samsung Gear Live), but we can't be certain if they will appear in AOSP or if the distribution of device specific source code will be left up to the manufacturers.
Google I/O was pretty amazing this year, right? We got the deets on Material design, a preview version of Android L, the formal release of Android Wear, the first manifestations of Android TV and Android Auto, and plenty of other bits and pieces. However, all of that content and all of those developer sessions can take forever to absorb, and professional developers just don't have time for that. Now that all of the videos have been posted, I've combed through every last one to narrow the list down to just the sessions that absolutely can't be missed.
Google's recently launched Android Wear platform had a bit of a rough weekend when it ran into an unexpected snag regarding paid apps – it couldn't install them. It turns out that the behavior could be traced to a Play Store security feature that was responsible for encrypting paid apps to make them more difficult to pirate; but in doing so, it had also made it impossible to extract and install any micro-apps contained within the apk.
Android is really turning into a jack of all trades, having become the OS of choice for phones, tablets, face computers, and now wristwatches. The combination of flexibility, open source code, and low cost of entry make it a prime candidate for countless utilitarian purposes. With the upcoming release of Android L, Google is aiming to make it even easier to deploy highly specialized environments with a new feature called Task Locking that allows a single app to take control of the interface and prevent users from switching apps or even seeing notifications.
You saw Android Wear a couple of months ago when Google unveiled the SDK and both LG and Motorola presented the first promotional pictures. Then you watched the Google I/O keynote that officially launched the LG G Watch and Samsung's surprise addition of the Gear Live. And now you've got a shiny, brand new Android Wear watch before you... but all you can think about is ripping into the digital guts of that thing and doing all of the awful things that Google never intended.
Back in KitKat, we were introduced to translucent system bars, which gave app developers the ability to make the navigation and status bars semi-transparent. Reclaiming as much of the screen as possible became an obsession for many fans as they demanded their favorite apps go "full bleed." With Android L, Google is treating us to even more flexibility by allowing developers to set their own color for the status bar, or even turning it completely transparent.
A couple of days ago, AOSP was graced with a series of freshly created "l-preview" branches and a massive push of brand new code. As we know now, quite a bit of that code push wasn't truly representative of the L developer preview. (Very sneaky, Google.) Most of the truly new updates belonged to GPL-licensed projects, which Google is obligated to release in a timely fashion. The remaining projects with "l-preview" branches were filled with a recent snapshot from the Master branch.