I hear you, but personally I am still of the opinion that an unlocked bootloader only protects you from an “Evil Maid” (and even then I don’t know of any successful "evil maid’ exploits on Android):
In my understanding, an unlocked bootloader is only a risk to an “evil maid attack” - your data is encrypted and safe unless your unlock pattern / pin is compromised.
I am genuinely open to a simple explanation of how it is a credible risk for privacy concerns… admitting that yes deep-state-level actors may have ways to trigger an exploit, but is this just due to an unlocked bootloader or more likely to something else?
But to the issue, yes I hope future builds will have this fixed. As noted, we have confirmed issues with the FP4 that may possibly be related to this:
Our developers note the following about a question of whether that above post is related to our issue of FP4 users with locked bootloaders not able to upgrade to v7.x:
yes, but the actual firmware is FP4.QREL.15.14.3… maybe there’s a problem with it too. Waiting for the new firmware FP4.SREL.15.14.4, not released on their website yet
So possibly FP is rolling out firmware updates across the line to address some issues. When they do they will be incorporated in our next builds following their release.