client: Fix using RegisterProfile RegisterProfile no longer works for registering GattProfile instances as this functionality has been moved to RegisterApplication. In order to make this more clear this replaces the (un)register-profile with (un)register-application and enable ObjectManager, here is an example how to register for 12345678-1234-5678-1234-56789abcdef1: [bluetooth]# register-application 12345678-1234-5678-1234-56789abcdef1 Application registered bluetoothd[8777]: src/gatt-database.c:manager_register_app() Registering application: :1.483:/ bluetoothd[8777]: src/gatt-database.c:proxy_added_cb() Object received: /org/bluez/application, iface: org.bluez.GattProfile1 bluetoothd[8777]: src/gatt-database.c:proxy_added_cb() Object received: /org/bluez/agent, iface: org.bluez.Agent1 bluetoothd[8777]: src/gatt-database.c:profile_add() Added ":1.483/org/bluez/application/12345678-1234-5678-1234-56789abcdef1" bluetoothd[8777]: src/gatt-database.c:client_ready_cb() GATT application registered: :1.483:/ [bluetooth]# unregister-application Application unregistered bluetoothd[8777]: src/gatt-database.c:profile_remove() Removed ":1.483/org/bluez/application/12345678-1234-5678-1234-56789abcdef1" bluetoothd[8777]: src/gatt-database.c:profile_release() Releasing ":1.483"

Diffstat

3 files changed, 68 insertions(+), 44 deletions(-)