11–20 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).
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.
To your philosophical point, I completely agree. New phones are pushed so frequently that devices become obsolete quickly. I mean, my Captivate was the first Samsung Galaxy, and now we're on the 3rd iteration already, and it's only been two years. While, I always get excited for new gadgets, the lack of support for anything over a year old is unacceptable. Few people have the inclination or money to buy a new phone so frequently. I'm not sure who to blame, but the rapid increase in technology plays a major role.
I'm assuming people here know a bit more about this than I do, so I'll ask. Why is CM still a 3rd party developer? I'm curious as to why Google/Samsung/Motorola etc hasn't bought them out and applied their talent to make the stock setup better? Honestly, I'd much rather buy a "XYZ phone, CyanogenMod version" over to the stock Touchwiz/SenseUI etc front end. Excuse my ignorance if this is a dumb question.
A 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.
I'm assuming people here know a bit more about this than I do, so I'll ask. Why is CM still a 3rd party developer? I'm curious as to why Google/Samsung/Motorola etc hasn't bought them out and applied their talent to make the stock setup better? Honestly, I'd much rather buy a "XYZ phone, CyanogenMod version" over to the stock Touchwiz/SenseUI etc front end. Excuse my ignorance if this is a dumb question.
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.
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.
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).
The Nexus S won't be getting Android 4.2 without going the Cyanogen route. So even with Nexus phones you still have to chose between buying a new phone every 2 years, not having the latest version of Android or installing Cyanogenmod.
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.
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.
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 throws globs of code over the wall with all of the support for older devices ripped out. And then CM presumably uses that tree as a starting point to make changes, instead of merging into a master CM tree.
CM might just be doing the best they can to cope with Google's broken process, but the whole philosophy of brittle trees tailored for specific devices is the philosophy of embedded development, not open source. So CM comes off as aiming to be the latest eye candy fluff mod for tinkerers, rather than a solid computing base for your phone.
I'm assuming people here know a bit more about this than I do, so I'll ask. Why is CM still a 3rd party developer? I'm curious as to why Google/Samsung/Motorola etc hasn't bought them out and applied their talent to make the stock setup better? Honestly, I'd much rather buy a "XYZ phone, CyanogenMod version" over to the stock Touchwiz/SenseUI etc front end. Excuse my ignorance if this is a dumb question.
Not a dumb question. Samsung hired, Steve Kondik, CM's lead developer in 2011. I'm not sure I've seen how this has affected Samsung, but I haven't really paid to much attention to their newer phones. Still, we won't ever see a CM phone by Samsung. Although I agree, that it would be preferred to any TouchWiz phone. http://www.theverge.com/2011/08/15/samsung-hires-cyanogenmod...
Thanks for the answers and I'm happy to see that samsung did that. I know for a fact, that if I was a company and someone was making MY product better....for free, that I'd be offering them a job. That is the kind of employee I want in house, self motivated and creative.