Google may have no plans to release an official Android 4.4 software update for the Samsung Galaxy Nexus. But the nice thing about phones that ship with unlocked bootloaders is that you can load your own software — and like most Nexus devices, there’s a pretty healthy developer community involved with the Galaxy Nexus.

So just a day after Google released the source code for Android 4.4 KitKat, developer Grarak released an early build of KitKat for the Galaxy Nexus. The developers behind SlimROms have also released the first builds of SlimKat for the Galaxy Nexus based on Android 4.4.

SlimKat Android 4.4 for the Galaxy Nexus

The software is based on the Android Open Source Project code, so it looks a lot like the software you’d get if you bought a Google Nexus 5. It’s still a bit rough around the edges, with some bugs — but developers are working to squash those pretty quickly. If you’re looking for a stable version of Android 4.4 for your phone, you’ll probably want to hold off on installing this custom ROM unless you want to help with development.

But the speed with which we got unofficial builds of Android 4.4 for the Galaxy Nexus is a good sign of things to come. Google may be abandoning support for its older phones, but the independent developer community will likely help keep it alive for years to come.

The Samsung Galaxy Nexus was released in October, 2011. Google’s official reason for dropping support is that the phone is more than 18 months old, and that companies regularly phase out support for devices once they hit that age. But there are plenty of people who bought the phone just over a year ago, before the Nexus 4 was announced. So not all Galaxy Nexus users have had the phone for 18 months or longer.

It’s also interesting that the Galaxy Nexus was the last Google Nexus phone to feature a removable battery and removable back panel — and also the last Nexus phone built by Samsung, a company that’s increasingly competing with Google by offering its own app stores and APIs for Android (although that hasn’t stopped us from getting a Samsung-built Nexus 10 tablet and a Google Play Edition Samsung Galaxy S4).

But maybe Google really just doesn’t want to spend the time and effort necessary to keep older Nexus devices up to date, when it’s pretty clear independent developers and enthusiasts who really care about these things will do them anyway.

Meanwhile, by pushing the latest versions of Google Play Services and other Google Apps to phones running Android 4.3 and earlier, Google can still offer updates and improvements to older devices without releasing firmware updates.

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign

or...

Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

6 replies on “Android 4.4 KitKat ported to run on the Samsung Galaxy Nexus”

  1. So they are implying that Android mobiles have only an 18 month shelf life from release date (not ‘purchase date’)??
    Android 4.4 software is said to be more efficient and able to run on a variety of older or lower end hardware than the Galaxy Nexus.

    What about the facts, * So many mobile contracts are for 2 years, * Not all Galaxy Nexus users have had the phone for 18 months??

    The Texas Instruments argument is weak, it’s the responsibility of Google to have made the relevant agreement with them at the time to ensure they would support that chipset for a ‘reasonable’ amount of time.

    This decision has Drastically devalued all Nexus devices and many other Android phones, as well as brand damage to the whole Android ecosystem itself.

    Honestly can’t believe they didn’t think this through properly, so many supposedly great technical minds, but crap business level decisions.

    1. I know I first read this speculation on androidpolice and then other sites started saying “google insiders’ were confirming it, yet all evidence suggests that TI still supports their chips and OMAP support is in the kernel, and there should be no problems with them.

      Honestly think google and google apologists just wanted to deflect some of the rage from their “18 month” update policy — stopping updates 6 months after end of sales.

      At least now it’s official, Android OEMs, including Google will NOT give support after 18 months — considering today’s mobile hardware that seems very short.

      Here’s hoping cyanogenmod inc takes off, otherwise I’ll be looking at non-Android devices.

      1. So you’re upset that you can’t run newer versions of Android, and your solution is to… not buy an Android phone next time?
        By the time my contract was up on my last iPhone is was nearly unusable with the latest software updates because it was so slow. I wouldn’t be surprised if you found the same thing on newer versions of Android (that happened to me with my first Android device – you could run ICS using cyanogenmod, but you didn’t want to).

        1. Still outrageous that a minor bump in Android versions wont get released on a “flagship” device.

      2. My Huawei ascend P1 is also OMAP based, and Huawei gave the same basic reason (TI) in December last year was the reason they were not releasing 4.1 for it. Then mid 2013 we heard that we might be getting Jellybean. Still waiting, still in beta…

Comments are closed.