A few days ago, we reported on the HTC Hero receiving both Ice Cream Sandwich and Jelly Bean ROMs. As if this wasn’t enough proof that Jelly Bean can run on practically anything, the Hero’s rebranded sibling, the HTC Droid Eris has now also received the same treatment.
Though the device has only a measly 528MHz processor and 288MB RAM, yet again, the talented developers on XDA prove that there are no boundaries when it comes to ROM development on older devices.
The Droid Eris, a Verizon branded HTC Hero with minor variations, has been given a taste of Jelly Bean by XDA Senior Member MongooseHelix. The ROM is of course a work in progress, and does have a number of issues:
There will also be some inherent lag due to the hardware limitations of the device, but the ROM is functional and gives Droid Eris owners a taste of Google’s latest Android revision without having to splash out on a new device.
If you want to give the ROM a try, head over to the ROM thread.
March 2, 2012 By: ElCondor
Perhaps you remember the days of the very first Android ports to Windows Mobile phones such as the HTC Touch Diamond and HTC HD2. Beside the fact that this groundbreaking development was one of the factors that ultimately led to the end of Windows Mobile development on XDA, it did bring some innovative features to the table. Dual boot for example. It was revolutionary to be able to choose between Android and Windows Mobile. After a few months, when people started to move to newer phones, and this innovation ultimately got buried under the huge
mess mass of development for Android phones.
It seems there is currently only limited active development for a dualboot system for native Android phones. There have been projects in the past, for example for the Samsung Galaxy S II, Droid Eris, Xperia Play and LG GT540, but it seems development is more focused on individual ROMs nowadays. Multi-device development – and yes, we use the word development a lot – is more and more subject to development on individual devices. In the past, developers collaborated to put together something great (Ervius Visual Kitchen, anyone?). The Android port to Windows Mobile, called XDANDROID, and the dual boot innovation are just few of the many examples of this.
Although it isn’t a bad thing that developers have a strong focus at individual ROM development, we probably all share the dreams of being able to boot into a clean, battery-saving and light-weight Ice Cream Sandwich ROM while also having the option to boot into another ROM, one that might be an experimental ROM or a ROM that is more focused on performance. Or any other combination. The open-source Android OS allows for many dramatic changes to be made to its structure, dualboot on Android has been proven to work on the Droid Eris, so why hasn’t development started yet? Why seems development of such innovative systems at a standstill? I say we fire up that innovation engine as soon as possible.
November 18, 2011 By: Will Verduzco
Google’s Mobile Product Manager Hugo Barra recently stated that the company had no plans to update the Nexus One to Ice Cream Sandwich, citing that the handset was simply too old to run the newer operating system. Many users felt unnecessarily abandoned, believing that a former flagship device under 2 years old could hardly be considered “too old” for updates. Having used a Nexus One as my primary device for eight months, the news made my heart sink ever so slightly.
Ironically enough, the first ICS SDK-port for the Nexus One actually had already appeared four days earlier. However, as is the case with the majority of SDK-ports, the lack of hardware acceleration made things dreadfully sluggish. Instead, AOSP builds are indeed the Droids you’re looking for.
Four days ago, we broke news of the ICS Source Code release and predicted an imminent rush of AOSP builds. We are happy to announce that not only has XDA forum member dr1337 begun the Nexus One AOSP porting effort, but several other devices have joined the tide. Thanks to the hard work by XDA forum members dizgustipated, MongooseHelix, stritfajt, jaybob413, onecosmic, Chaosz-X, and zFr3eak; the Nexus S, Droid Eris, Hero, Hero CDMA, Galaxy S I9000, Desire, and Desire HD now have their first tastes of Google’s latest treat.
Without further ado, here are the links to get started on your own device:
While none of the releases have quite the level of polish required to be made daily drivers, their mere presence just days after the source code release speaks wonders of the amazing talent housed within our development community.
If there are any other AOSP builds that I have left out, please send me a PM through the forums, and I will promptly add them to the list!
October 4, 2011 By: egzthunder1
It certainly didn’t take long. If you recall yesterday, we published an article about a port of the HTC Pico’s Rom to the Hero CDMA. This port came loaded with a lighter qvga version of the brand new Sense 3.5, which is also referred to as Sense Zero. We said that we were probably going to see ports of this on all other devices that were left for dead when it came to updates. Well, a little over 24 hours later and we found threads started by XDA members Hintay and TeamSuicide who ported the whole thing to the Sapphire, the Eris, and the Hero GSM. They all share similar hardware and it was simply a matter of time before it all came to be.
Each Rom has its own set of bugs but they are really all regular bugs of fresh Sense ports (WiFi issues, usb connectivity, etc), so keep in mind that they are not perfect yet. However, if you would like to help by leaving feedback, it would certainly be appreciated.
This is a port from the Nordic test of the 2.3.5 Sense 3.5 ROM from the HTC Explorer(Pico).
Want something published in the Portal? Contact any News Writer.
Thanks Jurellz for the tip!