Community meeting on 15th January 2026

So, to recap the current current state of 10 IV/V support, the only response given to AlmuHS’ question was: “the new blobs also introduce issues with suspending which has been a bit problematic to solve”. And that’s it, not a single word more, and not a single word about those “completely different approaches by enabling 10 IV/V through an officially supported community port” that Jolla - allegedly - “have been thinking about” since early November 2025, obviously without any outcome.

Summary:

  • even the latest Sony blobs retain serious issues problematic to solve, which has been the case with all of their releases over the past 2 years, so it’s clear that chances to have it ever fixed are close to zero
  • even though some 3 months ago they mentioned that they allegedly “have been thinking about taking different approach by enabling 10 IV/V through an officially supported community port”, it was both the first and the last time we’ve heard anything about it, and apparently nothing has been done in that direction as there has been absolutely no outcome of it. They didn’t even consult creators of the best community ports whether anyone would be interested in it. Nor did they ever respond to numerous questions whether they would enable Android support (AAS) for such a community port.

So - as Sony blobs remain broken and at the same time nothing is being done to take different approach towards this problem - this miserable soap opera will never end.

6 Likes

There was more chat really happening, not everything is captured by the logs. Here are other comments I quickly found:

  • Mal: audio recording fix is waiting to be merged, maybe I’ll merge it tomorrow, also there is fix to be added for headphone audio
  • Filip: a bit slow for Xperia 10 IV and V. but is there any light on the end of this looong tunnel?
  • Mal: Yes

Edit. I prefer reading the discussion from the matrix room rather than logs as it gives better understanding what was really discussed. Highly recommend this

Edit 2. Forget the first edit and read comment down below

8 Likes

The actual log files (.log.html, .log.txt) do contain everything that was said. The Minutes are generated summaries and only contain what has been added using special commands.

5 Likes

Ah, very good note! I might have missed that….

In which universe was there an option to say “No”, though?

1 Like

Non and that can also mean anything. But as mal said there, they have again been able to fix something new. But the Sony road definitely seems rocky to say at least

What’s the actual importance of some audio recoding fix while much more serious issues with suspending remain (since the beginning) and are “problematic to solve”? It’s like if one fixed a light bulb in a car with a seriously malfunctioning engine.

Hopefully it’s not like with the light of Earendel (WHL0137-LS) star, which is 28 billion light years away.

1 Like

“Deep links” (at least to a couple places, like the Store) would be great as an officially-supported feature.

Yeah, would be nice. It is officially supported (using D-Bus), but Sailjail doesn’t allow that D-Bus call and you cannot publish an app without Sailjail in the official Store.

So if you want to just make it work and don’t care about Store, you can: SfosBeginnerGuide/src/linkhandler.cpp at cbcbd7ae130b868807221a2b867f69fa41a601ae · RikudouSage/SfosBeginnerGuide · GitHub

1 Like

Why do you need dbus to open links when you can from qml directly: Qt.openUrlExternally(url);

Because you can’t open an internal store page like that.

1 Like