rfcomm: emit Channel=0 for a Server profile with no channel - #194
Merged
Conversation
…ne, so that it auto-assigns
cfraz89
force-pushed
the
rfcomm-server-channel-0
branch
from
August 15, 2026 16:13
4af7b52 to
60005b4
Compare
cfraz89
marked this pull request as ready for review
August 15, 2026 16:16
surban
approved these changes
Aug 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When rfcomm Profile role is Server, currently bluer omits channel from the dbus dict, which downstream in bluez results in no rfcomm socket being created, and channel attr ommitted from the sdp record.
This changes it to send channel: 0 instead, which is interpreted as auto, which is what we want.
This now behaves correctly in my usage.