google / google/bumble

Android 16 mixes up UWB and Bluetooth packet streaming endpoints

Open
#744 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
555
Forks
138
Avg merge
3d 15h
Merged PRs (30d)
9

Description

Hi there, it seems that when I follow the [documented steps for the Android Emulator](https://google.github.io/bumble/platforms/android.html) with an Android 16 image, I get an error that I'm connecting to a `ChipKind` of `UWB` and not `Bluetooth`. Obviously this means I'm connecting to the UWB packet streamer and not the Bluetooth one.

For reference here is the output from the Android emulator, where UWB and Bluetooth packet streamers are both activated:
```
INFO | Activated packet streamer for bluetooth emulation
INFO | Activated packet streamer for uwb emulation
```

Resulting in my error:
```
17:29:05.177 W bumble.transport.android_netsim: Unsupported chip type
17:29:05.177 W bumble.transport.android_netsim: 3
17:29:14.253 W bumble.transport.android_netsim: Received initial info: initial_info {
name: "Medium Phone"
chip {
kind: UWB
}
device_info {
name: "Medium Phone"
kind: "EMULATOR"
version: "35.5.10.0"
sdk_version: "36"
build_id: "BP22.250325.006"
variant: "sdk_gphone64_x86_64-user"
arch: "x86_64"
}
}
```

Is there a way to disable UWB emulation? Or else is there a way to select the Bluetooth endpoint? I assume since this is Android 16 it hasn't been implemented yet.

Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.