Google Nexus One CyanogenMod

Google recently announced that it would not be releasing a Google Android 4.0 software update for the Nexus One smartphone, because less than 20 months after release, it’s apparently “too old.” Instead, Android 4.0 Ice Cream Sandwich will focus on its newer flagship phones. First it will launch first on the new Samsung Galaxy Nexus phone and Google will push an update to the Samsung Nexus S soon after.

It’s kind of a shame to see Google abandoning support for a phone in such a short period. After all, if you bought a Nexus One in the US the day it came out, you might still be under contract with your wireless carrier.

But as blogger Michael Degusta shows with a rather informative (if incomplete) chart, the Nexus One has received fast and reliable software updates more regularly than any other Android device ever released. Most Motorola, Samsung, and HTC smartphone owners have things much worse.

Click the picture to see the full chart

Here’s the thing though: I don’t really care as much as I used to. Because over the past few years something really amazing has happened. We’ve seen independent developers breathe new life into old gadgets time and time again thanks to unofficial software updates.

Old hardware, new software

For years, one of the rallying cries for Linux-based operating systems is that they can give new life to older computers. Have a machine that shipped with Windows 95, but which doesn’t have the hardware to support Windows 98 (or Windows XP, or Windows 7)? No problem, just install Ubuntu, or something even simpler such as Tiny Core Linux or Puppy.

But that doesn’t just apply to older Windows computers. More than a decade ago HP released a line of mobile devices under the Jornada name. They ran Windows CE, had (barely) touch-typable keyboards, touchscreen displays, and were small enough to fold up and fit in your pocket.

Unfortunately they were also really expensive, and as a struggling student I couldn’t really afford one… until a few years later when you could find a used Jornada 720 for sale on eBay for under $200. I picked up a couple of these little devices and was thrilled with their mobility. They were great for taking notes on the go in my day job as a reporter.

What they weren’t great for was surfing the web — they were stuck with an outdated mobile version of Internet Explorer which couldn’t handle mdoern (even at the time) websites. At the time there weren’t many good alternative web browsers for Windows CE — so I turned to the world of Linux and discovered Jlime.

Jlime is a custom version of Linux designed to run on older handheld devices that were originally built to run Windows CE. That includes the HP Jornada line as well as older NEC MobilePro devices and a few other products. This allows you to install third party apps including alternate web browsers, text editors, and games.

When I was testing JLime in 2004 or so, I wasn’t really that impressed with the level of performance I was getting from the Jornada, but the project has come a long way since then — and more importantly, Jlime has been offering users with a way to get more out of their aging devices for the better part of a decade — long after HP and Microsoft stopped supporting the platform.

Here’s a video from a few years ago showing an HP Jornada 720 running Duke Nukem 3D:

Because Linux is based on open source software, independent developers can add features — or strip features. They can build Linux-based software that can run on supercomputers, but they can also squeeze powerful new software onto older devices with slower hardware — often allowing it to perform better than it did with the original hardware.

Sometimes that means finding ways to shoehorn Linux onto a 10-year-old HP Jornada. Sometimes it means replacing the operating system that came with an under-supported device just a year or two ago.

The Toshiba AC100 is a thin and light laptop-style computer which has a 1 GHz NVIDIA Tegra 2 dual core processor, a 10 inch, 1024 x 600 pixel display, and Google Android operating system. Toshiba hasn’t done a great job of supporting the product since it was launched in 2010 — but users that want to can install Ubuntu Linux to transform the device from an Android-based computer (which is limited by its lack of a touchscreen) into one that can run thousands of Ubuntu applications.

Android enters the scene

Sometimes Android is the solution rather than the problem though. Google’s Android operating system is designed to run on phones and tablets — and while Google works on major updates to the operating behind closed doors, the company generally (but not always) releases the source code once its ready to ship a major update.

