Google has reportedly started blocking access to its official apps (Maps, Chrome, Play Store etc) on uncertified Android devices. This change went into effect March 16th and affects any software builds made after this date. The development was first reported by XDA Developers, where developers who work on custom ROMs (unofficial tweaked versions of the OS) were unable to sign into their Google accounts on devices running an unofficial build of the operating system. Google is now checking the build date of your Android system image when you attempt to run Google apps. If you have an uncertified device and you’re running a version of the Android OS that was compiled after March 16th, 2018, Google apps won’t work. Even if you manage to sideload these apps (install from external sources) you won't be able to run them. Google is offering custom ROM users a workaround though. They can now register their device with a provided Android ID to allow Google apps to run on a device. There’s a 100 device limit per user, which shouldn't be an issue for most users but ROM testers, developers might have issues though. Google trying to lock Android down? While Android is an open-source operating system, the nature of its openness has been knocked down bit-by-bit by Google. While devices running Amazon's Fire OS and a Xiaomi's MiUI (in China) are technically 'Android devices' these are running highly customised versions of the Operating System with all the 'Googleness' ripped out. Google sees this as…
