================================================================================
#sailfishos-meeting: Sailfish OS, open source, collaboration -- October 15, 2026
================================================================================


Meeting started by rainemak at 16:00:47 UTC. The full logs are available
at
https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2026/sailfishos-meeting.2026-10-15-16.00.log.html
.



Meeting summary
---------------
* Meeting information and agenda can be found here:  (rainemak,
  16:00:47)
* LINK: https://forum.sailfishos.org/t/34402   (rainemak, 16:00:47)
* Brief introduction (5 min). Please prefix your name/handle with #info
  (rainemak, 16:00:47)
  * Raine Mäkeläinen, Jolla  (rainemak, 16:00:49)
  * Otto Mäkelä, community  (extechop[m], 16:01:02)
  * 247 community  (eve247, 16:01:58)
  * Peter G./nephros, community  (nephros, 16:02:03)
  * Alessandro / Orologiaio, community  (Orologiaio, 16:02:36)
  * Damien Caliste, community  (dcaliste, 16:02:44)
  * Balázs Szulovszky, community  (usbee, 16:03:07)

* Tracking of non-resolved Community Meeting topics  (rainemak,
  16:05:20)
  * ACTION: Community task board  (rainemak, 16:05:20)
  * LINK:
    https://forum.sailfishos.org/t/community-meeting-on-23rd-april-2026/29030/3
    (rainemak, 16:05:20)
  * ACTION: Jolla to update regarding recommended charging cables and
    chargers.  (rainemak, 16:05:20)
  * LINK:
    https://forum.sailfishos.org/t/community-meeting-on-7th-may-2026/29253/2
    (rainemak, 16:05:20)
  * ACTION: The Privacy Switch in relation to Ambiances  (rainemak,
    16:05:21)
  * LINK:
    https://forum.sailfishos.org/t/community-meeting-on-july-16-2026/30378/7
    (rainemak, 16:05:23)
  * No actions taken yet regarding community task board nor charger /
    cables.  (rainemak, 16:05:25)

* Are there plans to support PWAs? (10 mins -- usbee)  (rainemak,
  16:05:54)
  * <usbee> PWA (Progressive Web Apps) could be a really handy stopgap
    for  (rainemak, 16:05:54)
  * <usbee> missing native apps and also reduce the dependency on
    Android  (rainemak, 16:05:54)
  * <usbee> apps. For now it is only possible to create web shortcuts to
    the  (rainemak, 16:05:54)
  * <usbee> app grid but that’s it.  (rainemak, 16:05:55)
  * <Jolla> Yes, once we have time for completing the support. It’s in
    the  (rainemak, 16:06:05)
  * <Jolla> plans but not yet scheduled for any particular release.
    Browser  (rainemak, 16:06:05)
  * <Jolla> stack point of view, we are not too far from being PWA
    compatible  (rainemak, 16:06:05)
  * <Jolla> as most of the features that are part of the PWA are already
    there  (rainemak, 16:06:05)
  * <Jolla> in the engine. Getting rid of the browser user interface is
    the  (rainemak, 16:06:05)
  * <Jolla> simplest of them all. What we clearly do not have is install
    /  (rainemak, 16:06:07)
  * <Jolla> uninstall feature for the Sailfish Browser.  (rainemak,
    16:06:08)
  * <Jolla> Quote from mozilla.org: “PWAs typically look like platform-
    (rainemak, 16:06:10)
  * <Jolla> specific apps － they are usually displayed without the
    browser UI  (rainemak, 16:06:14)
  * <Jolla> around them － but they are, as a matter of technology, still
    (rainemak, 16:06:16)
  * <Jolla> websites.”  (rainemak, 16:06:18)
  * LINK:
    https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/What_is_a_progressive_web_app
    (rainemak, 16:06:20)
  * <Jolla> Finally, we don’t need to think PWA as a stopgap solution as
    it  (rainemak, 16:06:23)
  * <Jolla> should be an option along with the other options.
    (rainemak, 16:06:25)
  * LINK:
    https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps
    (rainemak, 16:06:27)
  * LINK: https://www.w3.org/TR/widgets/   (rainemak, 16:18:06)

