Technology

Google now blocks GApps on uncertified devices, but lets custom ROM users be whitelisted

Because Android is open source, it gives device makers the freedom to customize the software as they please. However, in order to ensure a level of consistency between Android devices, Google has cleverly leveraged their suite of popular Google apps and services to mandate that device makers follow a specific set of rules under the Compatibility Definition Document (CDD). A device maker must follow the CDD to pass the Compatibility Test Suite (CTS) so they can be allowed to pre-load their devices with Google apps and services. Previously, it was possible for uncertified devices to still make use of Google apps (shortened as ‘Gapps’ by the community), but now it appears that Google is cracking down—while still allowing custom ROM users to use Gapps!
Earlier this week, we received an anonymous tip from a person claiming to be within the industry. This person, who said they worked for an OEM/ODM, notified us that Google has started entirely locking out newly built firmware from accessing Gapps. This change apparently went into effect March 16th and affects any software builds made after this date (Google Play Services checks ro.build.fingerprint for the build date apparently).

(adsbygoogle = window.adsbygoogle || []).push({});

I reached out to my own contact in the industry who said this change was a year in the making as Google had provided prior warning to device makers, but my contact was unable to reproduce the issue on their own test device. Indeed, doing a quick search on the web reveals that people have been coming across this problem for at least a year, but could easily solve it by clearing Google Play Service’s data. What this new change might mean is that this workaround will no longer work, as Google’s A/B testing is over and the restriction will now be enforced more widely.

Leave a Reply

Your email address will not be published. Required fields are marked *