-
-
Notifications
You must be signed in to change notification settings - Fork 112
FAQ
CAPod shows you the battery level of your AirPods (left, right, and case) on your Android phone. It can also show a popup when you open the case, display a home screen widget, and optionally pause/play audio when you take an AirPod out of your ear.
That's roughly it. Apple locks down most of their AirPods functionality to iPhones, so no Android app — CAPod included — can do things like control ANC, adjust EQ, change tap gestures, or update firmware. CAPod squeezes out everything that's technically possible.
All official AirPods and Beats devices are supported. Check the README for a full list of supported models.
Some fake/clone AirPods work too, but it depends on the clone — many don't broadcast the data CAPod needs.
If your device isn't detected or shows limited info, email support@darken.eu with the model. Adding new devices is usually straightforward once I have test data.
Some fake/clone AirPods work, some don't — it depends on whether the clone broadcasts Apple-compatible Bluetooth LE data. Higher-quality clones that mimic Apple's protocol may be detected, while cheap ones typically aren't. There's no way to know in advance without trying.
Apple's AirPods protocol has been reverse engineered, so in theory these features are possible. The blocker is actually an Android bug — Android currently can't establish the specific type of Bluetooth connection that AirPods require for settings changes.
This is tracked in our GitHub issue #215 and in the official Android bug report (12,000+ upvotes). If/when Google fixes this, CAPod will add support for these features.
Apple's public Bluetooth LE protocol only broadcasts battery in 10% steps (10%, 20%, 30%, etc.). This is what every third-party app gets.
CAPod can show 1% granularity if you extract the identity and encryption keys from the AirPods case using a PC (Windows, Linux, or macOS). Check the Key Extraction Guide in the wiki for instructions.
The case doesn't broadcast battery information on its own — it needs at least one AirPod inserted to report its battery level. This is an Apple protocol limitation, not a CAPod bug.
Tips:
- Make sure at least one AirPod is inside the case
- Open the case lid near your phone to trigger a fresh broadcast
- Case battery typically only updates when the case is open
Try these steps:
- Check your profile — make sure the device profile you created in CAPod actually matches the AirPods model you're looking for
- Check unmatched devices — on the dashboard, tap the button to show unmatched devices. If your AirPods show up there, your profile doesn't match correctly
- Run the Troubleshooter — found in CAPod's support section, it tests your phone's BLE capabilities and suggests compatible settings
- Reboot your phone — sometimes the Bluetooth stack just needs a fresh start
If nothing shows up at all, not even as an unmatched device:
- Your AirPods might be a fake/clone that doesn't broadcast Apple-compatible data
- Your phone's Bluetooth stack might be buggy (common with custom ROMs)
I can't do magic, but feel free to email support@darken.eu — maybe I can help.
CAPod doesn't connect or pair your AirPods — that's done through your phone's Bluetooth settings. CAPod only reads the Bluetooth LE data that your AirPods broadcast nearby. Pair your AirPods with your phone first via Android Settings > Bluetooth, then CAPod will pick up the battery and status info automatically.
CAPod does not track your location. Android requires location permission to access Bluetooth LE scan results — this is an Android system requirement, not CAPod's choice. The app declares neverForLocation in its manifest, meaning it explicitly tells the system it doesn't use location data.
Without this permission, Android simply won't give the app any Bluetooth LE scan results, and CAPod can't detect your AirPods.
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)
The required mode depends on which reactions you've activated (e.g., auto pause needs "Always").
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.
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.
Free features (always available):
- Battery level display (left, right, case)
- Basic device detection and info
- In-app battery view
Pro features:
- Home screen widget
- Auto pause/play when removing/inserting AirPods
- Auto connect
- Case open popup notification
- Connection popup notification
- Theme customization (dark/light mode, accent colors, Material You)
- Widget appearance customization
The Pro upgrade keeps the app ad-free and supports solo development. CAPod is open-source — the FOSS version on GitHub/F-Droid offers a sponsor/donation option instead.
CAPod relies on Bluetooth LE broadcasts to detect ear status, not a direct connection to the AirPods (which isn't possible due to an Android system limitation). This means there can be a delay between removing an AirPod and the pause triggering.
You can reduce the delay by increasing the scan interval in CAPod's settings.
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.
Some Pro features (auto pause, ear detection, popup) are limited by Apple's protocol and your specific phone model — paying doesn't change what's technically possible. Before purchasing, the free version lets you verify that basic detection works on your device.
If you believe something is broken rather than limited, email support@darken.eu with:
- Your phone model and Android version
- Your AirPods model
- What specifically doesn't work
Refunds are handled through Google Play within 48 hours of purchase, or contact support@darken.eu for help.
Some countries have Google Play payment restrictions (e.g., Russia). The FOSS version of CAPod on GitHub has the same features. You can also email support@darken.eu for alternative options.
This is a rare bug reported on some devices (notably OnePlus). Try:
- Check CAPod's notification settings — make sure vibration is off for the notification channels
- Update to the latest version
- If it persists, email support@darken.eu with your phone model and CAPod version
This can happen if your profile isn't strict enough. For example, if you only selected the device type, and someone nearby has the same model, CAPod might pick up their AirPods instead.
The longer your own AirPods are near your phone, the more accurate detection becomes. For the best accuracy, enter the identity key (IRK) and encryption key in your device profile — check the Key Extraction Guide for instructions.
No. CAPod treats devices based on the data they broadcast. If a fake sends exactly the same data as real AirPods, CAPod can't tell the difference. The app is not an authenticity checker.
If AirPods are detected briefly but then disappear, this is often a Bluetooth stack issue in your phone's ROM — especially if it works for a short time after a reboot.
Try:
- Use the Troubleshooter in CAPod's support section — it will test and suggest compatible settings
- Manually try the compatibility options in CAPod's settings
If detection works while the app is open but stops when it's in the background, it's likely a battery optimization issue:
- Disable battery optimization for CAPod
- Some manufacturers (Xiaomi, Huawei, Samsung) aggressively kill background apps — check dontkillmyapp.com for your device
- Email: support@darken.eu (the developer reads every message)
- GitHub Issues: github.com/d4rken-org/capod/issues
- Discord: discord.gg/rrxxng35jq
When reporting issues, include your phone model, Android version, AirPods model, and a description of what's happening. Debug logs from CAPod's settings are extremely helpful.