Linked by Thom Holwerda on Wed 27th Nov 2013 23:23 UTC, submitted by Hiev
Google

Google has asked the CyanogenMod team to remove their installer application from the Google Play Store. All the application did was help users enable ADB on their Android device, so that the desktop side of the installer could take over and load the CM ROM onto the device.

After reaching out to the Play team, their feedback was that though application itself is harmless, and not actually in violation of their Terms of Service, since it 'encourages users to void their warranty', it would not be allowed to remain in the store.

While Google does have somewhat of a point - somewhat, somewhere, hidden deep inside - this is just entirely needless. I'm probably overly paranoid, but what are the chances that Samsung Google's OEM partners applied some pressure? CM is insanely popular, and once you have a taste of proper, crapware, TouchWiz-less Android, you don't want to go back.

Thread beginning with comment 577648
To read all comments associated with this story, please click here.
There are consequences
by wocowboy on Thu 28th Nov 2013 12:30 UTC
wocowboy
Member since:
2006-06-01

There are other "side effects" to installing CM or any other third-party ROM other than voiding the warranty on one's phone. Some of a phone's very important basic functionality may be missing or not work at all. I put CM 10.2 on my AT&T GS3 SGH I747, and while I really enjoy not having Samsung's bloat/crap-ware, I have no LTE functionality. The phone will not access AT&T's LTE network, and evidently the only way to bring that back is to put the stock ROM back on the phone. You can't change any setting anywhere to make the thing access LTE. Nowhere in CM's documentation does it warn you about that little missing feature. So I can see why Google is doing this, they don't want customers to be surprised and find that a major part of their phone no longer works.

Edited 2013-11-28 12:33 UTC

Reply Score: 7

RE: There are consequences
by The1stImmortal on Sat 30th Nov 2013 11:31 in reply to "There are consequences"
The1stImmortal Member since:
2005-10-20

I put CM 10.2 on my AT&T GS3 SGH I747, and while I really enjoy not having Samsung's bloat/crap-ware, I have no LTE functionality. [...] Nowhere in CM's documentation does it warn you about that little missing feature.


There's no current "stable" version of CM 10.2 for the AT&T GS3. There is a release candidate as of a week ago, for which the warning is "Last builds before stable release, few minor issues, mostly stable and safe for daily use" (emphasis added). Prior to that there was only Nightly and Milestone releases and they're both basically "Hey if it works for you, great!".

I have no idea if LTE works on the AT&T GS3 CM 10.1 stable builds or not - I'm in AU (so no AT&T model) and don't have a 4G capable GS3 available to test.

Also - given radio/smartphone interaction is goverened by very proprietary interfaces and libraries - this doesn't really surprise me. There's a host of regulatory and industry limitations around this area that we'd all be better off for them going away.

Reply Parent Score: 1