Tech News

Google Bringing The Virtual System With A/B Options

Google Virtual System With A/B Options


Google Bringing The Virtual System With A/B Options. According to rumors, Google will require virtual A/B support for GMS licensing on smartphones running Android 13 out of the box.

This means that after several years of falling behind the competition, Android 13 launch devices from companies like Samsung and Oppo could now support Seamless Updates.

For those who are unaware, Google accelerated software updates with Android 7.0 Nougat by using an A/B partitioning mechanism. The business increased support for splitting up some partitions into two separate “A” partitions and “B” partitions.

The partition you are presently using is your active partition; an upgrade to the inactive partition can be made in the background and then switched to with a short reboot.

On Android devices, this solution dramatically speeds up software upgrades. Some OEMs haven’t used this strategy yet, though. Samsung smartphones, for example, don’t have A/B partitions and take a lot longer to upgrade their software, rendering them inoperable for a while.

By requiring virtual A/B support for GMS licensing on devices arriving with Android 13, Google now seeks to change that.

Google previously tried to make all smartphones running Android 11 debut with virtual A/B compatibility. The business then changed its mind and recommended support for A/B system updates instead of enforcing it in the Android 11 Compatibility Definition Document (CDD).

Due to this, several Android OEMs have not yet added support for virtual A/B and, consequently, seamless updates to their systems devices.

Although Google is now requiring virtual A/B support for GMS licensing on Android 13 launch devices, the Android 13 CDD still does not force OEMs to provide it.

In order to do this, the business has updated the Vendor Test Suite (VTS) with new tests that mandate virtual A/B support for Android 13 launch devices.

Although these tests were combined before to the release of Android 13, the study notes that they “stay in place even after its introduction, in contrast to what happened during Android 11’s development.

” This implies that in order to receive GMS certification, all devices that support Android 13 must pass these tests.

In order to offer Google Mobile Services, OEMs releasing devices with Android 13 will essentially need to provide virtual A/B support. According to Esper, the only exception is that

“Android 13 launch devices shipping with earlier vendor software, thanks to the carve outs in the VTS test as a result of the Google Requirements Freeze (GRF) programs”

Now that Android 13 launch devices with GMS must have virtual A/B compatibility, Seamless Updates ought to be accessible on devices from all OEMs. Visit the Esper blog listed below for more details on virtual A/B and how it speeds up software upgrades.

Leave a Reply

Your email address will not be published. Required fields are marked *