Updates on Android Still Suck, and it's a Security Flaw

Posted by Matt Birchler
— 1 min read

This is the summer of link baity headlines it seems. This week’s piece is from Lorenzo Franceschi-Bicchierai: Goodbye, Android. It’s a solid article that I can relate to. I have long been a big Apple fan, but I spent most of 2014 with an Android phone so I can relate to many of Lorenzo’s complaints.

Some carriers and manufacturers are better than others, it’s true, but they all pretty much suck when it comes to pushing updates. There really isn’t a better way to put it.

iOS 9 will release sometime in September and will be available on any iPhone released in the past 4 years. For comparison, Android M is coming out around the same time and it will only be coming to people who bought a top-of-the-line Android phone in the past 12 months.

And this is not all Google’s fault.

When the same thing happens with Android, Google patches and then… god knows when the AT&Ts, Verizons, HTCs, and Sonys of the world will decide it’s important enough that they should care and send you the update with the patch

An Android update from Google needs to be implemented by the OEMs and then approved by each carrier individually. It’s a drawn out processes that’s wildly frustrating as a user. I had an HTC One during the release of Android Lollipop, and it was many months before the phone got updated. By that time, I was back to the iPhone.

Some will say that this is not a problem if you take your phone’s ROM into your own hands and flash something custom like CyanogenMod. But come on, this isn’t a reasonable expectation for >90% of people.

In the end, he comes to a very reasonable conclusion:

Or, lastly, you can give up, switch to Apple and buy an iPhone.

As much as my old self will hate me, I’m going to choose the last option.