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."
Enchantments? iOS doesn't have that. Android rules.
i'm concerned about bugs, intentional or not, that would allow someone access to my voice calls or other personal data... how feasible are those situations when using one of these 3rd party mobile operating systems rather than the one supplied directly by the mobile vendor with the device?
As a Droid Incredible owner, I'm pretty pissed off that Android 2.2 is so many months old and there's STILL no official build available for my device. Why can't I just go to a magic URL like google.com/android/2.2, then download a supported ROM for my device, and then install the new OS just like downloading a new version of Ubuntu for a PC?
You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
I have been wishing for OpenVPN support on my iPhone for some time now. The idea that you'll 'control your whole life' through your phone is so hollow until you have 'secure' tunnels to your resources. The person who put the effort in to get OpenVPN working on android has my respect. Good work!
So why should they build, test and support new roms for every different Android device out there? They've got enough on their plate developing the reference OS itself. You should be asking Verizon, or at least HTC.
With Ubuntu, a lot of people chipped in to write and make available many different device drivers so that a huge range of hardware could be supported. Phones too require different device drivers - but on phones, many of those drivers are still proprietary. Cyanogen (among others) is the best recourse we've got.
But for actual solutions - well, you could insist on buying only phones with minimal vendor changes from vanilla Android, thus reducing the amount of work needed for porting the latest OS. Vendors could devote more effort to supporting older hardware, since it's clear it's a big issue with customers. From Google's pov, they've said they're working on separating as much as possible from the base OS, so that the cooler stuff can be updated independently.
Only other "solution" I can think of is for Google to hold off releasing new versions until major vendors complete porting it to their older hardware. But all that would do is disadvantage Google's own customers to no purpose, just so that other vendors' customers don't know what they're missing, not to mention reducing the valuable feedback Google needs to work on the next version. Might as well go to an annual cycle and change their name to Apple 2.0.
Why would anyone engrave "Elbereth"?
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.
The proper response to that is of course to advertise widely and loudly which phones are locked down, and which aren't. People who want an open system will buy the unlocked phones, and those manufacturers will be rewarded with extra sales.
I really don't see the point for manufacturers to lock their phones like this. For networks, I can understand, but when I buy a phone without a contract, I should own it, without any limitations. If we want high-end, fully unlocked/unlockable phones, we need to make sure there's a market for them. Manufacturers would be stupid to deny that market.
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?).
Has anyone managed to, or even bothered to try to put a full linux distro on any of these instead of android?
I know the debian chroot thing has been around for a while, but I'd really love to be able to put debian or maemo or something like that onto another handset.
I love my N900, but there are newer, shinier toys out there but I like my mainstream mobile linux...
The Android open source community is fucking awesome.
Thank you.
After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
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.
None of that is neccesary. For a while I dispaired that Google was going the way of Apple, but they have since worked with Cyanogen and released all the apps as a seperate installable .zip file. The only difference is that you need to flash two zips instead of 1.
A company working WITH a mod guy to solve his problems and let him do his thing!? What is the world coming to.
I've tried a million different ROMs, and Cyanogen is teh BOM in my opinion. I've still got an old Magic (Sapphire, G2, or whatever they keep naming the same device), and every time a new version of Cyanogen comes out it's like getting a new handset.
It's awesome. ;-)