Independent developers have been grabbing code from the Android Open Source Project for the last few years, and making it their own by creating custom versions of Android (or “custom ROMs”) which can run on current or older phones or tablets. Often these custom ROMs offer advanced features that may not have come with your device, including tighter control over the display, sound, notifications, or applications on a device.

But one of the most impressive things we’ve seen with custom ROMs is that if Samsung, HTC, Motorola, or any other company decides not to offer software updates for your phone or tablet, there’s a good chance that you can find a custom ROM that will let you run the latest software anyway.

For some people this may not seem that important. After all, most Android apps are designed to run on older phones. So if you bought a phone running Android 2.1 a few years ago and it’s still running Android 2.1 today, then odds are that it will be able to run many of the latest games, web browsers, and other utilities released into the Android Market today.

But what about tomorrow? Eventually developers will stop supporting older versions of Android… and if the manufacturer of your device doesn’t offer an update, then you might feel the need to toss it aside and buy something new.

The custom ROM development community is making it possible to hold onto those older devices longer though — and that’s better for the environment and for your pocketbook than chucking older gadgets in the trash (or even recycling them) when they’re past their prime.

Phone makers, wireless carriers, and other interested parties want you to buy a new phone every few years because that’s how they make money. And odds are that if you’re reading this site, at some point you’re going to lust for a device with a faster processor, higher resolution display, or some other killer feature.

But it’s nice living in a world where you get to decide when your old device isn’t good enough anymore instead of the company that sold it to you.

My Nexus One 

For about 18 months I was running the stock Android operating system on my Nexus One phone. Every time Google pushed out an update, I was among the first to get it, and this made me happy. I could check out the new features as soon as they became available and be certain that I was getting the latest security updates as well.

I also root my phone… not necessarily because I need to play around with hidden aspects of the file system or change my boot logo or make other deep changes. I’ve been rooting my phone since last year because most phones running Android 2.3 offer no way to take screenshots without rooting your phone or plugging it into a computer and running the Android Software Developer Kit tools.

As a mobile tech blogger, I regularly want to snap a picture of my phone’s screen and sometimes I want to do that when I’m not near a computer. So I root.

Every time Google pushed out an update though, it removed my root access and I often had to find a new method for rooting the phone because older tools may have stopped working.

A few months ago I got tired of playing this game and when Google pushed out a new update, rather than spending hours or days looking for a way to root the phone, I decided to unlock the bootloader and install CyanogenMod 7.1.

Google Nexus One with CyanogenMod 7.1

CyanogenMod is one of the most popular custom ROMs for Android devices. In fact, you can even run CyanogenMod on some devices that didn’t initially ship with Android at all such as the HTC HD2 Windows Mobile phone, or the HP TouchPad webOS tablet.

After installing CyanogenMod on my Nexus One, I noticed that it felt faster, had more free space for apps, and offered more customization options. I’d been starting to think it was almost time to replace my phone… up until the moment I installed CyanogenMod.

Now it feels like a new device. It doesn’t have the fastest processor or the most storage. But it runs virtually every app I can throw at it, and never feels slow. I also know that there’s a very active team of developers behind CyanogenMod, so even though Google won’t be offering major Android updates for the phone, I suspect that future versions of CyanogenMod will bring Android 4.0 and other updates to my aging phone one day.

And CyanogenMod is just one of many alternate ROMs for the phone. Other popular alternatives include MIUI and OxygeN1mod.

HP TouchPad

HP introduced the TouchPad tablet in July, 2011. The company discontinued the tablet in August, after just a month and a half on the market.

The TouchPad was the first and only tablet to ship with the webOS operating system. While HP says it’s not pulling out of the webOS business (yet), the company no longer makes webOS phones or tablets. That makes the future of the TouchPad look pretty uncertain.

HP did manage to sell quite a few TouchPads after marking down the base price from $499 to $99 in order to clear out inventory, and it’s likely that there are at least a million TouchPad tablets in the wild today.

True to word, so far HP has kept up its promise to continue supporting the tablet. The company has released two software updates for webOS 3.0 since launching the device, improving performance and offering new features.

