Tune Sentry noise filters after first week of data

[thejaustin]

Summary

After the first week of production Sentry data, review the Issues list for recurring noise and update the filterShizukuNoise() function in HexodusApplication.kt accordingly.

What to look for

• Any exception types appearing in high volume that are expected/non-actionable
• Exceptions from Samsung system services that fire during theme application
• Binder-related exceptions not currently filtered (e.g. android.os.TransactionTooLargeException from overlay service)
• Errors from Shizuku permission flows that are user-facing, not bugs

Where to update

app/src/main/java/com/hexodus/HexodusApplication.kt → filterShizukuNoise()

Additional filters can also be set in Sentry dashboard → Project Settings → Inbound Filters without needing a code change.

Acceptance criteria

• Reviewed first week of Sentry data
• No high-volume noise issues in the default Issues view
• Crash-free session rate is accurate (not diluted by expected errors)