[###](https://) Device: Pixel 8
OS Version: GrapheneOS (latest release, post-reset)
Issue Context:
After performing a fresh reset of my Pixel 8 running the latest GrapheneOS, I encountered a few issues in the logs related to Trusty TEE initialization and Vanadium (Chromium-based browser) failing to load critical libraries. These errors appeared immediately post-reset. I’m concerned these could impact device security and functionality, so I’m looking for guidance.
Key Issues:
1. Trusty TEE Errors:
[GF_TA][E][gf_tee_storage][trusty_file_open] Unable to open LHBM_gf_fake_base_1.so on port com.android.trusty.storage.client.nsp
- Description: These errors indicate that certain files related to the Trusted Execution Environment (TEE) are failing to open, which could potentially impact secure operations like key management and file encryption.
- Impact: It’s unclear whether this impacts the overall security of the TEE, but as the TEE plays a crucial role in encryption and secure operations, it warrants investigation.
2. Vanadium Library Loading Failures:
cr_Linker: Unable to load library: libmonochrome_64.so
- Description: Vanadium (the Chromium-based browser in GrapheneOS) is failing to load
libmonochrome_64.so, which might affect browser performance or certain features.
- Impact: This may result in degraded performance or missing security features in the browser, which is a concern for users prioritizing privacy and security.
Next Steps and Questions:
- Are these issues expected behavior after a fresh reset on the latest version of GrapheneOS for Pixel 8, or do they indicate a deeper problem?
- Should I take any further troubleshooting steps or file a more formal bug report?
- I have full logs available and can share them securely if needed.
Additional Information:
If these logs reflect expected behavior after a reset, I’d appreciate any clarification. I’m happy to assist with further debugging or testing if required.
Thank you for your help.