CyanogenMod 10.0 Release
cyanogenmod.org
CyanogenMod 10.0 Release
1–10 of 77 posts
Re: CyanogenMod 10.0 Release
#2Don't care, I have a Nexus4 being delivered and won't ever have to install Cyanogen again! (I know its a little bit different but still I won't bother).
Re: CyanogenMod 10.0 Release
#3Cool. May even make the switch before long as I am still waiting for Samsung to release JB on the Galaxy Note.
Re: CyanogenMod 10.0 Release
#4Don't care, I have a Nexus4 being delivered and won't ever have to install Cyanogen again! (I know its a little bit different but still I won't bother).
a) What does it have to do with this post?
b) Google doesn't provide updates for Nexus phones indefinitely.
Re: CyanogenMod 10.0 Release
#5Don't care, I have a Nexus4 being delivered and won't ever have to install Cyanogen again! (I know its a little bit different but still I won't bother).
a) What does it have to do with this post? b) Google doesn't provide updates for Nexus phones indefinitely.
Cyanogenmod also provides many features that aren't found in the stock ROMs, like the option to modify what on-screen buttons are available, modifications to the lock screen and home screen launcher, etc
Re: CyanogenMod 10.0 Release
#6It really irks me that there are no builds for older devices. What is the point of installing CM and putting up with reduced and clunky functionality, just to be left by the wayside for updates? I don't know if this is due to CM or Google itself running amok on the upstream tree, but a philosophy that considers a two year old device obsolete is utterly preposterous.
Re: CyanogenMod 10.0 Release
#7Don't care, I have a Nexus4 being delivered and won't ever have to install Cyanogen again! (I know its a little bit different but still I won't bother).
cm > stock android, that's been my experience. When I got my Galaxy Nexus, I was on cm within 2 weeks.
Re: CyanogenMod 10.0 Release
#8It really irks me that there are no builds for older devices. What is the point of installing CM and putting up with reduced and clunky functionality, just to be left by the wayside for updates? I don't know if this is due to CM or Google itself running amok on the upstream tree, but a philosophy that considers a two year old device obsolete is utterly preposterous.
Unofficial ports will happen. CM can only fully support devices where there is at least one developer who owns the device and is willing to do the work. All their work is in the open. Just the same as any other open source project: if you want it, you need to do some work or pay someone to do it for you.
Re: CyanogenMod 10.0 Release
#9A few months ago I was about to get rid of my quite old Galaxy Vibrant, so with nothing to lose I installed CyanogenMod on it. It's worked so well I'm keeping it as my main phone for now - it's clean, stable, and looks much nicer than the Samsung ROM. The only downside is significantly reduced battery life, but I can live with that for now.
Will definitely be trying CM10 if it's supported for the Vibrant.
Re: CyanogenMod 10.0 Release
#10Don't care, I have a Nexus4 being delivered and won't ever have to install Cyanogen again! (I know its a little bit different but still I won't bother).
cm > stock android, that's been my experience. When I got my Galaxy Nexus, I was on cm within 2 weeks.
I have to agree. I had CM7 on my atrix and it saved my phone. I was this close "_" to getting rid of my phone because I was frustrated with the stock OS. CM7 fixed that, and gave my phone the last few months I needed out of it.
I just got the note 2 (which is dead sexy btw), and I"m going to hold off on custom roms until I get annoyed with the stock setup(ie, 2 weeks:) ). Happy to see that CM10 is kicking ass.