Using Droynis

From a finding
to a decision.

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.

You stay in control.

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

Read. Decide.
Check again.

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.

Open a finding

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.

Choose what to change

Use the Settings link to review the relevant setting. A notice may reflect a deliberate choice; the explanation gives you context.

Scan again

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

Choose how much
Android can show you.

72 Base checks, plus 18 ADB, 9 Shizuku and 9 Root checks in the beta catalog. Device and Android-version support still apply.

72 checks · no setup

Base access

Start with what Android makes available. No computer, Shizuku or root required.

  • Device integrity and lock screen settings
  • App permissions and suspicious app indicators
  • Network and radio settings exposed by public APIs

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

Understand the score.
Keep the context.

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 weights
SeverityWeight
Critical10
Warning5
Notice2
Info0

Mute a check you cannot act on

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.

Trust an app intentionally

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

Keep a record.
Share on your terms.

Markdown

A report you can read

Save or share an audit from the app’s menu. Markdown keeps the findings readable without requiring Droynis to send them anywhere automatically.

JSON

A report you can compare

JSON keeps a stable order so tools such as diff can compare two scans. Values Android could not provide remain explicit.

Optional schedules

Keep an eye on changes

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.

Personal details are hidden by default.

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.

App screenshot