REA's Android package path uses headless JADX for questions about DEX methods, while device and resource work have separate requirements. Begin with an APK you may inspect, record its build and hash, and identify the component behind one visible feature. A readable decompilation helps navigation; runtime behavior requires a separate authorized test.
Choose the APK layer
Inspect package identity, manifest and resources before following DEX methods. Use code references for a calculation and resource decoding for assets or XML. Native libraries inside an APK need a different path. Confirm the full JDK and headless JADX setup in official documentation.
Close with a check
Keep the method and source location beside relevant constants. Test a reconstructed rule against reference vectors or a controlled app scenario when permitted. Distinguish an observed result from an inference about all app versions.
Requirements & evidence
- Resource type
- Guide
- Category
- Unknown
- Host platforms
- Unknown
- Targets
- android
- Level
- Intermediate
- Source checked
- 2026-11-03T10:04:43.632194+00:00
Primary sources
- https://raw.githubusercontent.com/morluto/rea/main/docs/android-analysis.md
- https://raw.githubusercontent.com/skylot/jadx/master/README.md
Source descriptions establish documented scope. They do not establish that every workflow has been reproduced by AI Craft Pad.