Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow usage of libQt5Bluetooth.so.5 #99

Open
martonmiklos opened this issue Sep 12, 2017 · 10 comments
Open

Allow usage of libQt5Bluetooth.so.5 #99

martonmiklos opened this issue Sep 12, 2017 · 10 comments

Comments

@martonmiklos
Copy link

Title says all: no apps could be published to the Harbour which would utilise the Bluetooth.

With the boom of the BLE devices and the Bluez 5 supported devices it would be nice to allow these apps into the Harbour.

@jdrescher2006
Copy link

Come on guys it's 2017 and there is no bluetooth allowed?
Can someone even explain why this is the case?
I have two apps waiting to go to jolla store, only thing needed is bluetooth.

@martonmiklos
Copy link
Author

@jdrescher2006
I agree, and I would like to have some comment on it from the Jolla Employees.
Is there any blocking task with we can help with for e.g.

@jdrescher2006
Copy link

No answer from a representativ or anyone, this is exactly what I expected.
It's so sad but absolutely typical.
It's the same with e.g. paid apps. Requested since years but not even an inofficial statement why we don't get them. Just no communication at all and that's it.
You know, these are the main blockers keeping SFOS down: important libs (which do exist and work since years!!!) which are not allowed and missing paid apps.
Without these, there will never ever be high class apps! Why should a dev even bother?

@martonmiklos
Copy link
Author

martonmiklos commented Oct 19, 2017

@jdrescher2006
Well I would not position this problem to the same category as the paid apps. For the later there are a huge bunch of work which needs to be done in several places (Harbour app, payment methods, etc.).

But this is just the matter of allowing the usage of an existing library.
And yeah a comment like:

  • we do not want to do it (everyone should roll with his own implementation)
  • we do not have bandwidth for verification right now
  • whatever else

would be sufficient for me at the moment.

@jpetrell
Copy link

We haven't allowed QtBluetooth before since it is not a very mature Qt module and suffers from bunch of issues that we would like to fix in Qt first, but mainly because we really haven't had bandwidth. We are now actively discussing it though, so there is always hope. :)

@martonmiklos
Copy link
Author

martonmiklos commented Oct 19, 2017

Thanks for the explanation! Is there anything what the we can help with?

@jpetrell
Copy link

Help verify QtBluetooth API works on top of latest Sailfish OS release (e.g. Jolla C + Bluez 5):

  • QBluetoothLocalDevice test information queries, powering on/off, pairing/unpairing
  • QBluetoothDeviceDiscoveryAgent discover nearby devices, check that correct device info is exposed
  • QBluetoothServer can be used to communicate with Bluetooth device
  • QBluetoothServiceDiscoveryAgent returns valid services and service info
  • QBluetoothTransferManager can be used to transfer data to another device

Refactor Qt Bluetooth to get rid of synchronous D-Bus calls (counted 58 QDBusPendingReply::waitForFinished calls in qtconnectivity/src/bluetooth)

@martonmiklos
Copy link
Author

Thanks Joona!
So you are more curious about the non Low Energy stuff?
For the LE part I have compiled the Qt example, and it works pretty well according to my tests with various devices:
https://openrepos.net/content/martonmiklos/ble-scanner

@jdrescher2006
Copy link

Just a little reminder. It's well into 2018 now and still no bluetooth in Jolla store. No classic and no BLE.
By the way, for me it' a pure myth to say QtBluetooth is not mature. I have 2 apps with bluetooth classic support in openrepos. They have hundreds of users on different phones. There are NO bluetooth problems whatsoever -> pure myth and distraction on behalf of Jolla.
Face the thruth: you guys got your priorities completely messed up! How you were able to achieve this OS with all these basics messed up is an eternal mysterium for me.
I will write again if it's 2019. See you later...

@Thaodan
Copy link

Thaodan commented Mar 26, 2019

Update for 2019?
Soon this bug will be 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants