#sailfishos-meeting: Sailfish OS, open source, collaboration -- 9th October 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/24948 (rainemak, 16:00:00)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:00)
    1. Raine Mäkeläinen, Jolla (rainemak, 16:00:08)
    2. Otto Makela, community (ExTechOp, 16:00:09)
    3. mal, Jolla (mal, 16:00:13)
    4. Ruben -rubdos- De Smet, community (rubdos[m], 16:00:24)
    5. Ville Nummela, community (ViGe, 16:00:24)
    6. CLMA31, community (CLMA31[m], 16:00:32)
    7. David Llewellyn-Jones, community (flypig, 16:00:48)
    8. Matti Viljanen, Jolla (direc85[m], 16:01:01)
    9. Nico, community (Nico, 16:01:01)
    10. 247, community member (legacychimera247, 16:01:24)
    11. Pami Ketolainen, Jolla (Keto, 16:02:14)
    12. Thorsten M., community (mini_coe[m], 16:02:58)

  3. Amount of supported devices (10 mins -- CLMA31) (rainemak, 16:05:14)
    1. <CLMA31> I am too new here to have historical package and understand that (rainemak, 16:05:14)
    2. <CLMA31> this topic might be unpopular. But anyway is this list up to (rainemak, 16:05:14)
    3. <CLMA31> date: Supported Devices | Sailfish OS Documentation? If so has it (rainemak, 16:05:14)
    4. <CLMA31> been considered that most of the devices could be moved to (rainemak, 16:05:14)
    5. <CLMA31> “Ceased support” category? I don’t know if in reality keeping so (rainemak, 16:05:15)
    6. <CLMA31> many models supported causes any extra work for upkeep. But I (rainemak, 16:05:17)
    7. <CLMA31> would guess it does, which is why I ask. Wouldn’t it make more (rainemak, 16:05:19)
    8. <CLMA31> sense to focus only few models at the time and really fine tune (rainemak, 16:05:21)
    9. <CLMA31> the user experience? Maybe it would make development like the (rainemak, 16:05:23)
    10. <CLMA31> Perceived responsiveness of the UI easier and faster? (rainemak, 16:05:25)
    11. https://docs.sailfishos.org/Support/Supported_Devices/ (rainemak, 16:05:29)
    12. https://forum.sailfishos.org/t/perceived-responsiveness-of-the-ui/2499/82 (rainemak, 16:05:29)
    13. <Jolla> This we already somewhat answered in some other context. We said (rainemak, 16:06:30)
    14. <Jolla> that we're not dropping older officially supported Sailfish OS (rainemak, 16:06:30)
    15. <Jolla> devices. Quite commonly it's the kernel that dictates the timing (rainemak, 16:06:31)
    16. <Jolla> of dropping older devices. We actually have a matrix of things to (rainemak, 16:06:31)
    17. <Jolla> support being it number of devices, kernel version and AppSupport (rainemak, 16:06:31)
    18. <Jolla> which is making it more difficult. (rainemak, 16:06:33)
    19. <Jolla> (rainemak, 16:06:35)
    20. <Jolla> We have quite a wide community user base using in Xperia line (rainemak, 16:06:37)
    21. <Jolla> devices which is super good. You are reporting issues and using (rainemak, 16:06:39)
    22. <Jolla> them. That's also part of way of doing things -- we want to (rainemak, 16:06:41)
    23. <Jolla> support devices as long as it is feasible. (rainemak, 16:06:43)

  4. Open Sourcing: Expectations (10mins -- nephros) (rainemak, 16:15:03)
    1. <nephros> It’s great that the Open-Sourcing process has finally landed, (rainemak, 16:15:03)
    2. <nephros> and we have seen repos (currently: Weather and Notes, with (rainemak, 16:15:03)
    3. <nephros> Camera recently added) appear on Github. (rainemak, 16:15:04)
    4. <nephros> In communications prior to the relicensing and publishing, it (rainemak, 16:15:06)
    5. <nephros> has been said that depending on what happens with these “Test (rainemak, 16:15:08)
    6. <nephros> Balloon” applications, more could follow. (rainemak, 16:15:10)
    7. <nephros> What are the factors that are monitored at Jolla regarding this, (rainemak, 16:15:12)
    8. <nephros> or what is the expectation of what kinds of community (rainemak, 16:15:14)
    9. <nephros> contributions will happen? (rainemak, 16:15:16)
    10. <nephros> In other words, what would be something that would indicate to (rainemak, 16:15:18)
    11. <nephros> the ones in deciding positions that “Hey, Open-Sourcing has been (rainemak, 16:15:20)
    12. <nephros> a great success for us, let’s do more of that!”. (rainemak, 16:15:22)
    13. <Jolla> A very good question as well. As you may think, it's about the (rainemak, 16:15:24)
    14. <Jolla> traction being contributions, bug reports, feature proposals, (rainemak, 16:15:26)
    15. <Jolla> percieved welcoming, etc. At the same time, we want to be (rainemak, 16:15:28)
    16. <Jolla> transparent on these. You can go and check what these open sourced (rainemak, 16:15:30)
    17. <Jolla> apps do. What's the actual factor probably will be something that (rainemak, 16:15:34)
    18. <Jolla> has likely a bit of objective and subjective aspects as all cannot (rainemak, 16:15:36)
    19. <Jolla> be easily measured. (rainemak, 16:15:38)

  5. Unable to set lock pin for Android apps requiring it (mins -- CLMA31) (rainemak, 16:30:55)
    1. <CLMA31> There has been multiple persons reporting that they are unable to (rainemak, 16:30:55)
    2. <CLMA31> set lock pin for Android apps that require it. Usually the apps (rainemak, 16:30:55)
    3. <CLMA31> requiring the pin are quite crucial for peoples daily usage. Has (rainemak, 16:30:55)
    4. <CLMA31> this been investigated by Jolla and is this at some roadmap on (rainemak, 16:30:55)
    5. <CLMA31> planned fixes? Here is couple links of the subjects: Unable to (rainemak, 16:30:57)
    6. <CLMA31> set lock pin for Android apps requiring it & Android app (rainemak, 16:30:58)
    7. <CLMA31> requiring lock pin (rainemak, 16:31:00)
    8. https://forum.sailfishos.org/t/unable-to-set-lock-pin-for-android-apps-requiring-it/15806 (rainemak, 16:31:11)
    9. https://forum.sailfishos.org/t/android-app-requiring-lock-pin/8204 (rainemak, 16:31:11)
    10. <Jolla> This is well an understood topic but again not so easy to tackle -- so has been investigated. (rainemak, 16:31:11)

  6. Any new information about next gen Jolla phone (5mins -- CLMA31) (rainemak, 16:35:21)
    1. <CLMA31> Many of us are probably almost holding our breath if we could get (rainemak, 16:35:21)
    2. <CLMA31> some updates on next gen Jolla phone. Most interesting topic on (rainemak, 16:35:21)
    3. <CLMA31> this is, will there be next gen Jolla phone? There seem to be (rainemak, 16:35:21)
    4. <CLMA31> more and more interest for alternative solutions and as Sailfish (rainemak, 16:35:21)
    5. <CLMA31> offers just that, but many which or need better HW phone. Is (rainemak, 16:35:23)
    6. <CLMA31> there any updates regarding this? (rainemak, 16:35:24)
    7. <Jolla> Unfortunaly, we cannot reveal/expose this yet. (rainemak, 16:35:54)
    8. <Jolla> Please, do understand. (rainemak, 16:35:54)
    9. https://forum.sailfishos.org/t/next-gen-jolla-phone/23882 (rainemak, 16:37:42)

  7. Roadmap (10mins -- Cryx) (rainemak, 16:41:09)
    1. <Cryx> Having a general Roadmap again (and regular posts on the official (rainemak, 16:41:09)
    2. <Cryx> Jolla blog) would be an addition to this topic - right know we all (rainemak, 16:41:09)
    3. <Cryx> can just guess s into the blue to where the journey might go on (rainemak, 16:41:10)
    4. <Cryx> both software and hardware side. (rainemak, 16:41:10)
    5. <Jolla> A very good raise by Cryx. Thank you. (rainemak, 16:41:37)
    6. <Jolla> First thing is that we need to educate what is roadmap. Quite (rainemak, 16:41:37)
    7. <Jolla> commonly what happens is that one carves the published roadmap (rainemak, 16:41:37)
    8. <Jolla> into a stone. In reality, roadmap is a planning tool that changes (rainemak, 16:41:37)
    9. <Jolla> over time. That's also reason why rainemak has not opened too long (rainemak, 16:41:37)
    10. <Jolla> lasting roadmaps. It just cannot be a "snapshot" from a moment. #info <Jolla> We need to have a proper public tool that we can use as a (rainemak, 16:41:39)
    11. <Jolla> discussion platform. Surely, blog is not good for that. (rainemak, 16:41:41)
    12. <Jolla> (rainemak, 16:41:43)
    13. <Jolla> Still writing to Jolla Blog is good. We're open to take (rainemak, 16:41:45)
    14. <Jolla> contributions to there as well. Simple fact is that writing a (rainemak, 16:41:47)
    15. <Jolla> superior blog compared to writing to announchement to Sailfish (rainemak, 16:41:49)
    16. <Jolla> Forum takes much more time. Theoretically, we could communicate as (rainemak, 16:41:51)
    17. <Jolla> much as you'd like but that's always away from something else. (rainemak, 16:41:53)

  8. Xperia 10V (5mins -- koza) (rainemak, 16:50:52)
    1. <koza> Get some official statement when or if ever we will get camera and (rainemak, 16:50:52)
    2. <koza> rest of main phone features what does not work now ( mainly: (rainemak, 16:50:52)
    3. <koza> camera, jack audio, fingerprint). Just lot of people purchased (rainemak, 16:50:53)
    4. <koza> these Xperias because Jolla promised that until xmass 2024… so (rainemak, 16:50:54)
    5. <koza> would be nice to get real status to decide if selling device is (rainemak, 16:50:56)
    6. <koza> better solution for all who wasted money caused by Jolla (rainemak, 16:50:58)
    7. <koza> promises … thanks (rainemak, 16:51:00)
    8. <Jolla> We'll get back to this with the dedicated topic that we promised (rainemak, 16:51:08)
    9. <Jolla> earlier. We know that we get camera working, battery indicator (rainemak, 16:51:10)
    10. <Jolla> working, maybe some others as well. Fingerprint is a hard nut to (rainemak, 16:51:12)
    11. <Jolla> crack -- frankly it's very likely something that won't happen. (rainemak, 16:51:14)
    12. Filip, community (filip, 17:02:50)

  9. Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:03:52)
    1. https://github.com/sailfishos/jolla-camera/pull/2 (rainemak, 17:04:49)

  10. General discussion (whatever left -- meeting end target 30mins past) (rainemak, 17:12:52)
  11. Next meeting time and date (1 mins) (rainemak, 17:31:17)
    1. Next meeting will be held on Thursday 23rd October 2025 at 04:00pm UTC: 2025-10-23T1600Z (rainemak, 17:35:55)


Meeting ended at 17:37:04 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (243)
  2. rubdos[m] (28)
  3. CLMA31[m] (21)
  4. abr (21)
  5. ExTechOp (18)
  6. flypig (15)
  7. mal (13)
  8. Nico (10)
  9. Keto (10)
  10. direc85[m] (8)
  11. mini_coe[m] (7)
  12. ViGe (6)
  13. TheKit (6)
  14. piggz[m] (5)
  15. Cryx[m] (3)
  16. filip (3)
  17. sailbot (2)
  18. legacychimera247 (1)


Generated by MeetBot 0.1.4.