So, since last week, I’ve been updating my phone (Samsung Galaxy S Captivate) with the newest and latest experimental updates of CyanogenMod 10 (Android 4.1, code name Jelly Bean).
As expected, nightly builds are buggy. Very buggy. And unreliable. At first, they usually work, but then they progressively slow down, and become bloated. On top of that, the battery as been constantly getting drained in a matter of a few hours, whether I’m using the phone or not. It’s strange, but it seems to be getting better with each update.
Nevertheless, I continue to update. The latest CM9 RC (Release Candidate) 2 was very stable, and I’m fairly certain that not that much as changed between 4.0.4 and 4.1, besides minor UI changes, and the addition of Google Now’s app, the mute competitor to Apple’s Siri.
Thus, I’m fairly certain that as moders adjust CyanogenMod 10 for the Galaxy S1 progressively, it will work just as well as 4.0.4 did.
I’ll be keeping you posted.
Read the rest of this entry for my latest update on CM 10 for the Samsung Galaxy Captive (September 19th, 2012)
So I’ve been continuously updating at least once a week since the original post date. Each nightly release improves upon the previous one, except for the occasional “lemon”. A few new customization features have been added along the way, giving you back more of the controls you had back in CyanogenMod 7.2, which is great.
Unfortunately, each build, after a few days of use begins to become highly unstable and the UI locks down and crashes. This is particularly inconvenient to daily use.
However, I’m sure by the time we have a Release Candidate for CyanogenMod 10, the stability problems will be sorted out. In the mean time, I will continue to upgrade to Nightlies.
On a side note, I like the direction CyanogenMod is taking with their simple clean bootup animation. See it for yourself here.