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.
The latest version of the Play Store hit the scene a little over a week ago and introduced a tweak to the way permissions are displayed at install time, and it left some people feeling a little...uncertain. Gone is the ugly wall of poorly spaced, semi-specific permissions. The replacement is a short set of simplified categories, each with crisp-looking icons and buttons that reveal a brief description when tapped. Google filtered through roughly 145 permissions and narrowed them down to a dozen groups, plus one bucket for anything that remains.
If you used to play around with CyanogenMod Nightlies, but switched to the more stable M-series releases, it has probably felt like forever since M6 hit the scene. Well, M7 is hot off the compilers, just in time to fill that insatiable need to flash your phone or tablet. Don't forget, the M-series has officially taken the place of Release Candidates and Stable builds, so this is considered the most reliable version of CyanogenMod available.
Aside from Windows Media Player, there is probably no single video player more widely installed on computers than VLC. It may not have the prettiest interface (or icon), but everybody eventually turns to that huge orange traffic cone, especially for file types that simply can't play in anything else. While VLC provides a mostly full compliment of features, there is one request that has gone unanswered for a while: Chromecast support.
Back in April, owners of the Samsung Galaxy S4 Active were treated to the ultimate tease when an update to Android 4.4 KitKat began rolling out, only to be put on hold a few days later. The only explanation was a claim that AT&T and Samsung were "looking into potential improvements." It looks like the time has come -again- for the S4 Active to make the jump to KitKat.
Most people familiar with the Nexus program know that each new Android update usually brings with it a new set of driver "blobs" for each supported phone and tablet in the product line. Even though these proprietary binaries are usually the latest versions when they come out, Google still occasionally receives updates to the drivers even when it's not a good time to issue an OTA. As we've just witnessed from the long lead time on the 4.4.3 release, it can take quite a while before an update is rolled out.
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.
Ever since the unexpected delay between XE12 and XE16, the Glass team has been in a near rapid-fire mode with the OTAs. There were a staggering 5 updates of XE16 in the month of April (6 if you count the 2-parter with XE 12.1) and 3 official versions of XE17 during the month of May. As it turns out, there may be a fourth, unreleased May update to Google's experimental wearable.
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).