That's true, but I am not personally concerned about malicious images being flashed . As a developer, I will frequently flash unbootable and can't justify the risk of losing data.Nice work on the rom. I was able to get it up and running on MacOS without any issues. Although seems to be security concerns for using it as daily driver.. according to GrapheneOS lead keeping bootloader unlocked is highly unsecure as it opens up attack vector:
Locking the bootloader is important as it enables full verified boot. It also prevents using fastboot to flash, format or erase partitions. Verified boot will detect modifications to any of the OS partitions (vbmeta, boot/dtbo, product, system, vendor) and it will prevent reading any modified / corrupted data. If changes are detected, error correction data is used to attempt to obtain the original data at which point it's verified again which makes verified boot robust to non-malicious corruption.
In the bootloader interface, set it to locked:
fastboot flashing lock
The command needs to be confirmed on the device since it needs to perform a factory reset.
Unlocking the bootloader again will perform a factory reset.
BTW have you thought about joining GrapheneOS as Pixel 5 maintainer? You'd be a great addition to team and project is lacking Pixel 5 dev.
It's possible that my ROM will support verified boot in the future so you will have the option to lock the bootloader, but I wouldn't count on that happening in the near future since my ROM is in its early days and the underlying infrastructure is immature; AVB support will require managing signing keys securely between the different machines I build ROMs on.
As much as I want to get involved, I don't have the time for it and my own ProtonAOSP project is what I'm most satisfied with using as a daily driver on my own device. GrapheneOS is great from a security and hardening perspective, but its performance and UI are lacking due to being nearly uncustomized AOSP with performance. I understand that some people will prioritize security, but personally, I don't want to make that trade-off.
It should work as long as the bootloader is unlockable. The only low-level variants are the Pixel 4a 5G, Pixel 4a 5g UW (Verizon), and Pixel 5; other hardware variations should not matter at the software level.
Call recording is not a feature I'm personally interested in, and as a small project with no other core team members at the moment, I don't have time to add every feature people want while keeping the same level of quality across the board. It's also illegal to record calls without mutual consent in my location, so I wouldn't be able to use it anyway.Is there a native call recording function? one that records the other side as well, not just your side.
If not, do you plan to add it in or would rather not bother because of country laws?
I still don't have my device yet so I can't install it yet to find out myself.