[ad_1]
What you need to know
- Google may remove support for non-A/B updates.
- This means that Seamless Update is the only officially supported OTA update method.
- Some device manufacturers may still be looking to use legacy updates.
Seamless updates (also known as A/B updates) have been a feature of Android devices since 2016. Although the convenience of this over-the-air (OTA) update method has several benefits, not all device manufacturers are keen on it. Please adopt it. Now, there are reports that Google is preparing to remove support for non-A/B updates, which means it’s likely coming to more devices.
As Android expert Mishaal Rahman pointed out, AOSP’s comments point to the removal of support for non-A/B updates. If this is true, it means seamless updates will be his only officially supported OTA update mechanism.
Google is preparing to completely remove support for non-A/B updates from Android, leaving A/B updates as the only officially supported OTA update mechanism going forward. However, this does not prevent certain device manufacturers from continuing to use non-A updates. /B Because you can use your own… pic.twitter.com/gmSjNzCk50February 21, 2024
The majority of device manufacturers have already switched to seamless updates. But Samsung, one of the world’s biggest smartphone brands, has so far refused to move away from traditional updates. And now, even with the potential removal of support for non-A/B updates, as Rahman pointed out, Samsung may continue to circumvent this method of updating devices.
Seamless updates allow your Android smartphone to receive system upgrades while you use it. Active partitions run in the background and updates are applied to inactive partitions. When you are prompted to restart your device, your phone will switch to the new fully updated partition.
With traditional methods, users have to wait until the update is complete and cannot use their phone during that time. Meanwhile, Google has recently succeeded in speeding up seamless updates, although this approach often takes less time to complete and tends to use less storage space. In theory, by removing support for the legacy method, Google could encourage his Samsung (and others) to start using seamless updates.
However, as Rahman explained, device makers could continue to create their own update systems to avoid this problem, or they could “just revert Google’s changes.” Google had previously considered mandating the use of seamless updates since Android 11, and was considering mandating it again with Android 13, but decided not to do so. Years later, Samsung continues to resist seamless updates. Whether that can continue remains to be seen.
[ad_2]
Source link
