Samsung is one of the companies that is more serious with security patch updates, especially in the high-end. The South Korean company not only documents its update plans for each device, but it strictly complies with them, sometimes even taking care of the security of mobiles that have finished their cycle, as is the case with the Galaxy S7.
Beyond the constancy, sometimes the speed of the updates touches a limit that in the eyes of someone profane can be considered absurd, and even give a feeling that there is a trick or trick here. It really is that?
The Galaxy S10 with security patch from August to July, really?
One of Google’s best additions to the Android ecosystem was the monthly security patches. These patches are distributed through the Android source code and, although they arrive regularly on the Google Pixel, the rest of the manufacturers have to implement the code on each mobile.
In the last few hours an update with the security patch of August 1 has begun to be deployed on the Galaxy S10. But we are in June. Can Samsung travel through time? Does the South Korean company cheat its users?
No and noThe reality that happens here is very different, and we explain to you why these things happen.
When Google and manufacturers plan a security patch for a month, the date does not correspond to an end date from which, but an indicative date, a specification that follows a different calendar.
Versions usually have a schedule, but software development is complicated and planning plays a key role.
That date makes the security patch for a specific day correspond to a monthly cycle of some previous days. To take one example, the August 1 security patch will most likely include all patches deployed from June 25 to July 25.
Why these days? Well, before deploying a patch tests must be performed long enough to ensure the patch doesn’t break anything. And in case there is an error, there is time to apply all the necessary corrections for the date established by the patch.
When creating and maintaining software, it is usual to take into account a schedule that considers any delay. That an update arrives prematurely only implies that it went right the first time.
Knowing how the schedules work, the most likely thing that has happened in this situation is that Samsung has implemented the security patch as soon as it is available and the tests have been completely satisfactory, being able to release the patch two days earlier than expected. This time it has happened with Samsung, but it is common for it to happen with other manufacturers, such as Google or OnePlus.
How many days are the patches late compared to the actual date? This is something that only Google knows, but if we go to the information provided by the Google Pixel, they usually have security patches dated for the 5th of each month. This would not mean that Google takes longer than Samsung, but it does make us think that the patch on day 5 included all the security improvements implemented until the last day of the previous month.