[Bug 743220] New: bluetooth modules need to track transport state

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=743220
  GStreamer | gst-plugins-bad | git master

           Summary: bluetooth modules need to track transport state
    Classification: Platform
           Product: GStreamer
           Version: git master
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: nstoughton at aether.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=294938)
 View: https://bugzilla.gnome.org/attachment.cgi?id=294938
 Review: https://bugzilla.gnome.org/review?bug=743220&attachment=294938

State tracking for avdtp

The avdtpsrc and avdtpsink plugins use the MediaTransport1 interface from
bluez, which includes a property "State":

string State [readonly]

  Indicates the state of the transport. Possible
  values are:
    "idle": not streaming
    "pending": streaming but not acquired
    "active": streaming and acquired

The source and sink modules should track this, since if the state ever falls
below "active" the transport must be re-acquired (which includes updating the
file descriptor used to transfer data).

Attached is a patch that has been tested in the avdtpsrc module and appears to
work correctly. I would appreciate wider review.

Note that this patch removes support for bluez4 (I don't have any easy way to
develop or test on bluez4, and the property management is significantly
different n bluez4).

It also moves from the low-level libdbus interface to glib gdbus, using
generated code from gdbus-codegen for the introspection to the MediaTransport1
interface. This is a lot simpler, with all the nasty complexities of property
cache management handled by the generated code.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.