ATS Mini V4 Battery Care & Runtime Optimization
What You're Working With
An 800mAh internal lithium battery — modest capacity by modern-device standards, and genuinely worth understanding since this receiver's power management has some real quirks specific to its DIY/hobbyist hardware lineage.
The No-Power-Switch Reality
Stock hardware has no physical power switch — power is entirely software controlled via a long-press gesture that triggers deep sleep. Deep sleep genuinely reduces current draw significantly, but it's not the same as being fully off — some background drain continues. If you've flashed community firmware, be aware some versions repurpose the long-press gesture for a different function (a menu action rather than power control), which can mean there's no software-level way to power down at all on that specific firmware build.
The Physical Power Switch Mod
Given the above, a genuine physical power switch modification is a commonly recommended hardware mod in the community, specifically to give you a real "off" state that stops battery drain entirely regardless of what the current firmware's long-press gesture does. This requires opening the case and some basic soldering — a worthwhile project if you're using the receiver intermittently and don't want to think about slow standby drain between sessions.
Charging
USB-C charging, same cable used for firmware flashing — plug in, the display or an LED indicator (varies by hardware batch) should show charging status. Avoid leaving it on a charger indefinitely at 100% for extended periods if you're not using it — general lithium battery longevity best practice applies here same as any other lithium-powered device (partial charge for long-term storage is gentler on the cell than sitting at full charge for weeks).
What Actually Drains the Battery Fastest
- Display brightness — if your firmware exposes a brightness setting, this is usually the single biggest controllable power draw during active use.
- WiFi (on community firmware builds that support it) — leaving WiFi enabled when you're not actively using the web UI or downloading station data draws meaningfully more power than WiFi-off operation.
- Bluetooth (experimental, newer firmware) — similarly, only worth enabling when actively using BLE control, not left on by default.
- Speaker volume — driving the internal speaker at higher volumes draws more current than headphone listening at a comparable perceived loudness, due to the amplifier's power draw.
Extending Runtime for Field/Portable Use
- Lower display brightness to the minimum comfortably readable level.
- Disable WiFi/Bluetooth if your firmware has them enabled by default and you're not actively using either.
- Use headphones rather than the internal speaker for extended listening sessions if runtime matters more than convenience in that moment.
- If you've done the physical power switch mod, genuinely power off between sessions rather than relying on deep sleep for anything beyond short breaks.
Realistic Runtime Expectations
Actual battery life varies significantly based on the factors above plus which firmware you're running (WiFi-capable community firmware genuinely draws more than simpler stock firmware when WiFi's active) — rather than trusting a single quoted runtime figure, it's worth doing your own rough test at your typical settings to know what to actually expect for your use pattern.