41–50 of 77 posts
Don'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.
It 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.
What are you referring to? I consistently find that the functionality is much better than the vanilla ROMs.
I've been running the first nightly build of JellyBean for months now (it's not even a release candidate) and I've noticed almost no issues. It's easy to forget that I'm not running the standard Android experience!
That's really nice, but I don't think I'll be touching anything until this page is completed: http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S_III_(Veriz... It just freaks me out to follow directions found on some random forum.
It 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.
I agree. For a long time Samsung Captivate users like me were stuck with CM7. By some miracle the Captivate is supported by CM10, so I'm very excited to try it. There are other ROMs out there though. Part of the fun of flashing new ROMs is to try out the lesser known ones. There are still a lot of developers who support the older models. To your philosophical point, I completely agree. New phones are pushed so freque…
Being a cynic though, I feel that a lot of phones coming out having nothing to do with technology upgrades but instead have more to do with sustaining or growing revenue streams. Some of the iPhone upgrades have been so incremental yet so many people can't live without the newest one, even though they couldn't necessarily tell you what is new about it. I feel this way about vehicles too. Yes the styling changes, in the last couple of years fleet fuel economy has improved, and yes maybe the hp/lb (W/kg) have improved but fundamentally they are the same thing.
I still have my cappy not because there aren't newer and better phones out but because with a good rom it runs great, even though phones have been coming out for 2 years since. How hard has everyone had to twist samsung's arm to release software upgrades for their devices? I don't think it really comes down to money between the carriers and the phone makers but instead they see it as a threat. If everyone had the latest and greatest rom they would find their hardware still runs well for much longer than the average person holds on to their phone. It is simply controlled obsolescence. I am really, REALLY, happy that someone worked hard to build CM10 for the cappy as I can continue to use my perfectly good hardware for a long time.
That's really nice, but I don't think I'll be touching anything until this page is completed: http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S_III_(Veriz... It just freaks me out to follow directions found on some random forum.
Earlier quoted context omitted.
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.
Eh? The device was supported at one time. Ubuntu doesn't say "too bad, we no longer own any six year old Thinkpad T60's" when they release a new version. They simply leave the drivers for such devices, make changes that aren't expected to break specific hardware models, and get some stablish prereleases so they can take the occasional bug report for the leaky abstractions that did break. Contrast to Google who AFAIK…
It's not a huge problem because new x86-based computers still have to run Windows XP (they can probably run MS-DOS too) and, therefore, cannot be that much different from the six year old Thhinkpad of your example.
Earlier quoted context omitted.
You are fully welcome to contribute. CM isn't a commercial product, it lives because of its volunteers. You don't need to be a coder to help out. You can help out with documentation, helping people in the #cyanogenmod IRC channel, etc. These jobs free up CM developer time so they can work on code.
It would be in manufacturers interest to sponsor CM. It may even work out cheaper that maintaining their possibly less-competent/more-expensive in house teams.
It 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.
> reduced and clunky functionality What are you referring to? I consistently find that the functionality is much better than the vanilla ROMs. I've been running the first nightly build of JellyBean for months now (it's not even a release candidate) and I've noticed almost no issues. It's easy to forget that I'm not running the standard Android experience!
Earlier quoted context omitted.
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
Earlier quoted context omitted.
You're not listening. Linux on the PC works on pretty much any computer because Intel eradicated the competition . If you buy a new computer, you're almost certainly running an Intel chipset with an Intel CPU, and probably Intel graphics, NIC, etc. That makes supporting the Linux kernel for computers relatively trivial. This is not the case with mobile. You have dozens of CPU variants for each generation . Nevermind…
No, I've been listening. It's just that nobody has been making any actual points besides 'stfu'. So thank you for bringing the discussion back to technicals. Your point re: Intel peripherals is true today, but wasn't really true ten years ago. It's also a bit hard to talk about the Linux kernel today, as there is obviously a lot of money and other support such that every little piece is fully tended to by someone. So…