Community meeting on October 29, 2026

[rainemak]

Please note new time slot

Schedule: Thursday 2026-10-29T17:00:00Z

Sailfish OS Community Calendar (ICS format)

Even if you do not participate, topics tend to generate discussion. I want to see discussion happening. Thus, I’m proposing that we’d use 10mins as minimum topic duration. Maximum 6 topics a week. We’ll continue with the extended 90 mins meeting duration.

Jolla to check action points from the previous meeting. We agreed today that we’ll start to follow up action points on each meeting.

• The meeting will be held on oftc.net IRC #sailfishos-meeting .
• You can also join on Matrix or read-only on Telegram .
• Logs of previous meetings: 2026, 2025, 2024, 2023, 2022, 2021, 2020, earlier.

Topic proposals for the meeting:

• Add your name/nick using the template below to suggest a topic.
• Indicate how much time you’ll need so we can time-box the meeting accordingly.
• Please be as thorough as you can with your question/topic.
• If you can’t make the meeting please ask and name a substitute.

It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here and get responses that way.

We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isn’t clear enough it will be postponed. Also: always ask for more time than you anticipate your topic needs!

Please have your topics ready at least 3 days before the meeting so we can prepare good answers. Topics announced afterwards will be postponed to the next meeting.

Template for topic proposal: (post your topic proposals as comments to this forum topic).

• Name/IRC nick:
• Topic:
• Some details about the topic:
• Approx. time needed:
• Substitute (optional):

Open Pull Requests:
If you have, or know of, a pull request that’s been open for at least 3 weeks, but which you think deserves attention, please add a comment using the template below and we’ll consider it during the next meeting.

• Name/IRC nick:
• Open PR URL:

[usbee]

• Name/IRC nick: usbee

• Topic: Let’s talk about PIM capabilities.

• Some details about the topic: It is a bit complex topic but I feel like they are heavily connected and it is worth to discuss it as a whole package. Supporting Oauth doesn’t work by most providers. As a result it is not possible to sync IMAP, CalDAV and CardDAV inside a singular account. So setting up Fastmail for example needs to be done 3 times as 3 separated entries. Also syncing notes and todos is not possible at all. Even so there is no ToDo app as part of Sailfish OS. There is a notes app but it only works as an offline local app. There should be an option besides generic IMAP and generic CalDAV/CardDAV accounts for generic Oauth accounts too. I do believe that this set of features is essential on a phone to be able to use it as a PIM device so having a consideration and a timeline for it would already be a great thing.

• Approx. time needed: 15 mins

• Substitute (optional): Additionally I saw a feature request that utilizes WebDAV in a way I didn’t consider but sounds interesting enough to add it to the discussion here: Request: Support for generic WebDAV photo sources in Gallery

[PeegeeTips]

1. Name/IRC nick: PeegeeTips
2. Topic: Is it time to tell us about Jolla’s plans to update QT?
3. Some details about the topic: The topic itself is not new; we all know that QT5.6 is completely obsolete and that there are ‘reasons’ why Jolla hasn’t redeveloped components like silica using a current version of QT6. To a degree this didn’t matter as long as Jolla (and SailfishOS!) was on life support still eking out an occasional minor update on the aging Xperia 10 hardware, but this is not where we are now… Right now, we’re all in the happy position of looking back at a successful launch of new Jolla hardware, so I am being forced to look forward to consider what a healthy SailfishOS ecosystem look like? I don’t believe that looks like asking prospective app developers in 2027 to get excited about using an obsolete GUI toolkit from eleven years ago. One that bears little relation to tooling used right now to create their desktop and desktop apps. So, what’s the plan? Update QT6 / Adopt GTK / Something else…
4. Approx. time needed: 5m
5. Substitute (optional): apologies, i will read the discussion afterwards.

[hschmitt]

You would help everyone if you could condense your description to 20% at most. Thank you.

[usbee]

I shortened it. Shortening further would cause the loss of concrete requests.

[frankps]

This is almost a question about a more detailed roadmap towards SFOS 6 and beyond.

[usbee]

A more detailed roadmap would really be welcomed. System76 as an example has a very clear and decent roadmap for their future releases. I’d expect nothing less from Jolla aswell.

[nthn]

There used to be one, about ten years ago! But it was no longer updated during the dark ages, and eventually the old, outdated roadmap got taken offline. Let’s hope the reinvigorated interest in Sailfish will reinvigorate the roadmap as well.

[PeegeeTips]

almost, and yet decisively not:

deliberately kept it tightly focused on the future of QT in a world that has a successful Jolla Phone 2026 launch.

[CLMA31]

