Arthur Posted November 28, 2013 Posted November 28, 2013 Too many newbies bricking their phones I guess? CyanogenMod Installer Application Removed from Play Store Today, we were contacted by the Google Play Support team to say that our CyanogenMod Installer application is in violation of Google Play’s developer terms. They advised us to voluntarily remove the application, or they would be forced to remove it administratively. We have complied with their wishes while we wait for a more favorable resolution. To those unfamiliar with the application, it has a single function – to guide users to enable “ADB”, a built in development and debugging tool, and then navigates the user to the desktop installer. The desktop application then performs the installation of the CyanogenMod on their Android device. After reaching out to the Play team, their feedback was that though application itself is harmless, since it ‘encourages users to void their warranty’, it would not be allowed to remain in the store. We’ve seen hundreds of thousands of installations of the application, proving the demand for more choice, and that the need for an alternative Android experience exists. As we work through this new hurdle, we will continue to make available and support the installation process via our own hosting services. Fortunately, Android is open enough that devices allow for installing applications via ‘Unknown Sources’ (i.e. sideload). Though it’s a hassle and adds steps to the process, this does allow us a path forward, outside of the Play Store itself. The application can be found via the Get Started link on CyanogenMod.org. In addition to ‘sideloading’, we are submitting the application to the Amazon and Samsung app-stores. CyanogenMod Installer Removed From Play Store At Google's Insistence, Still Available For Sideloading [update: CM Installer Is Now Open Source] « Android Police
gtg93 Posted November 28, 2013 Posted November 28, 2013 I thought that it had been decided that flashing custom ROMs didn't void warranty in the US and EU, as long as it could be proven the software didn't cause the fault?
Arthur Posted November 28, 2013 Posted November 28, 2013 That's what I was thinking too. However, the situation is a bit different in the US where Cyanogen, Inc. are based.
gtg93 Posted November 28, 2013 Posted November 28, 2013 Surely just ban it from the US store then. Or even better, don't ban it - if Google are still aiming for Android to be an open platform, surely it's in their best interest to allow items such as this, that they can see is beneficial to some users, so just add a "WARNING: THIS MAY REMOVE YOUR WARRANTY" disclaimer...
Garacesh Posted November 28, 2013 Posted November 28, 2013 But installing CyanogenMod would overwrite all those nice little bits of code sending back your details
X-13 Posted November 28, 2013 Posted November 28, 2013 People complain about it being bloated, but again you have the option to disable apps. Not all apps, in fact I think you can't disable anything Samsung force installs. There's a load of stuff on my S4 that auto-runs but I have no option to disable it.
Arthur Posted November 28, 2013 Posted November 28, 2013 if Google are still aiming for Android to be an open platform, surely it's in their best interest to allow items such as this Google are trying to make (AOSP) Android as unappealing as possible without their proprietary apps. Google’s iron grip on Android: Controlling open source by any means necessary « Ars Technica
creese Posted November 28, 2013 Posted November 28, 2013 I used this last night, on a friend's S4. I also used it last week to Mod my Nexus 4
Danp Posted November 28, 2013 Posted November 28, 2013 Not all apps, in fact I think you can't disable anything Samsung force installs. There's a load of stuff on my S4 that auto-runs but I have no option to disable it. I do think there is a difference between Samsung and HTC, on my One with Sense I can disable any app I want.
Garacesh Posted November 28, 2013 Posted November 28, 2013 Not all apps, in fact I think you can't disable anything Samsung force installs. There's a load of stuff on my S4 that auto-runs but I have no option to disable it. Same for my XPeria. Some stock apps can be disabled, but not all of them.
sparkeh Posted November 28, 2013 Posted November 28, 2013 Same for my XPeria. Some stock apps can be disabled, but not all of them. That's why I rooted mine and got rid of the cruft. Phone works so much better now without crappy Facebook apps running when I don't even have a FB account.
X-13 Posted November 28, 2013 Posted November 28, 2013 That's why I rooted mine and got rid of the cruft. Phone works so much better now without crappy Facebook apps running when I don't even have a FB account. I rooted and flashed my Galaxy S, my battery doesn't even last a day now...
Garacesh Posted November 28, 2013 Posted November 28, 2013 That's why I rooted mine and got rid of the cruft. Phone works so much better now without crappy Facebook apps running when I don't even have a FB account. Workin' on it, but the phone has to be unlocked before you can get into the bootloader (at least, according to the guides I read) and EE won't give me the unlock code 'til 6 months into the contract.
sparkeh Posted November 28, 2013 Posted November 28, 2013 Workin' on it, but the phone has to be unlocked before you can get into the bootloader (at least, according to the guides I read) and EE won't give me the unlock code 'til 6 months into the contract. Does this help: Unlocking the boot loader | Sony Xperia
Arthur Posted November 28, 2013 Posted November 28, 2013 I rooted and flashed my Galaxy S, my battery doesn't even last a day now... Isn't that to be expected on a 3+ year old phone?
gtg93 Posted November 28, 2013 Posted November 28, 2013 my battery doesn't even last a day now... To be fair, I've the same issue on the S2 and have had since it's been about 6months old - and that was on the Stock ROM. On a phone of that age, I'd be shocked if it was the ROM causing it, and not just the age of the battery. My S2 lasted about half a day until I put Cyanogen on - I get just about a day now.
sparkeh Posted November 28, 2013 Posted November 28, 2013 My wife and I both have an Xperia U, I updated mine to ICS, rooted it, took off the unneeded apps. She left hers at stock Gingerbread. I barely get a day out of it now, hers goes on forever. Though I did read somewhere that Sony's ICS update was less then ideally implemented.
Garacesh Posted November 28, 2013 Posted November 28, 2013 Does this help: Unlocking the boot loader | Sony Xperia Nada. In your device, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked. 'Bootloader unlock allowed: Yes' cannot be achieved whilst the phone is locked to a specific carrier, according to information I found when I first got the phone. Which is why I need the unlock code from EE (I could buy it from one of those dodgy-looking sites online, but as implied by 'dodgy-looking', I don't trust them)
sparkeh Posted November 28, 2013 Posted November 28, 2013 Nada. 'Bootloader unlock allowed: Yes' cannot be achieved whilst the phone is locked to a specific carrier, according to information I found when I first got the phone. Which is why I need the unlock code from EE (I could buy it from one of those dodgy-looking sites online, but as implied by 'dodgy-looking', I don't trust them) Rats! Why do the carriers need to lock the phone >:-o
Garacesh Posted November 28, 2013 Posted November 28, 2013 I honestly have no idea. To stop you getting a new phone from them with a cheap contract and then a phone-less contract with someone else for the sim (therefore they don't get any cost for any usage over the limit)? But given you can't get new[er/est] phones with cheap contracts, and you're tied in and have to pay off the charges for the life of the contract even if you cancel early, I don't see the point. Either way, they're getting their money. Surely going over your limit isn't that expensive.
X-13 Posted November 28, 2013 Posted November 28, 2013 Isn't that to be expected on a 3+ year old phone? Not when it was perfectly fine BEFORE I installed Cyanogenmod.
gtg93 Posted November 28, 2013 Posted November 28, 2013 Is it definitely an official CyanogenMod? Rather than one someone's modified further? Seems odd from my experience of it across multiple handsets.
X-13 Posted November 28, 2013 Posted November 28, 2013 Is it definitely an official CyanogenMod? Rather than one someone's modified further? Yup. I grabbed it from their site. And Cyanogenmod is known to drain batteries.
abillybob Posted November 28, 2013 Posted November 28, 2013 Yup. I grabbed it from their site. And Cyanogenmod is known to drain batteries. Id have to argue that. Because Cyanogenmod has no bloatware and less services running at startup it actually should improve battery life. I have found this with 5different phones have installed it on...
gtg93 Posted November 28, 2013 Posted November 28, 2013 Because Cyanogenmod has no bloatware and less services running at startup it actually should improve battery life. I have found this with 5different phones have installed it on... Same here ^ I've never known it and have recommended it to many people - seems odd to me that you'd have these issues @X-13... maybe an issue specifically with the Galaxy S version of the ROM?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now