Slashdot Mirror
Google Starts Blocking 'Uncertified' Android Devices From Logging In (arstechnica.com)
Google logins on unlicensed devices will now fail at setup, and a warning message will pop up stating "Device is not certified by Google," reports Ars Technica. "This warning screen has appeared on and off in the past during a test phase, but XDA (and user reports) indicate it is now headed for a wider rollout." From the report: While the basic operating system code contained in the Android Open Source Project is free and open source, Google's apps that run on top of Android (like the Play Store, Gmail, Google Maps, etc.) and many others are not free. Google licenses these apps to device makers under a number of terms designed to give Google control over how the OS is used. Google's collection of default Android apps must all be bundled together, there are placement and default service requirements, and devices must pass an ever-growing list of compatibility requirements to ensure app compatibility. Android distributions that don't pass Google's compatibility requirements aren't allowed to be called "Android" (which is a registered trademark of Google), so they are Android forks. The most high-profile example of an Android fork is Amazon's Kindle Fire line of products, but most devices that ship in China (where Google doesn't do much business) fall under the umbrella of an "Android fork," too.
While Google's Android apps are only properly available as a pre-loaded app (or through the pre-loaded Play Store), they are openly distributed on forums, custom ROM sites, third-party app stores, and other places online. When a non-compatible device seller (or a user) loads these on a device, they can potentially trigger Google's new message at login. The message pops up when you try to log in to Google's services, which usually happens during the device setup. Users who purchased the device are warned that "the device manufacturer has preloaded Google apps and services without certification from Google," and users aren't given many options other than to complain to the manufacturer. At this point, logging in to Google services is blocked, and non-tech-savvy users will have to live without the Google apps. Users of custom Android ROMs -- which wipe out the stock software and load a modified version of Android -- will start seeing this message, too.
While Google's Android apps are only properly available as a pre-loaded app (or through the pre-loaded Play Store), they are openly distributed on forums, custom ROM sites, third-party app stores, and other places online. When a non-compatible device seller (or a user) loads these on a device, they can potentially trigger Google's new message at login. The message pops up when you try to log in to Google's services, which usually happens during the device setup. Users who purchased the device are warned that "the device manufacturer has preloaded Google apps and services without certification from Google," and users aren't given many options other than to complain to the manufacturer. At this point, logging in to Google services is blocked, and non-tech-savvy users will have to live without the Google apps. Users of custom Android ROMs -- which wipe out the stock software and load a modified version of Android -- will start seeing this message, too.
Yeah but to get the actual APK you can use stores that trick google into thinking it's a particular device to get the apk from google play store directly. For example, I want to play minecraft on the nvidia shield tv, but it isn't supported on play store, so I use a third party play store client to trick it into thinking it's a Nexus 9 or something compatible with the shield's processor. It's safer than trusting some dodgy apk site (I think?).
Did you miss the part about custom ROMs? I have a legitimate Galaxy Tab 10.1 which Samsung no longer supports, am I supposed to stick with Honeycomb forever?
Were that I say, pancakes?
As described in the XDA link, custom ROM users aren't shut out. Individual users can request whitelisting of up to 100 devices, and makers of custom ROMs can also contact Google to get their standard images approved by default.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
adb shell content query --uri content://settings/secure --where "name=\'android_id\'"
adb shell content delete --uri content://settings/secure --where "name=\'android_id\'"
adb shell content insert --uri content://settings/secure --bind name:s:android_id --bind value:s:
So there's going to be tons of apps to set your android_id. It's not going to stop many people from getting gapps, but it may well result in people having borked android_id's on previously "certified" phones.
IMO opinion would have been better to block access to gapps until the user acknowledges usage of uncertified device along with the obligatory "You may be insecure and apps may not work properly...." message.