An unexpected treat came zooming out of Google HQ today as Android 4.4.4 OTAs and factory images have started rolling out for Nexus devices. The changes have already been posted to AOSP and Al Sutton quickly followed up with a list of the changes that make up the latest update. Since 4.4.3 is only 2 weeks old, and I/O is merely a week away, we had a feeling this was just a security update, and it looks like that's all it is.
Samsung Galaxy Mega owners have probably felt a little bit ignored while they've watched one Samsung phone after another getting updates. After all, they only made it to Android 4.2.2 at the end of November, a month after KitKat was announced. They can finally say that they're running the latest version of Android (if we pretend that 4.4.3 didn't just come out). Starting today, an update to Android 4.4.2 will begin rolling out to the Galaxy Mega on AT&T.
Ask anybody that spends time in the security circles and they'll tell you that every large software project is bound to have a few long-standing vulnerabilities in the code. Fortunately, there are usually a few people who are paid to close up those holes so you, the customer, don't find yourself the victim of nefarious evildoers someday. Like so many before it, the latest update to Android came with a boatload of changes, at least one of which fixes a potentially dangerous vulnerability that can be used for numerous attacks, including a way to acquire root.
Unless you blacked out all of the news from yesterday to avoid a deluge of stories about what has been happening in Cupertino, you probably caught wind that there's a brand new update to Android. Whether you're manually installing the latest OTA or going all out with the factory images, you might be interested to know what is actually different. Thanks to Al Sutton, we've got a brand new changelog compiled from the list of code commits submitted to the Android Open Source Project (AOSP).
It's no secret that Bluetooth has been a problem child for Android, plagued with poor audio quality and connectivity issues. I've already covered a handful of common problems in a previous post, but another issue has been emerging in the last few months that threatens to virtually kill all Bluetooth operation on a device in the right conditions. The culprit is a nasty little oversight in the Bluetooth Low-Energy code added with Android 4.3 Jelly Bean.
Just minutes ago we posted about the discovery of an Android 4.4.3 changelog in AOSP and we've already found some interesting information. Among the individual project repositories, there are a few dedicated to Google-supported devices, mostly those in the Nexus family. In particular, we came across new references to an HTC device codenamed "Flounder," and another device belonging to Google with the name "Molly." This is the first time that these names have appeared in AOSP.
With most versions of Android, we're not used to seeing a changelog until a few hours after the AOSP code has been fully uploaded and somebody has had time to generate a comprehensive list. Imagine our surprise when such a list for KitKat 4.4.3 was discovered simply lying around on Google's servers. The file, named KK-MR2_changelist.txt, is located amidst Android's platform documentation. This is something of a first, since we'll actually learn about what's to come before the code is even available.
"Because the history of computing has taught us is that data will not be contained. Data breaks free. It expands to new media, crashes through barriers; painfully, maybe even dangerously. But, uh, there it is… Data finds a way." - Jeff Goldblum as Jeff Goldblum (Jurassic Gift Shop)
When we last left our favorite removable storage device, OEMs had begun adopting Google’s policy for restricting write access to SD cards.
When writing an Android app, one useful feature that developers use when dealing with a potentially long list of options is fast scrolling. First introduced in Android 1.5/Cupcake, this functionality allows a user to grab the scrollbar and drag it down to scroll section-by-section, rather than item-by-item. It appears, however, that the KitKat implementation of this classic Android feature has introduced a bug which is driving some developers crazy.
This bug is certainly one that affects developers more than end users.
Virtual Private Networks (VPNs) aren’t the sexiest topic out there, but they are a pretty vital part of daily operations for almost every major company and many small businesses. VPNs are used to securely connect a computer, tablet, or phone to a company's private network over the Internet, thus allowing people to work remotely while ensuring strict authentication and enforcing administrative policies. Even some power users are apt to set up a VPN if they want to make their home networks accessible while they're on the road.