format data in TWRP (and make a backup before)
Ok, signature spoofing is supported and works great with MicroG.
>grep -i encrypt sm-t320-enc.log 12-04 16:45:14.720 3610 3610 I ChooseLockGenericFragment: Ignoring PASSWORD_TYPE_KEY because device is not file encrypted 12-04 17:19:32.222 3610 3610 D SettingsActivity: Switching to fragment com.android.settings.security.EncryptionAndCredential 12-04 17:19:32.222 3610 3610 D SubSettings: Launching fragment com.android.settings.security.EncryptionAndCredential 12-04 17:19:32.242 3610 3610 D EncryptionAndCredential: NO dashboard tiles for EncryptionAndCredential 12-04 17:19:32.242 3610 3610 D EncryptionAndCredential: All preferences added, reporting fully drawn 12-04 17:19:43.734 237 9810 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place. 12-04 17:19:44.841 237 9810 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place. 12-04 17:20:09.631 9891 9911 D StorageManagerService: unlockUserKey: 0 isFileEncryptedNativeOrEmulated: false hasToken: false hasSecret: false
Encryption does not work, i've tried it once, but then gave up (lack of time). It should be possible, but I assume, TWRP should be fixed for that. One common error was that the data partition is too big and fills up the complete space for it, especially if you format data in TWRP. For the encryption, it's neccessary that there are some bytes left for encryption data.
Can you provide logcat during encryption fail on 19.1?I used 12140144K (12140160-16). Unfortunately encryption is still shows a progress bar (12+ hours). I use twrp-3.7.0_9-0-mondrianwifi.img (not the patched one from the first message). I will try the patched version.
I'm pretty sure I encrypted the device using lineage-16.0-20200411-UNOFFICIAL-mondrianwifi rom + twrp-3.7.0_9-0-mondrianwifi.img.
Will re-check both roms.
LE16+TWRP3.7.0 has same issue with encryption at the moment. Encryption is OK after FS resize fix.
this rom+TWRP3.7.0. I fixed fs (same size as for LE16). Device rebooted for encryption. I got password request on boot this time. But device won't boot and hangs on infinite boot logo (logo is animated).
LE19.1+TWRP3.6.2 (recommended in the first post) - no luck with encryption. FS size is large than FS size in TWRP3.7.0
LE18.1+TWRP3.6.2 - encryption works after FS resize.
I can reproduce what @Andrey Danin described:
Failed to mount '/data' (Invalid argument) Unable to recreate /data/media folder. Updating partition details... Failed to mount '/data' (Invalid argument) ...done Unable to mount storage Failed to mount '/data' (Invalid argument) Full SELinux support is present. Unable to mount /data/media/TWRP/.twrps MTP enabled.
New build available.It will work. The caveat is in "go back". "Enable taskbar" toggle is only visible when "on-screen nav bar" is ON (which is counterintuitive since taskbar and navbar are mutually exclusive, yet this is how it is at the moment). Once navbar is ON, you need to refresh the "Buttons" page... for that click on something at the level of System, for example Location, then go back to System-> Buttons and then the taskbar toggle will be visible.
With the baseline 19.1 functionality now working (thanks again @phoval !), perhaps this surfaces the nice-to-have's - 19.1 current usability stumbles:
- It would be sooooo nice for the Taskbar toggle being visible in Buttons unconditionally (regardless of Navbar enable status). The latest stock Samsung UI based on 12L has that.
- Grids: The only available is 6x5. Would be nice to have more choices, perhaps on par with 18.1. Fwiw, 5x6 seems to fit the aspect ratio more naturally and looks great in 18.1.
- Styles: Not available. The default 19.1 round icon shape is a bit lame, any other shape may be more appropriately modern, pleasing to the eye.
No, T520 is not the same hardware, It use Exynos soc.