We already covered a solution to fix the sensors issue. This caused the corruption of the phone’s calibration data stored in the said partition, ultimately leading to non-working sensors like proximity, gyro, etc. Earlier, TWRP 3.3 used the ‘persist’ partition on devices to store the recovery’s cache and log files.
The recovery now shows info about the ZIP file being installed to the inactive slot of an A/B device.
This should allow users to manually upgrade their phones using TWRP itself. This means users wouldn’t need to decrypt and convert the firmware package to a recovery-flashable ZIP anymore.
With this latest update, TWRP supports automatic detecting of SAR, allowing the recovery to properly mount the /system partition for flashing ZIP files, backing up and restoring NANDroid backups, and more. A very detailed and simple explanation was provided by Magisk developer John Wu. This particular Android code implementation has added a series of roadblocks for both the developers and users of TWRP in the past.
TWRP 3.4 is possibly one of the biggest updates to the custom recovery considering the large variety of changes it brings. From the new System-as-Root implementations to dynamic partitioning system in Android 10, a lot of these changes have posed new problems in TWRP development and real-time usage. Since the release of TWRP 3.3 a year ago we have observed some of the most drastic changes in the Android ecosystem.