Google this morning unveiled Android Wear, the project that will bring Android – and more importantly, Google Now – to smartwatches. Really, it's the project that will make smartwatches relevant. As part of the announcement, El Goog announced that it has already partnered with the likes of Motorola, LG, HTC, and Fossil for upcoming watches. Now, LG has made available information about its watch, which is dubbed the G Watch (as if it would be called anything else).
Google has just announced its plans for Android wearables, and this could make all those other smart watches look like they're standing still. Android Wear is an open Android-powered platform that lets developers plug into existing apps and take advantage of Google services like Now and voice search. There is a preview SDK available right now, and Google says wearables based on this platform are coming in 2014.
Google has updated its support pages and started sending out emails to alert users of Google Wallet to an upcoming change in the way NFC payments work. As of April 14th, tap and pay will require KitKat or higher. Older devices will no longer be supported after that date.
The reason for the change is Google's desire to only use Host Card Emulation (HCE) to make NFC payments work. That feature was introduced in Android 4.4, so it's the end of the line for Jelly Bean and earlier devices.
Update: It's come to our attention that, according to the LinkedIn profiles of two of GreenThrottle's founders, the company was almost definitely bought by Google last November, when GreenThrottle announced its impending shutdown. Both Matt Crowley and Karl Townsend list Google as their sole employer since November of 2013:
This almost definitely means the company was purchased last November, not more recently. Granted, there was still very little news coming out of Green Throttle at that time, so who knows what kind of situation they were facing when Google swooped in, though I can only guess it probably ended up being a good deal for Google more than it did GT.
Owners of the Galaxy S4 on T-Mobile can now get their itchy trigger fingers ready to hit that "check now" button. We've received a few tips today alerting us to the fact that the carrier is rolling out an Android 4.4.2/KitKat OTA to handsets now. According to the software update screen, the feature set doesn't appear to include much of anything that Google didn't add into the stock version of KitKat:
- OS upgrade - [KitKat OS 4.4.2]
- Music Album art will be displayed on the lock screen while playing music.
It's no mystery that Google has been poking around wearable gadgets for quite some time. The list of projects seems to keep growing as we hear about rumors of an LG-made smartwatch, another prototype watch designed by Motorola, and of course, Google's own Glass. Earlier today at SXSW, Sundar Pichai took to the stage to announce plans to release a brand new SDK for Android-based wearable devices in about two weeks.
We're getting closer and closer to a stable KitKat release of the popular aftermarket Android ROM, CyanogenMod. The "M" snapshot releases are more stable than a nightly, but not quite as final as a release candidate. The fourth M build for CyanogenMod 11 (Android 4.4) includes a wide range of updates that hadn't yet made it to the KitKat builds, according to the official CyanogenMod blog.
Most of these revolve around the custom applications that the CyanogenMod team adds to Android, though a few are more essential.
One of the fundamental differences between Android and every other mobile operating system is the practically unrestricted capability to run services. Without this freedom we could not enjoy something as powerful as a homescreen widget or as straight-forward as a Twitter client with background updates. Aside from games and very simple utilities, it’s becoming increasingly rare to find an app that doesn’t run a service, at least for a short span of time.
Intel's progress into the Android ecosystem hasn't exactly been earth-shattering. The number of high-end and mid-range smartphones equipped with an ATOM CPU still number in the single digits, making the x86 architecture a fairly low priority for app developers. In addition, Intel's emulator images have always lacked support for the Google APIs, leaving developers without the ability to test common staples like Google Maps or push messaging. Fortunately, that issue was recently rectified with KitKat as Google and Intel have finally shipped an x86 system image with Google API support.