Thanks. I shall soon use/test it.
One thing that concerns me after reading the changelog for CARBON-5.1.1-METICULUS-20160728-0825-codinalte update-2 is:
Is the resized partiion ever restored to original size? If full device encryption is performed many times, would the data partition consequently be reduced more than 16k from the original size? For example, If the device encryption is performed 100 times, would the resized amount be 1600k?
Is the CARBON-5.1.1-METICULUS-20160728-0825-codinalte update-2 build the first build to perform the partition resizing when device encryption is attempted?
At what point does the data partition resize occur? (For example, during ROM first boot, after using the Encrypt phone option in the Storage category from Settings, etc.)
As an aside: Are the encryption strategies/algorithms used by Andorid AOSP and Samsung's implementation different with regards to partition size requirements?