A while back, an experimental feature debuted in a Chrome for Android Beta release that seemed pretty innocuous - instead of tapping the overflow menu button to cause the dropdown to appear, you could now press, drag, and release to select an option in the list. From a touch device perspective, it's understandable why such an implementation would be desirable for some users, as it reduces the amount of tapping required for some tasks.
|David Ruddock||David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.|
If you've never heard of the Bluetooth MAP profile, I don't blame you. Bluetooth profiles are super, super boring stuff. But stay with me here, because you may be more interested in MAP than you thought.
Do you own a car that is "Bluetooth-enabled"? If your car's model year is somewhere in the neighborhood of the last 3 to 4 years and supports Bluetooth, it probably uses the MAP standard to communicate with your phone.
This feature is perhaps bigger news for app developers than end users, but it's an important one nonetheless. Ever used an app that feels really slow, clunky, and unresponsive - almost like a mobile web page? It probably is one! You see, many publishers of apps out there don't actually build real mobile apps. Credit card companies, cell phone carriers, airlines - you know, the sort of companies you kind of live to hate.
While many Nexus fans laud Google's software navigation button initiative, it's always been a bit irksome that they take up valuable screen real estate at times when they're not really needed. If you're reading a book, watching a movie, or playing a game, the software nav buttons are more a distraction than anything. In fact, until now, only the YouTube app (and perhaps a couple other system apps in certain circumstances) was able to hide those buttons.
A much-requested Android feature for some time now has been infrared support, with the likes of Samsung, LG, and HTC all outpacing Google to enable the technology on their devices. As such, a fragmented API ecosystem has emerged, and now Google's here to set things straight - or so it would seem at first glance.
Android's new IR blaster support only supports one real action: transmitting an IR signal. It does this with a new API and system service that any app can take advantage of on IR-equipped devices running Android 4.4 or higher.
Android 4.4 supports a couple of new Bluetooth features, but one of them will undoubtedly appeal to the cries of OCD sufferers more than the rest: as part of an extension to Bluetooth AVRCP 1.3, Bluetooth audio devices can now directly control Android's system volume. If you use a lot of Bluetooth speakers or headphones, you know how maddening this kind of problem can be. Because your audio output device has its own volume setting independent of your phone or tablet, you're never quite sure how loud things are going to be, or if you'll need to adjust one or the other to get the sound where you want it.
We all love listening to music on our phones. In fact, listening to music, audiobooks, or podcasts regularly on our smartphones is probably one of the few things we all really share in terms of our usage patterns. The problem with listening to audio for extended periods, though, is that it can really put the hammer down on your battery life. Now, there's more than one reason for this - streaming high-quality audio over the web probably consumes more battery than the actual act of listening, but the power consumption of the processor while decoding that audio isn't negligible.
Google Wallet's single-biggest problem to date in the US has inarguably been carriers. US carriers (except Sprint) wouldn't allow Google the necessary control of the "secure element" in order to make NFC payments, and as such, Google Wallet consumer adoption has essentially been trivial. With Android 4.4, that finally changes.
The new version of Android completely eschews the secure element paradigm and has instead opted for a virtual solution, using what Google calls "Host Card Emulation" technology to get the job done.
With a new version of Android comes a new promotional glamor site for Google's beloved mobile OS, and this time KitKat's getting the treatment. Android 4.4 packs a bevy of new features and capabilities, but if you want the basic rundown, Google's official splash for KitKat (here) is the prettiest way to educate yourself. (Bonus: here's an equally pretty site for the Nexus 5.)
If you're looking for a deeper rundown of Android 4.4's new features, don't worry, the Android Developers site has you covered with detailed, technical information about the new OS version.
Update: Here's an official Google Support answer stating the GNex will indeed be stuck in 4.3-land for eternity.
At the bottom of Google's official Android 4.4 announcement post on the company's blog, some rather pertinent information for current Nexus / GPE device owners is thrown in: OTA update news!
KitKat will be coming to the Nexus 4, Nexus 7 (presumably both models, but not explicitly stated), Nexus 10, and the Google Play Edition Galaxy S4 and HTC One.