![]() ![]() Now, Google has upped the Mainline Modules from 13 to 25 (which means more control at Google’s hand) and all of them are mandatory for OEMs to implement. ![]() With Android 11 though, things have changed dramatically. It was not mandatory for device manufacturers to comply with all Mainline Modules so many device makers skipped on it. With Android 10, Google selected 13 components (called Mainline Module) to be updated independently. And that’s where Project Mainline AKA Google Play System Update comes into play. It does not want to rely on OEMs to deliver critical bug fixes and enhancements. Google wants to change this and most importantly, control the security aspect of Android devices from its own end. But due to lackluster support from OEMs, millions of devices don’t get any update hence devices remain vulnerable to attacks. Soon after the bug fixes, Google releases the code to device manufacturers to patch their Android devices. Google does a stellar job at fixing bugs and patching new vulnerabilities. That was a bit of the backstory, but here is why Project Mainline is essential and what exactly it does. What is Project Mainline AKA Google Play System Update? With Project Treble, they separated the OEM dependency on the SoC vendor, and now with Google Play System Updated (codenamed Project Mainline), Google wants to break its dependency on OEMs for delivery of critical bug and security fixes. ![]()
0 Comments
Leave a Reply. |