Skip to content

/corebluetooth runtime mtu#466

Open
chmorgan wants to merge 2 commits into
deviceplug:devfrom
chmorgan:feature/corebluetooth-runtime-mtu
Open

/corebluetooth runtime mtu#466
chmorgan wants to merge 2 commits into
deviceplug:devfrom
chmorgan:feature/corebluetooth-runtime-mtu

Conversation

@chmorgan

Copy link
Copy Markdown

I'd like to be able to size payloads to the mtu and while the MTU branch added support the value was always 23 as apparently corebluetooth isn't updating the mtu property until after service discovery.

chmorgan added 2 commits July 16, 2026 19:42
CoreBluetooth's maximum write length is not reliably negotiated in the
initial connection callback. Infer and publish the ATT MTU after service
discovery, while resetting the exposed MTU to the default for each new
connection.

Rename the Rust integration test and its Android JNI/Kotlin entry points
from "after connection" to "after service discovery". The shared helper
discovers services before reading the MTU, so the old name overstated
connect-only coverage; the JNI export and Kotlin declarations must match
the renamed shared test.
@qwandor qwandor changed the base branch from master to dev July 16, 2026 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant