This story was originally published and last updated .
While smart speakers have rapidly become ubiquitous in many of our homes, there are practical things about them—like initiating a factory reset when you sell them—that just aren't intuitive without a bit of Googling. And since the Assistant (fortunately) won't abide your voice request to initiate one, that means this is one smart speaker and display feature that requires going hands-on. Fortunately, it's pretty easy in most cases for devices like Google Home, Nest Home, and Nest Hub.
We're pretty big fans of the C by GE bulbline here at Android Police, given the features, Assistant integration, and excellent price point. Although we pointed it out how tedious the reset process for the smartbulbs was in our reviews, the official video by GE Lighting describing the process is currently making the rounds, and it's pretty funny.
When a manufacturer releases a system update, there is a general assumption that the update will not break everything. If you have a Pixel C that hasn't received the Android 8.1 update yet (or you've been holding off), consider yourself lucky - many users discovered that the OTA triggered a factory reset.
Just a bit before the new Pixel 2 phones launched, Google released a new trade-in program that allows you to swap an older phone for credit that can be applied (in the form of a partial refund) on a purchase. Since it rolled out, there have been reports that the inspection being performed on phones isn't accurate, resulting in an incorrect trade-in value assessment. According to a statement by a Google rep, this issue seems to have been fixed, at least when it comes to Pixel phones and factory reset/device classification.
If there's one thing sure to ruin your day, it's a crashing smartphone. Even worse if the bug proves so bad that your phone eventually insists you do a factory reset, losing data in the process. This is exactly the situation that has befallen a number of Nexus and Pixel owners in recent days, and it's all to do with an adaptive icon bug that was discovered by the developer of third-party Facebook wrapper called Swipe.
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.
Something strange has begun happening to many of Google's OnHub and Wifi routers. The units are refusing to broadcast WiFi signal, and are requiring factory resets to function properly again. Many people refuse to use OnHubs or Wifis because Google has too much control over them, and it seems like they'll have a little more ammunition to use in arguments against these cloud-connected devices now.
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.
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.