CyanogenMod 9 is stable; 10 is underway
Tonight’s release is for the majority of our [Ice Cream Sandwich] 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." The Jelly Bean source code release forms the basis for the ongoing CM 10 work.
Posted Aug 10, 2012 16:13 UTC (Fri)
by kragil (guest, #34373)
[Link] (19 responses)
Posted Aug 10, 2012 16:46 UTC (Fri)
by servilio-ap (subscriber, #56287)
[Link] (18 responses)
Not even in nightlies? I have been running nightlies in the HP Touch for months and it has been very stable (for the features that work, that is).
>, but is it true that it lost the ability to remove permissions from apps?
Yes, that is lost.
Posted Aug 10, 2012 16:55 UTC (Fri)
by josh (subscriber, #17465)
[Link] (17 responses)
Posted Aug 10, 2012 17:37 UTC (Fri)
by servilio-ap (subscriber, #56287)
[Link] (15 responses)
http://forum.cyanogenmod.com/topic/44589-combining-cyanog...
It is not clear if the decision was to take out the permission management altogether when the powers that be weighted in on the issue.
Also found a couple of G+ posts where people ask about this but haven't got any answer, e.g.:
https://plus.google.com/117962666888533781522/posts/LtbxP...
I wonder if something like is what transpired with WhisperCore:
http://www.whispersys.com/whispercore.html
It was developed by the same people behind RedPhone and TextSecure.
There are alternatives, like PDroid, but it would be most useful if at least permission management was included out of the box, putting control back in the hands of the user.
Posted Aug 10, 2012 19:46 UTC (Fri)
by sb (subscriber, #191)
[Link] (14 responses)
Posted Aug 10, 2012 19:48 UTC (Fri)
by drag (guest, #31333)
[Link] (11 responses)
Posted Aug 10, 2012 21:03 UTC (Fri)
by cmccabe (guest, #60281)
[Link] (7 responses)
When you host something on an FTP server, it's usually because you have some relationship with the admins of that server. You can't get binaries up on ftp.kernel.org without talking to the kernel.org people. Whereas if you use megaupload or one of the thousand other file lockers, all it proves is that you know how to wait 15 seconds and click through some HTML forms.
I realize there are exceptions to these generalizations-- for example, the lwn.net web forum is one. Google+ seems to be another bright spot in the sea of mediocre web 2.0 walled gardens. But in general, there is a reason why mailing lists and ftp are preferred.
Posted Aug 10, 2012 22:58 UTC (Fri)
by ldarby (guest, #41318)
[Link] (6 responses)
The FTP protocol needs to die already, it's nearly 30 years old and has various problems with NAT and a terrible latency that HTTP simply does not have. On that point, those random filesharing sites that make you wait need to die as well!
Posted Aug 10, 2012 23:43 UTC (Fri)
by ldarby (guest, #41318)
[Link] (5 responses)
ROM = Read Only Memory = Semiconductor hardware that stores information which cannot under any circumstances be modified.
Using "ROM" to refer to an operating system (or more generally, a set of software) that can be installed into re-writeable memory, is just bizarre...
Posted Aug 13, 2012 18:26 UTC (Mon)
by Nico57 (subscriber, #63763)
[Link] (4 responses)
"Image" sounds even more confusing. :)
Posted Aug 13, 2012 19:46 UTC (Mon)
by ldarby (guest, #41318)
[Link] (3 responses)
Image (ISO) => CDR(W)
How much sense does burning a CDROM to a CDRW make? The same amount as flashing a ROM to a phone.
"EEPROM Image" would be correct and I wouldn't be surprised if that's what it actually was, and then instantly got abbreviated to just ROM, because no one would want to say "ee-ee-prom image". Pretty much like almost no one wants to say "Guh-nooo-linux" - too many syllables.
Posted Aug 13, 2012 20:17 UTC (Mon)
by nybble41 (subscriber, #55106)
[Link]
Of course, Android is nominally open source, so it shouldn't be necessary to mess with binary-level modifications. However, the fact that one can't actually build the unabridged equivalent of the Android system image shipping on any real hardware from just the published source code means that we are still at least partly at the "mod" stage rather than "distributions". Android has quite a bit of maturing to do to catch up with Linux on that front.
Posted Aug 14, 2012 8:02 UTC (Tue)
by mastro (guest, #72665)
[Link] (1 responses)
Posted Aug 14, 2012 17:37 UTC (Tue)
by Jonno (subscriber, #49613)
[Link]
That said, calling an RFS-image a "ROM" is really just legacy terminology, carried over to a replacement technology. Much like the term "broadband" is used to denote all fast network connections, even those not utilizing a broad frequency band...
Posted Aug 10, 2012 21:05 UTC (Fri)
by faramir (subscriber, #2327)
[Link]
Posted Aug 10, 2012 22:17 UTC (Fri)
by job (guest, #670)
[Link] (1 responses)
Also: if someone who is actually a real known person participating a discussion produces software I might consider looking at it or even installing it. If thed00d at hotmail does the same, then not so much.
Posted Aug 13, 2012 21:02 UTC (Mon)
by drag (guest, #31333)
[Link]
It's not much harder to purchase a random domain name and put a ftp server on some home cable TV connection. That is the sort of thing that was extremely common for years and years in Linux. It doesn't provide any sort of additional assurances or security beyond what a http link to 'megaupload.com' or whatever does.
> Also: if someone who is actually a real known person participating a discussion produces software I might consider looking at it or even installing it. If thed00d at hotmail does the same, then not so much.
Whatever. They are no more 'not anonymous' then 90% of 'old school' open source programmers out there.
fundamentally you are (and other people) complaining about here problem is the lack of maturity regarding the infrastructure that the new wave of developers are bringing in from experiences alien from your own. Whether you are aware of it or not, it doesn't matter. It is effectively a generation gap.
As projects mature so will the infrastructure they use.
If you wait around to get involved then it will just be that much more painful to try to convince these people to adopt practices that traditional OSS developers have developed over the past 20 or 30 years.
Posted Aug 10, 2012 21:42 UTC (Fri)
by clump (subscriber, #27801)
[Link]
Posted Aug 11, 2012 22:15 UTC (Sat)
by mfuzzey (subscriber, #57966)
[Link]
Posted Aug 10, 2012 17:50 UTC (Fri)
by servilio-ap (subscriber, #56287)
[Link]
http://news.ncsu.edu/releases/wms-jiang-tissa/
But the researchers haven't released the source for it.
Posted Aug 10, 2012 17:10 UTC (Fri)
by leoc (guest, #39773)
[Link] (6 responses)
Posted Aug 10, 2012 17:23 UTC (Fri)
by faramir (subscriber, #2327)
[Link] (3 responses)
1. Binary drivers - so can't upgrade to more recent kernel which ICS uses by default.
In some sense #1 is actually a #3. Theoretically, people could reverse engineer the binary drivers/write wrappers/etc...
Can anyone speak to the possible explanations above?
Posted Aug 10, 2012 17:37 UTC (Fri)
by JoeF (guest, #4486)
[Link] (2 responses)
Posted Aug 10, 2012 19:36 UTC (Fri)
by drag (guest, #31333)
[Link]
Posted Aug 10, 2012 20:41 UTC (Fri)
by yokem_55 (subscriber, #10498)
[Link]
Now in my experience on my original Droid Incredible, ICS does work pretty well, and I haven't come across any explicit compatibility problems, but I suspect that withholding official CM9 support from that class of devices is warranted.
Posted Aug 10, 2012 17:31 UTC (Fri)
by JoeF (guest, #4486)
[Link]
Posted Aug 13, 2012 6:11 UTC (Mon)
by Seegras (guest, #20463)
[Link]
So yes, "not supported" can very much mean "works, but it's less than enjoyable".
Posted Aug 10, 2012 17:17 UTC (Fri)
by job (guest, #670)
[Link] (3 responses)
Posted Aug 10, 2012 19:16 UTC (Fri)
by ldarby (guest, #41318)
[Link]
Posted Aug 11, 2012 4:02 UTC (Sat)
by keeperofdakeys (guest, #82635)
[Link] (1 responses)
Besides allowing easy updating, an inbuilt update manager should allow you to download deltas of the system, so you don't have to download a new 100MB image everytime you update.
Posted Aug 13, 2012 8:55 UTC (Mon)
by job (guest, #670)
[Link]
Posted Aug 10, 2012 18:22 UTC (Fri)
by jonabbey (guest, #2736)
[Link]
Posted Aug 10, 2012 20:12 UTC (Fri)
by tonyblackwell (guest, #43641)
[Link] (4 responses)
Posted Aug 10, 2012 21:06 UTC (Fri)
by drag (guest, #31333)
[Link]
Besides having a 'default' Android experience you do end up with some special features and other things that Cyanogenmod enables.
Also as it's hinted to above, if you have a popular model that is well supported by Cyanogenmod then you can depend on them to produce updates for your OS so that you don't have to depend on your carrioer or phone manufacturer. Even if Cyanogenmod drops official support you can still get hacks and more independently minded variations to install on your phone.
If your in the USA, or other country with a like minded populace, and you choose to purchase a subsidized phone with carrier-branded OS then there is no question about the superiority of Cyanogenmod. No question at all.
Posted Aug 10, 2012 22:21 UTC (Fri)
by donbarry (guest, #10485)
[Link] (2 responses)
That said, I'm rather disappointed that they did not make some effort to return some control to the user: not only is the ability to edit app permissions lost, but once a google account is attached, it is impossible to add device-local contacts (i.e., only cloud contacts can be entered).
One must wonder whether Kondik getting a job at Samsung has altered his allegiances.. He did fight against providing anonymizing data in a patch submission for CM7 -- because it would "piss off" carriers/Google. Well isn't the point that the device should serve *us*? If such a move caused pushback, then it would certainly reveal how these companies actually regard us -- the buyers of their hardware, but to them mere slaves and acolytes.
Posted Aug 11, 2012 1:03 UTC (Sat)
by rich0 (guest, #55509)
[Link] (1 responses)
I don't think it is a conspiracy or anything, but I think you basically are hitting at the issue. Those with the strongest desires to contribute to android are also those most likely to seek employment in this area, and that means they don't want to tick off those who benefit from the revenue model.
The other issue is that the strongest contributors get quite a bit in the way of donations, which means they tend to have shiny new hardware, which means they tend not to spend as much time on older handsets as they used to.
I won't begrudge these people their day jobs - their work on Android is a donation of time and I can't really call them "traitors" for wanting employment. That said, forks that add in the features users like would be desirable. There is no reason somebody can't just maintain some patches and just parallel the CM releases. Then again, solutions like LBE Privacy Guard also work and are about as effective, but require less device-specific work to implement.
Posted Aug 13, 2012 9:29 UTC (Mon)
by micka (subscriber, #38720)
[Link]
I didn't find much information on it, as for most apps it has a market page, and the rest is in chinese, so : is it free software ?
Posted Aug 10, 2012 20:15 UTC (Fri)
by rknight (subscriber, #26792)
[Link]
CyanogenMod 9 is stable; 10 is underway
If so I wouldn't be as sad, because I love that feature.
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
So "ROM" is not all that wrong.
You could go for "system image", "system archive" or simply "system update", but ROM tends to be the most universally understood and less ambiguous term.
CyanogenMod 9 is stable; 10 is underway
Image (software) => Phone with EEPROM
CyanogenMod 9 is stable; 10 is underway
s/EEPROM/Flash/
s/EEPROM/Flash/
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
One very disappointing bit of news is that now even Cyanogen is dumping support for the Nexus One and other older handsets past 7.2. This is one area where Android differs significantly from most Linux distributions, which generally support computers older than two years pretty well.
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
2. Hardware performance - not enough RAM/CPU power to run the code
3. Human bandwidth - not enough people on team to manage that many devices
CyanogenMod 9 is stable; 10 is underway
You need to repartition the internal flash, because ICS requires more space. That can scare some people. And that may mean moving apps to the sdcard. I use S2E with an ext4 partition on the external micro-sd.
And the N1 doesn't have things like the near field sensor.
But once the internal flash is repartitioned, CM9 works just fine on the N1. The inofficial builds just don't have the official CyanogenMod blessings.
And there are also inofficial JB/CM10 ROMs, but they are still considered alpha.
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
I run one of them (SpazeDog, formerly BCM) just fine.
CyanogenMod 9 is stable; 10 is underway
For the wishlist: an upgrade tool
For the wishlist: an upgrade tool
For the wishlist: an upgrade tool
For the wishlist: an upgrade tool
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway
CyanogenMod 9 is stable; 10 is underway