-
Name/IRC nick: arisel
-
Topic: bluetooth/ble support for android apps
-
Some details about the topic:
For quite some time there hasn’t been an easy to find clear official vision or roadmap for bluetooth/ble support within aliendalvik/for android apps.
However, there are quite some features which aren’t possible due to that in day-to-day sailfish user experience, like: -
being unable to connect to physical world interfaces like collecting parcels, opening some hotel doors,…
-
being unable to configure headsets above the pure audio profile,
-
being unable to connect most smartwatches,
-
being unable to use lots of companion apps for digital cameras, audio equipment, printers,…
There are some tidbits of information about the current situation and options floating around the forums, but nothing which would be an simple summary of the situation or vision.
So I think any official statement on a vision would benefit users in that they would be more aware about how this might affect them now, or in the future.
I would expect some statement along options like this (stolen from another thread): a) “we’ll never implement it as long as it’s not needed by one of our commercial customers, or we win a million in a local lottery”, b) “we plan to build some fake abstraction layer between sailfish and aliendalvik to make it possible with the stack similar to as it is now.”, c) “we will switch away from bluez over time and use one of the stacks android can handle for sailfish as well”, d) “we will support a 2-HW-device option over time”
(I know that some of those options make more sense than others, and there may be a lot more. This is just to clarify about what I’m after.)
- Approx. time needed:
- 2min if it’s just a statement
- 5min if further clarifications on my request are needed
I’ll try to join tomorrow, but I’m aware that this is way too late for tomorrows meeting. So I’m also happy to answer direct messages in-between, or join in a later meeting if that’s possible.