I also would like to see Qt upgrade! Tried to look from their website, does QT offer currently license which Jolla could use, but wouldn’t be required to pay for every sold phone extra license? If I’m not mistaken, Jolla would need Qt Pricing & Plans for Each Stage of Software Development the Qt for DC Professional license? Which would then need as a addition the Qt Distribution License for every sold phone? Or do you know how Qt licensing goes?

[PeegeeTips]

@CLMA31

Or do you know how Qt licensing goes?

No, no idea.

[yusssufff]

• Name/IRC nick: @yusssufff

• Topic: Softening a specific Harbour restriction: Add a “call” class to classify streams. Until now only the game and player call are available: Specifically, currently libaudioresource only offers player and game. A call type in libaudioresource should help any store app doing voice or video calls.

• Some details about the topic: Devs are working on getting video calls to work with the native telegram’s client Fernschreiber. There is a will to have the calls and video calls done in a Harbour-compatible way. They identified that to be published in Harbour, the “call” class should be available in libaudioresource. You can dig in here: Add Telegram voice & video calls (tgcalls + tg_owt) by JimKnopfIoT · Pull Request #583 · Wunderfitz/harbour-fernschreiber · GitHub

• Approx. time needed: 2mn

• Substitute (optional): I’ll do my best to be there, cannot promiss since i have huge workdays workload unfortunately.

[yusssufff]

• Name/IRC nick: @yusssufff

• Topic: Getting the community work on the Xperia 10 V’s cameras merged in @Jolla ‘s build

• Some details about the topic: Devs are working on getting Xperia 10 V Camera’s to work with the blobs version 4b. Most of the work actually doesnt imply messing with the binaries themselves (exept eventually for telephoto aka 0.6, but telephoto could be left on the side, as quite a non-essencial lense). Could @mal maybe have a look at incorporating that work into the official build? Even fast, as a quick hotfix for the 5.2 release? Having cameras now working on the 10 V would makes a huge instant change in usability, therefore the faster the better…Here is the link of the community work: [GUIDE] How to enable all cameras on Xperia 10 V

Edit: here is a second community guide effort: Xperia 10 V (zambezi): Enabling all cameras + Hardware video on Sailfish OS

• Approx. time needed: 3mn

• Substitute (optional): I’ll do my best to be there, cannot promiss since i have huge workdays workload unfortunately.

[parth007]

Name/IRC nick: Parth007

Topic: Xperia 10 V (5.1.0.11) – community fixes for SIM loss after boot, slow boot, mic and fingerprint

Some details about the topic:

I’ve been debugging the Xperia 10 V on 5.1.0.11 and have working fixes, all in one package: [GUIDE]Xperia 10 V:faster boot, mic, SIM recovery, fingerprint .

Questions for Jolla:

1. “No SIM card” after some boots: ofono crashes (SIGSEGV) ~60 s after boot during SIM setup, right after “session_read_info not implemented”. The restarted ofono sends setRadioPower 0 while the SIM is already active, so the modem powers the card down (uim POWER_DOWN, card error 0x17). Restarting only the RIL (vendor.qcrilNrd / qcrilNrd2) brings the SIM back; I use an automatic watcher for that now. ofono also segfaults when simply restarted. Is this known, and can it be fixed in ofono / ofono-binder?

2. Slow boot: bluebinder.service is Type=notify, so boot waits for Bluetooth, and the BT HAL often fails chip init at boot. Making bluebinder non-blocking cut a full reboot from 4:02 to 2:23. Could this go into the 10 V adaptation?

3. Mic: primary_audio_policy_configuration.xml only allows 24-bit for “primary input”. A 16-bit recording makes pulseaudio-modules-droid loop until RLIMIT_RTTIME kills PulseAudio, giving quiet or broken recordings and no sound until reboot. Adding a 16-bit profile (plus +12 dB gain) fixes it. Can this be shipped?

4. Fingerprint: the open-source HAL fails (“SetDataPath failed rc=1”) with the current egisap TA. Sony’s stock HAL plus a small shim to the et51x driver works (enrol, unlock, survives reboot). Is official fingerprint support planned for the 10 V?

Approx. time needed: 10–15 minutes

Substitute (optional): I’m in North America and work across several time zones, so I’ll try to join but can’t promise.

[CLMA31]

Late to the party, can be skipped, but I assumed this would have easy yes/no answer

1. Name/IRC nick: CLMA31
2. Topic: SailfishOS 5.3 and OP-mobiili
3. Some details about the topic: As Jolla showed in Stockholm, you guys have done some magic and gotten Revolut to work! That is great and I was wondering have you also been able to get OP-mobiili to work with 5.3? Just asking, if yes I’m happy to wait for release. In case no, I might need to consider some rather quick moves to solve the problem on personal level.
4. Approx. time needed: 1min, written answer is enough. No need to debate
5. Substitute (optional): None, I might not be able to join, but written answer is all I’m looking at. Kiiitos ja anteeksi

[CLMA31]

This one will be super interesting. I did some further investigation and brainstormed the found information with LLM (+LLM did full work estimation as I don’t understand anything from software world). It seems that each Jolla dev would need Qt dev license + every phone sold would need the device license and the price seems to vary between qty ballparks.

LLM estimated that the upgrade for all necessary repos would require veeery substantial work from Jolla (LLM estimate was +27 000 work hours). + then the actual licenses for devs and for every sold phone, which with my idiotic math indicates 6-figures yearly easily. With 15k-20k sold phones this year, might be quite a stretch with, there should be some EU / Finnish financial tools to help with this. I definitely see this as a shitty situation, but something needs to change if CRA kicks in next year will full force. I would imagine that SailfishOS would need to become compliant to get in to the B2goverment or B2B world.

[rainemak]

Let’s have the OP-mobiili question in the next meeting. Those AppSupport teaser stuff that we showed in Stockholm may or may not land to the Sailfish OS 5.3. Let’s see if we could get latest OP-mobiili tested with the plausible changes.

[Gepardi55]

That would be very useful for many Finnish users. These banking issues are quite important in general and would be worth to prioritize if possible.

[rainemak]

Minutes: #sailfishos-meeting: Sailfish OS, open source, collaboration -- October 29, 2026
Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2026/sailfishos-meeting.2026-10-29-17.00.txt
Log: #sailfishos-meeting log

[PeegeeTips]

Just add some exposure to what was discussed (thank you all):

17:21:25 #info I’d proposed that we would use this topic to discuss about potential toolkits. What other toolkits would you like to see?

17:22:12 Flutter (ducks’n’runs)

17:22:35 I’d like to see Kirigami app being functional on SFOS, so apps made for Plasma Mobile. For now plenty dependencies are missing for it.

17:23:01 usbee, I’d like to avoid kde library dependancy hell at all costs

17:23:21 <CLMA31[m]> I don’t have technical knowhow one bit (and don’t know any toolkits), but in Jolla’s eyes: is it easier to do the whole Qt upgrade or get rid of Qt all together?

17:23:37 Since KDE is also Qt based it would be nice to see some cooperation. I would even like to see a SailfishOS version shipped with Plasma Mobile. On desktop it’s normal for a distro to have multiple DE choices. 17:24:06 You’re looking for Mer

17:24:53 @poetaster Well, whether you like it or not there are plenty of native mobile Linux apps that are not functional whether they are GTK or KDE apps, because of lacking libraries. It is significantly easier to run the Android version of those apps if they exists than the native one.

17:25:01 usbee, I contributed some to rinigus and piggz efforts with 5.15 and the whole kde ecosystem. While there are ‘benifits’ I personally won’t go there again since I don’t want any of the kde apps.

17:26:03 @zhasha I’m looking for a mobile distro with Android AppSupport or equal and DE options. There aren’t any since Waydroid is pretty inferior to AAS in my eyes.

17:26:36 The support overhead for something like that would be enormous

17:26:47 Ok, we’re drifting. Jolla, QT6 plans outside of piggz & rinigus efforts?

17:27:43 <CLMA31[m]> I apologize before hand my technical lag of understanding and stupid question… But would it be possible to natively ship something what piggz and rinigus have pulled of so app development could direct more towards Qt6?

17:27:43 and then we have gtk which could be an option

17:27:55 switching toolkit would be a lot bigger effort than qt update

17:28:07 <CLMA31[m]> Thanks mal!

17:28:30 more like adding another toolkit as an option

17:28:31 yeah, let’s stick to QT please.

17:28:56 I’m thinking more like application developer point of view

17:29:00 rainemak, did you see the experimental flutter hello world?

17:29:35 GitHub - MrCyjaneK/flutter-sailfishos · GitHub

17:29:45 thanks, will check as well

17:30:51 <CLMA31[m]> Would it be possible for Jolla to ship the Qt6 packages alongside the current once so apps could direct to that? Similarly like currently is achievable through piggz and rinigus effort

17:32:01 CLMA31[m], I’d rather not start discussing technical possibilities here as that ends up being endless

17:32:23 <CLMA31[m]> Thanks for the answer

17:32:36 CLMA31[m]: well you also need to take into account disk space usage

17:33:08 <CLMA31[m]> But to me that would seem like something that possible could be done without throwing huge amounts of money to Qt?

17:33:37 <CLMA31[m]> Sure! But with Jolla phone and 256gb I would imagine it to be feasible

17:34:09 It also could be optional, like AAS or MicroG and other stuff.

17:34:15 Thank you all for your input… let’s move on