But even if HP pulls the plug on webOS altogether, the TouchPad has a future thanks to the folks at CyanogenMod.

A group of developers has been working hard to port Google Android to run on HP’s tablet, and two alpha versions have already been released. Anyone with an HP TouchPad can download and install Android on the tablet today thanks to CyanogenMod.

The software is still a little rough around the edges, and many users have experienced problems with the WiFi connection or with the tablet shutting off unexpectedly or refusing to resume from sleep without a reboot. But work is continuing to make Android on the TouchPad more stable.

There are already benefits to running the buggy Android build on the TouchPad though. When you install Android you’re no longer limited to the 10,000 or so apps available for webOS. You can choose from hundreds of thousands of apps designed to run on Android — most work just fine on the TouchPad.

The tablet also feels faster (if less stable) and generally more responsive when running Android. Best of all, when you load CyanogenMod you get a dual boot system, so you can always revert to webOS if you prefer the original software — and if HP continues to support it.

There’s also an active homebrew software community for webOS, so I suspect that if HP ever does drop the ball, there will be a community of interested folks willing to keep the platform alive indefinitely.

Looking ahead

Even if CyanogenMod disbands, or Google stops releasing source code for Android, I think the cat is out of the bag. When I got frustrated with my HP Jornada 7 years ago there weren’t many options available for making it more useful. If the same thing had happened with a device a few years earlier, there would have been even fewer options.

Today, there are a number of great solutions available for end users looking to squeeze more life out of their aging gadgets. And that’s just for consumers… folks with coding skills are constantly building their own custom solutions on top of the work done by others — and sometimes they’re kind enough to release the tools for the rest of us to use.

Google could stop developing Android tomorrow, but there would probably still be independent developers working to add features and improve the experience. In fact, I suspect the independent development community would become even more prolific if Google stepped back.

Unlike open source operating systems that are developed with community involvement, new versions of Android are currently produced behind closed doors before Google releases them to the public. That provides a disincentive for anyone (with the possible exception of the developers at Amazon who developed the software for the Kindle Fire) to make any really big changes — since they might not work with the next version of Android, and they almost certainly won’t be incorporated.

So while the Android development community is strong today, I suspect it would be even stronger if Google loosened its grip on the operating system.

If you hold onto a device long enough, odds are the battery will die, the memory will give out, or something else will fail. But it may happen long before you stop finding useful software for your mobile device. Once upon a time it was common for people to wear their devices into the ground because they were too expensive to replace regularly, or because the pace of technological advancement was so slow.

Now we can wear them into ground for different reasons: because the hardware is good enough to offer a valuable experience for years to come, as long as there’s a community of developers willing to support the product… and there probably is.

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


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.

Subscribe to Liliputing via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 9,532 other subscribers

