ORBII

Great question, and you're right to push on it, most "always listening" apps quietly die on Xiaomi/Realme/Vivo/Oppo and never tell the user. We treated that as the core engineering problem, not an afterthought. A few layers: 1. It's a foreground service, not background work. The listener runs as a microphone-type foreground service with a persistent notification and a wake lock. Android protects those far more than ordinary background tasks, that alone survives on most phones. 2. We don't pretend it runs forever. You arm it for a window (4 / 12 / 24 hours), and we send reminders before it lapses, so you always know whether you're covered. No false sense of protection. 3. Heartbeat + self-heal. The service writes a pulse every ~30 seconds. If your phone's battery manager kills it anyway, the app detects the gap the next time you open it, restarts it, and tells you it happened. A silent failure becomes a visible, recoverable one, which is the honest way to handle OEMs you can't fully control. 4. Device-specific setup. On phones known to be aggressive, we detect the skin (MIUI/HyperOS, ColorOS, Funtouch, One UI) and walk you through the exact Autostart + "no battery restrictions" toggles, with one tap straight into those settings. We also request the Doze/battery-optimization exemption and re-arm after a reboot. 5. It is not the only line of defense. Manual SOS, your trusted circle, one-tap 112, and an offline SMS path all work regardless of whether the background listener is alive. So even in the worst case where an OEM kills the service, you are never left with nothing. The honest version: no app gets 100% background survival on every OEM, anyone who claims that is lying. Our goal isn't "never dies", it's "when the phone interferes, you find out, it heals itself, and there are backup layers that don't depend on it at all."