i mentioned this already. no company who advertises their product would write anything about limitations and shortcomings. about limitations the user need to inform himself from other sources- like this forum.
so its normal, that Jolla didn’t mention NFC and BT is not working on App Support on their Website.
Somewhere on Jolla Page i read about not 100% warranty on all Android Apps
What you are missing here is that SFOS can do these things, I can make calls from my car, have access and can search for my contacts. And I listen to Spotify from appsupport.
You can’t win with emulating - it just buys some headroom provided its costs are reasonable. Being able to run some android applications is a welcome feature already. SFOS main purpose is not to outperform Android for the whole google store catalogue.
This reminds me the OS/2 WIN32 emulator times. Knowing how it ended, it’s not pleasant memories.
So I’m looking forward for SFOS v5, with its set of fixes & improvements, and - most intriguing - its new licensing conditions for existing hardware. If AAS gets better in general - I’ll take it. But if the OS and native apps come out enhanced, it’s even better and that’s where the effort should be allocated
Maybe it is normal that they don’t mention that it’s not working, but it certainly isn’t normal if it’s not working in an automotive infotainment platform, i.e. where it is the standard communication method with the driver’s phone.
In case of an automotive platform it is of zero relevance what SFOS can do, because most of the applications that majority of mainstream users (i.e. car owners) want to use aren’t available for SFOS but only for Android (or iOS), so without Bluetooth working in the AAS (Android Support) part of the Jolla’s Seafarix infotainment system all those apps will be unusable, and so will be the entire platform in the eyes of those car owners.
Don’t you really get that an in-car multimedia system is something completely different (and aimed at completely different user group - a typically mainstream user) than some geeky Linux / SFOS smartphone? Please don’t tell me that a typical Mercedes owner/driver (was it Mercedes that Jolla hinted that they have some sorts of plans / business with?) would want to fiddle with PureMaps (manually download and install OSMScoutserver, etc.) rather than just expect Google Maps or Sygic or Here or something like that) to work out of the box.
OK, so if SFOS + your car’s existing media system provides everything you need, then aren’t you just saying that this whole Jolla’s Seafarix automotive project is doomed to fail as no one will need it?
Agreed. It’s the same thing as with Linux and WINE. My needs are already covered with AAS right now so I’m content. I’m not expecting to run full Windows with all it’s spyware features on my Linux PC, nor do I want the same with Android on my SFOS phone. 
As if having Bluetooth supported in AAS forced one to do anything with it, or anything else. What kind of BS is that?
Like for example what? The Mind2 that since August 2024 people have been asking about what is it for and up to date no one gave any reasonable answer? 
How nice. A typical example of rushing into insults due to lack of argumentation. Well, that ends our conversation.
Just one remark, learn to read with understanding, because
has absolutely no sane relation with what I wrote, i.e. that Bluetooth is needed for Jolla’s Seafarix automotive platform (also heavily relying on AAS) i.e. in a type of devices where Bluetooth is the basic and standard communication method with the car driver’s phone. And if developed for Seafarix, it would naturally come to SFOS’ AAS, too. So first learn how to at least try to comprehend what you are so aggressively barking at, and only then it makes any sense to talk with you any further and bear with your insults.
Over and out.
You asked “what BS is this” and I replied to you what I meant with what I wrote in my reply to rtr2001. Your speculation about Seafarix doesn’t concern me in the slightest, nor was my reply to rtr2001 in any way or form in relation to you or your posts.
All I can say: Maybe BT compatibility will happen, maybe it won’t. Que sera, sera.
This post was flagged by the community and is temporarily hidden.
I did, because of your arrogant know-it-all attitude.
You do not own the truth, and moreover you spread lots of bullshit.
Calling all those who want to have serious discussions in this forum and do not want to be insulted and abused.
I received this mail as a personal post full of insults and abuse:
Is there a moderator in this forum?
Why is this person, who only insults, not excluded from this forum?
How many more insults do we have to endure?
This topic is temporarily closed for at least 4 hours due to a large number of community flags.
This topic was automatically opened after 36 hours.
I tend to block certain individuals. Helps.
The problem with some people is that instead of discussing THE TOPIC they mostly scold others and this way vandalize every thread they intrude.
In this specific case, instead of the actual Bluetooth related disussion, they feel in position to announce to everyone else that they don’t need Bluetooth in AAS themselves and therefore no one else should need it, and if one still does then he/she should switch to an Android phone instead, or else one is - let me quote it - “neurodivergent” and should go “two magic words” himself. A piece of (used) toilet paper is worth more than such output, so if such people are not interested in (or incapable of) normal on topic discussion, kindly go somewhere else. For example, create for yourselves a thread called “What I think about certain individuals” and vent your miasmas there, at least you’ll be on the topic…
Counterpoint: Finding AAS BT support shouldn’t be a top priority in the list of things for Jolla to work on also is a valid opinion that one can freely express. There are more inportant things I’d rather see improved. Like system stability and efficiency, bug fixes, a native browser that isn’t outdated and full of security holes and unmaintained, camera 2 api.
And QT 6 would be cool as well.
But note that no one has ever said that it should be top priority. People were merely saying that it would be good to have it one day.
Sure, but why do you think that you would get any of the above in exchange for still no AAS BT support?
And VoWiFi, and WPA3, and peace on earth. Or maybe just SFOS 5.0 for the 10 III, that doesn’t need any new fixed binaries from Sony (unlike 10 IV/V) so there’s actually no simple excuse why it still hasn’t been released, considering that it was scheduled for “August-September 2024”, i.e. 4-5 months ago.
https://www.youtube.com/live/1nEC3sVExAU?si=CKuo8pCtgRerp8sf&t=2440
As I already wrote: so start talking ON TOPIC. Because absolutely no one here (myself included) is interested in what you think about me or anyone else. Sadly, your last posts carry no other content than that…
This topic is temporarily closed for at least 4 hours due to a large number of community flags.