Thanks for the infoLegacy blobs
Legacy blobs
Legacy blobs
The services that are started by the legacy blobs we are using don't start at the right time at boot. This leads to several HALs not functioning correctly after boot. The one with the most issues is the camera HAL. I'm sure you've seen it yourself that the camera is unavailable after device boot on some other ROMs if you've flashed them and somehow a reboot fixes it
Encryption restarts several of these services, we need these restarts to get certain HALs to start correctly. I've never seen anyone with encryption report issues with the camera HAL or any other HAL because these are made to restart several times during encryption and are available after boot the way they are supposed to be
Also as per Google's CTS, Amy device that can support encryption at a speed higher than 50 Mbps should encrypt before the user sees the welcome screen. In our case the encryption performance is 150 Mbps+ (speed of the chip)
