Ok.
I understand trying to get Shizuku with Grapheneos is kinda 'pointless' - it defeats the point of a secure os. However, like alot in life, its the grey, not always black or white.
My question - is Grapheneos & Shizuku as insecure as running Lineageos/Stock. In my case, I would want Shizuku (wireless adb bugging) running all the time. I want to run a xposed framework module
I know, I know. You either have privacy or convenience. You can't have both. Maybe I want a blend, not perfect security and abit more convenience. Surely there are additional privacy features in Grapeheneos that still make it worthwhile ?
Or is it that by getting Shizuku to work, you blow a security hole so wide, you may has well just run LineageOS or stock Android ?
Here's what AI said...
The recommended best practices for running Shizuku securely on GrapheneOS involve several careful steps and considerations aimed at reducing security risks while enabling the desired functionality:
Understand the Risks: Using Shizuku requires enabling ADB debugging (usually wireless debugging), which inherently broadens the attack surface and weakens GrapheneOS's strong security model. It is generally discouraged on production daily driver devices unless you fully understand and accept the risks.
Disable Secure App Spawning: On GrapheneOS, you may need to disable "Secure app spawning" in system settings under Security for Shizuku to work properly.
Use Wireless Debugging Carefully: Enable wireless debugging in Developer Options only when needed. Pair devices carefully using the pairing code. Avoid leaving wireless debugging enabled persistently as it creates a network attack vector.
Keep Shizuku Updated: Use the latest official Shizuku version from trusted sources like GitHub or Google Play to ensure you have the latest security fixes and compatibility improvements.
Run Shizuku with Minimum Permissions: Only grant Shizuku the permissions it needs for your specific use case. Avoid enabling unnecessary permissions or settings.
Allow Background Operation: Make sure Shizuku is allowed to run in the background on GrapheneOS without restrictions or network access being limited, as some manufacturers disable background network access for apps, which can cause Shizuku not to work properly.
Monitor App Behavior: Regularly check that Shizuku or apps using it do not introduce suspicious network or system activity.
Restart After Reboot: Because of system limitations, Shizuku needs to be manually restarted after every reboot.
Avoid Root or Xposed Modules: If you are running GrapheneOS without root, ensure Shizuku and other apps do not rely on rooting or Xposed frameworks, which damage security.