Slashdot Mirror


CyanogenMod 9 Achieves Stable Release

New submitter jolle sends word that stable builds for CyanogenMod 9 rolled out to their servers last night, supporting a wide range of devices. Downloads here. From their announcement: "[This] release is for the majority of our ICS supported devices, the stragglers will catch up, and we will leave the door open for merging in additional devices from maintainers, external and internal. The team itself, will focus solely on Jelly Bean and maintenance of the CM 7 codebase. Many have wondered why we bothered to finish CM 9 when we are already active in CM 10 development. To that, our answer is: we don't like to leave things incomplete. There is no profit gained from what we do, so the satisfaction of completing a goal is our only reward. This release also serves as a release suitable for the masses, especially those who won't have 100% functioning releases of CM 10 immediately or are averse to anything branded as 'preview', 'alpha', 'beta' or 'nightly.'"

44 of 75 comments (clear)

  1. Re:Another terrible summary by esldude · · Score: 5, Informative

    You are right the summary was rushed and could have been better. If you don't know what CyanogenMod is, it is an alternate open sourced ROM for Android devices. Phones and tablets can have this replace the stock ROM getting you more control over your device, and some alternate features. Often glitchy Android devices with propietary ROMs work better with this CyanogenMod.

  2. AOKP Is Better by ilikenwf · · Score: 3, Interesting

    AOKP tends to be more polished/slick it seems. I realize there's Liquid, etc, but I've tried several roms including CM on my touchpad, Droid2, and VZW Nexus, and I always come back to AOKP.

    AOKP

    1. Re:AOKP Is Better by Anonymous Coward · · Score: 1

      Having more choices is always better than anything else - and infinitely better than shiny toys.

      Instead of starting a pissing contest, why not enjoy the choices you have?

    2. Re:AOKP Is Better by Roujo · · Score: 2

      AOKP is based (at least in part) on the CM code. They'd be doing something wrong if the end product was worse. =P

    3. Re:AOKP Is Better by Desler · · Score: 1

      Because he wasn't saying that CM shouldn't exist?

  3. Nook? by wiegeabo · · Score: 1

    I don't see Nook in the list. Although their site says other devices may come later.

    Anyone else see something specific about the Nook?

    1. Re:Nook? by SScorpio · · Score: 1

      The Nook doesn't have any experimental or nightly builds of CM9. Thus it's not support. Not all devices that are support by CM7 are being supported by CM9.

    2. Re:Nook? by TheGratefulNet · · Score: 1

      if you mean nook color (NC) then it does work with cm9. not great (tried it a few weeks ago, was unusable) but maybe its going to be worth going to soon.

      cm7 is great but the preview of cm9 was better. but it HAS to be as stable as cm7 is on the NC before I'll spend any more time on it.

      --

      --
      "It is now safe to switch off your computer."
    3. Re:Nook? by bill_mcgonigle · · Score: 2

      There's never going to be a stable cm9 for Nook Color. cm10 is already more stable than cm9 on it, so that's where all the developers went. As far as I know they've thrown code over the wall but nobody has built zips yet.

      There's supposedly a debian vm you can get with most of the bits installed to build it. Why nobody's done that and then synced the resultant images to an FTP site, I'm not clear on (so there must be more to it than that, right?)

      Anyway, use cm7 or self-build cm10 now for Nook Color.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    4. Re:Nook? by ChunderDownunder · · Score: 1

      Yep, some devices on CM 7.2 will skip ICS and go directly to Jelly Bean. e.g. my phone, a moto defy, has CM10 nightlies. RAM consumption and wifi connection are flakey, so I'll stick with Gingerbread stable for the time being.

      Whether the CM10 release is finished on such devices before Google release the next shiny code drop is an open question.

    5. Re:Nook? by nurb432 · · Score: 1

      Odd, my NT is running non-release CM9. It has been for a couple of weeks now at least.

      Unless he meant the NC, then i cant say anything intelligent as i don't have one so never cared to look into it.

      Or perhaps the NST... 'nook' is a family of devices..

      --
      ---- Booth was a patriot ----
    6. Re:Nook? by bill_mcgonigle · · Score: 1

      Whether the CM10 release is finished on such devices before Google release the next shiny code drop is an open question.

      Indeed! I think in the case of my device, the issue is more that Jelly Bean has a 3.x kernel with the OMAP support it needs, vs. a bunch of stuff that was backported to 2.6.32 and attempts to forward port that to 3.0 were not entirely successful by the community.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  4. Re:I only recent dove into C9 by poly_pusher · · Score: 1

    I've been very happy with CM9 on my Touchpad. You chose a good time to flash it. Early in the year I was paying close attention to their progress. It was very exciting when custom kernels and user performance improvements were frequently being released but that stuff has slowed quite a bit. I just updated my CM9 install after about 3 or 4 months and the latest releases are pretty awesome. I also have installed cm9 on my Droid 3 but that project seems to have died.

  5. Thank you! by rastoboy29 · · Score: 5, Insightful

    Thank you Cyanogenmod guys for making our phones not suck.

    Seriously, I really appreciate it.

  6. x86 port? by Eil · · Score: 2

    Seeing as Android is open source, are there any x86 ports of CyanogenMod? Even for just running in a VM like VirtualBox? Seems like having such a thing would at least increase user/developer interest.

    I know there have been some x86 ports of Android, but those have either been for very specific hardware (e.g., a certain model of netbook) or poorly maintained.

    1. Re:x86 port? by Anonymous Coward · · Score: 1

      Android/CM9 will always be hardware dependent. Hence the list of devices. CM developers/geeks/nerds pick their favorite devices and make CM9 work on them. CM does not automatically just work on all/every android device - due to difference in hardware/drivers/locked-unlocked bootloader etc.

      So, it's natural x86 ports will again be hardware specific.

      It's not magic bullet (but it's close).

    2. Re:x86 port? by ilikenwf · · Score: 2

      ...although, porting isn't that difficult if the device specific stuff is out there for the version of android the build is based on. That said, I'm pretty sure x86 is one of the build targets, in a qemu image.

      I think you'll be able to google and find premade VM's of x86 android. It does exist, and I'm not sure but I think it does for CM as well.

    3. Re:x86 port? by dns_server · · Score: 2

      If all you want to do is play around with a vm running android just download the official android sdk.
      This contains vm's to run android and is released ahead of the source code and any devices hitting the market.

    4. Re:x86 port? by gl4ss · · Score: 1

      http://www.android-x86.org/releases/releasenote-4-0-rc2

      says that they don't have ethernet for 4.0.. that's kinda bad. you could run the sdk emulators though, but they suck big time in performance..

      --
      world was created 5 seconds before this post as it is.
  7. Lack of non samsung support! by tnerb123 · · Score: 2, Insightful

    Cyanogenmod is great. But they have turned there back on the phones that started it all. A lot of phones have version 9 but they are totally unsupported versions. Its to bad because its a great ROM. It also looks like they sold out to Samsung. They seem to support even samsungs older phones which are worse off then some of there unsupported phones!

    1. Re:Lack of non samsung support! by diego.viola · · Score: 1

      It's open source so you can still help add support to the phones that are currently supported and contribute back no?

    2. Re:Lack of non samsung support! by jrumney · · Score: 2

      It also looks like they sold out to Samsung. They seem to support even samsungs older phones which are worse off then some of there unsupported phones!

      Samsung gives good support to third party developers, so their phones are well supported in return. Rather than blaming the Cyanogenmod developers for your device manufacturer's lack of support, and tossing out accusations of "sell-out", perhaps you would be better directing your anger at the device manufacturer that does not release specs or full source for their customized Android build.

    3. Re:Lack of non samsung support! by Grishnakh · · Score: 3, Informative

      I can't speak to Samsung specifically, but one of the problems with Android, compared to regular Linux (and this is also true for many embedded versions of ARM Linux), is that a lot of the device drivers are not open-sourced. And a lot of the others may be open-source, but haven't been merged into the mainline kernel, so they only work with specific kernel versions. So if a phone maker doesn't release their drivers as open-source, then porting a different CM/Android version to their phone may be impossible or extremely difficult.

    4. Re:Lack of non samsung support! by samoanbiscuit · · Score: 4, Insightful

      They didn't sell out to Samsung. Samsung rather, has reached out to them repeatedly, in order that it's phones run CM well. They even hired the lead dev last I heard. Why don't you ask your phone manufacturer to provide free devices and hire devs the way Samsung does?

    5. Re:Lack of non samsung support! by rtfa-troll · · Score: 1

      Sure; except none of us actually know what our manufacturers are doing. Some of the "supported" phones seem to have been completely hacked together in the face of total resistance from the manufacturer whilst other phones (HTC??) seem to have co-operative manufacturers but just bad luck. If the someone from Cyanogenmod side would tell us which manufacturers were co-operating and helpful, even better if broken down by individual phone, then we would be able to write off and complain to the manufactures that aren't helping whilst buying from the other ones. As it is "we" outside the community have no clue whether they have been cooperative or not.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    6. Re:Lack of non samsung support! by Calos · · Score: 1

      Easy, buy from the Nexus line :)

      Otherwise, Googling can tell you, but it can be painful. However note that Samsung did hire Cyanogen himself.

      --
      I vote based on politicians' actions, unless contrary to my preconceptions. Often wrong, never uncertain. #iamthe99%
    7. Re:Lack of non samsung support! by nighthawk243 · · Score: 1

      Yep. My Gnex is easy as hell to unlock

      Start phone in recovery, then open cmd and type "fastboot oem unlock".

  8. So I got CM9RC2 a few days ago... by f3rret · · Score: 1

    Well here's my impression, it's alright.

    Here's what annoys me - Lock screen: Old CM7 had the 'ok' button in the bottom left corner, now it is in the right, screws up my muscle memory. I end up typing in my lock screen PIN and hitting 0 instead of OK, very annoying.
    The same thing goes with the 'accept' call slider, before you had to move the slider to the left to accept a call, now you have to slide it to the right. Can't tell how many times I've accidentally hung up on someone calling me because I reflexively move the slider to the left.

    Other than that, no issues with the thing, it does seem very, very blue though. Like literally blue, the color, there's a lot of it.

    --
    Admit nothing. Deny Everything. Make Counter-accusations.
    1. Re:So I got CM9RC2 a few days ago... by brentrad · · Score: 1

      Those are all changes that Google implemented in ICS. My stock Galaxy Nexus behaves just like that. And yes, there's a lot of blue. :) Once I got used to it, I quite like it myself!

  9. I tried it... by EmagGeek · · Score: 1

    It's "ok." It's still not stable, but it's a good effort. I'll try it again in a few weeks, but the current build still crashes on my HTC.

  10. Re:ORLY? Re:Lack of non samsung support! by Dot.Com.CEO · · Score: 2

    Samscum? Really?...

    --
    Mother is the best bet and don't let Satan draw you too fast.
  11. Which device for CyanogenMod? by rtfa-troll · · Score: 1

    Okay, I want to buy a device for CyanogenMod. I don't want the hassle of jailbreaking and I want to know for sure that it will keep working even if I try an upgraded manufacturer's ROM. The official supported device list doesn't say anything. The install instructions all start with "now root your phone". How can I find out a list of recommended phones including information about how easy the install is?

    --
    =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    1. Re:Which device for CyanogenMod? by cduffy · · Score: 1

      Okay, I want to buy a device for CyanogenMod. I don't want the hassle of jailbreaking and I want to know for sure that it will keep working even if I try an upgraded manufacturer's ROM.

      Buy a Nexus-series device from Google. "Jailbreaking" those is a matter of running an official, vendor-supported tool (which tells you that you're voiding all vendor support on the software stack) -- however, they also can be reverted back to stock vendor ROMs, which Google has for download.

    2. Re:Which device for CyanogenMod? by nighthawk243 · · Score: 1

      If you want to run anything other than the stock ROM, you're going to need to root the phone. Even a developer oriented phone such as the Galaxy Nexus requires that you root/unlock the boot loader to flash a new ROM. If you're in IT, you've probably been able to follow directions to some extent; there are a plethora of them online. I'd say the easiest phone to unlock/root is the Galaxy Nexus since it is a developer phone and isn't heavily locked down like some (*cough*Motorola*cough*) are.

      CM and AOKP are NOT supported by any manufacturer, so you will never receive them as an official OTA update.

    3. Re:Which device for CyanogenMod? by rtfa-troll · · Score: 1

      If you want to run anything other than the stock ROM, you're going to need to root the phone. Even a developer oriented phone such as the Galaxy Nexus requires that you root/unlock the boot loader to flash a new ROM.

      Thanks for your comments. Based on this and other comments I will probably go for a Nexus 7 and put CM10 on it. I have no problem "rooting" the phone by an officially supported mechanism such as a bootloader. What I don't want to know about is using a security flaw to root things. That's something that can a) just go away at any time and b) is illegal in some places. If I got the phone for free I might consider that, but I'm never going to give money to someone who's forcing me to break the law.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  12. No Nexus 7? by Doc+Ruby · · Score: 1

    I'm surprised Nexus 7 isn't supported. There are tables, but only the Advent Vega, Nook Color and HP Touchpad.

    --

    --
    make install -not war

    1. Re:No Nexus 7? by Doc+Ruby · · Score: 1

      Root! I like my open source OS to be open, not just visible.

      --

      --
      make install -not war

    2. Re:No Nexus 7? by Ancantus · · Score: 1

      Typing this right now on a rooted CM10 Nexus 7. It may not be supported (give them time) but it works quite well.

      --
      Violence is the last refuge of the incompetent. -- Isaac Asimov
    3. Re:No Nexus 7? by Doc+Ruby · · Score: 1

      What does it give you that the factory distro doesn't?

      --

      --
      make install -not war

    4. Re:No Nexus 7? by Ancantus · · Score: 1

      Not much at the moment, just some extra settings (and I am not an expert, this is my first android device with CM). I wanted it just to give it a try, and I am intending on custom compiling it at some point to try and play around with some kernel features.

      But from what I have seen, its really surprisingly stable. I have not had any issues so far.

      --
      Violence is the last refuge of the incompetent. -- Isaac Asimov
  13. CDMA phone support lacking? by Dr.Dubious+DDQ · · Score: 1

    I'm likely going to be switching from T-Mobile to US Cellular (due to coverage issues where I live now), and am seriously disappointed to see that their phones are all apparently unsupported (except for one discontinued older model, the "Samsung Mesmerize"). The CDMA versions of the Galaxy S II and S III seem to be excluded.

    Anybody know if any of US Cellular's phones are likely to see support any time soon? After years of happy Cyanogenmod at T-Mobile I'd really hate to be stuck with a manufacturer "skin" version again...

  14. Re:ORLY? Re:Lack of non samsung support! by mrmeval · · Score: 1

    Yes. I've been calling them that since the 90s.

    --
    I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
  15. Re:ORLY? Re:Lack of non samsung support! by MrNiceguy_KS · · Score: 1

    ... all they had to do was provide ICS without their crappy interface(s) like swype and the crapware they load on..

    I've got a Samsung Epic - the Galaxy S with a slide-out keyboard. I'll agree with you about the bundled crapware and their Touchwiz interface, (or whatever it's called). But Swype is simply awesome.

    Currently running ICS, and one of the first things I did after flashing was install Swype.

    --
    Redundancy is good And also good.
  16. Re:ORLY? Re:Lack of non samsung support! by mrmeval · · Score: 1

    The major problem with anything over 2.2 is 911 calling which is sporadic at best. If there were open hardware specs on the radio or S* would at least compile the driver for some flavor of ICS it would fix that issue.

    --
    I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty