Article 6D91R Android 4.4 KitKat is truly dead, loses Play Services support

Android 4.4 KitKat is truly dead, loses Play Services support

by
Ron Amadeo
from Ars Technica - All content on (#6D91R)
Android-KitKat-640x426.jpg

(credit: Google)

The Android ecosystem rightfully gets a lot of slack for being unable to deliver operating system updates to everyone in a timely manner, but there's more to Android updates than just OS support. App updates can keep a phone chugging along even after the updates have stopped, and Google's do-it-all super app, Google Play Services, contains a ton of app APIs and features and enables the really important stuff like Play Store transactions and advertisements.

Google just announced Play Services is dropping support for an old version of Android, and while OS development might stop at just three or four years, Play Services goes back way longer than that. Google announced Play Services is dropping support for Android 4.4 KitKat, which is now 10 years old. Support isn't really being artificially cut off, either. Google says KitKat's active device count is "below 1 percent," so there's not much reason to support it anymore.

studio64_L9Nw6w4ygg-980x671.png

Google's Android Platform chart has KitKat at 0.5 percent. (credit: Google)

These devices will stop getting Play Services updates after July, and then it's anyone's guess as to how much longer they will work. At some point, Google will change something, and your device will become a brick. Old, unsupported Android devices can't log in to a Google account, which is a prerequisite for opening half of the apps that come with your phone. You'll be locked out of the Play Store, Gmail, Google Maps, and other Google products, with no way to see these old versions again. Luckily, someone saw all this coming and took screenshots of every old version.

Read 1 remaining paragraphs | Comments

External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments