4 ms·
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 b
by mindslight 14y ago
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.
- dsr_ 14y agoUnofficial 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.
- mindslight 14y agoEh? 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 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.
- andybak 14y agoUbuntu is a commercial venture. It pays people salaries. You do the same to someone working on a CM ROM for your phone and I'm sure your request will be granted.
- mindslight 14y agoI only picked Ubuntu for a timely example. This philosophy has applied to the Linux kernel and Linux distributions for at least the past 15 years.
- beagle3 14y agoSo, because Linux distribution packagers have been able to provide you with free timely updates, you expect Cyanogen team to do so too? Why do you think you deserve anything?
- maratd 14y agoYou'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 the unique brew of components that goes into every different model even from the same manufacturer. Every phone needs at least one developer who spends his time maintaining the kernel and drivers for that phone for each and every update. Now, follow along. Developers are nerds. Nerds like new and shiny things. The probability of any developer sticking around with an old phone is zero. Hence, no updates. If this is a problem, learn how to code and keep your obsolete hardware working. Nobody owes you anything. It's up to you. The cyanogenmod project doesn't maintain any phones. They just help organize various developers who are interested in specific phones and combine their work into a cohesive product. No interest in a phone? No release for that phone.
- rplnt 14y agoThe Intel CPU with AMD64 instruction set :)
- mindslight 14y agoNo, 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 my real question is why do the old drivers have to leave the tree or at least become perma deprecated? Is there that many breaking interface changes for which drivers cannot be mostly mechanically updated? I know this is a problem that the kernel devs managed just fine over the years (sure there's been individual broken drivers accompanying major changes, but there's a big difference between saying 'the latest kernel breaks your network card' and indefinitely unsupporting your entire computer. Maybe I'm just looking at the wrong level of CM publishes (just the releases) and hence I'm out of touch on the actual status of "unsupported" workings on various devices. And sheesh, the alleged entitlement is the same as with any open source project - I put my faith in the project and would like to continue doing so. I'm not asking for them to conjure up someone to magically do extra work to support my device, I'm asking why they don't change their process such that this extra work is unnecessary in the first place.
- omnisci 14y agoLast I checked, CM was free, done by the work of volunteers. Sooooooo, yeah. Either help (if you have the knowledge) or don't complain about it. I'm not trying to be a dick here, but come on, it's free! Don't look a gift ROM in the mouth.
- deleted 14y ago[deleted]
- rbanffy 14y ago> Ubuntu doesn't say "too bad, we no longer own any six year old Thinkpad T60's" when they release a new version. 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.
- mindslight 14y agoBut we're talking about source compatibility, not binary compatibility. So getting around the quirks of the old devices is an already solved problem, even if it needs to be #ifdef'd out for the newer devices. The problem isn't technical, it's a philosophy that treats every device as an opaque special case, rather than factoring out the common parts and abstracting out the differences. Of course the incidental complexity continues to pile up. I've got 18 years of experience running Linux, compiling my own kernel and packages on a Slackware base up until 2002 or so. In that time I also did embedded design and development for about five years, using cp/zip/email as the ultimate revision control. I know the two philosophies pretty damn well, and I'm unequivocally stating that Android and CM are being run as embedded development projects, where code flexibility and maintainability take a back seat to just making working blobs for specific device configurations. This is ridiculous for what purports to be an open source OS running on a computer roughly equivalent to a desktop PC circa 2000. But alas, I'm being downvoted into oblivion by non-technical fanboys who probably think that flashing a phone is a highly technical activity, rather than just annoyance due to manufacturer obfuscation (this isn't you - which is why I'm replying to your comment. it's general frustration with the non-thinking HN masses these days). The incidental complexity from the non-scalable development philosophy has built up so much that most people are incapable of even seeing my simple point. So then, I'm out. I'll keep dreaming of being in a place where I'd have the time to dedicate to making an actual open source user-centric mobile OS to run on mass market hardware. Android will make a great Windows XP.
- CJefferson 14y agoNo, sorry. You are wrong. Every phone is a horrible special case, and those #ifdefs do not simply map forward from one version of the OS to another, unlike on a PC where a single set of drivers will get most computers to a basic working state. More importantly, how do you suggest they debug? When a phone OS is incorrectly configured, the most likely behaviour is simply hanging with a black screen. Distributing such releases would be worse than useless. If you want to put in the work to make CM work on your device, there are plenty of people who would help you.
- carlob 14y agoThere have been unofficial CM10 builds for other devices before the first official ones started. I'm running a fairly stable one on my HTC for daily use.
- bullwinkle12 14y agoI 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 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.
- rbanffy 14y ago> By some miracle the Captivate is supported by CM10 It's no miracle. A generous, competent and unpaid volunteer decided to build the support for the Captivate. If your device is not supported, you are free to download the source and fix whatever breaks yourself or pay for someone else to do it.
- dmritard96 14y ago"rapid increase in technology plays a major role" some of this is true. For instance the difference between each iteration of the galaxy series seems to come with substantial hardware improvements. 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.
- runjake 14y agoYou 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.
- shimon_e 14y agoIt 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.
- runjake 14y agoYou're likely under the mistaken assumption that the customer in this equation is the consumer, but you would be incorrect. The customer in this equation are the carriers. And CM doesn't really benefit them.
- anonymouz 14y agoOthers have already said that it's a community project and so YMMV with respect to older phones. I have a Samsung Galaxy S (the first one). Since this phone has quite a following I got very lucky: CM has continuously been releasing updates for it, even though it's a very old phone by todays standards. I've been using CM7 on it, now have CM9 installed and am in the progress of upgrading to CM10. CyanogenMod's support for this phone has been awesome.
- stefantalpalaru 14y agoI run CM9 on the same model but I'm reluctant to upgrade on account of the 100+ open issues on the bug tracker[1] and the forum feed-back[2]. I guess I'll wait a little longer. [1]: http://code.google.com/p/sgscm10/issues/list http://code.google.com/p/sgscm10/issues/list [2]: http://forum.xda-developers.com/showthread.php?t=1778526 http://forum.xda-developers.com/showthread.php?t=1778526
- codelust 14y agoBeen on the CM10 nightlies ever since they started coming out for the SGS. If you are upgrading from CM9, be warned that you will wind up with a new partition layout and new user data by the time you're done with the upgrade. Till recently, it was pretty stable and a brilliant release. There was some issue that led to awful battery drain as I kept progressing through the daily builds in the past few weeks. Resolved it by going through a full wipe than just cache wipes. My phone is 2-years-old now and it has been a good run. For its ruggedness (multiple and frequent drops, couple of dunks in water, clumsy usage), I just don't want to give it up, but it seems like they may have trouble doing CM11 on it. Do turn off zRAM in the performance options for better stability.
- chimeracoder 14y ago> 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!
- mindslight 14y agoJust various little things that are off - general laggier response than sense rom, a text message along with every voicemail, odd power management with the screen not turning on when it's supposed to, lack of FM radio, etc. All little niggling things that I've been willing to put up with for an immature project with a solid foundation, with the expectation that it will mature into something greater.
- josegonzalez 14y agoAre you sure you're using the actual official CM release, or just an unofficial port? I have no problems on my Galaxy S2 (T-Mobile even!) even remotely similar to yours.