The problem
Current state of upstream Android is quite bad with encryption security, due to some dubious decisions made by Google. Who on years would limit user's passwords to 8 or 16 chars? It's completely insane horse battery staple approach, if you know what I mean. Well, this problem is luckily solved in GrapheneOS, well done!
But another upstream security problem still exists in GrapheneOS: random asks for user password even when fingerprint is set and used.
This problem leads to several major SECURITY problems:
User is obliged to enter they password or PIN code in a crowded surroundings, like bus, train, underground, public places.
To enter password not only literally showing it to a bunch of people, but also under 10+ cameras that are recording it, like in shops, elevators and other places.
User is forced to use much shorter passwords due to the fear of being forced to enter long password while riding a bike, running or other situations, when entering long passphase is not possible, just because some google 8-char-limited developer wants you to.
Remember, PIN/password is the only thing that protects data in case the phone with GrapheneOS is in others hands. It can power off due to timeout, but still give away you data because you were forced to enter password under 5 high quality cameras.
There is exactly NO reason to behave like that are ruin user's password/PIN experience.
Proposed solution:
Add an option to completely disable this random passwords check. Completely, no random asks at all, no "reminding". The user should know it and be able to refuse forced reminding in insecure situations.
I would love to have this feature on GrapheneOS.
Notes:
Maybe some combination with power/volume buttons should be making the password entering forced (not possible on GrapheneOS, but possible on iphone?).
Forcing entering password when switching between profiles maybe should be changed too, because currently using them is painful, but it's a separate issue. At least user decides to change profile by their own, not because some Google person decided so at random moment.