thusfar #GrapheneOS has been great. just have to get used to the new keyboard, the fact that my phone is now bigger and the normal digital migration problems
for some reason its really struggling to reliably connect to my wireguard network which is a bit annoying, but not the worst
@bram the aosp keyboard that graphene ships by default sucks really bad, i've personally used anysoftkeyboard in the past but ended up sticking to the default because i find it uncomfortable to manage a separate install of the same keyboard app on every profile 
i think graphene wants to change the default keyboard eventually though so that's good
@Jupp_Schmitz @bram never used it and i don't exactly feel comfortable running it knowing Network permission can be bypassed by using inter-process communication to an app that has it, like google play services 
i'd rather run as little google software as needed, i only use play services for notifications, i'd rather run that than several other arguably more data hungry apps like whatsapp
No bypassing anything to play services on #GrapheneOS.
One of the 1000 great things there.
@Jupp_Schmitz @bram graphene does have a plan to add app communication scopes but for now this is how it works on android in general
with *mutual* consent applications can communicate with each other so the effective permissions of that set of google apps will be whatever google play is allowed to do + the individual permissions of every other google app, since we can confidently assume all google apps can communicate with play services and viceversa
bram dingelstad 
Max
a53bdb
Childless Bambino 
Synnef
JuSchi