Skip to the content.

ZORON-X Documentation

Welcome to the official documentation for ZORON-X, the ultra-intelligent power conservation engine for Android devices.

The ZORON-X Philosophy

Zoron-X abandons traditional continuous-throttling and static power profiles. Instead, it utilizes an aggressive Race-To-Idle strategy combined with deep contextual awareness:

  1. Execute Rapidly: Workloads are executed in highly optimized microbursts. We boost frequencies and un-park cores temporarily to finish the task as fast as possible.
  2. Deep Sleep Mastery: Once the task completes, the system is immediately forced back into a suspended state.
  3. Batching: Network and alarm wakeups are aggregated and processed simultaneously rather than waking the device repeatedly.
  4. Context Awareness: The device shouldn’t run a generic “powersave” mode when you’re gaming. Zoron-X intelligently detects your environment (screen state, touch frequency, active app, battery state) and adapts on the fly.

Our ultimate target is to achieve the Maximum Deep Sleep Time Ratio without compromising on UI smoothness, instant touch responsiveness, or notification reliability.

Core Algorithms

1. Intent Prediction Engine

The zoron_intent_engine runs completely in the background without relying on heavy Android dumpsys commands. It reads directly from raw hardware paths (sysfs and /dev/input/event*) to monitor:

Based on this, it predicts the user’s intent and transitions the device seamlessly between five distinct states:

2. Autopilot (UsageStats Heuristic Mode)

Using Android’s UsageStatsManager, the Autopilot service scans foreground activity every 10 seconds.

3. Delta-Based Fastpath

Switching power profiles traditionally causes UI stutter due to rebuilding cpuset configurations and resetting CPU governor matrices. Zoron-X utilizes a “Fastpath” engine (zoron_fastpath.sh) that intercepts profile switch commands. It compares the requested sysfs values against the currently applied sysfs values. Only deltas (changes) are actually written to the kernel. This eliminates micro-stutters during dynamic transitions and drastically lowers CPU overhead by up to 90%.

4. Microburst Engine

When a sudden heavy workload is detected, Zoron-X triggers a microburst. It instantly forces the CPU into performance mode, completes the execution in milliseconds, and then uses the Fastpath engine to immediately drop back to the standard profile. This guarantees snappiness without sustained battery drain.

5. Process Tiering Monitor

The zoron_process_monitor periodically scans /proc to evaluate running apps. It scores them based on OOM adjustments, CPU time consumed, and current state, assigning tiers (Foreground, Background, Cached, Dormant). Misbehaving background apps are aggressively frozen to prevent wakelocks.

Root vs. Non-Root Compatibility

ZORON-X supports both Rooted (Magisk/KernelSU) and Non-Rooted devices natively.

[!IMPORTANT] Recommended for Root Devices: ZORON-X is designed primarily for rooted devices to achieve optimal results. Non-root fallback mode is recommended only when the device has a heavily worn-out battery that cannot be replaced.

Why Do Rooted Devices Require Explicit Battery Savers?

Rooted devices are often modified with custom ROMs, third-party kernels, and administrative tweaks. These custom packages frequently bypass standard OEM power configurations:

Due to these factors, rooted devices require an explicit battery saver like ZORON-X to actively park unused cores, throttle scaling governors, batch doze alarms, and restrict aggressive background threads.

Why Do Stock (Non-Rooted) Devices Not Require It?

Stock non-rooted devices running factory firmware (Pixel, Samsung, OnePlus, etc.) are already tuned at the hardware level by the OEM’s battery engineers:

Because stock devices are highly optimized out-of-the-box, adding third-party battery savers can introduce redundant background overhead.

ZORON-X Non-Root Fallback Engine

ZORON-X provides a Non-Root Fallback mode for cases where a user has a stock device with a heavily degraded (worn-out) battery that cannot be physically replaced. In this fallback mode, ZORON-X runs a Java-based daemon to apply supplementary settings-level optimizations:


Getting Started

  1. Download the latest release from GitHub.
  2. Flash the module zip via Magisk or KernelSU.
  3. Reboot your device.
  4. Open the Zoron-X companion app to monitor real-time telemetry, battery graphs, and configure Autopilot settings.