Details

    • Type: Epic Epic
    • Status: Open
    • Priority: Not Evaluated Not Evaluated
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Epic Name:
      QtBluetooth Backlog
    • Epic/Theme:

      Description

      General backlog for possible tasks/features in QtBluetooth – things not necessarily ever committed to but under consideration.

      Past releases and future plans:

      • Qt 5.3
      • Qt 5.4
        • Port Bluez code to Bluez 5.x (QTBUG-32085)
        • Support Bluetooth Low Energy Client/Central on Linux (QTBUG-31719)
          • Tech Preview
          • Supported on Linux with Bluez 4 and 5
      • Qt 5.5
        • Bluetooth Low Energy Client/Central for Android (QTBUG-40923)
        • Bluetooth Low Energy Client/Central for iOS (QTBUG-40700)
        • MacOSX (classic and Low Energy Client/Central) (QTBUG-40464)
      • Qt 5.6
        • iOS 9 support added
        • General bugfixes throughout the API and platforms. For more details see dist/changes-5.6.0
      • Qt 5.7
        • Bluetooth Low Energy Peripheral API added (Technology Preview)
        • Access to BTLE connection parameters on Bluez (QTBUG-52428)
        • Signed write support added for Bluez and Android (QTBUG-41175)
      • Qt 5.8
        • Bluetooth Peripheral API support on iOS and OS X (QTBUG-53485)
        • WinRT port (Bluetooth Low Energy Client/Central) (QTBUG-37779)
      • Qt 5.9
      • Medium to Long term goals

        Issue Links

          Issues in Epic

          There are no issues in this epic.
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

            Hide
            Ekkehard added a comment -

            will do this later. just have to finish some BT LE work so my customer (german enterprise) can do tests. we have a custom BT LE device connected scanning thru all networks (telekom, O2, Vodafone, ...) and all technologies (GSM, LTE, ...) and notifying the app about current pegel. Already done this app for BB10 - now must also be running on Android, iOS. To help me to understand how Qt does all this BT LE stuff I'm developing a new example app (and publish to github later) because current examples are outdated and not fully-featured. my goal is to provide a example where all errors and states are correct handled and all data nicely presented using QtQuickControls2

            Show
            Ekkehard added a comment - will do this later. just have to finish some BT LE work so my customer (german enterprise) can do tests. we have a custom BT LE device connected scanning thru all networks (telekom, O2, Vodafone, ...) and all technologies (GSM, LTE, ...) and notifying the app about current pegel. Already done this app for BB10 - now must also be running on Android, iOS. To help me to understand how Qt does all this BT LE stuff I'm developing a new example app (and publish to github later) because current examples are outdated and not fully-featured. my goal is to provide a example where all errors and states are correct handled and all data nicely presented using QtQuickControls2
            Hide
            Ekkehard added a comment -

            while going on with my tests als got unhandled error code 34 from QLowEnergyController while discovering Services

            D BluetoothGatt: onClientConnectionState() - status=34 clientIf=5 device=00:A0:50:31:59:17
            D BluetoothGatt: close()
            D BluetoothGatt: unregisterApp() - mClientIf=5
            W QtBluetoothGatt: Unhandled error code on connectionStateChanged: 34
            

            and also getting unknow error code 8 - happened switching a device OFF while connected and waiting for Notifications

            D BluetoothGatt: onClientConnectionState() - status=8 clientIf=5 device=00:07:80:3A:09:EB
            D BluetoothGatt: close()
            D BluetoothGatt: unregisterApp() - mClientIf=5
            W QtBluetoothGatt: Unhandled error code on connectionStateChanged: 8
            

            are these known bugs or should I open a new one ?

            Show
            Ekkehard added a comment - while going on with my tests als got unhandled error code 34 from QLowEnergyController while discovering Services D BluetoothGatt: onClientConnectionState() - status=34 clientIf=5 device=00:A0:50:31:59:17 D BluetoothGatt: close() D BluetoothGatt: unregisterApp() - mClientIf=5 W QtBluetoothGatt: Unhandled error code on connectionStateChanged: 34 and also getting unknow error code 8 - happened switching a device OFF while connected and waiting for Notifications D BluetoothGatt: onClientConnectionState() - status=8 clientIf=5 device=00:07:80:3A:09:EB D BluetoothGatt: close() D BluetoothGatt: unregisterApp() - mClientIf=5 W QtBluetoothGatt: Unhandled error code on connectionStateChanged: 8 are these known bugs or should I open a new one ?
            Hide
            Alex Blasche added a comment -

            The error code 8 is what you filed already which was fixed a while ago: QTBUG-59918

            Error code 34 is new to me. It is not unhandled. It is mapped to QLowEnergyController::UnknownError which is not wrong. If it happens more often I might add a dedicated error enum. That's the main purpose of the warning (to discover new things )

            Show
            Alex Blasche added a comment - The error code 8 is what you filed already which was fixed a while ago: QTBUG-59918 Error code 34 is new to me. It is not unhandled. It is mapped to QLowEnergyController::UnknownError which is not wrong. If it happens more often I might add a dedicated error enum. That's the main purpose of the warning (to discover new things )
            Hide
            Ekkehard added a comment -

            aaah ... too many bug reports - sorry mentioning the code 8 again
            will watch the 34 and see when it happens again and from what devices
            just playing around with all scenarios and always watching the log to see what comes up from device, service, characteristic, descriptor while doing read, write, notify, connect, disconnect, switch on-off and so on
            so I overlooked that the 34 was mapped to Unknoiwn
            over all: I really like the way Qt has implemented all this stuff. great work !

            Show
            Ekkehard added a comment - aaah ... too many bug reports - sorry mentioning the code 8 again will watch the 34 and see when it happens again and from what devices just playing around with all scenarios and always watching the log to see what comes up from device, service, characteristic, descriptor while doing read, write, notify, connect, disconnect, switch on-off and so on so I overlooked that the 34 was mapped to Unknoiwn over all: I really like the way Qt has implemented all this stuff. great work !
            Hide
            Ekkehard added a comment -

            noticed this:
            switching devices OFF: getting error code 8
            switching device OFF and ON again before QT has delivered a disconnect SIGNAL:

            • one device gives me error 34
              this was reproducable
              so I mapped this one to ConnectionError
            Show
            Ekkehard added a comment - noticed this: switching devices OFF: getting error code 8 switching device OFF and ON again before QT has delivered a disconnect SIGNAL: one device gives me error 34 this was reproducable so I mapped this one to ConnectionError

              People

              • Assignee:
                Alex Blasche
                Reporter:
                Alex Blasche
              • Votes:
                15 Vote for this issue
                Watchers:
                30 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Gerrit Reviews

                  There are no open Gerrit changes