Repository navigation
Rooted Features
Rooted Features adds advanced cellular and signaling checks that are not available from standard Android app access alone. These checks are useful for deeper diagnostics, but they depend on device root access, available radio logs, and vendor behavior.
Standard Android APIs intentionally limit low-level radio details for privacy and platform security. Rooted mode is useful when you need deeper telemetry to investigate suspicious behavior with more context.
This switch turns all rooted-only monitoring on or off in one place. Turning it off immediately disables rooted checks and returns scanning to non-root behavior.
This sets how often rooted diagnostics run. A faster interval can catch short-lived events more often, while a slower interval reduces load and battery impact.
This watches radio logs for silent signaling patterns associated with type-0 SMS behavior. It is useful for detecting hidden device-presence probes that may not appear as normal text messages.
This controls how many recent log lines are inspected each cycle for silent SMS markers. Higher values improve coverage but increase processing work.
This controls how often repeated silent SMS alerts can re-fire. Longer cooldowns reduce duplicate noise, while shorter cooldowns show repeated events quickly.
This enables deeper parsing of rejection details from radio logs. It is useful for understanding repeated registration failures and distinguishing random dropouts from persistent problems.
This controls how many recent log lines are scanned for reject details. Higher values improve context depth but use more processing each cycle.
This controls repeat spacing for reject-cause alerts. Longer cooldowns keep notifications cleaner, while shorter cooldowns expose rapid repeated rejects.
This enables checks for movement while channel identity remains fixed longer than expected. It is useful for identifying forced or abnormal channel behavior patterns.
This sets how many repeated samples are required before lock analysis can alert. Higher values require stronger evidence, while lower values respond faster.
This sets the minimum pinned duration before an alert can fire. Longer durations reduce false positives, while shorter durations increase sensitivity.
This sets how much movement must occur while channel identity stays pinned. Higher values require clearer movement evidence, while lower values can alert in smaller travel windows.
This sets the worst allowed location uncertainty for channel-lock checks. Lower values require cleaner location confidence, while higher values allow noisier samples.
This controls how often repeated channel-lock alerts can re-fire. Longer cooldowns reduce repeat noise, while shorter cooldowns make repeated behavior more visible.
The rooted diagnostics view helps confirm whether root commands and log access are working on the current device. If diagnostics are unavailable, rooted alerts may not trigger even when the toggle is on.
Rooted features improve visibility but they do not prove intent by themselves. Use repeated patterns over time and location, then combine them with non-rooted alerts for better confidence.