![]() ![]() This is generally down to one of four reasons. While it's true that Android Partners (read: all major OEMs) received security patches well in advance of their release, many are painfully aware that they possibly won't receive a security update for months after its release. Why do I need to wait so long to receive a security patch on my phone? These updates can happen if new vulnerabilities and bugs have been found, if Google decides to remove certain patches from the monthly bulletin due to it breaking critical components, if Google updates a patch to resolve a bug created by the previous version of the patch, and other reasons. ![]() *Note: Google can, and often does, update the patches for the latest security bulletin all the way until the public release. Patches for the Android framework issues disclosed in the May 2019 security bulletin, for example, were provided to Android partners at least as early as March 20th, 2019*. Google provides patches for all issues for OEMs to merge and test, though vendor component patches are dependent on the vendor. Android partners are notified of all Android framework issues and Linux kernel issues at least 30 days before the bulletin is made public. If you are an Android Partner, you immediately have it a whole lot easier. If the OEM does not have access to the source code, then they must wait for the vendor to issue a fix. Note that if the vendor has given the OEM access to the source code of the closed-source component(s), then the OEM can fix the issue(s) themselves.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |