[Xiaomi Redmi Note 3 [Snapdragon] ROMs, Kernels, Re] schlowmo:
Full Disk Encryption not working

[MENTION=5857684]TheStrix[/MENTION] First of all thank you very much for this ROM and for making it official!

Unfortunatley I've got a bug to report, I'm not sure if it's enough to post it here or if I should report it through the official CM Bugtracker (or any other?). So if you like me to report it at another place, please tell me and I will.

If I try to encrypt the phone via "Settings --> Security --> Encrypt Phone" the phone shows the "droid logo" for 1-2 seconds and then it soft reboots without any encryption happened. Here is the relevant logcat portion:

08-03 14:34:49.793: D/Cryptfs(355): unmounting /data succeeded
08-03 14:34:49.794: I/Cryptfs(355): keymaster module name is Keymaster QTI HAL
08-03 14:34:49.794: I/Cryptfs(355): keymaster version is 256
08-03 14:34:49.794: I/Cryptfs(355): Found keymaster1 module, using keymaster1 API.
08-03 14:34:49.794: D/QSEECOMAPI:(355): QSEECom_get_handle sb_length = 0xa000
08-03 14:34:49.794: D/QSEECOMAPI:(355): App is already loaded QSEE and app id = 3
08-03 14:34:49.807: E/keymaster1_device(355): TA API Major Verion: 1
08-03 14:34:49.807: E/keymaster1_device(355): TA API Minor Verion: 0
08-03 14:34:49.807: E/keymaster1_device(355): TA Major Verion: 1
08-03 14:34:49.807: E/keymaster1_device(355): TA Minor Verion: 10
08-03 14:34:49.807: E/keymaster1_device(355): HwKmClose
08-03 14:34:49.807: D/QSEECOMAPI:(355): QSEECom_dealloc_memory
08-03 14:34:49.807: D/QSEECOMAPI:(355): QSEECom_shutdown_app, app_id = 3
08-03 14:34:49.808: I/Cryptfs(355): keymaster module name is Keymaster QTI HAL
08-03 14:34:49.808: I/Cryptfs(355): keymaster version is 256
08-03 14:34:49.808: I/Cryptfs(355): Found keymaster1 module, using keymaster1 API.
08-03 14:34:49.808: D/QSEECOMAPI:(355): QSEECom_get_handle sb_length = 0xa000
08-03 14:34:49.808: D/QSEECOMAPI:(355): App is already loaded QSEE and app id = 3
08-03 14:34:49.810: E/keymaster1_device(355): TA API Major Verion: 1
08-03 14:34:49.810: E/keymaster1_device(355): TA API Minor Verion: 0
08-03 14:34:49.810: E/keymaster1_device(355): TA Major Verion: 1
08-03 14:34:49.810: E/keymaster1_device(355): TA Minor Verion: 10
08-03 14:34:50.268: D/DrmLibTime(431): got the req here! ret=0
08-03 14:34:50.268: D/DrmLibTime(431): command id, time_cmd_id = 770
08-03 14:34:50.268: D/DrmLibTime(431): time_getutcsec starts!
08-03 14:34:50.268: D/DrmLibTime(431): QSEE Time Listener: time_getutcsec
08-03 14:34:50.268: D/DrmLibTime(431): QSEE Time Listener: get_utc_seconds
08-03 14:34:50.268: D/DrmLibTime(431): QSEE Time Listener: time_get_modem_time
08-03 14:34:50.268: D/DrmLibTime(431): QSEE Time Listener: Checking if ATS_MODEM is set or not.
08-03 14:34:50.268: D/QC-time-services(431): Lib:time_genoff_operation: pargs->base = 13
08-03 14:34:50.268: D/QC-time-services(431): Lib:time_genoff_operation: pargs->operation = 2
08-03 14:34:50.268: D/QC-time-services(431): Lib:time_genoff_operation: pargs->ts_val = 0
08-03 14:34:50.268: E/QC-time-services(431): Lib:time_genoff_operation: Connection failed !!
08-03 14:34:50.268: D/DrmLibTime(431): QSEE Time Listener: ATS_MODEM is not set. Fallback to Android system time.
08-03 14:34:50.268: D/DrmLibTime(431): QSEE Time Listener: Retrieved Android system time: 1470227690
08-03 14:34:50.268: D/DrmLibTime(431): time_getutcsec returns 0, sec = 1470227690; nsec = 0
08-03 14:34:50.268: D/DrmLibTime(431): time_getutcsec finished!
08-03 14:34:50.268: D/DrmLibTime(431): iotcl_continue_command finished! and return 0
08-03 14:34:50.268: D/DrmLibTime(431): before calling ioctl to read the next time_cmd
08-03 14:34:50.269: E/keymaster1_device(355): Generate key send cmd failed
08-03 14:34:50.269: E/keymaster1_device(355): ret: 0
08-03 14:34:50.269: E/keymaster1_device(355): resp->status: -30
08-03 14:34:50.269: E/Cryptfs(355): Failed to generate keymaster1 key, error -30
08-03 14:34:50.269: E/keymaster1_device(355): HwKmClose
08-03 14:34:50.269: D/QSEECOMAPI:(355): QSEECom_dealloc_memory
08-03 14:34:50.269: D/QSEECOMAPI:(355): QSEECom_shutdown_app, app_id = 3
08-03 14:34:50.270: E/Cryptfs(355): keymaster_create_key failed
08-03 14:34:50.270: E/Cryptfs(355): Cannot create encrypted master key
08-03 14:34:50.270: E/Cryptfs(355): Error enabling encryption after framework is shutdown, no data changed, restarting system

I'm using the recommended firmware version from this thread, just in case it turns out to be a firmware issue with the qualcomm keymaster. If you need any further informations/logs please let me know.