Slashdot Mirror
Android Fork Brings Froyo To 12 Smartphones
jj110888 writes "CyanogenMod has just been updated to version 6.0, bringing Android Open Source Project 2.2 (Froyo) to several devices. This fork includes enchantments to many of the built-in apps, Ad-hoc network connectivity, OpenVPN support, Bluetooth HID, Incognito browsing, extensive control over audio and UI elements, and more found in the extensive CHANGELOG. The CyanogenMod team uses an instance of Google's gerrit tool for code review and patch submission, helping make this former backport of Android 1.6 to T-Mobile's G1 into thriving development for the G1/MyTouch/MyTouch 1.2, Droid, Nexus One, HTC Aria, HTC Desire, HTC Evo 4G (minus 4G and HDMI output), Droid Incredible, and MyTouch Slide. HTC Hero (including Droid Eris) are coming soon for 6.0, with Samsung Galaxy S devices expected to be supported in 6.1."
review.cyanogenmod.com
They end up patching most vulnerabilities faster than the handset makers, but there is always the chance of users not understanding root and not reading the permissions their apps require. One of the many good things about android though is that it shows you what the app wants wants before installing, if you don't read/know what you're installing, who's really to blame at that point?
Mine just came OTA (over the air) last night. Or you can do a manual update as shown here: http://www.droid-life.com/2010/08/31/manual-update-droid-incredible-to-android-2-2/
Well, yes, if you go check the release notes it'll tell you exactly what doesn't work. It'll be a small list. On current version I think there's a bug that occasionally prevents phone from sleeping, draining battery. It'll be fixed.
CM ROMs do NOT include Sense UI -they are "clean" Android. Personally I like Sense, which is why I'm using the AuraxTSense 7.1 ROM from XDA Devs on my HTC Desire. It's lovely. Now the CM code is out, they basically set a gold-standard baseline for others to tinker with.
Seriously, the community ROMs tend to be more stable than the OEM ones - and they fix bugs, rather than ignore them.
You shouldn't really talk when you obviously don't know anything about the subject of conversation. The number of phones that Cyanogen supports is not "dwindling" it is actually booming. Up through CM 5.0 he only supported 3 phones (G1, MyTouch, Nexus one) but with the development of 6.0 he recruited rom developers for all the other phones listed above. This just happened a few months ago and this article is discussing the fruits of their labor. Additionally, the encrypted bootloader you were mentioning on the Droid X/2 has been broken and full custom roms can be installed http://www.engadget.com/2010/08/30/custom-droid-x-roms-starting-to-break-loose-efuse-be-damned/. Really, try to lighted up with FUD and do some more reading before you decide the whole modding community is dwindling and doomed.
Wow. You should really inform yourself better before telling other people they're spreading FUD - and I'd recommend looking for information in places OTHER than blogs.
The Droid X and Droid 2 bootloaders have NOT been cracked, they're still encrypted, keeping you from booting a kernel such as the one included in Cyanogenmod. While read/write access to the system partition and a working recovery are a good step in the right direction, Droid X/2 development is stuck at exactly the same spot where Milestone modders have been stuck for the better part of a year now.
True custom ROMs like Cyanogenmod are NOT possible without bootloader access!
The FUD about the Droid X having been cracked wide open is pretty much what blogs like Droid Life have been spreading all over the internet, and it's just wrong. No custom kernel, no custom ROM. You can heavily modify the existing ROMs, but you MUST keep the kernel that Motorola signed for your device. Note that the developers who made Clockworkmod on the Droid X possible state explicitly that ROMs with custom kernels aren't possible with their recovery...
Remember the Milestone alarm-clock fiasco? The phone would just not wake up properly when it was time to sound an alarm, resulting in the phone being completely useless as an alarm clock. This was a kernel bug that was left unfixed for MONTHs, until the .36 bugfix release of Android 2.1 was pushed just weeks ago... the only way to fix it was by flashing a different kernel. Luckily it was discovered that the Telus version of 2.1 didn't have this bug, and that the kernel from that version could be flashed onto any Milestone due to them all using the same signature. With full bootloader access, custom kernels without this bug (like they've been available for the bootloader-unlocked Droid all along) would have been usable right away, and the problem would have been fixed by the community more or less right away.
And that's just one example of why it's important to have full bootloader access for flashing custom kernels. There are many more... like being able to create a ROM like CyanogenMod for the device. Many of the tweaks built into Cyanogenmod are kernel-level changes, and while you may be able to get somewhere by loading kernel modules at runtime (like the overclocking module for the Milestone), you'll have a tough time replicating all the functions of a full custom kernel that way.
Like I probably mentioned in my earlier post, even HTC is moving in this direction (albeit slowly), with some sort of runtime-protection of the system partition that's apparently uncrackable so far on the Desire and IIRC some other phones too (Legend?).
Correct, they don't include Google Apps as part of the ROM.
They are distributed separately
Download, and flash in the same way as the ROM. No hassles at all.