Slashdot Mirror
Android Modder Tries To Outmaneuver Google
itwbennett writes "Google recently sent a cease-and-desist letter to Steve Kondik, the creator of Cyanogen, a popular souped-up version of Android, asking him to stop distributing applications such as Gmail with his modified software. 'We make some of these apps available to users of any Android-powered device via Android Market, and others are pre-installed on some phones through business deals,' wrote Dan Morrill on the Android developer blog. 'Either way, these apps aren't open source, and that's why they aren't included in the Android source code repository.' Now, Kondik thinks he's found a workaround. He plans to release a 'bare bones' version of Cyanogen without the applications, leaving it to modders to make a backup copy of the Google applications that shipped with their phone for later reinstallation before hacking away at the Android software. 'The idea is that you'll be able to Google-ify your CyanogenMod installation with the applications and files that shipped on your device already,' Kondik wrote."
This actually seems like a more-or-less legitimate point by Google. I'll probably get flamed for this, but it seems like people may have overreacted a little bit.
Google Cache
The current state..
The last few days have been difficult. What has become clear now is that the Android Open Source Project is a framework. It's licensed in such a way so that anyone can take it, modify it to their needs, and redistribute it as they please. Android belongs to everyone. This also means that big companies likes Google, HTC, Motorola, and whomever else can add their own pieces to it and share these pieces under whatever license they choose.
I've made lots of changes myself to the AOSP code, and added in code from lots of others. Building a better Droid, right?
The issue that's raised is the redistribution of Google's proprietary applications like Maps, GTalk, Market, and YouTube. These are not part of the open source project and are only part of "Google Experience" devices. They are Google's intellectual property and I intend to respect that. I will no longer be distributing these applications as part of CyanogenMod. But it's OK. None of the go-fast stuff that I do involves any of this stuff anyway. We need these applications though, because we all rely so heavily on their functionality. I'd love for Google to hand over the keys to the kingdom and let us all have it for free, but that's not going to happen. And who can blame them?
There are lots of things we can do as end-users and modders, though, without violating anyones rights. Most importantly, we are entitled to back up our software. Since I don't work with any of these closed source applications directly, what I intend to do is simply ship the next version of CyanogenMod as a "bare bones" ROM. You'll be able to make calls, MMS, take photos, etc. In order to get our beloved Google sync and applications back, you'll need to make a backup first. I'm working on an application that will do this for you.
The idea is that you'll be able to Google-ify your CyanogenMod installation, with the applications and files that shipped on YOUR device already. Or, you can just use the basic ROM if you want. It will be perfectly functional if you don't use the Google parts. I will include an alternative app store (SlideMe, or AndAppStore, not decided yet) with the basic ROM so that you can get your applications in case you don't have a Google Experience device.
I'll have more updates soon as I get all the code hammered out.
Thanks for all the support thru all of this.
This entry was posted on September 27, 2009, 9:41 am and is filed under Home.
This is not a work around. He will comply with Google's wishes and most everyone will be more or less happy. Google keeps their proprietary apps available for license and he gets to have his distro without having to pay for a distribution license.
A compromise that is win-win all around.
There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
I have a rooted G1 and use Cyanogenmod: it provides several enhancements, such as root, which allows for Wifi/bluetooth based tethering. It is also somewhat more responsive and quicker than the official firmware. It does have less battery life, and can be less stable then the official version however. While it is true that Android is open source, Android without many of the base apps such as Gmail/Google maps is not particularly useful. Still though, this won't prevent me, and other users from using this mod. And since I paid for the phone, and by extension, the applications that came with the phone, I should be able to transfer them to a new operating system on the same phone.
It isn't outmaneuvering, I'm sure this is what Google had in mind. No licenses being broken, and a strong modder community.
I don't think that's actually true.
I think this solves their complaint, this means that the code is being left with the end user, and is not being distributed by them.
Curiosity was framed; ignorance killed the cat. -- Author unknown
I love my Android G1 (with Cyanogen's Mod). But Google is not Android, nor vice versa. Google created Android, and then spun it off to the Open Handset Alliance (OHA).
This means that Google is now an application developer for Android, just like any other application developer. Android supports competitive markets (and there are at least 3 Android markets out there). Gmail isn't the only email interface, Google Maps is not the only maps interface.
I love my Android phone, but I don't love the Google apps -- they're too intrusive. I'd love a Google-less G1, and I'm down for trying the new mod without the Google apps if it will work fine.
Again, Google is not Android. Android is Android, maintained by the Open Handset Alliance. Cyanogen might be wiser to join the OHA, actually, and license the apps if he wants them.
The WINE and ReactOS projects don't provide MS Office, IE or Media Player. FPGB (http://games.slashdot.org/story/09/09/29/0516251/Gameboy-Color-Boot-ROM-Dumped-After-10-Years) doesn't provide GameBoy cartridges. MAME makes you responsible for finding your own ROMs. Et cetera, etc.
Nothing for 6-digit uids?
Android is an open source operating system. But not all apps that run on it are open source. How is that a "dirty little secret"? Google never claimed anything different.
This is essentially how it works on any platform you're hacking. You can release all the open-source bits, modifications, and instructions you want (modified roms, killhdinitrd, dsmos), but the minute you combine that with proprietary software (Google Apps, Tivo software, Mac OS X DVD's), you're in hot water. So the usual result is anyone who wants to remain legitimate distributes only the modifications, and allows users to bring in the proprietary bits themselves. It's worked well, and keeps everything legally clean. Perhaps a little more work for the end user, but hacking has never been point-and-click.
Tivo hacking, Mac OS X hacking, now GooglePhone hacking. No different.
I don't know what kind of crack I was on, but I suspect it was decaf.
If you download the sdk they have an emulator.
Heck - Windows doesn't provide MS Office.
My HTC Touch Pro2 ships with Windows Mobile, Office Mobile, IE Mobile, and Windows Media Player. I went to the XDA Developers forum and downloaded a cooked ROM containing Windows Mobile, Office Mobile, IE Mobile, and Windows Media Player. An Android ROM customizer gets a cease-and-decist from Google. To my knowledge, no Windows Mobile ROM customizer has gotten a C&D from Microsoft. I'm no Microsoft fanboi, but I *am* confused as to why Google would raise a stink over their product being distributed in such a way that it will ONLY be useful on devices that already came with the software. It's not like he lifted it from an Android handset and is selling it in the App Store or even ported it to the iPhone and is giving it away for free on Cydia or something like that. I guess I just don't understand how being distributed on cooked ROMs that only work on handsets that originally came with the code and will only be used by a subset of Android owners is going to harm Google.
This isn't an "outmaneuver", it's precisely the right thing to do. It's no different from other open source projects with closed source components, like emulators that require a ROM image to function, or the Second Life client that requires proprietary Vivox components for voice.
WINE and ReactOS aren't redistributions of Windows.
This is more like if MS told people making Windows XP slimming programs to not distribute Calculator with their mods because MS owns Calculator.
Of course, you can't redistribute Windows like that, where you can Android.
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
There's the Zii Egg...
In the case of any "open source" based device what is going to happen is the manufacturers learn quickly that some portion of the user community will do completely unexpected things with the device and the software on it. Often, this will violate various agreements, including potentially trade agreements governing the use of the device in places. This is especially true with cell phones - wouldn't you like to have a cell phone that **ALWAYS** gets a channel rather than competing with other phones in your area? Nevermind that the tower owner might not like this hack, there is little that can be done to stop it, especially with a more "open" phone.
The other thing that is expected - and is clearly happening - is people get confused about licensing and what is and what is not free to redistribute. The end result is again, there is no control over content. In this case the developer/distributor decided to comply with Google's request. They could have just as easily said bugger off, and if they were in a non-compliant country there would be little Google could do about it. And that is assuming they could find the person at all.
Sure, it looks obvious to manufacturers that an "open" device might be cheaper to start with. But there are other costs that are just beginning to become apparent. Most of these are mitigated by locking down the device so it might have "open" roots but is unmodifyable. As in the case of things like Tivo, Archos, Kindle, etc. the manufacturers have done quite a bit to ensure this sort of problem doesn't come up. Unfortunately, what we are going to see with "popular" devices is they will get pried open, exposed, hacked, and proprietary content redistributed and modified.
I'm just waiting for the first person that figures out a way to use the cell service with a Kindle for some other purpose. Something that costs Sprint enough that they want to cancel their agreement with Amazon. Something that doesn't involve destroying the Kindle to rip the cell modem out.
There are a few technical pieces missing from the comments here, and this story is still definitely developing. From Cyanogen's twitter feed today: "This is about proprietary device drivers and not Google at this point. These drivers are not redistributable."
This is a nice reminder that there's likely no building a usable phone room without infringing on some agreements. I do not expect this to change in the near future; what this means is that a sort of 'merge' or 'overwrite' or patch system will need to be put in place for people modding their phones.
This will take a little time to build would be my guess, but isn't insurmountable; I think the complexity of building such a thing should fit inside of the typical hacker attention span that's been piqued right now.
IWell there's the android netbook, the Acer Aspire One D250m, so I can't imagine an android-does-ipod-touch will be far behind.
He just said he didn't need a phone.
The N810 isn't a phone. The upcoming N900 is, however.
"Complying with demands" is not "outmaneuvering".
http://www.wired.com/gadgetlab/2009/09/google-cracks-down-on-android-developer/
"The Android engineers at Google are now making available previously unreleased components â" makefiles and configuration files â" that will give independent developers the ability to create Android releases in the same manner that Google does, but without using Googleâ(TM)s proprietary apps. These engineers are working with volunteers from the community and have already begun working on alternatives to the proprietary Google applications."
It doesn't sound as contentious as the OP but it definitely seems like Google is taking the right tact on this to me.