Google appears to be clamping down on uncertified builds of the Android OS. Developers are reporting that they are unable to log in to Google accounts while using unverified firmware; a move that appears to force OEMs to provide a more consistent Android experience.
Developers on unverified versions of Android have reported that they are unable to sign into Google’s services through their devices. Instead, all they get is a warning message explaining what needs to be done.
The open source nature of Android allows, in theory, just about anyone to build their own version of the operating system. Which is pretty much why every manufacturer has an in-house variation.
However, these manufacturers are expected to comply with a set of rules set out in the Compatibility Definition Document, and then pass a Compatibility Test Suite. Doing so will allow them to pre-load Google’s app suite into the device. Of course, until recently, failure to comply would simply result in nothing bad actually happening. Aside from users having to sideload the apps instead of having them pre-installed.
This move seems like a better method of exercising some control over Android, while still allowing developers and OEMs to continuing with their own customisation work. It would also clamp down on less scrupulous manufacturers who take liberties with the security of their operating system.
On the other hand, it is going to be a whole lot more troublesome for those who prefer to install the own ROMs. Seeing that every new build will have to be registered separately; not to mention the 100 device ID limit on registration.
[Source: XDA Developers]
