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.
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.
It looks like all of the recent Nexus devices are covered - everything from the 2012 Nexus 7 up through to the Nexus 5. Of course, just because branches have been published for these devices, it is not absolute confirmation that this entire list of devices will receive an official L release.
Last year, at Google I/O 2013, some major new features and improvements were announced for Google Cloud Messaging (GCM) -the replacement for Cloud to Device Messaging (C2DM). A couple of the new bits were even featured during the keynote, particularly notification syncing, which the audience loved. The one thing most people don't know is that most of the coolest things announced that year were marked as beta and locked behind an application process.
The Android team has been hard at work replacing old code that hasn't scaled well with newer and more powerful hardware. We've long known that the camera API was destined to see a massive update, but we were missing details like a release date or exactly what was coming. Thanks to the L release, we can finally see what has been in the works for all these many months.
One of the most important aspects of the new Camera 2 API is a dramatic increase in performance over the previous interface.
Android 4.4 contained a number of interesting and very powerful features for developers, many of which went unused or misunderstood for quite a long time. Since it was introduced in KitKat, The Storage Access Framework (SAF) may be one of the best examples of an API that has been underutilized, despite offering a great method to provide cleaner and more informative interfaces. I even theorized that it may ultimately take the place of file system access.