Assuming you don't live under a rock, you probably know the Nexus 5 launched on the Play Store last Thursday. In the US, Google's newest handset will cost you $350 for the 16GB model, and $400 for the more capacious 32GB variant. The launch went relatively smoothly, though stock of the 16GB Nexus 5 quickly evaporated - for the black version, within minutes - and latent purchasers of the 32GB version are now in for a weeks-long wait before enjoying the sweet embrace of KitKat.
|David Ruddock||David's phone is an HTC One. He is an avid writer, and enjoys playing devil's advocate in editorials, imparting a legal perspective on tech news, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.|
Looking for the new Android 4.4 wallpapers? We've got 'em, ready for your downloading pleasure. There are 8 wallpapers in total, 6 of which have a native resolution of 3966x3966, so you can put them on pretty much anything! The two nature wallpapers are at a slightly smaller 3966x2644, since they're actual photos. Here they are.
Update: The colorful wallpaper everyone was after - the one with the number 5 - was hiding in a different place, but we found it after all.
Advertising revenue is a huge part of doing business in the mobile apps space for a large number of developers. As such, from that practice have emerged methods to send advertisers information about you to better serve appropriate ads. Oftentimes, the way your advertising "profile" is specifically identified is less than ideal from a security standpoint. Many apps use your phone's IMEI - a potentially personally-identifying number - as your advertising identification number because every modern smartphone has one.
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.