Skip to content
Jiumi
中 EN

Download and guide

About ten minutes from installing to reading your first record. Everything happens on the phone, with no root or computer.

Contents 01Before you start 02Download and install 03Choose how to start 04Start monitoring 05Reading the records 06Network and domains 07Managing apps 08Export and updates 09Good to know

01Before you start

  • A phone on Android 11 or later.
  • Starting with Wireless debugging needs Wi‑Fi; you can use root or Shizuku instead.
  • Wireless debugging is in Developer options. Some phones keep Build number under About phone › Version.

02Download and install

Jiumi App Reading the latest version…
  1. On the phone, tap Download APK, then open the file when it has downloaded.
  2. If the system blocks installing unknown apps, allow your browser to install apps as it suggests, then come back.
  3. Once installed, open Jiumi and choose how to start on its first page.

The APK is offered only from the project's GitHub releases. When Jiumi updates itself, it checks the size, SHA-256 and signing key before installing.

03Choose how to start

The first time you open Jiumi, pick a way to start, then follow the steps on the page: each ticks itself off, and the button at the foot always does the step at hand. All three work the same; Wireless debugging is recommended, and you can change it later under Settings › Environment.

Wireless debugging (recommended)No root. Pair once on this phone
  1. Allow notificationsYou enter the pairing code in Jiumi’s notification. Tap Allow notifications; if you refused before, allow it in system settings as prompted.
  2. Turn on Developer optionsTap Open About phone and tap Build number seven times until it says you are a developer, then come back. Some phones keep it under Version.
  3. Pair with Wireless debuggingTap Start pairing, turn on Wireless debugging and tap “Pair device with pairing code”. Keep that dialog open, pull down the notifications and enter the six-digit code in Jiumi’s.

You pair once. USB debugging is not needed; only ADB persistence uses it.

RootMagisk, KernelSU or APatch
  1. Allow notificationsThe notification shows the monitor’s status. Tap Allow notifications.
  2. Grant rootTap Authorize; your root manager asks once, and Jiumi checks again when you come back from it. Jiumi uses root only to switch to the Android shell identity and start the monitor, so it sees and does exactly what it does over Wireless debugging, and root is never kept.
ShizukuShizuku is installed
  1. Allow notificationsThe notification shows the monitor’s status. Tap Allow notifications.
  2. Start ShizukuIf it isn’t installed, tap Get Shizuku; then start it the way its app explains, with Wireless debugging or a computer. Shizuku must run as the shell, not with root; if you have root, choose Root instead.
  3. Allow Jiumi in ShizukuTap Authorize; Shizuku asks once whether Jiumi may use it.

04Start monitoring

On the Monitor tab, tap Start. The debugging connection closes as soon as the monitor runs; a “Monitoring” notification stays, and Stop, there or in Jiumi, ends the session.

Restarting the phone, updating Jiumi or turning off Developer options stops the monitor, and the card says Monitoring interrupted. Tap Resume to continue the same session; the gap is not counted as monitored time.

ADB persistence (optional)

With ADB persistence on in Settings, and USB debugging on too, Jiumi has the system open a local debugging port as well: until the phone restarts, the monitor can be started or resumed even without Wi‑Fi.

05Reading the records

Needs attention

At the top are just four things: sent data in the background, read sensitive data in the background, read the same data again and again, and kept trying after being refused. Open one to see how it is judged and which apps it covers.

Timeline

One record per line: the time, the app and what it did. Repeats of the same thing close together are merged, ×N counting them, and a burst of network connections folds into one line. At the top, narrow it to Background.

By type

Twelve groups, each named by what was done: Get location, Read device and SIM IDs, Access contacts and accounts, Access the clipboard, Connect to the network… Each opens the apps and the times.

Labels on a record

  • Done in the background The app was not on screen: running behind a notification, or switched away from.
  • Done with the screen off The screen was off when it happened.
  • Refused The app got nothing: the permission was refused, or the app does not hold it.

Jiumi would rather miss one than misreport one: calls that return only the app's own information are left out, and records with no known caller are not shown.

06Network and domains

By type › Connect to the network sums up by app: how many destinations, how much sent and received, those that sent most in the background first. Each app's Network activity lists every address it reached.

Record domains (optional)

Turn on Settings › Record domains and confirm the VPN once. Jiumi's VPN receives DNS queries only and passes them unchanged to the DNS servers of the network you are on; no other traffic goes through it. Connections then show the domains apps looked up, not just IP addresses.

  • Another VPN can't run while it is on.
  • With Private DNS set to a named provider, or in apps with their own encrypted DNS, those lookups are not seen.

07Managing apps

Under an app’s name on its page you can disable, enable or delete it, or remove a preinstalled app for this user. The app is backed up before deleting and can be installed again from Apps › Deleted; disabling can be undone any time and keeps its data. Disabled apps carry a snowflake badge and deleted ones a trash badge.

After every change, Jiumi reads the state back from Android to confirm it took effect. If Android refuses, it says why instead of quietly trying another way.

Permissions

In an app’s details, tap Permissions to see the permissions it declares, grouped by location, camera, contacts and so on, and turn each off or on. Manageable permissions turns them all off at once; turning it back on restores only the ones Jiumi turned off. Permissions the system locks are shown as read only.

Network access

In an app’s details, tap Network access and turn off Allow network access, and that app can no longer reach the network. It uses Android’s own firewall, not a VPN. The switch is locked, with the reason shown, when the app shares a UID with other apps, the rule was set by another tool, or Jiumi can’t confirm only this app is affected; phones without this interface say so too.

Jiumi warns before you touch something the phone relies on; core system components stay locked until you turn on Expert mode in Settings › Advanced.

08Export and updates

Settings › Export logs saves the records of a chosen range as a ZIP: a readable timeline, the raw tables and a note on each.

On opening, Jiumi checks for a new version at most every six hours (you can turn this off in About) and mentions each new version once. You can also come back here any time and install the latest over the old one; your records stay.

09Good to know

  • Jiumi knows which app, when, which kind of data, where it connected and how much it sent, never the content.
  • Reads that go around system services, such as reading files directly or system properties, are not seen; some system calls carry no method name and can't be classified.
  • Connection tables are read every five seconds; a shorter connection may show no address, though its traffic is still counted.
  • Disabling or deleting system components can break features, so confirm before you do. Jiumi is provided as is, with no promise that its records are complete.