I’m in a regular job and thus won’t be able to participate, I dare. But maybe someone else could…
I wonder what level of Bluetooth support Jolla will provide for car makers.
I think this is the other way round ( connect a mobile phone TO the car-SfOS). Apps running locally on the car-system wouldn’t need Bluetooth for anything, probably, plus the apps on SfOS are native anyways and SfOS already provides full Bluetooth support for native apps.
So Sailfish OS right now should be fine for you.
Some of the messages in this thread have been flagged and are in danger of veering off-topic.
If you think this is happening, can I recommend that rather than replying in the thread directly, you can instead press the “time posted” text at the top right of the post you want to reply to, followed by “+ New Topic” to break the discussion out into a separate thread.
If you do this, we can also move over older messages in the thread into the new topic on request as well.
This helps keep things clean and so that the title of the topic matches what’s being discussed.
oh really? From the official changelog:
Some XA2 devices suffer from the loss of audio during voice calls. Reported here .
Lol. You haven’t ever used it. You just complain and contradict yourself.
for your information, currently I have Xperia 10 which after update to the latest sfos has problems with touch sensitivity freezes and worse battery life. Some time ago I had xperia x with SFOS 3 where SFOS experience was really bad:
- bad camera
- no encryption
- browser useless
- no good phone lock option
Now the camera is better,browser is finally usable but it seems there’s problem with touch support. There’s encryption but it’s very very weak and very easy to crack, still no good phone lock option.
Not to mention the still existing following problems: - impossible to set different sound for alarms,
- impossible to share multiple items from gallery at once
- bad keyboard UI which makes it cumbersome to type
- not possible to switch songs using volume keys
- no RTC alarms
- still no support for all phone functionality like radio
- no way to wakeup phone with swyping or tapping the screen.
- problems with car BT connectivity I mean it connects but I can’t call using car radio
So yes I’m trying to use SFOS as my secondary phone. You may not believe me but I’m walking actually with two phones and it’s true SFOS progress is big compared to SFOS3 but there’s still a lot of work to consider this phone as a daily driver.
I wrote this only for you but I don’t think it’s the good place to write about it.
You say this:
Then you list minutia. Stop being a hypocrite.
I have DD’d SFOS since 3.3 with zero major issues. It is just fine.
so because you don’t have issues, means that everyone else are faking them?
Or maybe you have way different expectations? You know world moved a bit and what’s working minimum changed a lot.
Still that minimum I said is hard with SFOS as I pointed out with the changelog entry and other reports around the forum. Such things should not exists for a daily driver where you must depend on the phone. Tbh I didn’t yet test conference call with SFOS and found out right now that it seems I can’t find the wait
on the dialpad, there’s pause
but where’s wait
? Good that conference calls works but the ui for that is not great tbh.
Can Android support Bluetooth? It has been discussed for nearly two years. I haven’t seen any progress
If you are asking if anything has changed, the answer is no.
If you are asking if it is possible ever, nothing has changed probably. Everything is theoretically possible, it might just not be practically possible.
I’ve been a Sailfish user since the first hour starting with the Jolla phone.
Full Bluetooth support and working NFC is essential for me, as there are more and more applications that require these. Since version 4.x, GPS Android apps are also constantly crashing and are therefore almost unusable. If sailfish does not fully support these basic features, I will unfortunately have to part with Sailfish. So dear Sailfish developers try to get this working, I would love to stay a sailfish user.
The missing Android Bluetooth support is a severe issue and this needs to be fixed somehow.
I suggested implementing the entire Android bluetooth stack additionally, e.g. through an additional bluetooth dongle (or alternatively by somehow “software-switching” the build-in bluetooth to either SfOS or Android solely). In a similar manner in what e.g. vmware or virtual-box does by allowing direct hardware access to the emulator. I wonder if this idea has ever been discussed further?
This would address the show-stopper problems I have, leaving only convenience issues.
If it was able to be done without a reboot, it would be pretty acceptable. (Even with a reboot, it would be OK)
I would go further and say that it would be better to have a properly working switching solution, that a bug-ridden seamless solution.
It would also be far better to have a switching solution sooner than a seamless solution later.
[To clarify, bluetooth support in Android is not something that is currently a showstopper for me personally, as I don’t have much bluetooth technojunk, and I don’t use rental cars and scooters, doorlocks and so on]
Here is how virtual box does the trick:
Way to go. VirtualBox, SailfishOS = of course Host OS. Thank yoy)
Thank you for mentioning the importance of Blue Tooth!
Hi @flypig is this Issue somehow on Jollas To Do list? I would like to use a fitnes tracker but its not working, because of the missing bluetooth support in the Android App Support. Would be great to have a statement from Jolla on this topic.