We are in July and the Galaxy S10 already have a security patch in August: how is it possible?

Share on facebook
Share on twitter
Share on linkedin
Share on reddit
Share on email
Share on whatsapp

Table of Contents

Samsung is one of the companies most seriously it has with updates, patch, security, especially in the high range. The south Korean company not only documents its update plans for each device, but that meets to the letter, sometimes even taking care of the safety of mobile and ended their cycle, as is the case of the Galaxy S7.

Beyond the record, sometimes the speed of updates touches on a limit that in the eyes of someone profane can be considered absurd, and even to give a sense of that here, no trick or trap. Is it really so?

The Galaxy S10 with security patch August in July, really?

One of the best added Google to the Android ecosystem were security patches monthly. These patches are distributed through the source code of Android and, although the Google Pixel come with regularity, the rest of manufacturers have to implement the code in each cell.

We are in July and the Galaxy S10 already have a security patch in August: how is it possible? 1

In the last hours has begun to deploy an update with the security patch from 1 August in the Galaxy S10. But we’re in June. Does in Samsung can travel back in time? What tricks the south Korean company to their users?

Not, and notthe reality that happens here is very different, and we explain why these things do happen.

When Google and the manufacturers are planning a security patch for a month, the date does not correspond to an end date from which, but a date guideline, a specification follows a different timetable.

We are in July and the Galaxy S10 already have a security patch in August: how is it possible? 2The versions usually have a calendar, but the software development is complicated and planning plays a key role.

That date makes the security patch of a particular day corresponds to a monthly cycle a few days earlier. For example, the security patch August 1, the more likely it is that it includes all the patches deployed from 25 June to 25 July.

Why are these days? Because before deploying a patch you should perform tests with enough time to ensure that the patch does not break anything. And in the case of an error, you have time to apply all the necessary corrections to the date set for the patch.

To create and maintain software it is usual to take into account a planning that consider any delay. That an update arrives before the time only implies that it came out right the first time.

Knowing how they work, the schedules, what most likely occurred in this situation is that Samsung has implemented the security patch as soon as it’s available and the tests have been fully satisfactory, being able to roll out the patch two days earlier than expected. On this occasion it has happened with Samsung, but it is usual to pass with other manufacturers, such as Google or OnePlus.

Google Pixel 4 XL

How many days have delayed the patches with respect to the actual date? This is something that only Google knows, but if we go to the information provided by the Google, Pixel, these often have security patches with the date to the 5th of each month. This does not mean that Google will take more than Samsung, but if it makes us think that the patch of the day 5 included all of the security improvements implemented up to the last day of the previous month.

The input We are in July and the Galaxy S10 already have a security patch in August: how is it possible? it appears first on The Android Free.