When Google started hurling lawyerisms at the maker of the souped-up, stripped-down Cyanogen custom Android ROMs, the outlook was pretty grim. Luckily for Android hackers, Cyanogen and Google have reached an agreeable, albeit still stupid, compromise.
The issue Google takes with CyanogenMod isn't that it fundamentally changes Android—they're generally open to that, seeing as it's an open source project and all—but that the custom ROMs contain binaries of Google proprietary applications, like Maps, Talk and Gmail. Of course, this is a technicality, because the devices Cyanogen writes his customs ROMs for all ship with these apps in the first place. That's why Google's cease and desist spree seemed so silly, but also why it'll be so easy to legally circumvent. From Cyanogen:
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.
I mean, I'm glad this won't amount to more than a small bump in the road for Cyanogen, but what exactly did Google accomplish here, aside from some hilariously bad PR?
UPDATE: A lot of folks in the comments are emphasizing that Google has good reason to uphold their copyright, if not just for precedent. That makes sense. What doesn't make sense, though, is why, given that they're so willing to communicate and cooperate with Cyanogen now, Google didn't just open a discussion in the first place, instead of sending him Cease and Desist letters. That was the bad PR. Discuss! [Cyanogen via Lifehacker]