After Google dropped the L-bomb on Cyanogen, he reportedly opened up talks with the boys in Goo. It sounds like they may have finally reached a compromise in their little disagreement.
So the Cyanogen mod is back. It’s just slightly scaled down. Google didn’t like the fact that the mod builder was providing copies of their pre-made applications with his mod, so they made him remove them. Doesn’t make much sense really, since they come pre-installed in the actually Android phone. The mod builder has said that in order to install his mod in the future and still retain those applications, you’ll need to make a backup. And yeah, he’s working on a way to do that automatically.
In other words, if you want Gmail, GTalk, and Google sync, you’ll have to install the Cyanogen mod, and then reinstall those components. Not the most elegant solution, but it beats being shut down entirely.
So while Google might have been a little heavy handed in their approach, it sounds like the end result will be ok. We’ll just have to be patient and let things work themselves out.
[via Gizmodo]
Hmmm good..
Not exactly true.
You’re relying on dated information.
After Google dropped their little bombshell, it became apparent that proprietary drivers and such from HTC, Qualcomm and other providers are still a huge obstacle.
As such, Cyanogen seems a bit freaked-out (according to his Twitter posts). He’s gone from optimistic to downright pesimistic in the matter of just a few hours late this afternoon.
Apparently, he won’t be releasing anything until they come up with a way to legally do it right.
Is this the beginning of the end for xda? Where has HTC been all this time when chef’s were busy putting out thousands of roms for WinMo phones?
This is not a good sign.
How are the licenses of GTalk, Google Sync and Gmail offered/sold to the mobile makers?
Perhaps it’s an exclusive alliance perc thingy.
It’s gotta be substantial if Google feels a need to keep non-licensers from offering it just for show even if everyone knows it doesn’t matter in the end.
@rouel – I think there’s more to it than just the vagaries of licensing and/or inter-company politics.
Right up-front, there are liability issues. If a dev releases a glitchy ROM with faulty Google Apps, whose reputation is at risk? The guy running a mod server from his spare bedroom’s closet can get away with tweeting his regrets (’Whoops!’), but a big screw up or two could seriously affect adoption of the OS. Plus, for corporations, reputation ≈ stock valuation.
Likewise, god forbid one of the ROMs turns out to be malware. Who gets blamed (read: sued) if phones are bricked, accounts are hacked or phone systems are compromised? You figure the critics and lawyers will go after the small-time dev or the well-known company that boasts about free gourmet meals and day care?
Also, even if licensing was the bottom-line issue, there are some intangible subtexts…like corporate image. I think it is no coincidence that Google’s counsel sent a C&D only after the most recent cyanogen release. Look at the headlines it generated…
http://tinyurl.com/yh5q4ay
http://tinyurl.com/n9rfu7
http://tinyurl.com/yl9o9yv
http://tinyurl.com/mvovmt
Now, imagine Android Market is _your_ brand-new, unreleased app. (Remember, you’ve been reading stuff like this: http://tinyurl.com/y8qvfrk) How would you and your team feel, reading those cyanogen blurbs? How would your corporate partners and shareholders feel, not to forget your genuine licensees (in this or any other endeavor)? And how will you answer the inevitable questions they ask?
Meanwhile, I will happily go along with suggestions that Google could have done a better job of handling this. Appearances are important, when communicating with the faithful, especially in light of the whole ‘not evil’ thing. And who decided it was Ok to let the engineers issue ‘feel good’ statements, mid-crisis? I’m sure Mr. Morrill meant well, but his blog post (http://tinyurl.com/ycxkanu) reads like a treacly Xmas letter you might get from a dotty Lutheran aunt. ;)