“It wasn’t quick or easy, but we are extremely proud of this release and what it represents for us as a group. The jump from 2.3.7 to 4.0.4 in many ways was a fresh start for this project, and as much as the code changed, the structure and organization of CM as a whole changed as well. It meant a lot of hard work, and late nights, but also a ton of fun. We are in this for the challenge, and the reward is always the satisfaction received when we release it to the masses as a ‘stable’ product. This RC1 brings us a step forward toward that payoff.” CyanogenMod is an absolutely amazing project, an amazing piece of software. Been running CM9 on my SII for months, virtually without issues. It absolutely baffles me OEMs don’t just use this instead of their own Sense or TouchWiz crap. This is so much better it’s just not funny anymore.
For us Galaxy Nexus users, CyanogenMod is late to the game. AOKP FTW
I’m sure other people with bloatware-filled FrankenAndroid phones will put it to good use though.
isnt AOKP based on CM source?
I got an old Nook Color for super cheap and was looking forward to running CM7… and it’s been pretty awful. Lots of crashes. Terrible UI. The basic Nook Color Android-based software is light years better (though limited). And CM9 is pretty buggy evidently on this little reader/tablet.
I was disappointed since I’ve heard such good things about CM. Maybe I will try another build or something.
I don’t think it is CM’s fault in this case.
I also own a Nook Tablet (not the color though) and I can tell you that B&N has locked the NT to the bone. It is just way too difficult to mod and, of course, the amount of devs working for it is far more limited than the ones working to port to a Samsung device, for example. I have read threads on XDA that point out to the reverse engineering of things like the bluetooth module.
I also have a SGS2 and it feels like a breeze to use. Sadly can’t say the same about NT.
But I suggest you waiting for the full release on the Nook and give it a spin.
Interesting. I’ve been dual booting CM7 for several months on my Color and not 1 crash. Just making Bluetooth available has been kind of a big deal on this as it does allow me to use a mini wireless keyboard/trackball.
The only problem that I’ve encountered that I just haven’t fooled with yet is a shortened battery charge life(I’m phrasing this badly, I have to charge it more often), but buying the Color as a refurb may well have contributed to this.
Otherwise, pretty satisfied.
I am not entirely happy with the Samsung-provided ICS ROM on my Galaxy Note. There is nothing specifically wrong with it, but e.g. TouchWiz tends to be somewhat lacking. I’ve been leery of trying out CM mainly because I do not wish to lose S-Pen – functionality, that’s one of the two main reasons of why I got the phone in the first place. It seems though that CM is starting to get quite stable even on the Note, so perhaps this RC1 is now worth trying.
I have an AT&T Note and use an unoffical build of the CM9 R0 Rom on it. Other than the S-Pen not working yet, it is _very_ stable and reliable, more so than the official Samsung Rom. But yeah, the S-Pen thing kinda sucks…
Just watch out for the “brick bug”. I just helped a friend root his Galaxy Note GT-N7000 and I was sweating bullets that we would end up bricking the thing because of that inexcusable corruption bug that Samsung introduced into their official ICS kernels. Who here thinks that wasn’t just an innocent mistake on Samsung’s part?
Edited 2012-06-27 04:32 UTC
strange this bricking issue people have experienced. I read and followed the xda instructons, installed a new kernal rooted that and not the Samsung gb one and then proceeded to migrate to a cm9 nightly build.
No issues what so ever. I am now on the Paranoid Rom for my note which is based on cm9 but brings great tablet functionality to my Note.
Also using Papyrus and Notes Mobile for great S-pen apps.
One of the reasons for getting my Note was cm9, that and decent screen and stylus.
I still believe it’s related to people installing some crap on their phones that interferes with the flashing and/or them just doing something wrong. I have some chainfire-kernel with CWM installed on my Note with rooted stock ROM, installing it went without a hitch.
At the moment I’m doing a CWM backup, then I’ll install CM9 RC and Google Apps
CM was never a reason for me for getting the Note, the large screen and stylus on the other hand were. In hindsight I should have waited a bit longer and bought something with a dedicated hardware-button for camera, it really ticks me off to no end that there is only an on-screen button for that.
Well, if somebody bricks their Note at this point it’s because they didn’t read the warnings and instructions. But it’s definitely because of an unknown condition related to something that the user installed, but rather to a kernel function that permanently corrupts the internal memory of the device. And it appeared for the first time on ICS ROMS from Samsung.
Well, as a reply to myself and as a note to anyone who owns a Galaxy Note: CM9 RC is rock-solid, much faster and smoother than stock, and it looks downright gorgeous. Truly a marvelous piece of work from all the CM development. There is a catch, though: there is no way of configuring the S Pen for left-handed use, it only works for right-handed people. I went to CM irc channel to ask if there are even any plans to add such support, but the answer was a no. Too bad, I had to revert back to stock
I posted a week or so ago about my experience with ICS on an Evo4g – running unofficial CM9-RC0 at that.
http://www.osnews.com/permalink?523363
TLDR I’m a fan. There’s also a rant about hardware drivers. Feel free to ignore that. 😉
No love for i9000
No need to wait.
There’s a huge array of CM derived ICS ports for i9000 [1].
I suggest you give’em a try. *
– Gilboa
[1] http://forum.xda-developers.com/forumdisplay.php?f=665
* I’m on the SGS2, so I can say that I tried any of them; However, both my SGS2 and my wife SE X8 use semi/half-derived CM ports (VK-ICS and GingerDX respectively) and the quality of both ROMs is top-notch.
Edited 2012-06-27 17:24 UTC
Works fine on my S2 with no, as of yet, issues.
The tethering through wifi issue that I had has also gone.
CM 7.2 goes stable.
CM 9.0 goes RC.
It’s enough to make me seriously consider the steps required to unlock the bootloader on my Xperia Pro (which Fido, in their infinite wisdom, has removed the ability to do).
Can anyone point me to a decent, well written guide to putting CM9 on an SGS2?
Thanks!
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_G…
Cheers. I’ll need to weigh up the pros and cons before I decide whether to actually go for it, but I’ll have a good look.
Thanks again.
you can get 50% of the way to an improved, customized state just by installing a new launcher. the next 25% comes from all the work and risk to install a new rom, and the next 25% comes from a custom kernel.
start with a new launcher and see if that satisfies you
Seconded. Switching to LauncherPro took the Motorola Admiral I tested from painful to pleasant to use. If it weren’t for the buggy dialer and texting on that device (which no launcher can fix), I might have kept it.
I did the same for my sister’s Nook Color once I put CM7 on it for her. The default launcher in CM7 is just too slow and crash-prone.
You can replace the dialer and texting apps just as easily as the launcher app.
Well as I found out the hard way, changing the dialer and texting “apps” really just changes the UI. The core software, where the crashes and bugs happen, is untouched without a complete ROM replacement.
Yeah, I’ve had an Android of one kind or another for a couple of years now and I’m a veteran of Launcher Pro and Go Launcher especially. Currently using Apex Launcher on my S2 and I can heartily recommend it to anyone with ICS on their phone.
https://play.google.com/store/apps/details?id=com.anddoes.launcher
thom, I think Sense or TouchWiz are mostly launcher changes, which arent really done by the custom roms. the CM9 launcher looks like like the normal one, and other roms use launchers that you can get from the app store.
These folks are almost doing the impossible. Pretty impressive work.
Even just the current stable version… but I don’t want to risk bricking my only phone, especially when I don’t have the money to get it replaced in case it does happen. A Google search brings up some help for my phone model (LG Optimus V), but the articles always seem to assume that you run Windows… and I don’t. Worse, they all seem to have different information–with some suggesting replacing the firmware just to “root” it.
Sounds a bit extreme to me, but then, I’ve only modded routers before. My WRT54GL was so much easier to learn to mod… information was the same everywhere. Make sure a wired connection is between the computer and router, login to router’s web admin page, upload firmware… wait and done. It’s running Tomato USB right now, and was running the original Tomato firmware for several years before it.
Edited 2012-06-27 21:46 UTC
1
Browser: Mozilla/4.0 (compatible; Synapse)