* Solving the SMS receiving problem (5 mins -- legacychimera247)
  (rainemak, 16:18:28)
  * <legacychimera247> Some weeks ago my local record shop wrote me an
    sms to  (rainemak, 16:18:28)
  * <legacychimera247> notify me about a very limited release, i didn’t
    see  (rainemak, 16:18:28)
  * <legacychimera247> that, but casually i was going in there for other
    (rainemak, 16:18:28)
  * <legacychimera247> things so i could order the record in time. The
    reason  (rainemak, 16:18:28)
  * <legacychimera247> why i didn’t see the message is that my Jolla
    Phone 2  (rainemak, 16:18:29)
  * <legacychimera247> didn’t receive any message. It’s not a JP2
    problem,  (rainemak, 16:18:31)
  * <legacychimera247> it’s a Sailfish one cause i’ve been plagued with
    this  (rainemak, 16:18:33)
  * <legacychimera247> bug since forever on my XA2 and i sadly see
    situation  (rainemak, 16:18:35)
  * <legacychimera247> is not changed on newer releases of Sailfish.
    Will this  (rainemak, 16:18:37)
  * <legacychimera247> ever be solved?i lost count of lost messages
    through  (rainemak, 16:18:39)
  * <legacychimera247> the years due to this bug, and it would be nice
    to see  (rainemak, 16:18:41)
  * <legacychimera247> it solved, since i consider sms the most basic
    (rainemak, 16:18:45)
  * <legacychimera247> functionality of a phone...  (rainemak, 16:18:47)
  * <Jolla> There are a lot of possible root causes triggering this. As
    a rule  (rainemak, 16:18:49)
  * <Jolla> of thumb with issue reports, when we have clear steps to
    reproduce  (rainemak, 16:18:51)
  * <Jolla> an issue it’s much more easier to fix it. Then when it comes
    to  (rainemak, 16:18:53)
  * <Jolla> SMS or anything operator related things start to get
    complex. For  (rainemak, 16:18:55)
  * <Jolla> example, this particular issue could potential be operator
    (rainemak, 16:18:57)
  * <Jolla> specific, sim card type specific e.g. multi sim, country
    specific,  (rainemak, 16:18:59)
  * <Jolla> etc... As an example, in Finland some operators do not queue
    (rainemak, 16:19:01)
  * <Jolla> secondary sim SMSes meaning that in order to receive an SMS
    to the  (rainemak, 16:19:03)
  * <Jolla> secondary SIM it has to be in the network. This kind of
    behaviour  (rainemak, 16:19:05)
  * <Jolla> has nothing to do with the used operating system.
    (rainemak, 16:19:07)

* Visibility of Jolla/Sailfish OS (5 mins  -- Cryx)  (rainemak,
  16:27:09)
  * <Cryx> See linked topic - mainly I want to point Jolla (and the
    community)  (rainemak, 16:27:09)
  * <Cryx> to probably gain a better visibility…  (rainemak, 16:27:09)
  * LINK:
    https://forum.sailfishos.org/t/european-tech-sovereignty-catalogue/34613
    (rainemak, 16:27:09)
  * <Jolla> Notes and we’re working on these. Thank you for point this
    one.  (rainemak, 16:27:09)

* Reason OP-mobiili & S-pankki has stopped working (10mins – CLMA31)
  (rainemak, 16:29:08)
  * <CLMA31> Newest versions of OP-mobiili and S-pankki has stopped
    working. I  (rainemak, 16:29:08)
  * <CLMA31> would guess that some of Jolla employees is affected by
    this as  (rainemak, 16:29:08)
  * <CLMA31> well. As both still work with android forks like e/OS
    reason  (rainemak, 16:29:08)
  * <CLMA31> probably isn’t google integrity api, but some other shield
    that  (rainemak, 16:29:08)
  * <CLMA31> detects it is running in emulator. Unfortunately I don’t
    have  (rainemak, 16:29:09)
  * <CLMA31> know how to collect relevant logs or understand what is the
    (rainemak, 16:29:11)
  * <CLMA31> problem so I would be interested to hear if Jolla employees
    have  (rainemak, 16:29:15)
  * <CLMA31> been able to pin point the root problem yet? And if so, is
    this  (rainemak, 16:29:17)
  * <CLMA31> AAS specific problem or something else? Depends of answers
    to  (rainemak, 16:29:19)
  * <CLMA31> first two question, but in case someone in Jolla looked in
    to  (rainemak, 16:29:21)
  * <CLMA31> this, does it seem possible to fix this problem? We aren’t
    yet in  (rainemak, 16:29:23)
  * <CLMA31> dire situation as old versions work, but sooner or later
    they  (rainemak, 16:29:25)
  * <CLMA31> stop of working...  (rainemak, 16:29:27)
  * <Jolla> Yes, we noticed the same. No need to spend 10mins here.
    (rainemak, 16:29:29)

