9c728deebbed51145933f401d9fcc880c42fcd92
Every scoped app's cold start pays whatever cost the hook installation itself takes, so it's the one place worth trimming here — there's no standing service or background work anywhere else in the module. Previously any enabled feature caused both Settings.Secure and Settings.Global to get hooked with the full combined key set, even though each key only ever lives on one of them (accessibility/mock-location keys are Secure-only, adb/dev-options keys are Global-only). Splitting the key maps by actual canonical class means an app that only needs e.g. ADB+dev- options hidden skips hooking Settings.Secure entirely, roughly halving the reflective hook-install calls for that case. Co-Authored-By: agent <agent@bdeshi.space>
Languages
Kotlin
94.6%
Shell
5.4%