latest
Google is reportedly mandating virtual A/B support for GMS licensing on devices launching with Android 13. Thanks to this, Android 13 launch devices from manufacturers like Samsung and Oppo could finally feature support for Seamless Updates, after several years of trailing behind the competition.
[Update: Not Required] Google is requiring Virtual A/B on new Android 11 devices, paving the way for mandatory Seamless Updates
Google backtracked on requiring OEMs support virtual A/B on new Android 11 devices, which would have paved the way for seamless updates.
With Android 7.0 Nougat, Google introduced a partition scheme designed to speed up software updates. In Nougat, Google added support for duplicating certain partitions so that inactive partitions can get updated in the background and then swapped to active with a quick reboot. This "A/B partition" setup allows for "seamless updates" to take place on supported Android devices, much like Google's Chrome OS. However, Google has never mandated the use of A/B partitions, so many devices out there that don't support seamless updates. That could change with Android 11, however, as Google is making it mandatory for newly launched devices to support virtual A/B partitions.
Magisk v17.1 released with better Android Pie and A/B device support
Magisk v17.1 has been released with better support for Android Pie and A/B partition devices. You can get the full changelog here and download Magisk!
When it comes to rooting your Android smartphone, everybody points to Magisk by XDA Recognised Developer/Recognised Contributor topjohnwu as the best place to get started. It's one of the easiest ways to root your Android smartphone, and it has full support for Magisk Modules too. These modules allow you to systemless-ly replace files on your device's /system partition. The biggest selling point for Magisk came about as a means to hide root from SafetyNet. This enabled users to play games like Pokemon Go even when their phone was unlocked and rooted.
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
When Android Nougat released, it had us talking about all kinds of new features. We got a newly updated user interface for starters along with long-awaited multiwindow capabilities and Vulkan Graphics API support. But one under-the-hood addition flew over the heads of most users. Android Nougat introduced "Seamless Updates" on devices that support A/B partitions. The vast majority of existing Android devices (excluding the new Google Pixel and Google Pixel XL) did not have A/B partitions at the time and thus couldn't take advantage of seamless updates. The basic premise of this feature is that the device has a second set of the system, boot, vendor, and other important partitions, and when you get an OTA update the update happens in the background while the second set of partitions are patched which lets you reboot into an updated software build seamlessly. If an update fails, you'll be kicked back to a working build, meaning companies will have fewer headaches to deal with and consumers are better protected.
LineageOS 15.1 now supports A/B devices starting with the Motorola Moto Z2 Force
LineageOS 15.1 now officially supports A/B devices starting with the Motorola Moto Z2 Force. Expect support for the Pixel 2 XL, Xiaomi Mi A1, and more soon.
One of the more exciting changes that Android Nougat 7.0 brought was the introduction of A/B dual partition scheme for devices launched with this OS version. This change tackled how Android system updates are applied to devices, with the aim to provide a seamless upgrade experience to the user where a simple and quick reboot brings them into the updated OS. This change also added the benefit of a failsafe which ensured that at least one workable booting system remains on the device during an OTA update, allowing devices to "rollback" to the older system if an OTA fails to boot.
Here's a list of Android devices that support Seamless Updates
Android Nougat added an update system called "seamless updates" where updates take place in the background thanks to a dual A/B partition setup. We've put together a list of Android devices that support the A/B seamless system updates, come check it out!
While some of our readers feel lucky to even receive updates on a consistent basis, others might dread them because of how long an update can take. On most Android smartphones and tablets, an update can take a couple of minutes of your time as the updater has to patch all of the system files which can't happen while you're booted into Android. That's why Google introduced "seamless updates"—a new A/B dual partition scheme with Android Nougat.
How to check if your Android device supports Seamless Updates
Users can easily check if their Android device supports seamless updates by running a command. They can also choose to download the Treble Check app from the Play Store to see if their device has an A-only partition system or the A/B partition system.
Android Nougat introduced support for seamless updates with the A/B partition system. Devices that support the new partition system have two sets of partitions, a_slot and b_slot. The term "seamless updates" is used because all updates are now downloaded to the inactive slot. When a user reboots to finish installing, the device seamlessly switches over to the inactive slot, thereby eliminating downtime. User data is shared between the partitions.
EXCLUSIVE: Pixel Software Updates, Partition Changes, Dual Booting & Seamless Custom ROM Updates
Speaking with TWRP's lead developer, Dees_Troy, on the matter, we believe that it may be possible to exploit seamless updates to provide dual-booting.
During this year's Google I/O, Google officially introduced Android Nougat which has brought several much-needed usability enhancements to those of us lucky enough to own a modern Nexus device. There were some features Google outlined during Google I/O that didn't find their way into final Nougat production builds for current Nexus devices, most notably seamless updates.