Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. QDBus: how to retreive object path
Forum Update on Monday, May 27th 2025

QDBus: how to retreive object path

Scheduled Pinned Locked Moved Unsolved General and Desktop
qdbusobjectpathavrcp
2 Posts 2 Posters 1.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mark81
    wrote on 20 Jul 2016, 12:22 last edited by
    #1

    Hello, I'm trying to implement some function of AVRCP protocol. Here the documentation:

    http://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/media-api.txt

    what I don't understand is how to retreive the object path of my player:

    Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX/playerX

    I'm not sure if it is returned from some DBus methods or I have to manually build it using the bluetooth address and the local device.

    K 1 Reply Last reply 21 Jul 2016, 11:57
    0
    • M Mark81
      20 Jul 2016, 12:22

      Hello, I'm trying to implement some function of AVRCP protocol. Here the documentation:

      http://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/media-api.txt

      what I don't understand is how to retreive the object path of my player:

      Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX/playerX

      I'm not sure if it is returned from some DBus methods or I have to manually build it using the bluetooth address and the local device.

      K Offline
      K Offline
      kshegunov
      Moderators
      wrote on 21 Jul 2016, 11:57 last edited by kshegunov
      #2

      @Mark81
      Hi,

      I'm not sure if it is returned from some DBus methods or I have to manually build it using the bluetooth address and the local device.

      It is not, you have to handle it manually. From what I can discern from your link it's a path you construct out of device names. If the service is compliant you can usually list the objects it exposes.

      Kind regards.

      Read and abide by the Qt Code of Conduct

      1 Reply Last reply
      0

      2/2

      21 Jul 2016, 11:57

      • Login

      • Login or register to search.
      2 out of 2
      • First post
        2/2
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved