CyanogenMod 9 Achieves Stable Release

← Back to Stories (view on slashdot.org)

CyanogenMod 9 Achieves Stable Release

Posted by Soulskill on Friday August 10, 2012 @10:22AM from the less-filling-tastes-great dept.

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.'"

75 comments

Min score:

Reason:

Sort:

Another terrible summary by Anonymous Coward · 2012-08-10 10:25 · Score: 0

What is CyanogenMod?
1. Re:Another terrible summary by esldude · 2012-08-10 10:29 · 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. Re:Another terrible summary by Anonymous Coward · 2012-08-11 04:10 · Score: 0
  
  You are right the summary was rushed and could have been better.
  And how is that different then the 99% of the stuff on slashdot? Even more so with the name 'Soulskill' or 'timothy' listed as 'editor'.
AOKP Is Better by ilikenwf · 2012-08-10 10:36 · 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 · 2012-08-10 11:50 · 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 · 2012-08-10 12:39 · 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 · 2012-08-10 13:42 · Score: 1
  
  Because he wasn't saying that CM shouldn't exist?
4. Re:AOKP Is Better by Anonymous Coward · 2012-08-10 23:35 · Score: 0
  
  Oh yeah, that's a great choice if you happen to HAVE 1 OF THE 2 DEVICES THEY SUPPORT.
  What are you, a shill for AOKP?
Nook? by wiegeabo · 2012-08-10 10:42 · 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 · 2012-08-10 11:01 · 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 · 2012-08-10 11:03 · 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 · 2012-08-10 11:22 · 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 · 2012-08-10 11:52 · 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 · 2012-08-10 13:50 · 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 · 2012-08-13 06:09 · 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)
I only recent dove into C9 by Anonymous Coward · 2012-08-10 11:10 · Score: 0

I only just flashed my HP Touchpad to Cyanogen 9 Sunday night, so I'm getting a big kick out of this news. Android is awesome.
1. Re:I only recent dove into C9 by poly_pusher · 2012-08-10 11:31 · 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.
2. Re:I only recent dove into C9 by Anonymous Coward · 2012-08-10 12:23 · Score: 0
  
  Be careful, CM9 "allegedly" (see CM forum) allows the battery to drain completely on the Touchpad (rather than recognizing low battery and shutting itself off).
  A Touchstone charger is apparently able to revive the TP after this happens, now you are warned to monitor the battery yourself and "not let it go too low".
Thank you! by rastoboy29 · 2012-08-10 11:35 · Score: 5, Insightful

Thank you Cyanogenmod guys for making our phones not suck. Seriously, I really appreciate it.

