-
Notifications
You must be signed in to change notification settings - Fork 47
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
advertising max/min interval being ignored #142
Comments
Yes, and if they seem to be correct it would help to see what is going on in |
I see the same behavior with
Because these showed nothing when running the programs
I looked for the dbus org.bluez.LEAdvertisement because it has advertising interval setting When looking at both output, I saw the HCI command with the default min max interval parms:
And the dbus message for bluetoothctl of
and for bluer program of
It looks to me that that the min/max intervals are never sent so the defaults are used (but I'm not very familiar with dbus messages). However, I see in the bluer code in Advertisement function register_interface that they are sent. @surban do you think this is enough evidence of a bluez issue to file an issue with them? |
Yes, seems to be a bluetoothd bug. |
I added the issue bluez/bluez#833 |
I'm seeing the same problem as issue #21. I'm running on Debian and with Blue Z 5.74
And experimental features (although the same issue happens without them)
And when I advertise using the program
https://github.com/potto216/bluer-cmd/blob/main/le_advertise/src/main.rs
with the command lineI see the advertisement has the min/max interval between 600 msec and 900 msec
Advertisement { advertisement_type: Broadcast, service_uuids: {123e4567-e89b-12d3-a456-426614174000}, manufacturer_data: {}, solicit_uuids: {}, service_data: {}, advertising_data: {}, discoverable: Some(false), discoverable_timeout: None, system_includes: {}, local_name: None, appearance: None, duration: None, timeout: None, secondary_channel: None, min_interval: Some(600ms), max_interval: Some(900ms), tx_power: None, _non_exhaustive: () }
But the HCI with
btmon
shows it is being ignoredand over the air captures show the advertisement is being ignored.
@surban Would looking at the d-bus messages be the next step?
The text was updated successfully, but these errors were encountered: