wubwab There's nothing about GrapheneOS that would cause this sort of problem. Keep in mind that the majority of code comes from AOSP. Assuming this is a bug, it would likely be a bug in firmware that GrapheneOS cannot modify or fix. You can search the internet for this issue and you can find very few reports, but they're out there, like this or this. If the same happens to stock OS users, it's not an issue unique to GrapheneOS. Also, seeing so few reports on a regular basis shows that whatever the issue may be, it's extremely rare.
It's understandable to be upset by this, don't get me wrong, but given the information we have and mentions of the same issue elsewhere on the internet by stock OS users, it's clearly not an issue with GrapheneOS.