Roon ARC crashes on Samsung Galaxy S22 with Jabra Enhance Pro 30 (ref#ILPNUT) [Ticket In]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· When using Roon ARC on Android with Jabra hearing aids, the app crashes. This is a Samsung Galaxy S22 with Jabra Enhance Pro 30 hearing aids. Playing music through e.g. Spotify works fine through the hearing aids. Additionally, playing through another Bluetooth device works fine.

Tell us about your home network

· This is through Roon ARC, which works, and happens externally to my network.

Hi @Richard_Kolkovich,

Thank you for the additional details — that helps clarify what’s happening here.

The Jabra Enhance Pro 30 uses Bluetooth LE Audio (with Auracast) and Android’s Hearing Aid / accessibility audio path, which is different from the standard Bluetooth A2DP profile used by most headphones.

Roon ARC on Android currently relies on the standard Android media audio stack, and hearing aids that route audio via the LE Audio / Hearing Aid profile can behave differently from regular Bluetooth devices.

This appears to be a compatibility issue with Android’s LE Audio / hearing aid routing.

We’ve passed this information along for further review, but at the moment we don’t have a confirmed timeline or workaround to share. In the meantime, using standard Bluetooth headphones or speakers with ARC would be the most reliable option.

Thank you for reporting this and for the detailed device information — it’s very helpful for investigation.

Hi @Richard_Kolkovich,

Thank you again for submitting this detailed report. The team has an investigative ticket in the pipeline.

If you’re willing to take a few moments to upload ADB (Android-level) logs that capture the crash, it will greatly expedite developers’ efforts to pin down the problem. This is fully optional and entirely safe/secure. Below are the steps for capturing the crash in ADB logs and uploading them to our servers.

First, connect your PC to your Android phone and install ADB (instructions are here (all platforms)).

Then:

  1. Type adb shell in Terminal

  2. Type logcat v (ref: 
    Logcat command-line tool  |  Android Studio  |  Android Developers
    )

  3. Reproduce the crash with the hearing aids and let Terminal print logs for 3-5 more seconds

  4. Select output from the moment you started the reproduction of the bug till the very end

  5. Upload the log here to our secure upload servers and give us a ping
    https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

We’ll keep an eye out for your response. Thank you!

Connor,

I would gladly upload some logs but this is my dad’s phone, and I won’t have access to it until I see him again next month. If you still need the logs, I can get them for you at that time and upload them.

Thanks,
Richard

OK, I was able to walk him through enabling developer mode and luckily have a Linux box I could ssh into to get logs. I’ve uploaded them (roon_arc_crash.log) for your perusal. :slight_smile:

Hi @Richard_Kolkovich,

Thank you to both you and your dad for graciously taking the time to gather logs remotely. You’ve gone above and beyond for our team and this will no doubt expedite development’s effort to pin down what’s wrong.

We’ll pass this along to our QA team for reproduction internally. From there, we should have sufficient information to put a ticket in the pipeline for a fix.

We don’t have a timeline to resolution to share at this time, but we’ll certainly keep you apprised as the ticket moves through the pipeline.

Thank you again.

There is now a ticket in the development pipeline and a fix is forthcoming. We will share a note here when the fix is expected to be included in an #earlyaccess release.