GrapheneOS
Annoyance: different profiles have different screen brightnesses
This is obviously an unintended side effect of duplicating substantially all of the OS information across profiles. It's just quite annoying to have the screen suddenly become invisible (or blast you in the eyes) because you switched profiles. Probably the same case could be made for suddenly changing all the various volume settings. The way things are at the moment would only make sense if switching profiles almost meant that your physical environment resumed its previous context!
I don't expect urgency on this but it would be really nice if this could be fixed. Maybe just walk through the drawer and decide which features (e.g. flashlight) should be unified between profiles and which shouldn't.
If this feature would be implemented, the value should vary by an insignificant random number, just not to add another value that could help linking multiple profiles to the same device(if apps can see the value)
For me, however, it's a wonderful feature. I love it having separate brightness settings -- I have couple of the "normal" profiles and separate "maps & navigation" profile -- and on the latter I have the brightness dialed to the max exactly as I need it. Without separate brightness settings every time I switch to/from this profile I'd have to disable auto brightness and turn the brightness to the max, or the other way around. Incredibly tedious.
An option to decide if they should be linked/disconnected would be great indeed, I'm just saying for some people the current behaviour is great.
@controlrepo No reason we can't have a toggle which says "Separate brightness controls for different profiles". Everyone would be happy. This could be extended to literally any drawer setting that one might want to (dis)unify. It only gets weird when we think about settings which control a single physical resource, such as Flashlight or Bluetooth or Screen Record; in that case, you could either persist the state across profile changes (which is how wifi currently works) or change it every time the profile is changed (if and only if the target state is different).
@Lppsoeht I would be fine with this as equivalent to maintaining the same brightness across profiles. But you raised an important point, which is whether apps can even see this value. I honestly think they can't (likewise with your wifi SSID name, sound volume, notification volume, etc.). It would be nice to get an official statement on this.