Battery Page (Overview)

🔋 Battery Page — Overview & How to Use

The Battery page in CellHasher Control lets you spoof battery values and manage power-related behavior for single devices or entire clusters. This is essential for stable, long-running automation: many Android devices still check battery state even when hard-wired, and letting the system think the battery drained to 0% can cause unexpected reboots or throttling. Use the Battery page to keep devices stable and avoid downtime.

Important: If a device reports 0% battery (even when hard-wired) it may reboot or throttle. Always set a safe battery level (e.g., 100%) and a reasonable temperature (≈25°C) for continuous operation.

🔎 What you see on the Battery page

  • Device Selection panel (top): Select individual device cards or use Select All to target many devices at once. Each card shows current spoofed battery %, temp, and charge state.

  • Battery Automation (left): Pre-defined Battery Sets (Set 1, Set 2, etc.) that you create and apply. Each set stores:

    • Battery Level (%)

    • Battery Temperature (°C)

    • AC Charging enabled/disabled

  • Battery Controls (right): Quick action buttons for:

    • Enable / Disable AC Charging

    • Enable / Disable USB Charging

    • Unplug Device (simulate unplug)

    • Set to Full (100%)

    • Reset Battery State (clear spoof and return to real device values)

    • Custom-level input fields (set a numeric battery % or temperature)

  • Apply buttons: Apply the selected set to your selected devices.

⚙️ Why spoof battery values (and how it helps)

Many phones and tablets still run battery checks even when powered by a chassis. If the system believes the battery is draining to 0% it may:

  • Force reboots (device returns to boot screen)

  • Trigger thermal or battery-protection profiles (throttling)

  • Stop background tasks or automation flows

By spoofing stable values you:

  • Prevent unexpected reboots

  • Maintain consistent performance and behavior

  • Avoid OS-level battery safety features that would otherwise interrupt automation

Recommended baseline for continuous operation:

  • Battery Level: 100%

  • Battery Temperature: ~25°C

  • AC Charging: Enabled (if chassis supplies power)

🧭 How to use Battery Automation (step-by-step)

  1. Select devices at the top (individual cards or Select All).

  2. In Battery Automation, either:

    • Use an existing set (click Apply Set X)

    • Or create a new set: click + Add Battery Set, choose level & temp, toggle AC charging, then Save.

  3. Click the set’s Apply button — the selected devices will receive the spoofed battery values.

  4. Verify device cards update to show the new battery % and temperature.

⚡ Quick Actions

  • Set to Full (100%) — Instantly sets selected devices to 100% battery. Use for immediate stabilization.

  • Reset Battery State — Clears spoofing and returns devices to their real readings. Use only for testing or troubleshooting.

  • Enable/Disable AC or USB Charging — Toggle charge source simulation to match your physical setup.

  • Custom Level / Temp — Enter a numeric value and click Set Level / Set Temp to apply a one-off spoof.

🧰 Examples & Best Practices

  • Long-running automation / miners / farms:

    • Apply a Battery Set with 100%, 25°C, AC charging enabled.

    • Run a scheduled task to re-apply the set every X hours if your setup resets battery state on reboot.

  • Testing or power-cycling scenarios:

    • Use Reset Battery State after tests to return devices to real battery reporting.

  • When swapping devices or hubs:

    • Verify ADB and device connectivity before applying battery sets. If a device shows 0% unexpectedly, set it to 100% immediately to avoid automatic reboot.

🩺 Troubleshooting

  • Spoof didn’t apply / values unchanged:

    • Ensure the device is selected and authorized (ADB keys or USB authorization accepted).

    • Check ADB connection (Reset ADB on Settings page if stuck).

    • Verify the device supports battery spoofing (some OEM firmwares heavily restrict ADB hooks).

  • Device reboots after spoof applied:

    • Confirm spoof values (set to 100% and 25°C).

    • Ensure AC charging is enabled if the chassis supplies power.

    • Check system logs (Terminal / Device logs) for OS-level reasons.

  • Spoof disappears after device restart:

    • Battery spoofing is ephemeral — re-apply using an automation set or script at boot.

    • Consider adding a startup automation to apply the desired Battery Set on device reconnect.

🔁 Automating re-application

For clusters where devices may reboot, create an Automation Flow that:

  1. Waits for device online event

  2. Applies your preferred Battery Set (100% / 25°C / AC on)

  3. Logs success and retries on failure

This prevents manual intervention after reboots and keeps fleets stable.

✅ Quick Checklist before running automation

PreviousNetwork Page (Overview)NextScreen Mirroring (Overview)

Last updated