10 replies on “Giving old gadgets, new life (or how to interrupt planned obsolescence)”

  1. I’m firmly in the “open” camp, but it’s well to recognize there’s a downside to all this: 1) You have to be a techie, and the vast majority of people aren’t, and 2) it takes time to tinker; even for techies, time isn’t always a luxury. For many people and many situations, it’s “better” to simply buy the latest commercial product.

    All this reminiscing is preaching to the choir. There isn’t anything really insightful here.

    There is a reason Windows prevailed against Linux, and there’s a reason why people clamored for the latest Apple toy.

    1. To be fair… my point here isn’t necessarily that open source software is better — but rather that the tinkerers have found ways to keep old devices strong.

      The same would be true if they figured out a way to shoehorn Windows 8 onto a Palm Treo phone (which is highly unlikely). 

      But you’re right — most people in the market for gadgets like tablets probably won’t take the time to perform these sorts of upgrades when it seems easier to just buy a new product. But some will.

      I’m pretty certain that a very large number of people who picked up HP TouchPads this summer did so with the hopes of installing Android on them. 

      I’m also always amazed at how many people jailbreak their phones. There’s a fairly small group of people developing jailbreak tools, but a huge number of people using them. 

  2. I really think that the custom ROM community should charge a few bucks for their ROMs. This would allow them to support more devices and spend more time doing it. Who wouldn’t pay $5 for a good update to keep their device working for another year?

    1. I think their “business modell” works just fine. Take CyanogenMod for example. They have a donate button on their page. Like their work and have a few bucks to spare? donate!

      CyanogenMod is so popular, that they had official contact with nVidia helping with driver support, they had Sony Ericsson DONATE ~20 Devices to them, to get them supported, and their head developer “Cyanogen” was even officialy hired by Samsung to work for them.

      The reason why most custom roms are not only more current, more stable and FASTER ontop of having more features than most every official manufacturer rom is because their developers are having fun with what they’re doing, and most importantly, are doing it to have a cool rom on PHONES THEY OWN AND USE THEMSELVES.

      Charging people for Roms, to in turn buy additional phones just for the sake of supporting more models is like a second job, not the hobby to tinker with your gadget to make it better and sharing your results.

  3. This Article hits all the High Points of why i went with Android rather then iOS when i replaced my aging Windows Mobile 2002/2003 Device.

    Android is OpenSource, and while there was an active Modding Community for the non-free WinMo, Android is much more flexible.

    I am STILL using the T-Mobile G1, first ever Android Phone from 2008.
    It went from 1.0-1.6, until it was declared “to weak” for 2.0 and OFFICIALY abandoned.

    Thanks to the Modding Community it went from 2.0 all the way to -currently- 2.3.7 and feels as snappy now as it did with the last official 1.6, which is a true testiment to the dedication modders put into custom kernels and system tweaking of a much heavier os for a device that was deamed obsolete roughly 2 years ago.

    1. I’ve toyed with the idea of installing Android on my old Dell Axim PDA, but honestly that would just be a because-I-can experiment at this point, since I do have a reasonably good Android phone. 🙂

      1. Well, the modding community kept my G1 alive, and it’s my daily driver, so at least for me it’s not a “because-i-can” but a “because-i-have-to”.

        But i guess i’ve saved up enough to get the Galaxy Nexus when it comes out. Realy wanted to wait for ICS to get a device with no hardware buttons at all.

        1. Yeah, the Galaxy Nexus looks pretty amazing — but I’m not completely sold on buttonless designs yet. I want to see how well it’s implemented.

          The one thing I really miss about my Dell Axim is that I could hit a button to play/pause/skip tracks while listening to music or podcasts without pulling the PDA out of my pocket. It’s tough to do that without buttons.

          While most Honeycomb tablets I’ve used have worked reasonably well with buttonless designs, I’m testing out the Velocity Cruz T408 right now, and it has on-screen buttons with Android 2.3 Gingerbread. Most of the time they work as you’d expect, but when reading eBooks in the Amazon Kindle app, they have an annoying tendency to cover the top line of text for a few seconds whenever you tap the display the wrong way.

          I really don’t expect that to be a problem with ICS… but I also don’t really see buttons as a problem for phones… I think the only reason Google is moving away from them is because they don’t work as well on tablets, and rather than have developers write one app for tablets and another for phones, they’re pushing for a unified interface for both — even if it makes more sense for tablets than phones.

          1. My Problem when it comes to “buttons vs. buttonless” is that i don’t like the capacitive touch fields, can’t warm up to ’em at all.

            Either have a real, physical, clicky button, or not have them at all.

            The Problem with Android phones is that there just aren’t any RECENT ones that use real buttons. At this point in time the most recent phone (available in europe) to implement all of the android buttons as clicky buttons is the HTC Desire, and that by no means can realy be concidered “recent”.

            So i opted for waiting for an offering to do away with the capacitive ones alltogether 😉

          2. Fair enough. 

            I actually got used to the capacitive buttons on my N1 pretty quickly, but to each their own… and I do still miss the clicky buttons on the Axim. 🙂

Comments are closed.