Google apps and services can be installed on GrapheneOS as regular sandboxed apps. You can test both with and without Google Mobile Services on GrapheneOS.

Devices without Google Mobiles Services are increasingly popular and apps should fully work without it. Many popular mainstream apps do including even the Facebook app suite.

There are alternatives to Google services. For example, apps can default to FCM when present while offering UnifiedPush as an alternative.

It was a poor repair. They likely either forgot to reconnect it or broke it.

Pairing with a specific Bluetooth devices doesn't require the Nearby Devices permission. Pairing uses a case-by-case consent system. The Nearby Devices permission doesn't allow pairing with arbitrary Bluetooth devices but rather scanning for them. See here for Bluetooth:

https://developer.android.com/develop/connectivity/bluetooth/bt-permissions

At a low level, the different parts of the Nearby Devices permission are split up and we could eventually expose separate control over those, but that would add complexity and more to maintain.

Can you provide more details on what's wrong?

Try enabling the per-app exploit protection compatibility mode as an initial step. This works for most banking apps which don't work with the defauilts.

GrapheneOS isn't rooted and fully preserves the standard security model along with greatly improving it. You should report this to their customer support and leave a review about it on the Play Store too. Don't include a link in the review to avoid it being spam filtered. Give their customer support a link to https://grapheneos.org/articles/attestation-compatibility-guide.

Try enabling the per-app exploit protection compatibility mode as an initial step. This works for most banking apps which don't work with the defauilts.

GrapheneOS isn't rooted and fully preserves the standard security model along with greatly improving it. You should report this to their customer support and leave a review about it on the Play Store too. Don't include a link in the review to avoid it being spam filtered. Give their customer support a link to https://grapheneos.org/articles/attestation-compatibility-guide.

It currently has to be supported by each app and there isn't a way to force apps to use another font beyond forking them.

There will likely be customization for this eventually, at least a choice between several fonts built into the OS.

Similarly to how most apps don't use the system there, a subset of apps don't use system fonts and wouldn't be impacted by changing the system fonts. It wouldn't be as widespread as the vast majority of 3rd party apps not using the system theme though.