The user facing features of Android 8.0 were mostly already known before yesterday's grand reveal of the Oreo name and the final version, but there are usually other tweaks that only become apparent after a bit of time looking through the documentation. One interesting new discovery is a feature called Rescue Party, which is designed to combat a much publicized recent Android problem, the infamous bootloop. Read More
In our final Android 6.0 Compatibility Definition Document post, we'll be looking at a small[-ish] clause added in the security section of the CDD. Previously, Google had not actually defined any particularly specific requirements about factory resets for Android devices. While all devices have such a function, they may differ in their efficacy and level of security post-wipe. And while we don't have any reason to believe a particular manufacturer is not already meeting these new requirements (a point I will stress), it's good to see Google is at least laying down a clear mandate on this issue going forward.
Basically, it was possible, pre-Android 6.0, for a manufacturer to merely conduct a logical wipe when doing a factory reset of a device. Read More
This isn't a news story, but more of a "public service announcement" about an Android feature not everyone may be aware of. If you've ended up here because your Android phone is telling you that, after a factory reset, you cannot log into your device for 72 hours (3 days), I don't have much good news: you're going to have to wait it out.
If you want to know why exactly this happens, regardless of whether or not it has affected you, this post will at least show you how to avoid falling victim to this security measure again if you find it to be too much trouble, as well as why this feature exists to begin with. Read More
Update 2: This exploit probably won't work on most Galaxy S III's as long as they have the most recent OTA update, as we demonstrate on video here.
This issue is, unsurprisingly, a lot more nuanced than the video here lets on. The bug is based in the stock Android browser, is in fact quite old, and has been patched in more recent builds of Android - this is probably why Nexus devices running the most recent OTAs are unaffected. The fact is, this is not a Samsung problem, it's an old Android problem that has been known about for some time.