Choosing protection options
Core protection is always on. Turn on the rest to match your threat model and your users' environments.
Core protection (always on)
DEX packing with AES-256-GCM encryption, startup anti-debug/anti-Frida key entanglement, and O-MVLL native obfuscation are applied to every build by default.
Obfuscation options
String encryption and arithmetic/control-flow obfuscation make code harder to read in a decompiler. They're ART verifier-safe with automatic fallback.
RASP detections
Hook/Frida detection and debugger detection have very low false positives and are recommended. Tamper detection (self-checksum, APK) catches integrity violations.
Environment detections (false-positive trade-off)
Root/emulator/ADB detection can also catch legitimate users (developers, custom ROMs, testing), so they're opt-in. All clean-exit by design; enable them selectively for higher-risk apps (payments, games).
A recommended starting point
Start with core protection + string/code obfuscation + Frida/hook & debugger detection + monitoring, then add root/emulator/ADB based on your threat model.