The non-existence of Android backup and restore

People change phones. They want their programs and data to show up on their new phones. Apple has solved this problem. Somehow, Google has not. As explained here, settings can be synced through Google’s sync API. It is however useless except for Google’s own apps and whoever uses their API (maybe nobody).

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).
(Read the article)

Google marks bugs it doesn’t want to deal with as ‘obsolete’

Apparently Google has a habit of marking bugs it doesn’t want to deal with as obsolete. According to Google’s own Life of a Bug explainer, a bug categorized as “Obsolete” means,

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.
(Read the article)

android dialer idiocy

So on the Android dialer, if you turn down the system volume, the in-call DTMF tones are also turned down in volume. (See here — I’ve verified this.) Now guys, I know it saves a few lines of code, but WTF?