Over the past several days we’ve shown you CyanogenMod 10.1 running on the Nexus 4, Nexus 10, and even the Samsung Galaxy S III. These were official “nightly” builds, straight from the CyanogenMod team. Nightlies, as you likely know, are works in progress. They have known bugs in them. They are not feature complete. They haven’t been tweaked and polished. They are, however, sometimes stable enough for use as a daily driver — at least if you’re one of the more adventurous among us.
What about older devices? Where’s the love for them?
Even Google has cut off Jelly Bean support for their “older” smartphones, so it should come as no surprise that “older” phones are also being excluded from CyanogenMod as well — at least from the “official” builds. That’s the nice thing about the CyanogenMod project, if you want to pick up support for a device, you can do it. If you want to make CyanogenMod work on an old device, or an officially unsupported device, you can do that, too!
How did it turn out? Hit play, and let’s take a look!
Obviously, running Jelly Bean on such “old” hardware isn’t as snappy as it is on today’s powerhouses. Benchmark scores were abysmal. Apps were slow to launch and even slower to switch between. Ironically, that was about it. Everything else, especially anything having to do with the launcher or “core” apps was surprisingly responsive.
Geekbench 2: 417
Is it fast enough to be your daily driver? If you’re still using your HTC Vision, probably so. Here are a couple links to help get you started:
- CM10.1 (Unofficial) Experimental for HTC Vision / T-Mobile G2
- GAPPS for Android 4.2.x
Source: XDA Developers