TySS-Dev/capod
1
0
Fork 0
mirror of https://github.com/d4rken-org/capod.git synced 2026-09-14 18:26:11 -04:00
Code Issues Packages Projects Releases Wiki Activity

docs(faq): Drop the removed monitor mode, scanner mode and scan interval settings 

Monitor mode was removed in 5.1.2 and scanner mode in 5.1.6; both are now
derived from profile state. The FAQ still told users to pick between them and
to raise a scan interval that never existed in the current app. Replaces those
with the actual levers: the paired device assignment on the profile, the auto
connect toggle, and the hardware batching compatibility option.
darken
2026-08-21 09:42:58 +02:00
parent 9a39867d28
commit cbfd03c7a2
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
FAQ.md
+9 -8
@@ -91,18 +91,19 @@ Without this permission, Android simply won't give the app any Bluetooth LE scan
Android requires a foreground service notification for apps that run in the background. CAPod needs this to keep monitoring your AirPods via Bluetooth LE.
How much CAPod runs depends on the **monitor mode** setting:
- **When app is open** — only monitors while you're in the app, no persistent notification needed
- **When device is connected** — monitors when your AirPods are paired/connected
- **Always** — continuous monitoring (uses more battery)
There is no monitor mode or scanning mode setting to pick. CAPod works out how much it needs to run from your device profile:
The required mode depends on which reactions you've activated (e.g., auto pause needs "Always").
- **No paired Bluetooth device assigned to a profile** — CAPod only updates while the app is open. Nothing runs in the background and there's no persistent notification, but reactions like auto pause won't work either.
- **A paired device is assigned** — CAPod monitors in the background while that device is connected.
- **Auto connect is enabled on that profile** — CAPod monitors continuously, so it can reconnect your AirPods for you.
If you want to hide the foreground notification but still run in "Always" mode, enable the **extra notification** setting in the app. This way the foreground notification can be muted in your system settings, and you'll only see a notification when a device actually connects.
So the way to trade battery against features is the profile itself: assign a paired device under Profile settings > Paired device, and turn Auto connect on or off. How aggressively CAPod scans for Bluetooth LE broadcasts is also picked automatically, based on whether your AirPods are currently connected and whether the app is in the foreground.
If you want to hide the foreground notification but keep monitoring, enable the **extra notification** setting in the app. The permanent "Device status" notification can then be muted in your system settings, and you'll only see a notification when a device actually connects.
### Samsung warns that CAPod uses a lot of battery in the background
Samsung's device maintenance app flags any app running a foreground service as "high background consumption" — even if the actual battery usage is low. This is how Samsung reports it, not necessarily how much battery CAPod actually uses. You can check real battery usage in Settings > Battery > CAPod. If CAPod shows excessive drain, try switching from "Always" to "When device is connected" monitor mode.
Samsung's device maintenance app flags any app running a foreground service as "high background consumption" — even if the actual battery usage is low. This is how Samsung reports it, not necessarily how much battery CAPod actually uses. You can check real battery usage in Settings > Battery > CAPod. If CAPod shows excessive drain, turn off Auto connect for the profile, which drops CAPod from continuous monitoring to monitoring only while your AirPods are connected.
### What does the Pro/upgrade version include?
@@ -126,7 +127,7 @@ The Pro upgrade keeps the app ad-free and supports solo development. CAPod is op
On phones that have the updated Android Bluetooth stack, CAPod 5.0+ can supplement BLE broadcasts with an AAP connection, which generally makes ear detection faster and more reliable. On phones that haven't received the fix yet, CAPod has to rely on BLE broadcast polling alone, so some delay is inherent between removing an AirPod and the pause triggering.
You can reduce the delay by increasing the scan interval in CAPod's settings.
Some delay is inherent when CAPod has to rely on BLE broadcasts alone, and many phones make it worse by grouping those broadcasts before handing them over. You can cut that down under Settings > General > Compatibility options > "Disable hardware batching", which makes the system forward Bluetooth LE data immediately instead of in batches. It costs a little battery.
A common issue: on some AirPods firmware versions, the in-ear status only updates for the primary pod (the one using the microphone), not both. This appears to be a bug in Apple's firmware. If auto pause only works when you remove one specific AirPod, this is likely the cause.