Second verse, same as the first. Two days ago the CyanogenMod ROM team announced a security update to the CM 10.1 platform, incorporating the "Master Key" security patch that Google had already issued back in February. Yesterday another, more intricate exploit in the same vein was posted by a Chinese blog, and again, Google has rapidly moved to patch the problem in Android... which won't be much comfort to those running an older release.
Hot on the heels of Bluebox's disclosure of the "Master Key" exploit, a Chinese blog has posted details of a similar vulnerability. This attack also sidesteps a bug in the signature verification step and allows seemingly innocent APKs to include a potentially dangerous payload; and like its brethren, Google has already patched the flaw and posted it to the Android Open Source Project (AOSP). The information comes to us from a China-based group (or possibly individual) calling itself the Android Security Squad.
Scary tales about Android malware have been told since before people started guessing what dessert name would start with the letter 'D' (it's "Donut," in case anybody has forgotten.) Most of those claims came and went, amounting to little more than ghost stories. Unfortunately, there are a few real ghouls and goblins for which we should be afraid. Back in February, one such monster was discovered lurking about that allowed modified APKs to be installed on your device while successfully side-stepping the cryptographic signature used to prevent that very thing.
Google has just published the platform distribution numbers collected over the past two weeks, and things are finally looking up for the 4.1+ crowd. It's been a long, tedious, tiring trek, but Android 4.1.x/4.2.x, collectively known as Jelly Bean, has finally become the dominate OS – surpassing Gingerbread by 3.8 percent. It may not be a huge amount, but Jelly Bean is currently running on 37.9 percent of all devices – a full 4.9% more than last month's numbers.
HTC has confirmed that the One S - something of an unloved stepchild in the 2012 One line of phones - will not be receiving any future Android or Sense version upgrades. We contacted HTC and received a similar statement: the One S will be staying on Android 4.1 with Sense 4+.
The One S received its last major update in December, which was the aforementioned Android 4.1 / Sense 4+ firmware.
While Samsung has been dipping its toes into the single-screen multitasking world, Google has yet to do the same. According to noted Android and Google tipster ryan_socio (Ryan Matthews, not his real name), that's about to change. Ryan posted a message to The Verge's social user section, detailing an upcoming version of the YouTube Android app that will let users watch videos and interact with the rest of Android at the same time.
Good light meters are expensive. The other problem with light meters is that they're often clunky and outdated in appearance. Pricey and ugly as they may be, they're a hugely convenient tool for photographers looking to get their exposures right the first time.
Lumu is looking to address both of those problems with the similarly-named Lumu light meter for smartphones. The Lumu, to put it simply, is both beautiful and awesome.
I totally missed this in my Android 4.3 teardown, but luckily there are some fellow tinkerers out there, namely Kevin of TeslaCoil Software (maker of fine products such as Nova Launcher and WidgetLocker), picking up my slack. It looks like Google is planning some cool notification services for 4.3, possibly something that gets third party apps into the mix!
Contained in the leaked S4 Android 4.3 build are all sorts of notification-related changes.
Wow. Out of the blue, an Android 4.3 rom hits the internet, and it's not built for the Nexus 4, or 7 or 10, but for the Samsung Galaxy S4. What a strange turn of events.
Of course, I couldn't stop myself from diving right in, and while I don't have a Galaxy S4 to show you screenshots, that's really not a big deal, because this leak pretty much looks identically to 4.2.
Yesterday, we reported on an alleged Android 4.3 Jelly Bean ROM originally posted by SamMobile. Since then, we have – in usual style – been digging away, looking for goodies. In the midst of that search, Ron noticed something – the Roboto files in the ROM were up to 30% bigger than the versions found in 4.2.2.
My first guess as to what would cause a file size difference was the presence of additional glyphs.