Users have been complaining for a while now that there hasn’t been any sea level change in terms of Android functionality and aesthetic improvements. While to some extent that is true, the reality is that Google has been working arduously in the background to make Android genuinely a modular, safe, and simple to update operating system. In this context, we’re referring to the most recent Google Play System Update for Android, which is now accessible on Android 10 and 11. So without further ado, let’s get started learning more about the Google Play System Update.
Google Play System Update on Android 10
You might see a Google Play System Update message downloading updates in the background if your device is running Android 10 or 11. You are then prompted to restart the device so that all the modifications take effect. Although it appears to be an app update, why does it require you to restart the device? Do firmware updates and security fixes have anything to do with Google Play System Update? Let’s investigate.
Google introduced Project Treble with Android 8 in an effort to decouple vendor-level components from the kernel. On the user’s side, the adjustment didn’t appear to be significant, but for OEMs, it represented a significant shift. Finally, they could upgrade the firmware independently of SoC manufacturers like Qualcomm, Mediatek, etc.
You can see that Google has consistently worked to separate components from the essential Android frameworks so they can be updated without the need for intermediaries.
Google aims to break its need on OEMs for the delivery of crucial bug and security fixes through Google Play System Updated (codenamed Project Mainline), which is intended to replace Project Treble, which separated the OEM’s dependent on the SoC manufacturer.
What is Project Mainline AKA Google Play System Update?
That was some of the background information; now let’s look at Project Mainline’s importance and its specific functions. Google performs a fantastic job at patching new vulnerabilities and resolving issues. Google makes the code available to device manufacturers for patching Android devices shortly after the bugs are fixed. However, millions of devices don’t receive any updates due to poor support from OEMs, leaving them open to assaults.
Google wants to fix this and, more crucially, take direct control of Android device security. It wants to avoid depending on OEMs for crucial bug fixes and improvements. Project Mainline, also known as the Google Play System Update, enters the picture at this point. Google chose 13 parts (known as the Mainline Module) for Android 10 to get separate updates. But there was a significant problem. Many device manufacturers cheated because it was not required that they adhere to all Mainline Modules.
But with Android 11, everything is very different. The number of Mainline Modules has now increased from 13 to 25 (giving Google more power), and OEMs are required to implement each one. Manufacturers are required to integrate all 25 modules into their system, even if your device is being upgraded from Android 10 to Android 11. What are the 25 Mainline Modules and what do they do, then? Look at the table below, then.
List of Project Mainline Modules
Google has listed the 25 Project Mainline Modules that can be updated on Android 10 and Android 11 devices via Google Play System Update. Delivering these modules takes the form of an APEX package that Google created especially for Google Play System Update. APK containers are another delivery method for some of the modules.
|Module name||Package name|
|Captive Portal Login||com.android.captiveportallogin|
|Network Stack Permission Configuration||com.android.networkstack.permissionconfig|
|Telemetry Train Version Package||com.google.mainline.telemetry|
|Time Zone Data||com.android.tzdata|
How is Google Play System Update Different from Security Patches?
After discussing security so much, it is natural to wonder how Google Play System Update differs from the security updates that device manufacturers occasionally distribute. Security patches typically contain kernel-level fixes that have upstream patches that originate straight from Linux development. However, both are different things and serve different objectives. The Google Play System Update can’t affect it.
While Google Play System Update aims to address problems with its own parts. For instance, the Android Permission Controller can alter the rules for granting and managing permissions. In a similar vein, Google can directly handle any media codec-related issues.
It’s important to remember that Google Play System Update aims to improve its components as well as close security gaps discovered in them. For instance, starting with Android 10 and on forward, Google is quite likely to change the Permission Manager’s UI element and policy without requiring a firmware upgrade.
In conclusion, Google Play System Update and Security fixes are two distinct processes. In actuality, the patch dates for both can vary. From Settings -> About Phone -> Android Version -> Google Play System Update, you may check for updates.
Google Play System Update Explained For You
That concludes our discussion of the recent Google Play System Update, which has greatly improved Android 10 to 11. Similar to Project Treble, it does not seem like a significant change to the user, but there has definitely been a paradigm shift. You will receive immediate bug fixes that you would not have otherwise known about, improving and enhancing your experience. We anticipate that Project Mainline will continue to include more and more Android components. That’s all we have to say, though. Please leave a remark below if you have any questions.