* timeline for fix for GPS works-once-only in AAS on JP2 (5mins –
  teleshoes)  (rainemak, 16:38:16)
  * <teleshoes> So the bug is: it seems that GPS doesn’t work in any
    apps that  (rainemak, 16:38:16)
  * <teleshoes> have location sharing permission with Allow only while
    using  (rainemak, 16:38:16)
  * <teleshoes> the app (RaceJoy) instead of Allow all the time (GMaps).
    this  (rainemak, 16:38:16)
  * <teleshoes> might be a coincidence. the broken apps get a gps fix at
    (rainemak, 16:38:16)
  * <teleshoes> startup, but then wont update unless i open GMaps and
    switch  (rainemak, 16:38:17)
  * <teleshoes> back (and then it gets one more fix).  (rainemak,
    16:38:19)
  * <teleshoes>  (rainemak, 16:38:21)
  * <teleshoes> but my QUESTION is: is this known, is it fixable, is it
    (rainemak, 16:38:23)
  * <teleshoes> perhaps fixed, and will it be deployed before oct17th
    when my  (rainemak, 16:38:25)
  * <teleshoes> race is :)?  (rainemak, 16:38:27)

* The Jolla Ringtone Project: The Missing Pieces—The Musician(s) Behind
  It and the future (5mins – fingus)  (rainemak, 16:38:44)
  * <fingus> We’d like to learn more about the Jolla Ringtone Project
    and its  (rainemak, 16:38:44)
  * <fingus> fantastic outcome. The presentation at the Jolla Phone Day1
    (rainemak, 16:38:44)
  * <fingus> event was impressive, but one question remained
    unanswered—and  (rainemak, 16:38:44)
  * <fingus> the YouTube Shorts doesn’t address it in a satisfactory way
    (rainemak, 16:38:44)
  * <fingus> enough. Why was this particular musician (and band?)
    chosen?  (rainemak, 16:38:46)
  * <fingus> Maybe you could tell us this story in an entertaining way.
    I  (rainemak, 16:38:48)
  * <fingus> think this is an important question because the ringtones
    for the  (rainemak, 16:38:50)
  * <fingus> four different TOH back covers play a significant role in
    shaping  (rainemak, 16:38:52)
  * <fingus> the identity of the new Jolla Phone. Perhaps there’s still
    some  (rainemak, 16:38:54)
  * <fingus> information about it that hasn’t been shared yet.
    (rainemak, 16:38:56)
  * <fingus>  (rainemak, 16:38:58)
  * <fingus> In the future, can we expect more TOH back colors and new
    (rainemak, 16:39:00)
  * <fingus> ringtones from this fantastic musician/band?  (rainemak,
    16:39:02)
  * <Jolla> This musician felt like a good match. We’ll get back to this
    topic – stay tuned.  (rainemak, 16:39:04)

