#sailfishos-meeting: Sailfish OS, open source, collaboration -- 18th December 2025

Meeting started by rainemak at 16:00:00 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: (rainemak, 16:00:00)
    2. https://forum.sailfishos.org/t/25774 (rainemak, 16:00:00)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:00)
    1. Affe Null, community (AffeNull[m], 16:00:28)
    2. jojomen, community (jojomen, 16:00:31)
    3. Ville Nummela, community (ViGe, 16:00:32)
    4. mettska, community (mettska, 16:00:33)
    5. Heng Ye, community (heng, 16:00:44)
    6. Matti Viljanen, Jolla (direc85[m], 16:00:49)
    7. mal, Jolla (mal, 16:00:52)
    8. Otto Mäkelä, community (Guest33872, 16:01:48)
    9. Raine Mäkeläinen, Jolla (rainemak, 16:02:47)
    10. Nico, community (Nico, 16:03:58)
    11. Andrew Branson, Jolla (abr, 16:03:59)

  3. Mainline Linux kernel support for Jolla phones (20-30 mins -- asked by affe_null) (rainemak, 16:06:02)
    1. <affe_null> There is a growing community of mobile Linux enthusiasts who (rainemak, 16:06:02)
    2. <affe_null> are interested in running new close-to-mainline kernels (rainemak, 16:06:02)
    3. <affe_null> instead of vendor kernels originally developed for Android. (rainemak, 16:06:02)
    4. <affe_null> Some people are already asking about mainline support for (rainemak, 16:06:02)
    5. <affe_null> the new Jolla phone. In the past, similar requests have been (rainemak, 16:06:03)
    6. <affe_null> dismissed as not realistic. I think that many things have (rainemak, 16:06:05)
    7. <affe_null> changed now. We don’t have a fully working phone with a (rainemak, 16:06:07)
    8. <affe_null> mainline kernel yet, but some are getting extremely close. (rainemak, 16:06:09)
    9. <affe_null> (rainemak, 16:06:11)
    10. <affe_null> This looks like a good opportunity for Sailfish OS, since (rainemak, 16:06:15)
    11. <affe_null> using a mainline kernel could help with providing longer (rainemak, 16:06:17)
    12. <affe_null> support for devices, attract more developers, and replace a (rainemak, 16:06:19)
    13. <affe_null> lot of low-quality/unmaintained/proprietary manufacturer (rainemak, 16:06:21)
    14. <affe_null> code with community-developed open-source software. (rainemak, 16:06:23)
    15. <affe_null> (rainemak, 16:06:25)
    16. <affe_null> Would Jolla be interested in officially supporting community (rainemak, 16:06:27)
    17. <affe_null> mainlining efforts for supported devices? Are there any (rainemak, 16:06:29)
    18. <affe_null> chances that a close-to-mainline kernel for the Jolla C2 or (rainemak, 16:06:31)
    19. <affe_null> the new Jolla phone will eventually be integrated into (rainemak, 16:06:33)
    20. <affe_null> Sailfish OS, perhaps as an optional alternative? I would (rainemak, 16:06:35)
    21. <affe_null> like to discuss the requirements for this. (rainemak, 16:06:37)
    22. <Jolla> Unfortunately we do not have resources to officially support (rainemak, 16:06:39)
    23. <Jolla> community mainlining efforts. Contributions of course welcome (rainemak, 16:06:41)
    24. <Jolla> to the Jolla C2 git repositories. (rainemak, 16:06:45)
    25. <Jolla> (rainemak, 16:06:47)
    26. <Jolla> Or are you actually asking to support efforts themselves not the (rainemak, 16:06:49)
    27. <Jolla> mainlining itself? (rainemak, 16:06:51)

  4. Additional details on J2 (5mins -- asked by JoshuaStrobl) (rainemak, 16:36:56)
    1. <JoshuaStrobl> 1. U.S. band information - It is communicated that there (rainemak, 16:37:02)
    2. <JoshuaStrobl> will be support for U.S. market (roaming). Could more (rainemak, 16:37:02)
    3. <JoshuaStrobl> specifics be provided on which bands will be supported? (rainemak, 16:37:02)
    4. <JoshuaStrobl> I have at least one friend I could order the device for (rainemak, 16:37:02)
    5. <JoshuaStrobl> that I’ll be meeting up with in Prague next year, but he (rainemak, 16:37:02)
    6. <JoshuaStrobl> needs to know if it’d even support his network. (rainemak, 16:37:03)
    7. <JoshuaStrobl> (rainemak, 16:37:05)
    8. <JoshuaStrobl> 2. Cyan cover? My cyan Jolla One needs a friend. That is (rainemak, 16:37:07)
    9. <JoshuaStrobl> all. (rainemak, 16:37:09)
    10. <JoshuaStrobl> 3. Could STLs or similar of the back cover be made (rainemak, 16:37:11)
    11. <JoshuaStrobl> available so folks can make their own back covers? (rainemak, 16:37:15)
    12. <Jolla> Let’s try to talk about Jolla Phone or Jolla Phone (2026) (rainemak, 16:37:17)
    13. <Jolla> whenever possible :-). (rainemak, 16:37:19)
    14. <Jolla> (rainemak, 16:37:21)
    15. <Jolla> 1. We will design the cellular band configuration to enable (rainemak, 16:37:23)
    16. <Jolla> global travelling as much as possible. Too early to communicate (rainemak, 16:37:25)
    17. <Jolla> actual bands. (rainemak, 16:37:27)
    18. <Jolla> (rainemak, 16:37:29)
    19. <Jolla> 2. Having a Jolla One color friend sounds like an interesting (rainemak, 16:37:31)
    20. <Jolla> idea, let’s see. (rainemak, 16:37:33)
    21. <Jolla> (rainemak, 16:37:35)
    22. <Jolla> 3. We’ll open source the hardware and software interface specs (rainemak, 16:37:37)
    23. <Jolla> of The Other Half so anyone can design, 3D-print, or produce (rainemak, 16:37:39)
    24. <Jolla> their own modules. So, answer to your question is yes. (rainemak, 16:37:41)
    25. https://forum.sailfishos.org/t/the-other-half-returns-community-innovation-program/26011 (rainemak, 16:43:30)

  5. Future plans of the Qt update (10mins -- asked by CLMA31) (rainemak, 16:43:50)
    1. <CLMA31> During the summer community meeting there were talks that the (rainemak, 16:43:55)
    2. <CLMA31> biggest reason Qt update haven’t happened was that there was (rainemak, 16:43:55)
    3. <CLMA31> not yet any customer willing to pay for it. After that Sami (rainemak, 16:43:55)
    4. <CLMA31> mentioned that there had been thinking of splitting the (rainemak, 16:43:55)
    5. <CLMA31> SailfishOS to fully open source version where Qt update could (rainemak, 16:43:55)
    6. <CLMA31> then be done and keeping other version for B2B customers. Has (rainemak, 16:43:57)
    7. <CLMA31> there been any development on this front? On other hand, I (rainemak, 16:43:58)
    8. <CLMA31> hope that financial situation of Jolla has improved and who (rainemak, 16:44:00)
    9. <CLMA31> know, maybe there could be money even to pay for Qt (rainemak, 16:44:02)
    10. <CLMA31> licenses :slight_smile: PS: STUNNING job with the J2 launch so (rainemak, 16:44:04)
    11. <CLMA31> far! Really excited to get my hand on one (rainemak, 16:44:06)
    12. <Jolla> No development updates to share now. A model where we would (rainemak, 16:44:18)
    13. <Jolla> have fully open source version and keeping “current” for B2B (rainemak, 16:44:18)
    14. <Jolla> customers could be still an option. (rainemak, 16:44:18)

  6. Unable to call local emergency from lock screen (5-10 mins -- asked by CLMA31) (rainemak, 16:48:19)
    1. <CLMA31> There has been great discussion about the problem in here (rainemak, 16:48:19)
    2. <CLMA31> Reliable emergency calls - #11 by jrg and at least here Unable (rainemak, 16:48:19)
    3. <CLMA31> to call local emergency number, only 112 - #30 by moripeluka. (rainemak, 16:48:19)
    4. <CLMA31> There has been reports that it is not possible to call local (rainemak, 16:48:19)
    5. <CLMA31> emergency numbers from lock screen, only 112. This sounds at (rainemak, 16:48:21)
    6. <CLMA31> least easy and important thing to fix why I want to raise the (rainemak, 16:48:22)
    7. <CLMA31> problem. There has been also reports that calling to the (rainemak, 16:48:24)
    8. <CLMA31> emergency service hasn’t worked at all in the urgent need. It (rainemak, 16:48:26)
    9. <CLMA31> would be great to hear if Jolla has been able to investigate (rainemak, 16:48:28)
    10. <CLMA31> that and is there hopes to get that working reliable? (rainemak, 16:48:30)
    11. https://forum.sailfishos.org/t/reliable-emergency-calls/26085/11 (rainemak, 16:48:32)
    12. https://forum.sailfishos.org/t/unable-to-call-local-emergency-number-only-112/20800/30 (rainemak, 16:48:34)
    13. <Jolla> Should go without saying that this is a topic that we are (rainemak, 16:48:43)
    14. <Jolla> taking seriously. We do not know yet what exactly is the (rainemak, 16:48:43)
    15. <Jolla> mechanism on how operators select the devices that are banned (rainemak, 16:48:43)
    16. <Jolla> nor how the devices are identified. Same time this probably (rainemak, 16:48:44)
    17. <Jolla> affects other custom Android ROMs. (rainemak, 16:48:46)

  7. AAS-Support on community ports (5mins -- asked by mettska) (rainemak, 16:57:20)
    1. <mettska> I believe I read somewhere in the past, that Jolla is (rainemak, 16:57:26)
    2. <mettska> thinking about supporting AAS on community ports. The port (rainemak, 16:57:26)
    3. <mettska> for the Xperia 1IV/5IV seems to have a high quality. Is there (rainemak, 16:57:26)
    4. <mettska> a chance it could be (the first) supported community port? (rainemak, 16:57:26)
    5. <mettska> (rainemak, 16:57:26)
    6. <mettska> Here you find the information and discussion about the port (rainemak, 16:57:27)
    7. <mettska> itself: Sony Nagara (Xperia 1IV and 5IV) port (rainemak, 16:57:29)
    8. https://forum.sailfishos.org/t/sony-nagara-xperia-1iv-and-5iv-port/25136 (rainemak, 16:57:31)
    9. <Jolla> It’s very unlikely that Xperia 1 IV / 5 IV would be the first (rainemak, 16:57:55)
    10. <Jolla> community port to get the AppSupport (and other commercial (rainemak, 16:57:55)
    11. <Jolla> components). Currently we are very busy with all related to (rainemak, 16:57:55)
    12. <Jolla> Jolla Phone product program. Further, we give ourselves a bit (rainemak, 16:57:55)
    13. <Jolla> of Christmas break. Surely, we have been thinking how to expand (rainemak, 16:57:55)
    14. <Jolla> AppSupport for community ports. More on that later. (rainemak, 16:57:57)

  8. Waiting for the end of FOSDEM before to close J2 sales. (5mins -- asked by Ric9k) (rainemak, 17:01:26)
    1. <mettska> Someone evoked this on the Sfos TG: J2 could have some (rainemak, 17:01:26)
    2. <mettska> success during FOSDEM. (rainemak, 17:01:26)
    3. <mettska> (rainemak, 17:01:26)
    4. <mettska> Isnt’t it a bit too bad to close the sales just before the (rainemak, 17:01:26)
    5. <mettska> end? (rainemak, 17:01:27)
    6. <Jolla> We are seriously considering the 10k as an upper limit for the (rainemak, 17:01:56)
    7. <Jolla> pre-orders as a manageable amount and working capital for the (rainemak, 17:01:56)
    8. <Jolla> components. Please also note the memory chip prices are (rainemak, 17:01:56)
    9. <Jolla> skyrocketing increasing the Bill-of-Materials (BoM). (rainemak, 17:01:56)

  9. Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:06:41)
  10. General discussion (10 mins or something) (rainemak, 17:09:45)
  11. Next meeting time and date (2 mins) (rainemak, 17:21:33)
    1. Next meeting will be held on Thursday 15th January 2026 at 04:00pm UTC: 2026-01-15T1600Z (rainemak, 17:24:08)


Meeting ended at 17:25:23 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (162)
  2. jojomen (18)
  3. mal (17)
  4. AffeNull[m] (13)
  5. Nico (10)
  6. ExTechop- (10)
  7. direc85[m] (5)
  8. mettska (4)
  9. heng (4)
  10. abr (4)
  11. JoshuaStrobl[m] (3)
  12. mini_coe[m] (3)
  13. sailbot (2)
  14. ViGe (2)
  15. piggz[m] (2)
  16. roundedrectangl (2)
  17. Guest33872 (1)
  18. cquence (1)
  19. Keto (1)


Generated by MeetBot 0.1.4.