My experiences with CyanogenMod7 on the HTC EVO 4G

So last week a buddy of mine (who also owns an EVO) said to me, "Hey, when is Sprint going to get their act together and release a Gingerbread update for the EVO?" And I responded, "Well, actually... I just saw a leak of the Sprint ROM go up on XDA recently. Do you want to give it a try?"

And after discussing the possibilities, benefits and risks of rooting and flashing his EVO, we actually decided to ignore the Sprint leak (for now) and give CyanogenMod 7 a go.

The main reasons:
1. The Sprint leak really doesn't seem release ready. Personally, I've played around with questionable leaks in the past on my Hero, but I wasn't about to drop that onto my buddy, who is probably capable of dealing with the intricacies of a not-quite-release version of android, but likely has less free time to screw around with it than I do.
2. I freaking love CyanogenMod. Cyanogen (the guy, not the ROM) and his team has earned a reputation for putting out quality android ROMs, both in stability, performance, and added features.

So last weekend I flashed CM7.0.0 onto my EVO, and this morning I finished flashing the latest update for the EVO, 7.0.2.1.

My thoughts so far:
Gingerbread on the EVO is nice. Generally, the taskbar, menus and other android-specific UI elements have been standardized and given some nice touch-ups to improve the general look-and-feel of the OS. And my phone so far has had far better battery life than I did while running Fresh 3.5 (a Sprint-Sense-UI-based ROM).

CM really adds some nice UI tweaks as well. I LOVE the PowerControl widget in the notification/task bar. I love the new customizable lockscreen (you can set up a shortcut to launch an app directly from the lock screen).

At the risk of sounding like a broken record, whenever I venture away from the Sprint Sense UI I do miss their nice calendar agenda widget. I have the CalWidget running in CM7, but visually and functionally you just can't beat the Sense UI experience there.

Some other perks of CM7:
- All of the glory of Gingerbread on the EVO
- Customizable lockscreen gestures
- An updated (stock android) camera app
- An updated (stock android) music app
- A download manager (helps if you haven't installed a File Manager app)
- Improved power management
- built-in over-clock/under-clock support
- built-in JIT compiler support



So I plan to stick with this as my daily ROM for at least a few weeks. If XDA finds a better leak of the pending Sprint update, or any of the ROM developers manage to release a nice GB + Sense-UI variant based on the Sprint leak, I may give that a shot for comparison purposes.

CyanogenMod 6 for the Hero

For fellow Hero modders like myself, you probably already know that Sprint and HTC announced that they would not be pursuing an official, Sense-ified version of Froyo for the Hero. So I have been running CyanogenMod on my Hero for several weeks now, and I must say it has been a very satisfying experience.

The basic facts:

CyanogenMod is based on the AOSP (Android Open Source Project)

CM6 is a stable build of Android 2.2 (Froyo)

My configuration preferences:

JIT enabled

SetCPU overclock capped at 614Mhz (roughly 16% OC)

Froyo native apps2sd support enabled, moved non-essential apps only

I have been running CM6 for a while now, and while I managed to find a respectable config for SetCPU to overclock the Hero processor, my battery life was unpredictable, and unfortunately I could burn through a freshly charged battery in as little as 6 hours, even though I kept my cap at 614Mhz and used profiles that should have scaled down based on battery charge.

Tonight I am switching away from SetCPU to the Collin_ph battery tweak to see if I can solve some of the battery issues I have been experiencing. If anyone else has some recommendations for customizing the collin_ph settings, so far I am sticking with my original cap of 614Mhz, both for stability and for battery life, but if there are any other setups that are considered "stable" I am open to suggestions.

Other observations:

- One of the first things I missed was the agenda view from the HTC Sense calendar widget. I did find that CalWidget was a sufficient functional substitution, albeit ugly as dirt. 

- I also am running FancyWidget to replace the beautiful clock/weather widget that is the signature of the HTC Sense UI improvements.

- The stock Android camera/camcorder UI is uglier than Janet Reno. (Does anyone have a recommended alternative?)

- Google Voice integrates nicely to replace the HTC Sense visual voicemail, and the Froyo-only GMail is also rather slick.

- JIT on Froyo actually works. (I realize that others may be successful at enabling JIT in an Android 2.1 rom, and actually got a performance boost out of it as expected, but in my experience it was a waste of my time even trying.)

When Flipz releases a Fresh ROM update based on the latest Sprint update I may nandroid my current setup and switch back for a bit, just to see what Sprint has come back with to fix the dialer issues, but for now I am very happily enjoying Froyo on the Hero, and recommend it for anyone with a little time and the willingness to tinker.

Thankyou's go out to:

Cyanogen and team, for bringing us the awesomeness that is CyanogenMod

darchstar, for porting CM6 for the Hero CMDA

XDA Developers, from which I have learned nearly everything I know about modding

Jesus Christ, for saving my soul from sin and death, and freeing me from the fear of voiding the warranty on my Hero

Android 2.1 JIT compiler a waste of time

So I have been experimenting with a JIT compiler in Android, and I have to say, it is really frustrating when the HTC Hero runs out of internal memory because of the memory requirements of JIT, and Android 2.1 automatically reboots itself. Besides that "feature", it works great.

I have read that Android 3 will have built-in support for JIT, and I imagine that phones newer than the HTC Hero will come with more built-in memory, so until then I think I will switch back to the standard Dalvik VM and get my geeky kicks elsewhere. (Such as with OC'ed kernels.) For now.