touch-packages team mailing list archive

[Michael Zanetti <michael.zanetti@xxxxxxxxxxxxx>]

Some info:

The backend for the module is shipped with QtConnectivity, hence doesn't
have any trust prompts around. That backend will talk to BlueZ over
D-Bus on the system bus for the most part. Additionally, OBEX & RFCOMM
(the two most interesting profiles for a start) read from/write to unix
file descriptors to exchange data with the remote device. Those files
are created by bluez and the descriptors handed over to the app in order
to read from/write to it. Reading through the code, file transfers also
seem to require temporary files on its own.

http://code.qt.io/cgit/qt/qtconnectivity.git/tree/src/bluetooth/qbluetoothtransferreply_bluez.cpp

What subset exactly is to be opened on the system D-Bus, I don't know
exactly atm. However, I do have a Content-Hub plugin and a proof of
concept service for sharing files (both, sending and receiving) around
in here:

https://code.launchpad.net/~mzanetti/+junk/ubtd (They were created back
in the days with Bluez4 and will require some updating to work with
Bluez5 but I think they can make good examples or even be the start for
the BT file sharing implementation we will need).

I think the OBEX file sending/receiving will definitely needed to be
implemented in the system, and with that can be unconfined/trusted. That
said, we might want to allow apps doing so too, but I think that's not
sooo critical for a start.

The RFCOMM/L2CAP on the other hand is really something that Apps will
want to use. That's the basis for things like multiplayer BT games, BT
remote controlling stuff or also connecting to any other BT enabled
gadget.

When it comes to Low Energy, my experience gets a little thinner, but
looking at the QtBluetooth backend implementation it seems to be the
same as RFCOMM. It requests a L2CAP socket (in form of a file
descriptor) exchanges data through that.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1526836

Title:
  Add qml-module-qtbluetooth support

Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-touch-meta package in Ubuntu RTM:
  Fix Released

Bug description:
  Add to the seed
  Make available in the ota9 framework
  Add apparmor policy

  API reference at http://doc.qt.io/qt-5/qtbluetooth-index.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526836/+subscriptions