Hello,
I have been using GrapheneOS for years, first on a Pixel 4, then Pixel 6 and since a few weeks I switched to the Pixel 7 Pro, I think the system is very great and I know it very well by now.
In the meantime, I have also switched several family members to it, I have certainly already had 5-10 devices in operation, so I also have very good comparison possibilities in case of problems.
Now I have several problems with my Pixel7Pro, which in this form, with exactly the same GrapheneOS configuration did not occur with my Pixel6 or the Pixel6a of my sister:
1) Wifi call no longer works. All network settings are exactly the same as on my old Pixel6, the APN settings are the same and I use the same sim card (Germany, Telecom D1). Just now I also put the sim card again into the Pixel6a with GrapheneOS, there it works right away. I do not know what else to do and it must be a device-specific problem of the Pixel7Pro. Whether it works with the stock OS I unfortunately do not know.
2) I use several apps that have permission to install apps, such as AuroraStore, NeoStore/F-Droid, but also Signal, Vanadium and others.
The problem is, I give permission, which works, but then an hours / days later the permission is gone again, so for example with AuroraStore I have already given permission at least 5 times, such a problem was not existent with the Pixel6. I do not know yet exactly how much time passes until GrapheneOS reverses the permission.
3) The Pixel7Pro has an LTPO display and should thus be able to switch variably between 10hz-120hz. If you activate the "Show refresh rate" function in the developer settings, where the current frame rate is displayed at the top left, it switches exclusively between "60Hz" and "120Hz". It never goes lower than 60hz, so if the numbers are correct, the LTPO display doesn't seem to work properly.
4) I don't know if this is a real problem, but I find the battery lasts a bit shorter than my Pixel6 with the same configuration. Are there any known bugs that could be responsible for this?
For all 4 issues, I'm pretty sure this is purely at the software level and therefore either an AOSP or GrapheneOS issue. Are there any known bugs here or does anyone have any other explanations for the misbehavior?
I thank everyone who answers me and would like to take this opportunity to thank the development team in general.