| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Unfortunately, powering on/off Bluetooth adapters has become longer,
and less reliable over time, so front-ends need more information to
be able to figure out what it happening.
As a first pass, export whether the adapter is in the process of being
turned on, or turned off, based on our own request.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Simplify the discovering/discoverable properties, and especially the
transition between default adapters by always having the adapters be
discoverable when discovering, and offer up a single new property as a
ways of controlling both: "default-adapter-setup-mode"
|
|
|
|
| |
It's not been used since bluez 4.x.
|
| |
|
|
|
|
|
|
|
| |
Fix BLUETOOTH_TYPE_AUDIO and _BLUETOOTH_TYPE_NUM_TYPES after speaker
type addition.
Fixes: c9a513a6338f673bc26c2aa995f657048173be1e
|
| |
|
|
|
|
| |
Closes: #77
|
|
|
|
|
|
| |
As those property objects were not used anywhere anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=782530
|
|
|
|
| |
We're missing icons for the remote control, wearable and toy types.
|
|
|
|
|
|
| |
Move _BLUETOOTH_NUM_COLUMNS outside the enum so that the prefixes
are correctly stripped, eg. GnomeBluetooth.Column.DEFAULT not
GnomeBluetooth.Column.LUETOOTH_COLUMN_DEFAULT (yes, with the missing B)
|
|
|
|
|
|
| |
Since it is used more than once in the code we store it to easier access.
https://bugzilla.gnome.org/show_bug.cgi?id=701399
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
96% symbol docs coverage.
208 symbols documented.
4 symbols incomplete.
8 not documented.
BluetoothChooser
BluetoothChooserButton
BluetoothChooserButtonClass (<items>)
BluetoothChooserClass (<items>)
BluetoothChooserCombo
BluetoothChooserComboClass (<items>)
BluetoothClient
BluetoothClientClass (<items>)
|
|
|
|
|
|
|
|
| |
More work to do:
89% symbol docs coverage.
202 symbols documented.
2 symbols incomplete.
26 not documented.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And bluetooth_client_set_discoverable() private helper.
|
|
|
|
| |
So remove it!
|
|
|
|
| |
Add BluetoothClient and plugin documentations, update the others.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hunted down by Peter Hurley <phurley@charter.net>.
Description
If the remote device is disconnected when the applet starts, the applet
will be unable to initiate connection to the audio interface of the
device.
Cause
Incorrect use of g_hash_table_lookup in the device_list_nodes() function
in lib/bluetooth-client.c
Discussion
For a given device, device_list_nodes() loops through the known
detectable interfaces (those in detectable_interfaces[]) and adds
them to the returned hash table if calling the interfaces's
.GetProperties dbus method returns true.
The value of the "Connected" property is then stored as the associated
value with the interface name as the key in the hash table.
The *connectable* interface "org.bluez.Audio" is only added if at least
either of the *detectable* interfaces "org.bluez.Headset" or
"org.bluez.AudioSink" were added the the hash table in previous
iterations within device_list_nodes().
However, the test for whether those *detectable* interfaces were added
is not correct. Currently, g_hash_table_lookup() is used to determine
if the interface names are in the hash table. g_hash_table_lookup()
will return NULL if the the key is not present in the hash table,
OTHERWISE IT RETURNS THE VALUE ASSOCIATED WITH THE KEY. If that value
is 0 (== BLUETOOTH_STATUS_DISCONNECTED), the logic mistakenly believes
that the key is not present in the hash table, and as a result, fails
to add the only connectable audio interface "org.bluez.Audio".
Recommend
Either use g_hash_table_lookup_extended() to test for key presence
or change enum BLUET00TH_STATUS_DISCONNECTED to be != 0.
|
|
|
|
| |
As used in the A2DP and Headset services.
|
|
|
|
|
| |
To mark services as being connected, disconnected, or
connecting.
|
|
|
|
| |
To simplify enumeration in other applications.
|
|
So as to avoid confusing readers of the code.
|