Skip to content

Fix single-bud NPE crashes, BluetoothSocket reflection, and add rootless Charging Case Sounds - #764

Open
bshea-1 wants to merge 5 commits into
librepods-org:mainfrom
bshea-1:fix/airpods-stability
Open

Fix single-bud NPE crashes, BluetoothSocket reflection, and add rootless Charging Case Sounds#764
bshea-1 wants to merge 5 commits into
librepods-org:mainfrom
bshea-1:fix/airpods-stability

Conversation

@bshea-1

@bshea-1 bshea-1 commented Sep 3, 2026

Copy link
Copy Markdown

Summary of Changes

This PR resolves multiple background service crashes, improves Bluetooth socket reflection compatibility, optimizes notification resource usage, and adds rootless Charging Case Sounds toggle support.

1. Background Stability & Crash Prevention

  • Single-Bud Battery NPE: In AirPodsService, querying battery state when only one earbud is connected or before battery packets arrive caused multiple NullPointerException crashes on ?.level!!. Added a safe getDisplayBatteryLevel() helper to coalesce left and right bud levels safely.
  • Intent Extra Null Safety: Handled nullable intent.getParcelableExtra("device") without force unwraps (!!) and guarded device access.
  • Array Bounds Check: Added bounds check in onBatteryInfoReceived() before indexing battery status elements.

2. Bluetooth Connection Hardening

  • Socket File Descriptor: Fixed invalid fd = 1 parameter (STDOUT_FILENO) passed to reflected BluetoothSocket constructors (changed to -1 for uninitialized socket state).
  • Dynamic Constructor Fallback: Added dynamic constructor inspection fallback to match available constructor signatures across various Android vendor builds.
  • Early Hidden API Exemption: Loaded bluetooth_socket early in LibrePodsApplication.onCreate().

3. Battery & Notification Optimization

  • Removed high-frequency updateNotificationContent() calls from the tight raw socket packet read loop (while (socket.isConnected)), preventing SystemUI notification spam and reducing CPU wakeups.

4. Media Controller Typo Fix

  • Fixed MediaController conversational awareness default volume calculation from / 0.4 to * 0.4.

5. New Feature: Charging Case Sounds Toggle (Rootless)

  • Added Capability.CASE_SOUNDS for AirPods Pro 2 and AirPods 4 ANC.
  • Exposed a toggle under Connection Settings controlling IN_CASE_TONE_CONFIG (0x31 over AACP), allowing rootless control of case speaker chimes.

fix(android): resolve background NPEs, socket reflection, and add cas…
89036d0 
…e sounds toggle

- Fix KotlinNullPointerException on single-bud usage and uninitialized battery states in AirPodsService
- Fix BluetoothSocket reflection constructor with valid fd (-1) and add dynamic fallback resolver
- Add rootless Charging Case Sounds toggle for AirPods Pro 2 and AirPods 4 ANC via AACP
- Remove per-packet notification updates in raw socket read loop
- Fix default conversational awareness volume calculation in MediaController
- Add NativeBridge and ProGuard hardening for JNI bindings
@hanslauch325-eng

hanslauch325-eng commented Sep 3, 2026

Copy link
Copy Markdown

hey is there a way you can make the toggle sounds setting work for the AirPods Pro 3? I could test if you want

@bshea-1

bshea-1 commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Hi @hanslauch325-eng, I just pushed a fix to support the case sounds toggle for AirPods Pro 3! Could you test it out and see if it works for your device?

How it was implemented:

  1. Model Recognition for Case Model A3122: Added "A3122" (the AirPods Pro 3 MagSafe Charging Case model number) to AirPodsPro3.modelNumber alongside A3063, A3064, and A3065, ensuring the app properly resolves the device and its Capability.CASE_SOUNDS when queried.
  2. Fixed AACP Status Caching Bug: In AACPManager.setControlCommandStatusValue, previous control states were only being removed if the new byte array matched the old one, causing toggled states (0x01 enabled vs 0x02 disabled for IN_CASE_TONE_CONFIG 0x31) to leave duplicate stale entries that prevented the UI from reflecting the updated state. We now ensure existing identifiers are cleared before inserting the new status.
  3. Preference Persistence & Reconnection Sync: Added caseSoundsEnabled state persistence via SharedPreferences in AirPodsViewModel and configured AirPodsService to re-apply the user's stored case tone configuration over AACP upon reconnecting.
  4. Extended AACP Command Support: Registered IN_CASE_TONE_VOLUME (0x40) to handle incoming tone status packets streamed by newer generation firmware.

Please let me know if it works for you!

@bshea-1

bshea-1 commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

If you'd like an easy way to download and test without building from source, pre-built signed Release APKs are published on the release page:

📦 Release Downloads:

🔗 Release Page: LibrePods v1.0.0-rc2 (AirPods Pro 3 & Stability Fixes)

@hanslauch325-eng

hanslauch325-eng commented Sep 4, 2026

Copy link
Copy Markdown

Hey thank you really much, sadly it did not work for me I dissabled the charging case sounds but it still played them. I collected some logs I hope they can help
_data_user_0_me.kavishdevar.librepods_files_logs_airpods_log_20260904_172000.txt

@bshea-1

bshea-1 commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Hey @hanslauch325-eng, thank you so much for testing and providing the logs! Those logs were extremely helpful in diagnosing what's going on.

What the logs showed:

  1. The AACP socket and command succeeded: The app connected to your AirPods Pro 3 and successfully sent the disable tone packet: 
    09-04 17:20:22.852 D AACPManager: Sending packet: 04 00 04 00 09 00 31 02 00 00 00
09-04 17:20:22.852 D AACPManager: Control command: 31 - 02
  2. How AirPods Case Sync works physically:
    Bluetooth on Android connects to the earbuds, not directly to the charging case. When you toggle the switch in the app, the earbuds receive the 31 02 command and store it in their internal NVRAM.
    To transfer this setting to the case, you must:
    • Put both earbuds back inside the charging case.
    • Close the lid and wait ~5 seconds.
      During those 5 seconds, the earbuds flash the new configuration into the case microcontroller via the physical charging pin contacts. If the earbuds are in your ears when you toggle the setting and the case is tested without docking them first, the case won't know the setting changed yet.

Additional updates in this new build:

  • Extended Feature Handshake (0x4D): Added the extended initialization packet (04 00 04 00 4D 00 0E 00...) during connection, which newer AirPods Pro 2 / Pro 3 firmware requires to unlock extended registers.
  • Case Tone Volume Mute (0x40): In addition to IN_CASE_TONE_CONFIG (0x31), the app now also sends IN_CASE_TONE_VOLUME (0x40) with volume 0x00 on disable and 0x50 on enable to ensure tones are fully muted.

Updated Download:

You can download the updated build here:
app-foss-release.apk (v1.0.0-rc2 with latest fixes)
(Release page: https://github.com/bshea-1/librepods/releases/tag/v1.0.0-rc2-airpods-fix)

Let me know if placing the buds in the case and closing the lid for ~5s after toggling resolves it for you!

@hanslauch325-eng

hanslauch325-eng commented Sep 4, 2026

Copy link
Copy Markdown

Hey,
I installed the new APK and disabled the charging case sounds with the toggle, then placed the AirPods back in the case and I waited for like 10 seconds. After that I plugged the case in for charging but it still makes the sounds, I also tried with double tap to put them in paring mode and the case stil makes the sound. Anyway here are the logs again.

_data_user_0_me.kavishdevar.librepods_files_logs_airpods_log_20260904_201055.txt

@bshea-1

bshea-1 commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Hey @hanslauch325-eng, I really appreciate you testing this and sharing the updated logs.

Insights from the new log:

  1. The Chime Volume channel (0x1F): In the log, when querying all device registers, your AirPods Pro 3 reported: 
    Control command received: 1f - 64 50  (CHIME_VOLUME: 100% max, 80% current)
    On newer AirPods Pro 3 / Pro 2 firmware, case sounds and chimes are tied across three registers: IN_CASE_TONE_CONFIG (0x31), IN_CASE_TONE_VOLUME (0x40), and CHIME_VOLUME (0x1F).
  2. Pairing Mode Tones vs Charging Tones:
    • Pairing mode chime: When triggering pairing mode (double-tapping front capacitive sensor / holding setup button), Apple's case microcontroller plays the pairing chime directly from hardware ROM as a physical safety/confirmation beacon — even on an iPhone with "Charging Case Sounds" turned off, entering pairing mode will always sound.
    • Charging plug-in sound: This is the sound controlled by software settings.

What was updated in this build:

  • Multi-channel Muting: The app now synchronizes all tone channels (0x31, 0x40, and 0x1F) together, setting chime/tone volume to 0x00 on disable and restoring it on enable.
  • Dispatch Robustness: Added remaining control command definitions (0x3E, 0x3F, 0x41) and prevented early returns in packet dispatching so all tone packets are sent without dropping.

Download Link:

app-foss-release.apk (Updated Build)
(Release page: https://github.com/bshea-1/librepods/releases/tag/v1.0.0-rc2-airpods-fix)

Please try installing this update, toggling the switch, and placing the buds in the case with the lid closed for a few seconds before testing the charger plug-in sound. Thank you again!

@hanslauch325-eng

hanslauch325-eng commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

Hello,
Sadly it is still not working I tried it again disabling then putting them back in the case waiting for 10 seconds and plugging the case in it still makes the charging case sounds

_data_user_0_me.kavishdevar.librepods_files_logs_airpods_log_20260904_222618.txt

@bshea-1

bshea-1 commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Hey @hanslauch325-eng,

Thank you so much for taking the time to test this and capture detailed logs across multiple iterations. Your help was genuinely invaluable in understanding what was happening behind the scenes.

Why Case Sounds Cannot Be Toggled From Android:

After performing a deep-dive analysis into the logs and Apple's firmware architecture:

  1. The Case Has No Direct Bluetooth Radio: The charging case microcontroller has no Bluetooth connection to Android; it only communicates with the earbuds through the physical charging pogo pins (1-wire serial bus) when the buds are docked inside.
  2. Apple's Authenticated Cryptographic Sync: On modern AirPods Pro firmware, the earbuds require an authenticated iCloud cryptographic session before their firmware will commit hardware configuration changes into the case's secure EEPROM. Over a standard AACP Bluetooth socket on non-Apple devices, the earbuds receive the command but ignore the instruction to flash the case microcontroller.
  3. Hardware-Hardcoded Sounds: Certain tones (like entering pairing mode via the button or double-tap) are generated directly by the case ROM/hardware regardless of software settings (even on iOS).

How to Turn Off Case Sounds:

If you have access to an iPhone, iPad, or Mac, you can connect your AirPods to it once and disable "Enable Charging Case Sounds" in iOS/macOS settings. Because the case saves that preference directly into its onboard EEPROM, it will permanently remember to keep charging sounds disabled even when you use them on Android going forward!

Clean Release Build:

I've cleaned up the experimental case sounds code from the PR/release to keep the codebase clean, while preserving all the stability improvements (single-bud NPE crash fixes, socket reflection fallback, and AirPods Pro 3 model support):
app-foss-release.apk

@hanslauch325-eng

hanslauch325-eng commented Sep 4, 2026

Copy link
Copy Markdown

alright, no problem. Im glad I could help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@bshea-1 @hanslauch325-eng @codeninjasfl