-
Notifications
You must be signed in to change notification settings - Fork 113
Configure MTU via peripheral builder #867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
twyatt
wants to merge
7
commits into
main
Choose a base branch
from
twyatt/mtu
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e4dd3bf
Configure MTU via peripheral builder
twyatt eefe636
Default to 517 MTU request and update documentation
twyatt d7e4f5f
Fix MTU documentation
twyatt 07082d4
Revert out-of-scope coroutine context change
twyatt c2c890c
Cap the max write length to 512 on Android 13+
twyatt bce7bae
Merge branch 'main' into twyatt/mtu
twyatt c76948d
`./gradlew formatKotlin`
twyatt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If
requestMtu()fails at this point (throwingGattRequestRejectedException), is it cancelling the connection? Shouldn't it be able to continue the connection with the default MTU?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it would cancel the connection.
I believe that is desirable though.
The
requestMtuis just that: requesting an MTU. Assuming properly behaving firmware, the firmware will respond with the MTU to settle on. Hence why Android 14+ always (no matter what value you specify) requests the max (517) and lets the firmware respond with what it actually supports.If the MTU request fails, then I'd imagine there is a bigger problem at hand, as the firmware should really always be OK with any MTU request and simply respond with what it supports. My guess is that any failure seen at this stage will be because of a faulty connection or misbehaving firmware.
Core Bluetooth always negotiates an MTU on connection (you can't disable that). I'm guessing (I have not verified though — it would be very difficult to test), that a failure at the time of requesting an MTU, it would also result in either the firmware telling it what MTU it will accept or a loss of connection.