Community meeting on 6th November 2025

Announcements
1

Please note new time slot

Schedule: Thursday 2025-11-06T16:00:00Z :world_map: :date:

Sailfish OS Community Calendar (ICS format)

Please note changing of clock on last Sunday of October (standard time).

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 agreed 9th October to extend meeting time slot to 90mins. Same time slot still.

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:
3 Likes
2

  • Name/IRC nick: Frank Paul Silye (frankps)

  • Topic: Jolla C2 order backlog

  • Some details about the topic: Could Jolla give us an update on the backlog situation? Estimated shipping time October 1st was 6-8 weeks. Where are we now? When will you start shipping out ordered devices?

  • Approx. time needed: less then 5 minutes

  • Substitute (optional): I will not be present as I’m not using IRC, but I’m reading the meeting logs here in the forum.

3 Likes
3

There is a web based client available at
https://webchat.oftc.net/ so you don’t have to install any client software.

2 Likes
4

Thank you, I used IRC a lot through the years. I’m spending time with my two young boys when the community meetings are finding place. It is as simple as that - family comes first :heart:

3 Likes
5
  • Name/IRC nick: pherjung
  • Topic: GTK support
  • Some details about the topic: The Librem 5 supports an increasing number of GTK apps. While they do not adhere to Sailfish OS UI/UX guidelines, they are Linux apps and would increase the number of apps available on Sailfish OS. Are there any plans to support GTK, and how much effort would it take?
  • Approx. time needed: 5 minutes
  • Substitute (optional): Unfortunately, I won’t be present.
10 Likes
6
  • Name/IRC nick: ExTechOp
  • Topic: Sony Xperia 10 IV/V port status
  • Some details about the topic: A functional Sony device port has now been “real soon now” since Love Day 2 in August 2024, but they still suffer from serious issues because of Sony binary blobs. Also, a Jolla announcement on the status of the Sony devices port has now been teased for months, but even this hasn’t materialized. This is just getting embarrassing. Please put out an official statement outlining some kind of time scale when things will begin to happen, or just admit it’s never happening. If all this fails, at least give a time scale when you’ll be able to clarify things.
  • Approx. time needed: 10 minutes
15 Likes
7

  • Name/IRC nick: balta

  • Topic: Security patch level updates of the Android runtime

  • Some details about the topic: Google releases monthly security patches for Android, but sadly these are never applied to the android app support runtime of SailfishOS. You can check your security patch level in Settings → Android App Support. As these patches contain security fixes they should be included regularly in SailfishOS updates as well. Right now on the 10V the level is from August of 2024, I think on older devices this will be even older. Also some apps will check this and refuse to start, e.g. I cannot use Teams for my job right now because of a too old security patch level. Is this a big effort for Jolla to provide an update or is it something like simply triggering a CI chain?

  • Approx. time needed: 5 minutes

  • Substitute (optional): Sadly because of private appointments I cannot promise to be available

8 Likes
8

This should cover this community meeting topic Update on Jolla C2 Q4/25 production batch. We can have this still as a discussion topic if you like so.

6 Likes
9

Thanks for the update. It answers my question in advance of the community meeting.

3 Likes
10

Indeed it is older. On my 10 iii running 5.0.0.71 the Android security patch level is 5th February 2024, soon coming up to two years out of date.

11
  • Name/IRC nick: Fellfrosch
  • Topic: How shall we deal with trolls in the forum
  • Some details about the topic: Trolls quite often ruin a discussion in the forum. It is quite easy for them to do so, because threads get blocked when they get flagged. This is stopping quite often good and helpful conversation. So the question is how do we want to deal with this problem in future. For me the better solution instead of freezing threads would be temporary bans for people who misbehave and don’t cling to the forum rules.
    I already started a thread about that problem here:
    Please stop closing threads because of trolls
  • Approx. time needed: 10 minutes
  • Substitute (optional): Unfortunately because of private appointments I cannot attend.
13 Likes
12

Minutes: #sailfishos-meeting: Sailfish OS, open source, collaboration -- 6th November 2025
Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2025/sailfishos-meeting.2025-11-06-16.00.txt
Log: #sailfishos-meeting log

9 Likes
13

Wow, is @rainemak suggesting we could see ‘goodbye lipstick, welcome Weston’ arch? i’m all for it, maybe a separate thread is in order, also the screw aosp, welcome ODP blob adaptations, officially supported community ports??? Nope, it’s not april 1st, wtf is happenning?

4 Likes
14

I’m all for officially supported community port with AAS support. That is everything I ask for, since Jolla can’t solve the licensing puzzle as a company, but the community can live on top of Lineage and with AAS it would be a dream device. Especially the better hardware ones, like 1 and 5 IV (and probably newer later).

14 Likes
15

Happy to read about sailfish-compositor plans and poc earlier! In addition to Weston another alternative might be to base the sailfish-compositor on wlroots (https://gitlab.freedesktop.org/wlroots/wlroots/), which is a modular modern Wayland compositor library/framework used by multiple compositors.

I don’t know Weston and wlroots enough to estimate if it’s easier to adapt Weston to sailfishos or make something suitable for sailfishos with wlroots.

9 Likes
16

I would say that choosing different approach is actually a MUST, or else those devices will never get beyond Sony ODP’s buggy blobs that clearly aren’t going to get fixed anytime soon, if ever. So it is actually a matter of either ever making those devices normally usable, or not.

As other people report elsewhere, there are 100% functional Lineage OS releases for both those devices, so let’s free the 10 IV / V from the dead end of buggy and not-to-be-ever-fixed Sony blobs and enable them to do it a way similar to LOS, whatever it takes from the licencing perspective: making it a “community port”, requiring the user to get the blobs from a LOS distribution and flashing them separately, or whatever else. Whatever can finally make those devices normally usable, now that it is literally impossible to buy the 10 III in a decent condition. I don’t know what I’d do if my 10 III breaks anytime soon, as there’s literally nothing to replace it with for SFOS. And that’s while a brand new and powerful 10 V has been catching dust in my drawer since May 2024.

So yes, please make it an “officially supported community port”, or whatever else could permit it becoming fully usable with SFOS.

As for releasing AAS for such a “community port”, YES, I’d be happy to buy a licence for it, and pay for it not less than what a 10 IV / V SFOS licence would cost otherwise.

20 Likes
17

There is also Louvre GitHub - CuarzoSoftware/Louvre: C++ library for building Wayland compositors.

This compositor replacement cant come soon enough.

2 Likes
18

Unsure what @rainemak means by supported community port, like “we can’t, plz help, AAS will be free for you in return”?

Not really my jam, got my FP5 and will buy Android AppSupport for it the moment I can. Take my money.

4 Likes
19

give me an officially supported community port for the 10vi (that I own) and the 10vii (that I want to own), and i’ll be delighted.

1 Like
20 
16:33:12 <rainemak> #info <Jolla> We have also been thinking about completely different approaches by
16:33:14 <rainemak> #info <Jolla> enabling this thru an “officially supported community port” -
16:33:16 <rainemak> #info <Jolla> community port and we enable AppSupport to it – would that work for
16:33:18 <rainemak> #info <Jolla> the community?

Yes, if I hadn't already moved beyond considering the 10vi/v.
If it's the best way to support that sat around with those devices in hand, great, but i'm no longer interested in buying a long since superceded handset.