GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
348 stars 19 forks source link

Bluetooth crash on Samsung Galaxy Buds Pro2 #3908

Closed TheDonnerParty closed 3 weeks ago

TheDonnerParty commented 3 weeks ago

Crash on pairing and using. Other Bluetooth devices work fine

thestinger commented 3 weeks ago

Is there a crash log? Unclear if this is an upstream Android issue or GrapheneOS-specific. It's possible for it to be an upstream Android issue which occurs with AOSP but not the stock Pixel OS due to them using a different Bluetooth module version. Will avoid marking it as an upstream bug until we have more info but it probably is one.

TheDonnerParty commented 3 weeks ago

type: crash osVersion: google/komodo/komodo:14/AD1A.240530.047/2024082302:user/release-keys uid: 1002 (u:r:bluetooth:s0) cmdline: com.android.bluetooth processUptime: 0s

signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr 400be98ce33c6c0 threadName: bt_main_thread MTE: enabled

backtrace: /apex/com.android.btservices/lib64/libbluetooth_jni.so (le_audio::utils::GetAudioContextsFromSourceMetadata(source_metadata_v7 const&)+220, pc 6af2ac) /apex/com.android.btservices/lib64/libbluetooth_jni.so ((anonymous namespace)::SourceCallbacksImpl::OnAudioMetadataUpdate(source_metadata_v7, le_audio::DsaMode) (.0d5db357950ce8eb70c0dd71343de7ab)+500, pc 687b44) /apex/com.android.btservices/lib64/libbluetooth_jni.so (base::debug::TaskAnnotator::RunTask(char const, base::PendingTask)+204, pc b0800c) /apex/com.android.btservices/lib64/libbluetooth_jni.so (base::MessageLoop::RunTask(base::PendingTask)+360, pc b074f8) /apex/com.android.btservices/lib64/libbluetooth_jni.so (base::MessageLoop::DoWork()+460, pc b0781c) /apex/com.android.btservices/lib64/libbluetooth_jni.so (base::MessagePumpDefault::Run(base::MessagePump::Delegate)+112, pc b0a0e0) /apex/com.android.btservices/lib64/libbluetooth_jni.so (base::RunLoop::Run()+72, pc b17158) /apex/com.android.btservices/lib64/libbluetooth_jni.so (bluetooth::common::MessageLoopThread::Run(std::1::promise)+344, pc a23998) /apex/com.android.btservices/lib64/libbluetooth_jni.so (bluetooth::common::MessageLoopThread::RunThread(bluetooth::common::MessageLoopThread, std::__1::promise)+56, pc a23408) /apex/com.android.btservices/lib64/libbluetooth_jni.so (void std::1::thread_proxy<std::1::tuple<std::1::unique_ptr<std::1::thread_struct, std::__1::default_delete<std::1::thread_struct> >, void ()(bluetooth::common::MessageLoopThread, std::1::promise), bluetooth::common::MessageLoopThread*, std::1::promise > >(void)+92, pc a23fec) /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void)+204, pc 825dc) /apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68, pc 72fa4)

thestinger commented 3 weeks ago

Resolved for the next release. An existing patch was missing for the special temporary Android Open Source Project branch for 9th generation.

TheDonnerParty commented 3 weeks ago

That was fast!  Thank you!

William

Sent with Proton Mail secure email.

On Sunday, August 25th, 2024 at 3:20 AM, Daniel Micay @.***> wrote:

Resolved for the next release. An existing patch was missing for the special temporary Android Open Source Project branch for 9th generation.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

thestinger commented 3 weeks ago

It's an issue we discovered a while ago and got them to fix upstream so we knew crash traceback already. The patch is missing in the AOSP Bluetooth module for the Pixel 9 family device branch so we just had to cherry-pick it over and there was another one missing we added too. It's just caused by new devices temporarily using a device branch for AOSP and the stock Pixel OS that's a bit out of sync with what it should be. Stock Pixel OS uses a Bluetooth APEX module that's different so they likely avoid this because of that.

TheDonnerParty commented 3 weeks ago

Thank you, Daniel!  This is very helpful.  Thanks for the follow-up.  It is greatly appreciated!

Best Regards,

William

Sent with Proton Mail secure email.

On Sunday, August 25th, 2024 at 4:13 AM, Daniel Micay @.***> wrote:

It's an issue we discovered a while ago and got them to fix upstream so we knew crash traceback already. The patch is missing in the AOSP Bluetooth module for the Pixel 9 family device branch so we just had to cherry-pick it over and there was another one missing we added too. It's just caused by new devices temporarily using a device branch for AOSP and the stock Pixel OS that's a bit out of sync with what it should be. Stock Pixel OS uses a Bluetooth APEX module that's different so they likely avoid this because of that.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.