* timeline for fix for GPS works-once-only in AAS on JP2 (5mins –
  teleshoes)  (rainemak, 16:43:04)
  * <teleshoes> So the bug is: it seems that GPS doesn’t work in any
    apps that  (rainemak, 16:43:04)
  * <teleshoes> have location sharing permission with Allow only while
    using  (rainemak, 16:43:04)
  * <teleshoes> the app (RaceJoy) instead of Allow all the time (GMaps).
    this  (rainemak, 16:43:04)
  * <teleshoes> might be a coincidence. the broken apps get a gps fix at
    (rainemak, 16:43:04)
  * <teleshoes> startup, but then wont update unless i open GMaps and
    switch  (rainemak, 16:43:05)
  * <teleshoes> back (and then it gets one more fix).  (rainemak,
    16:43:07)
  * <teleshoes>  (rainemak, 16:43:09)
  * <teleshoes> but my QUESTION is: is this known, is it fixable, is it
    (rainemak, 16:43:11)
  * <teleshoes> perhaps fixed, and will it be deployed before oct17th
    when my  (rainemak, 16:43:15)
  * <teleshoes> race is :)?  (rainemak, 16:43:17)
  * <Jolla> This could be same as FMI issue (Finnish Meteorological
    (rainemak, 16:43:19)
  * <Jolla> Institute). Needs more investigation. What we  (rainemak,
    16:43:21)
  * <Jolla> can say is that we do not have a fix for this (not yet).
    Thus, the  (rainemak, 16:43:23)
  * <Jolla> fix will not be deployed before October 17.  (rainemak,
    16:43:25)

* High CPU usage by AAS system_server process (5 mins -- Orologiaio)
  (rainemak, 16:50:37)
  * <Orologiaio> There’s an abnormally high cpu usage by the AAS
    system_server  (rainemak, 16:50:37)
  * <Orologiaio> process when AAS is running (see the bug report). I was
    not  (rainemak, 16:50:37)
  * <Orologiaio> the one to create the report, but I started noticing
    this as  (rainemak, 16:50:37)
  * <Orologiaio> the cause for the occasional battery drain I was seeing
    with  (rainemak, 16:50:37)
  * <Orologiaio> Finlayson version .18, and the issue persists also with
    the  (rainemak, 16:50:38)
  * <Orologiaio> .20 upgrade. Is the Jolla team aware of this? How can
    the  (rainemak, 16:50:40)
  * <Orologiaio> community help to troubleshoot the issue and find a
    fix?  (rainemak, 16:50:44)
  * LINK:
    https://forum.sailfishos.org/t/high-cpu-usage-by-system-server-aas/33503/
    (rainemak, 16:50:46)
  * <Jolla> Yes, we are aware of this. We have not managed to reproduce
    this.  (rainemak, 16:50:48)
  * <Jolla> We had a "blind" fix proposal, but we don't think it was
    conclusive  (rainemak, 16:50:50)
  * <Jolla> whether the fix worked. Thus, it was not merged.  (rainemak,
    16:50:52)
  * LINK:
    https://docs.sailfishos.org/Support/Help_Articles/Collecting_Logs/Collect_Logs_with_Logcat/#xperia-xa2-xperia-10-xperia-10-ii-xperia-10-iii-xperia-10-iv-xperia-10-v-and-jolla-c2
    (rainemak, 16:55:13)

* Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla)
  (rainemak, 16:58:24)
  * LINK:
    https://forum.sailfishos.org/t/release-futo-keyboard-with-swipe-and-offline-voice-input/32610/335
    (usbee, 17:00:05)

* General discussion (10 mins)  (rainemak, 17:02:46)
  * LINK:
    https://forum.sailfishos.org/t/roadshow-community-meeting-stockholm-oct-22/34246
    (rainemak, 17:03:06)

* Next meeting time and date (2 mins)  (rainemak, 17:23:52)
  * Next meeting will be held on Thursday October 29, 2026 at 04:00pm
    UTC: 2026-10-29T1600Z  (rainemak, 17:25:03)

Meeting ended at 17:25:29 UTC.




Action Items
------------
* Community task board
* Jolla to update regarding recommended charging cables and chargers.
* The Privacy Switch in relation to Ambiances




Action Items, by person
-----------------------
* **UNASSIGNED**
  * Community task board
  * Jolla to update regarding recommended charging cables and chargers.
  * The Privacy Switch in relation to Ambiances




People Present (lines said)
---------------------------
* rainemak (204)
* usbee (32)
* CLMA31[m] (18)
* eve247 (16)
* extechop[m] (11)
* Orologiaio (10)
* Rikudou[m] (10)
* nephros (6)
* sailbot (2)
* abr (2)
* dcaliste (1)
* Keto (1)
* mal (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot