Run the audit
The Base tier needs no setup. Droynis reads public Android APIs and reports what the current user or profile allows it to see.
Using Droynis
Start with the access your phone already allows. Open a finding to see its evidence, explanation and Settings link. Decide what to change, then scan again.
The audit never changes settings or removes apps. Extra access adds visibility; it does not turn Droynis into an automatic repair tool.
A practical workflow
The Base tier needs no setup. Droynis reads public Android APIs and reports what the current user or profile allows it to see.
Read the value, its source, why it matters and what you can do. If Android will not provide a reliable value, the result is Unknown.
Use the Settings link to review the relevant setting. A notice may reflect a deliberate choice; the explanation gives you context.
After your changes, scan again to see the updated findings. You can export a report when you want to keep or compare the result.
Optional access tiers
72 Base checks, plus 18 ADB, 9 Shizuku and 9 Root checks in the beta catalog. Device and Android-version support still apply.
Start with what Android makes available. No computer, Shizuku or root required.
Grant two permissions once from a computer. These grants unlock read-only dumpsys checks.
adb shell pm grant io.github.capitan0n.droynis android.permission.DUMP
adb shell pm grant io.github.capitan0n.droynis android.permission.PACKAGE_USAGE_STATSConnect the phone with USB debugging enabled. These commands grant Droynis permission to read diagnostic and usage data. Scan again, then turn USB debugging off. Grants survive a reboot; pm revoke removes them.
Use Shizuku for settings ordinary apps cannot read. Also covers the Base and ADB checks.
Read the Shizuku project. Droynis uses a fixed set of allowed reads, not an unrestricted command prompt.
Optional, off until you turn it on. Runs a fixed set of read-only commands and includes earlier tiers.
Root changes the security model of your phone. It is an optional access tier, not a requirement to use Droynis.
108 beta catalog checks across all tiers. Availability also depends on Android version and device support. More access gives visibility; Droynis still does not change settings.
Reading the results
Passed weight ÷ scored weight × 100
The score includes passed and failed checks. Any critical failure caps it at 40, so many small passes cannot hide one critical gap.
Unknown, N/A and muted checks do not count. If no scored check is available, there is no score.
| Severity | Weight |
|---|---|
| Critical | 10 |
| Warning | 5 |
| Notice | 2 |
| Info | 0 |
For example, a patch only the manufacturer can ship. Muting excludes it from the score; it does not turn a failed check into a pass.
An app may need broad access for its purpose. Trusting it stops checks from counting it, while keeping the app visible in the evidence.
Reports and scheduled scans
Save or share an audit from the app’s menu. Markdown keeps the findings readable without requiring Droynis to send them anywhere automatically.
JSON keeps a stable order so tools such as diff can compare two scans. Values Android could not provide remain explicit.
Daily or weekly scans are off by default. When enabled, they can notify you of what got worse or was fixed; Android battery limits can delay scans.
Export hides IP addresses, DNS and proxy servers, trusted computers and Wi-Fi names by default. Review a report before you choose to share it.