Digitalia I'm relatively new to both Pixel devices and Graphene OS, and I've been learning the system through experimentation.
Learning purely by experimentation can be done, but it is likely to be more laborious than a mixture of consulting reference materials plus experimentation. For example:
Digitalia My question: Why would most apps need obligatory access to sensors?
That's not what's happening. Documentation is here: https://grapheneos.org/features#sensors-permission-toggle
Digitalia Time Access – I modified time access to network-based only, so the time isn't as accurate. I don't mind this since I don't use the device as a watch, but I honestly didn't realize this could potentially affect apps or Graphene OS functionality.
It's not clear to me exactly which changes were made, but in modern systems knowing accurate time is a security matter.
Digitalia In my effort to strengthen privacy, I made several changes to my settings and I'm now wondering if I may have gone too far.
Certificate-chain issues for widely-used apps are quite unexpected. The most-common causes are disabling CAs and incorrect system date and time.
Digitalia I'm worried I may have inadvertently broken something while pursuing greater privacy.
I think that's possible, especially if a lot of changes were made in a short period of time without a detailed list of the changes being recorded.
Digitalia Should I reset everything to the original settings, or are my current configurations reasonable?
People here are generally reluctant to recommend a full reset, because it can take a lot of work to back up data first and restore afterward. But if many unknown changes were made it might be a good idea.