Google preparing to ditch support for non-A/B updates from Android

Android’s seamless update feature (aka A/B updates) has been around for several years, offering users a more streamlined update experience. Google Pixel users should already understand the benefits that come with A/B updates. Despite this, some major phone manufacturers, including Samsung, have resisted adopting the technology. However, Google’s recent moves suggest change is on the horizon, potentially forcing OEMs to adapt or find workarounds.

Seamless updates work by having two system partitions (A and B). While you use your phone on one partition, the other can be updated in the background. When it’s time to reboot, your phone simply switches to the updated partition, minimizing downtime and making the update process far less intrusive.

Google’s code comments discovered (H/T 9to5Google) within the Android Open Source Project (AOSP) indicate that the company is preparing to remove support for “non-A/B” updates. This means the traditional update method, where devices are unusable during the update process, may soon become technically incompatible with future Android versions.

Samsung has long favored the conventional update method. If Google goes ahead with removing support for non-A/B updates, Samsung could face a choice with three main options. The first of which will be to embrace the A/B seamless update method, aligning with Google’s direction and offering a smoother update experience for users.

The second and third options, as mentioned by Mishaal Rahman, could be ‘workarounds’. Samsung and other brands could potentially create a custom update solution, which could prove complex and time-consuming. Alternatively, they can override Google’s changes within its customized version of Android, potentially leading to compatibility issues in the future.

While conventional updates may take less time and use less storage, they leave users unable to use their devices during the update process. Seamless updates offer a more user-friendly experience at the potential cost of slightly higher storage requirements.

This potential change by Google has the potential to spark debate within the Android community. Is Google right to force seamless updates as the new standard? Do the benefits outweigh the potential drawbacks for manufacturers like Samsung? Do share your thoughts in the comments section below.