aboutsummaryrefslogtreecommitdiff
path: root/src/bluez.vala
Commit message (Collapse)AuthorAgeFilesLines
* src/*.vala: Fix license headers having been a mix of GPL and LGPL license ↵Mike Gabriel2020-10-301-2/+2
| | | | text fragments. Adapt to GPL-3, fully.
* src/bluez.vala: Make BLUEZ_BUSNAME 'const string' (not 'static const string').Robert Tari2020-10-261-1/+1
|
* in bluez.vala, silence a startup g_warning by calling ↵Charles Kerr2016-02-141-8/+15
| | | | init_bluez_state_vars() before we start listening for org.bluez on the bus
* in bluez.vala, update our state properties when org.bluez vanishes from the busCharles Kerr2016-02-141-3/+10
|
* in bluez.vala, create a symbolic name for bluez' busnameCharles Kerr2016-02-141-4/+5
|
* (trivial) remove trailing whitespaceCharles Kerr2016-02-141-2/+2
|
* in bluez.vala, watch for org.bluez to be owned/unowned on the system busCharles Kerr2016-02-141-11/+34
|
* Check for NULL when getting cached properties Address and UUIDsRobert Ancell2015-09-281-4/+7
|
* Remove unused argument in DBus interfaceRobert Ancell2015-08-071-3/+3
|
* Support Bluez 5Robert Ancell2014-12-111-235/+173
| | | | | | | | | When enabling/disabling and setting discoverability we now do this for all adapters. This requires us to remove the "Set Up New Device" item since gnome-bluetooth no longer has a bluetooth wizard stand alone application. Instead we rely on the unity-control-center panel for device setup.
* Toggle rfkill again so that we have a chance of persisting the bluetooth ↵Mathieu Trudel-Lapierre2014-09-221-1/+1
| | | | state across reboots.
* change the bluetooth.supported property whenever bluez' default adapter ↵Charles Kerr2013-12-061-0/+2
| | | | changes its object path.
* add a 'connected' property as a simple hook to whether or not we have any ↵Charles Kerr2013-12-061-1/+20
| | | | connected bluetooth devices
* make org.bluez.Adapter's set_property() call nonblockingCharles Kerr2013-10-141-17/+6
|
* if killswitch exists and is valid, prefer its use over toggling ↵Charles Kerr2013-10-141-11/+13
| | | | org.bluez.Adapter's Powered property
* if /dev/rfkill doesn't exist or isn't writable, then try to handle bluetooth ↵Charles Kerr2013-10-111-15/+106
| | | | toggles simply by toggling bluez Adapters' Powered property
* add an action whose state shows whether or not bluetooth is supported by the ↵Charles Kerr2013-10-101-0/+2
| | | | hardware, used by ubuntu-system-settings
* copyediting: whitespace, type inferenceCharles Kerr2013-08-061-22/+18
|
* copyediting: fix lines that wrapCharles Kerr2013-08-061-13/+25
|
* copyediting: fix indentation in Service, fix copyright & author comments in ↵Charles Kerr2013-08-051-0/+2
| | | | bluez, service, main
* copyediting: readability + grouping related methods togetherCharles Kerr2013-08-051-71/+106
|
* silence g_message scaffoldingCharles Kerr2013-08-051-1/+1
|
* fully implement the bluez/device backend. in the desktop profile, add ↵Charles Kerr2013-08-051-39/+249
| | | | menuitems for the devices.
* initial support for individual devices in Bluetooth classCharles Kerr2013-08-031-5/+47
|
* improve documentation on Killswitch, Bluetooth, and BluezCharles Kerr2013-08-011-2/+5
|
* add a bluetooth backend to track bluetooth being enabled, being hard/soft ↵Charles Kerr2013-08-011-0/+97
| | | | blocked, and its devices.
* Use GnomeBluetooth instead of bluez directlyRobert Ancell2012-12-041-180/+0
|
* Check device classRobert Ancell2012-10-111-0/+5
|
* Fix visible toggleRobert Ancell2012-10-111-0/+4
|
* Abstract out bluez moreRobert Ancell2012-10-111-5/+134
|
* Get killswitch workingRobert Ancell2012-10-111-0/+42
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 21:03:55 +0000