--
expandfairuse.org
1. Re:Thank you! by Anonymous Coward · 2012-08-12 21:17 · Score: 0
  
  I second this. My Galaxy S i9000 was abandoned by Samsung. If not for CM9 running perfectly on it (including the radio which other ROMs don't do very well in India), I would have had to buy a S2 or S3. Many thanks.
x86 port? by Eil · 2012-08-10 11:37 · 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 · 2012-08-10 11:55 · 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 · 2012-08-10 11:59 · 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 · 2012-08-10 14:33 · 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 · 2012-08-10 23:09 · 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.
Lack of non samsung support! by tnerb123 · 2012-08-10 12:01 · 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 · 2012-08-10 13:06 · 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 · 2012-08-10 13:21 · 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 · 2012-08-10 14:04 · 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 Anonymous Coward · 2012-08-10 17:00 · Score: 0
  
  The main CyanogenMod guy was hired by Samsung a while ago.
  He said it wouldn't change anything. Nobody believed him. Now look at the situation. Hmmm...
5. Re:Lack of non samsung support! by samoanbiscuit · 2012-08-10 17:24 · 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?
6. Re:Lack of non samsung support! by Anonymous Coward · 2012-08-10 20:37 · Score: 0
  
  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.
  CM didn't turn their back on anyone, they didn't have much choice but to drop devices.
  CM will only go stable for devices that are 100% (or near to it) working. My HP Touchpad still isn't stable due to the camera not working. Everything else is fine, and I've run it on the nightlys for months now. But until the camera issue is sorted (if it ever is), it will forever remain "unstable"
  Same with my ZTE Blade. Due to qualcomm not released updated drivers for it's chipset that can run on ARM v6, I'm "stuck" at CM 7.2. It's not CM's fault, as the lack of drivers and no documentation makes a big difference to video playback, and CM won't release a sucky version. It's no biggy though, I've just downloaded a ROM from elsewhere. YouTube HQ doesn't work, and it just generally screws up every now and then, but I've got ICS, which is a bit quicker in general use.
7. Re:Lack of non samsung support! by rtfa-troll · 2012-08-11 01:41 · 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();
8. Re:Lack of non samsung support! by Calos · 2012-08-11 03:57 · 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%
9. Re:Lack of non samsung support! by nighthawk243 · 2012-08-11 07:43 · Score: 1
  
  Yep. My Gnex is easy as hell to unlock
  
  Start phone in recovery, then open cmd and type "fastboot oem unlock".
Slightly Off topic by Anonymous Coward · 2012-08-10 12:02 · Score: 0, Offtopic

My wife has the trusty Google Nexus S (a great phone IMHO - and i'm an iPhone owner)... This morning, her Nexus S had a Jelly Bean update message. 10 minutes later - it was installed and running. After a few hours, all appears to be good. IMHO, the Nexus S is one hell of a phone - and I believe her Nexus 7 will prove to be just as kick-ass with its longevity and future updates.
Kudos to Google for a damn good job.
So I got CM9RC2 a few days ago... by f3rret · 2012-08-10 12:41 · 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 · 2012-08-10 13:45 · 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!
2. Re:So I got CM9RC2 a few days ago... by Anonymous Coward · 2012-08-10 18:11 · Score: 0
  
  You do realize that Android isn't just open source, but many of it's components are (easily) user replaceable.
  You can replace the lock screen (among other things) with applications you can find on the Play store, and even certain ROMs (TexasIce JB for Nexus One) has a little tool that lets you pick any of the previous lock screens -- all the way back from 1.5!
Yeah right by Anonymous Coward · 2012-08-10 12:49 · Score: 0

Me goes to cyanogenmod website. Check devices, click G2. "Stable" mod 7.2. "Experimental" mod 7.2. "Nightly" mod 7.2.
ICS? I don't think so.
1. Re:Yeah right by Anonymous Coward · 2012-08-10 14:09 · Score: 0
  
  http://forum.xda-developers.com/archive/index.php/t-1425324.html
I tried it... by EmagGeek · 2012-08-10 13:42 · 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.
The crack flashers moved to JB a long time ago by srwood · 2012-08-10 13:57 · Score: 0

Cyanogenmod used to be the shiz, now with the growth in the number of developers the Android world moved to Jelly Bean three months ago leaving CM in the dust.
1. Re:The crack flashers moved to JB a long time ago by Anonymous Coward · 2012-08-11 10:09 · Score: 0
  
  Do you have even the vestigial remains of a clue regarding what you are talking about?
Binary-only device drivers suck by Anonymous Coward · 2012-08-10 17:32 · Score: 0

No CyanogenMod 9/10 for my less than 2 year-old device. Manufacturers refuse to update to Ice Cream Sandwich/Jelly Bean, and refuse to release source code for their binary-only device drivers. CyanogenMod understandably won't support it with hacks. Makes my next decision easier: Nexus or nothing.
ORLY? Re:Lack of non samsung support! by mrmeval · 2012-08-10 17:36 · Score: 0

The Samscum Galaxy S aka Vibrant will not be getting support anytime soon as CM team never figured out how to get 911 working and samscum only supplies a binary blob driver. Samscum abandoned it when they decided it was too 'decrepit' to accept ICS when all they had to do was provide ICS without their crappy interface(s) like swype and the crapware they load on..

--
I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
1. Re:ORLY? Re:Lack of non samsung support! by Dot.Com.CEO · 2012-08-10 19:15 · Score: 2
  
  Samscum? Really?...
  
  --
  Mother is the best bet and don't let Satan draw you too fast.
2. Re:ORLY? Re:Lack of non samsung support! by Anonymous Coward · 2012-08-10 20:23 · Score: 0
  
  Samscum? Really?...
  Indeed.
  One day, society will grow up a little and not resort to petty name calling to make a point.
  Until then, we always have this comic to remind us of how little we have learned:
  http://penny-arcade.com/comic/2002/07/22
3. Re:ORLY? Re:Lack of non samsung support! by mrmeval · 2012-08-11 21:57 · 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
4. Re:ORLY? Re:Lack of non samsung support! by MrNiceguy_KS · 2012-08-13 01:54 · 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.
5. Re:ORLY? Re:Lack of non samsung support! by mrmeval · 2012-08-14 10:01 · 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
Which device for CyanogenMod? by rtfa-troll · 2012-08-10 20:00 · 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 Anonymous Coward · 2012-08-10 23:53 · Score: 0
  
  Good luck. About a year ago I was dazzled by all the shiny new things in Cyanogenmod and decided to make the switch because the phone I had at that time was on the "supported" list. That was the most painful experience I've ever been through, due to buggy software, unavailable software, and horrible performance problems with core functionality following the Cyanogenmod "upgrade". In the end I decided to just buy another identical phone from eBay and put the one that had Cyanogenmod on the shelf. I appreciate that Android offers more flexibility for developers to do things that iOS doesn't allow. Since that time I decided to just bite the bullet and give iOS/iPhone a try and you know what? Sure, there are a few nifty things I had on Android that I miss being able to have a bit more control over, but the overall experience is better on iPhone. Plenty of people love their androids and with good reason--it can be a great platform. This is just an anectdote of my experience with Cyanogenmod and why it was one factor that finally made me try the iPhone...and actually like it.
2. Re:Which device for CyanogenMod? by Anonymous Coward · 2012-08-11 01:29 · Score: 0
  
  just bite the bullet and give iOS/iPhone a try
  If I wanted an iOS device I would just buy one. In fact; I have. Whilst I don't use it much myself, it does what I expected. However, it's horribly limited in certain ways and I would like to have something more. Something in the direction of the Nokia N900 I used to have which was totally flexible; really powerful and a great tool to have for things that iOS is a total pain for. I want to have a more or less free device on which I know that the stuff that works is stuff that can't be taken away from me later and on which I can experiment with using things like remote shell commands.
  Your story; the fact that things end up a complicated mess if I go for locked in hardware; is precisely why I want to choose the hardware which gives the best, simplest CyanogenMod experience. If you have another alternate system (mer based?) that will do what I want, the please feel free to suggest. iOS doesn't suit for this need. If nothing else because I already have access to iOS and I'm looking for a system which fills in the holes in that.
3. Re:Which device for CyanogenMod? by cduffy · 2012-08-11 04:05 · 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.
4. Re:Which device for CyanogenMod? by nighthawk243 · 2012-08-11 08:11 · 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.
5. Re:Which device for CyanogenMod? by rtfa-troll · 2012-08-11 08:47 · 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();
6. Re:Which device for CyanogenMod? by Anonymous Coward · 2012-08-13 05:44 · Score: 0
  
  Android is still much better than any other mobile operating system out there even after using unofficial sources.
  You still can't find any app that will do what tasker can do on any other mobile operating system. Not from "unofficial sources" or from anywhere.
  I have to give the other mobile operating system adaptations out there some credit however. Software reliability is pretty decent.
  That company in canada which will remain nameless is also decent for software reliability. Not to mention hardware reliability and ruggedness.
  Ashame these other companies are firing employees left and right. Thats something i just won't support not on this planet not in this life.
  ps:
  With tasker on android and all the ports i can set things so when i turn my wireless headset on my wifi connection turns on, as well as any other radio I wish.
  Then when i turn my wireless headset off, all those radios turn off.
  Show me another mobile operating system or any software from another mobile operating system that will let me do that on their LATEST platforms.
  Here's the correct answer: You can't!
Good work. by Anonymous Coward · 2012-08-10 20:55 · Score: 0

Since I installed CyanogenMod on my ZTE Blade I can do anything with my phone! But it kernel panics when I try to call someone...
No Nexus 7? by Doc+Ruby · 2012-08-10 23:52 · 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 Anonymous Coward · 2012-08-11 00:42 · Score: 0
  
  Nexus 7 has Jelly Bean already... why would you want ICS?
2. Re:No Nexus 7? by Doc+Ruby · 2012-08-11 01:18 · Score: 1
  
  Root! I like my open source OS to be open, not just visible.
  
  --
  --
  make install -not war
3. Re:No Nexus 7? by Anonymous Coward · 2012-08-11 05:35 · Score: 0
  
  You can root JB with the stock ROM.
4. Re:No Nexus 7? by Ancantus · 2012-08-19 06:59 · 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
5. Re:No Nexus 7? by Doc+Ruby · 2012-08-19 09:41 · Score: 1
  
  What does it give you that the factory distro doesn't?
  
  --
  --
  make install -not war
6. Re:No Nexus 7? by Ancantus · 2012-08-20 03:19 · 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
CDMA phone support lacking? by Dr.Dubious+DDQ · 2012-08-11 00:36 · 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...

--
Hacker Public Radio is our Friend
1. Re:CDMA phone support lacking? by Anonymous Coward · 2012-08-11 05:38 · Score: 0
  
  Go to xda. Someone usually ports cyanogen to the phone. My tilt 2 had a cm port.
Re:Coward APK dishonors his family by Anonymous Coward · 2012-08-12 19:32 · Score: 0

shut up you illicit penis-licker.