But as far as full-system backup and restore options go, you either have to root your system and use Nandroid or Titanium to backup to the phone storage itself, or you have to rely on adb backup. adb is Android Device Bridge, something that is accessed through the Developer Mode on Android. It feels like Google has given up on this feature midway through and just left it flopping around, because it simply does not work. Although I haven’t had trouble getting backup to work (‘adb backup -apk -shared -all -f [file]‘), I could not get restore (‘adb restore [file]‘) to work automatically because of this bug (which incidentally is also obsoleted).

It turns out you need to get into Settings->Apps and kill as many running processes as you can, and then while restore is going on, monitor through adb shell and logcat | grep Backup, and continuously pm disable a number of running processes including com.google.android.googlequicksearchbox, com.google.android.plus, com.google.android.music, or whatever else restore is stuck on. If you’re lucky, the restore process finally “finishes” and half of your apps and data are restored, while the rest are either not installed, or installed as some old OS-default version, including Google’s own apps like Talk, Maps, etc. on account of Google Play services not being restored. Yeah, thanks, Google!

Obsolete: Similar to Unreproducible, but with a reasonable certainty that the bug did exist in the reported version but was already fixed in a later release.

…which is a lie. I give two pieces of solid evidence for why this is a lie.

Exhibit A. An egregious bug with the Media Transfer Protocol (MTP) on Android that has been reproducible by hundreds, if not thousands of users, on practically all Android phones, and has been reported since late 2012, and which still exists to this day in the latest Android Marshmallow, has been marked as “Obsolete” in 2014. Now you tell me if this bug is either “unreproducible” or “with a reasonable certainty … fixed in a later release”? Persistent users have filed a new bug report that is now “Assigned.” Let’s see what life outcome this incarnation of a bug has.

Exhibit B. According to Reddit, Google closed 11889 bugs (actually 11879) within a couple of days with the status “Obsolete” in December 2014, the above-mentioned bug among them. In comparison, the total number of bugs closed in the same period was only 11988, so this was a massive purge. Now, it is not humanly possible to evaluate nearly twelve thousand bugs in two days to determine whether “with a reasonable certainty … the bug did exist … but was already fixed.” The logical conclusion is therefore nobody bothered to look at these bugs and nobody bothered to triage when they reached potential end-of-life. Sounds like a broken bug handling system to me.