[Galaxy S 4 i9505 Original Android Development] bvlgvr:
Encryption now possible?

So does this mean that it is not (yet) possible at all to have a dual boot setup (using dual boot patcher) with encrypted ROMs?

What does the most recent post in the above mentioned github issue #126 mean:? "The new implementation has been completed and merged into master."

Does it mean that encryption should now in fact be supported with dual boot?

Let me explain what I intend to do: I'd like to have a setup with two ROMS (on my S4 mini GT-I9195). One daily usage ROM and one "sandbox" ROM.

(Just saying: I do know there is this privacy guard functionality ...)

daily usage ROM

this ROM would contain the usual kinds of personal data (contacts, browsing history, ...)

I'd try to keep most data collectors out of this ROM, so no google apps, no play store, no google services, no other data collecting apps

this ROM would be encrypted (including ext sd card so the sandbox ROM can't read it)

could be cyanogenmod (CM13) for example

sandbox ROM

would contain as little personal data as possible, no email, no contacts, ...

would have all the usual google services and play store, gapps, ... installed to enable all apps relying on such stuff to run

I would use this ROM to occasionally make use of apps which have questionable functionality concerning privacy and security

could be cyanogenmod or also Touchwiz

wouldn't need to be encrypted

ideally no root

I have a dual boot setup with Touchwiz 4.4.2 and CM13 (6.0.1) at the moment. I tried to encrypt CM13 which didn't work. CM13 tries to encrypt then instantly reboots. Logcat shows:

01-01 02:23:03.996 E/Cryptfs (188): Cannot remove dm-crypt device
01-01 02:23:03.997 I/Cryptfs (188): Enabling support for allow_discards in dmcrypt.
01-01 02:23:03.997 I/Cryptfs (188): target_type = crypt
01-01 02:23:03.997 I/Cryptfs (188): real_blk_name = /dev/block/vold/private:179_34, extra_params = 1 allow_discards
01-01 02:23:19.689 D/CryptdConnector(613): SND -> {1 cryptfs getfield SystemLocale}
01-01 02:23:19.690 I/Ext4Crypt(188): ext4 crypto complete called on /data
01-01 02:23:19.690 I/Ext4Crypt(188): No master key, so not ext4enc
01-01 02:23:19.691 D/CryptdConnector(613): RCV <- {200 1 -1}
01-01 02:23:22.058 E/Cryptfs (188): Cannot remove dm-crypt device
01-01 02:23:22.059 I/Cryptfs (188): Enabling support for allow_discards in dmcrypt.
01-01 02:23:22.059 I/Cryptfs (188): target_type = crypt
01-01 02:23:22.059 I/Cryptfs (188): real_blk_name = /dev/block/vold/private:179_34, extra_params = 1 allow_discards
01-01 02:23:26.835 D/CryptdConnector(613): SND -> {2 cryptfs getpw}
01-01 02:23:26.835 D/VoldCryptCmdListener(188): cryptfs getpw
01-01 02:23:26.835 I/Ext4Crypt(188): ext4 crypto complete called on /data
01-01 02:23:26.835 I/Ext4Crypt(188): No master key, so not ext4enc
01-01 02:23:26.835 I/Ext4Crypt(188): ext4 crypto complete called on /data
01-01 02:23:26.835 I/Ext4Crypt(188): No master key, so not ext4enc
01-01 02:23:26.837 D/CryptdConnector(613): RCV <- {200 2 -1}
01-01 02:23:26.837 D/CryptdConnector(613): SND -> {3 cryptfs clearpw}
01-01 02:23:26.837 D/VoldCryptCmdListener(188): cryptfs clearpw
01-01 02:23:26.837 I/Ext4Crypt(188): ext4 crypto complete called on /data
01-01 02:23:26.837 I/Ext4Crypt(188): No master key, so not ext4enc

Any ideas anyone? Could I go for some kind of manually setup encryption?