16:00:47 <rainemak> #startmeeting Sailfish OS, open source, collaboration -- October 15, 2026
16:00:47 <sailbot> Meeting started Thu Oct 15 16:00:47 2026 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:47 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:00:47 <rainemak> #info Meeting information and agenda can be found here:
16:00:47 <rainemak> #link https://forum.sailfishos.org/t/34402
16:00:47 <rainemak> I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and bee-hive.
16:00:47 <rainemak> #topic Brief introduction (5 min). Please prefix your name/handle with #info
16:00:49 <rainemak> #info Raine Mäkeläinen, Jolla
16:01:02 <extechop[m]> #info Otto Mäkelä, community
16:01:46 <eve247> hello
16:01:58 <eve247> #info 247 community
16:02:03 <nephros> #info Peter G./nephros, community
16:02:36 <Orologiaio> #info Alessandro / Orologiaio, community
16:02:44 <dcaliste> #info Damien Caliste, community
16:03:07 <usbee> #info Balázs Szulovszky, community
16:05:11 <rainemak> do we have anybody else from Jolla, abr, Keto maybe direc85[m] ?
16:05:20 <rainemak> #topic Tracking of non-resolved Community Meeting topics
16:05:20 <rainemak> #action Community task board
16:05:20 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-23rd-april-2026/29030/3
16:05:20 <rainemak> #action Jolla to update regarding recommended charging cables and chargers.
16:05:20 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-7th-may-2026/29253/2
16:05:21 <rainemak> #action The Privacy Switch in relation to Ambiances
16:05:23 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-july-16-2026/30378/7
16:05:25 <rainemak> #info No actions taken yet regarding community task board nor charger / cables.
16:05:41 <Keto> o/
16:05:53 <rainemak> let's get going
16:05:54 <rainemak> #topic Are there plans to support PWAs? (10 mins -- usbee)
16:05:54 <rainemak> #info <usbee> PWA (Progressive Web Apps) could be a really handy stopgap for
16:05:54 <rainemak> #info <usbee> missing native apps and also reduce the dependency on Android
16:05:54 <rainemak> #info <usbee> apps. For now it is only possible to create web shortcuts to the
16:05:55 <rainemak> #info <usbee> app grid but that’s it.
16:06:05 <rainemak> #info <Jolla> Yes, once we have time for completing the support. It’s in the
16:06:05 <rainemak> #info <Jolla> plans but not yet scheduled for any particular release. Browser
16:06:05 <rainemak> #info <Jolla> stack point of view, we are not too far from being PWA compatible
16:06:05 <rainemak> #info <Jolla> as most of the features that are part of the PWA are already there
16:06:05 <rainemak> #info <Jolla> in the engine. Getting rid of the browser user interface is the
16:06:07 <rainemak> #info <Jolla> simplest of them all. What we clearly do not have is install /
16:06:08 <rainemak> #info <Jolla> uninstall feature for the Sailfish Browser.
16:06:10 <rainemak> #info <Jolla> Quote from mozilla.org: “PWAs typically look like platform-
16:06:14 <rainemak> #info <Jolla> specific apps － they are usually displayed without the browser UI
16:06:16 <rainemak> #info <Jolla> around them － but they are, as a matter of technology, still
16:06:18 <rainemak> #info <Jolla> websites.”
16:06:20 <rainemak> #link https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/What_is_a_progressive_web_app
16:06:23 <rainemak> #info <Jolla> Finally, we don’t need to think PWA as a stopgap solution as it
16:06:25 <rainemak> #info <Jolla> should be an option along with the other options.
16:06:27 <rainemak> #link https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps
16:06:58 <usbee> Sounds fair thanks!
16:07:45 <Rikudou[m]> I guess WebNFC will not be part of that?
16:08:10 <rainemak> We may need to add something for the app store... let's see
16:08:22 <Rikudou[m]> And is there any timeline? Like, this year, next year, in five years?
16:08:40 <rainemak> Rikudou[m], in same bucket as location api for web apps
16:09:23 <rainemak> Rikudou[m], I doubt that it would happen during this year... let's say so.
16:09:24 <abr> i'm here!
16:09:31 <Rikudou[m]> Lovely, thanks
16:10:02 <usbee> Chrome based browsers also has the ability to "install" non PWA websites too that literally is just running the website chromeless (aka without browser UI). That also would be nice even though it's strictly speaking not part of PWA support.
16:10:04 <Rikudou[m]> Will the apps be distributable in the store? Or would we need to wrap it in a native webview?
16:10:23 <rainemak> Rikudou[m], would be nice if we get it implemented for 5.x where x is greater than 3
16:10:44 <Rikudou[m]> Sounds fair, great!
16:10:46 <nephros> Was it the N9 or some other ancient phone that had a kind of "Web App Generator" app? Where you would put in an URL and it put it in the "launcher" as a regular application?
16:11:14 <rainemak> usbee, I doubt that it only without ui, usually it would have same origin policy applied as well.
16:11:20 <rainemak> "it is only"
16:11:30 <usbee> Sailfish OS has a feature to put web shortcuts into the app launcher but that just opens the browser with the regular browser UI.
16:12:02 <rainemak> Rikudou[m], no webview wrapping as those should be managed by the Sailfish Browser
16:12:03 <abr> yeah they need their own profiles too to keep the data separate from the rest of the web
16:12:19 <nephros> usbee: tes I know but I mean something different.
16:12:20 <usbee> @rainemak you can freely pick any website and there is an option to create shortcut and if you launch from the desktop icon it will be in chromeless mode as if it was a PWA.
16:12:42 <CLMA31[m]> dcaliste: Wait Damien, I thought you are Jolla employee as yoi have been goat with tge email! 😮 sorry for offtopic...
16:12:46 <rainemak> usbee, correct, and when bookmarking to app grid we do not apply any special handling for navigation
16:13:38 <nephros> What I mean is maybe there needs to be a generic wrapper/configurator function which sets up all of the requirements, and then creates a launcher icon.
16:13:51 <Rikudou[m]> I mean for distributing the PWA in the Jolla Store, e.g. something like https://developer.android.com/develop/ui/views/layout/webapps/trusted-web-activities
16:13:53 <rainemak> usbee, understood but I'd assume that it launches browser when trying to navigate away from the starting domain
16:13:55 <usbee> Also just came in my mind: Firefox has a feature to isolate tabs from each other. Now this could be the same with installed apps wheter they are PWA or simple websites if the user places an icon for them in the app grid to improve privacy.
16:14:58 <rainemak> usbee, i.e. creating a surfing board without browser user interface is not nice
16:15:39 <usbee> Well, Chrome solves it by opening a regular browser window if the link goes to a different domain. Most of the time it solves these kind of issues.
16:16:36 <rainemak> nephros, yes it had wgt support back in then.
16:16:45 <rainemak> s/in//
16:17:06 <rainemak> it even had w3c spec
16:18:06 <rainemak> https://www.w3.org/TR/widgets/
16:18:13 <rainemak> let's move on
16:18:28 <rainemak> #topic Solving the SMS receiving problem (5 mins -- legacychimera247)
16:18:28 <rainemak> #info <legacychimera247> Some weeks ago my local record shop wrote me an sms to
16:18:28 <rainemak> #info <legacychimera247> notify me about a very limited release, i didn’t see
16:18:28 <rainemak> #info <legacychimera247> that, but casually i was going in there for other
16:18:28 <rainemak> #info <legacychimera247> things so i could order the record in time. The reason
16:18:29 <rainemak> #info <legacychimera247> why i didn’t see the message is that my Jolla Phone 2
16:18:31 <rainemak> #info <legacychimera247> didn’t receive any message. It’s not a JP2 problem,
16:18:33 <rainemak> #info <legacychimera247> it’s a Sailfish one cause i’ve been plagued with this
16:18:35 <rainemak> #info <legacychimera247> bug since forever on my XA2 and i sadly see situation
16:18:37 <rainemak> #info <legacychimera247> is not changed on newer releases of Sailfish. Will this
16:18:39 <rainemak> #info <legacychimera247> ever be solved?i lost count of lost messages through
16:18:41 <rainemak> #info <legacychimera247> the years due to this bug, and it would be nice to see
16:18:45 <rainemak> #info <legacychimera247> it solved, since i consider sms the most basic
16:18:47 <rainemak> #info <legacychimera247> functionality of a phone...
16:18:49 <rainemak> #info <Jolla> There are a lot of possible root causes triggering this. As a rule
16:18:51 <rainemak> #info <Jolla> of thumb with issue reports, when we have clear steps to reproduce
16:18:53 <rainemak> #info <Jolla> an issue it’s much more easier to fix it. Then when it comes to
16:18:55 <rainemak> #info <Jolla> SMS or anything operator related things start to get complex. For
16:18:57 <rainemak> #info <Jolla> example, this particular issue could potential be operator
16:18:59 <rainemak> #info <Jolla> specific, sim card type specific e.g. multi sim, country specific,
16:19:01 <rainemak> #info <Jolla> etc... As an example, in Finland some operators do not queue
16:19:03 <rainemak> #info <Jolla> secondary sim SMSes meaning that in order to receive an SMS to the
16:19:05 <rainemak> #info <Jolla> secondary SIM it has to be in the network. This kind of behaviour
16:19:07 <rainemak> #info <Jolla> has nothing to do with the used operating system.
16:20:01 <rainemak> There could still be a bug (even bugs) in the SMS receiving but hard to fix as we cannot reproduce here in Finland
16:20:28 <eve247> let me clarify, i do have a single sim in my jolla 2, and my xa2 is the single sim variant
16:20:58 <rainemak> multi sim == two sim cards for the same phone number
16:21:15 <eve247> maybe i should try to deactivate the second sim on the jp2?
16:21:43 <usbee> That's dual SIM you have that's different
16:22:10 <eve247> phone is dual sim yes, but i have only one sim and it's in slot one
16:22:29 <usbee> I personally don't have issues with SMS. I'm on One HU network with the Jolla phone with a single SIM.
16:22:43 <eve247> last year i switched my carrier and got a new sim with that, but nothing is changed
16:23:02 <rainemak> eve247, which operator?
16:23:14 <usbee> Yup, that's the simplest setup. Multi SIM is simething that is made for some specific use cases like for example my MNO provides dedicated Multi SIM for Apple Watches.
16:23:30 <eve247> well, it's not the jp per se, it's sailfish as i was having the same exact problem even with the xa2, like i had this problem forever
16:23:46 <eve247> @rainemak i'm with Vodafone Italy
16:24:13 <usbee> You should try if the issue presists with an Android phone if that's possible to rule out SFOS as a root of problem
16:24:14 <eve247> before i was with Ho-Mobile (a sub brand of Vodafone Italy)
16:24:46 <eve247> @usbee unfortunately i used android for like 2 years on my xa2 and i didn't have this problem
16:24:55 <rainemak> eve247, how frequently this happens?
16:25:05 <usbee> Or you can ask friends or colleagues or forums online if others has SMS issues on that network too.
16:25:21 <rainemak> usbee, correct
16:25:24 <eve247> @usbee, i already tried, none have problems
16:25:39 <usbee> Did your XA2 used to use SMS or RCS?
16:25:49 <eve247> @rainemak i don't know but could roughly estimate i get 3 messages out of four
16:26:12 <eve247> no rcs, i guess the xa2 is too old for that
16:26:26 <rainemak> odd, but issue noted
16:26:38 <rainemak> we don't need to debug it here... let's move on
16:26:40 <usbee> RCS is supported by Android for a long time so I think it should had that
16:26:57 <eve247> i need to do some further testing on the average of sms lost anyway
16:27:09 <rainemak> #topic Visibility of Jolla/Sailfish OS (5 mins  -- Cryx)
16:27:09 <rainemak> #info <Cryx> See linked topic - mainly I want to point Jolla (and the community)
16:27:09 <rainemak> #info <Cryx> to probably gain a better visibility…
16:27:09 <rainemak> #link https://forum.sailfishos.org/t/european-tech-sovereignty-catalogue/34613
16:27:09 <rainemak> #info <Jolla> Notes and we’re working on these. Thank you for point this one.
16:27:10 <extechop[m]> While still using Sony Xperia 10III I occasionally received multiple copies of the one text message that was sent me, apparently message reception acknowledgements were lost.
16:27:14 <eve247> well if it had i had probably deactivated
16:28:03 <rainemak> let's continue SMS debugging at the end in the "General discussion"
16:28:20 <eve247> still, i hope one day this issue is solved, because i'm a little bit tired of hearing people that i should switch to whatsapp as i never reply to sms (especially since i miss them :P )
16:29:00 <rainemak> thanks Cryx[m] for this pointer
16:29:03 <rainemak> moving on
16:29:08 <rainemak> #topic Reason OP-mobiili & S-pankki has stopped working (10mins – CLMA31)
16:29:08 <rainemak> #info <CLMA31> Newest versions of OP-mobiili and S-pankki has stopped working. I
16:29:08 <rainemak> #info <CLMA31> would guess that some of Jolla employees is affected by this as
16:29:08 <rainemak> #info <CLMA31> well. As both still work with android forks like e/OS reason
16:29:08 <rainemak> #info <CLMA31> probably isn’t google integrity api, but some other shield that
16:29:09 <rainemak> #info <CLMA31> detects it is running in emulator. Unfortunately I don’t have
16:29:11 <rainemak> #info <CLMA31> know how to collect relevant logs or understand what is the
16:29:15 <rainemak> #info <CLMA31> problem so I would be interested to hear if Jolla employees have
16:29:17 <rainemak> #info <CLMA31> been able to pin point the root problem yet? And if so, is this
16:29:19 <rainemak> #info <CLMA31> AAS specific problem or something else? Depends of answers to
16:29:21 <rainemak> #info <CLMA31> first two question, but in case someone in Jolla looked in to
16:29:23 <rainemak> #info <CLMA31> this, does it seem possible to fix this problem? We aren’t yet in
16:29:23 <usbee> Regarding to visibiliy I vividly remember that Telekom (T-Mobile in Hungary) and Mozilla teamed up around 2014 and they promoted Firefox OS heavily and they sold Alcatel phones in a short period of time. I do believe that masses can be reached through partnership with MNOs. That would boost visibility greatly. On the other hand that would require provide some sort of added value to the specific market that would differentia
16:29:25 <rainemak> #info <CLMA31> dire situation as old versions work, but sooner or later they
16:29:27 <rainemak> #info <CLMA31> stop of working...
16:29:29 <rainemak> #info <Jolla> Yes, we noticed the same. No need to spend 10mins here.
16:29:55 <CLMA31[m]> Have you beeb able to pinpoint root cause?
16:30:33 <CLMA31[m]> Like, is it something that can be fixed in AAS or did they do some nasties and we need to drop them at somepoint?
16:30:47 <rainemak> Not that I'm aware of
16:31:59 <CLMA31[m]> Can Jolla collect necessary logs themselves or is it helpful to community collect them?
16:32:03 <rainemak> Yes
16:32:19 <extechop[m]> Yes to which?
16:32:22 <rainemak> As you speculated, we do have OP and S-pankki users
16:32:50 <CLMA31[m]> Thought so and hope common problem helps here :D
16:33:16 <rainemak> extechop[m], yes to first :-)
16:33:53 <CLMA31[m]> There was community member who has friend in OP, who asked deeper info about the problem so he could push it further in OP. Unfortunately at least I have zero knowledge what logs would be beneficial for OP
16:34:22 <CLMA31[m]> Would it make sense to open direct communication line between Jolla and OP?
16:34:49 <rainemak> I likely doesn't harm to have secondary OP channel as well
16:34:52 <rainemak> It
16:35:58 <CLMA31[m]> What would be preferred way of Jolla to open this channel?
16:36:35 <CLMA31[m]> Or did you mean that Jolla already has primary channel open and community should upkeep this secondary channel?
16:36:56 <rainemak> CLMA31[m], let's take this offline (PM in Forum)... we don't need to spend everybody's time for OP debugging
16:37:11 <CLMA31[m]> Sure!
16:37:20 <CLMA31[m]> Thanks for the answers :)
16:37:38 <rainemak> I have a correct to OPs mobile app development. I could have another connection as well.
16:37:46 <rainemak> I have a connection to OPs mobile app development. I could have another connection as well.
16:38:16 <rainemak> #topic timeline for fix for GPS works-once-only in AAS on JP2 (5mins – teleshoes)
16:38:16 <rainemak> #info <teleshoes> So the bug is: it seems that GPS doesn’t work in any apps that
16:38:16 <rainemak> #info <teleshoes> have location sharing permission with Allow only while using
16:38:16 <rainemak> #info <teleshoes> the app (RaceJoy) instead of Allow all the time (GMaps). this
16:38:16 <rainemak> #info <teleshoes> might be a coincidence. the broken apps get a gps fix at
16:38:17 <rainemak> #info <teleshoes> startup, but then wont update unless i open GMaps and switch
16:38:19 <rainemak> #info <teleshoes> back (and then it gets one more fix).
16:38:21 <rainemak> #info <teleshoes>
16:38:23 <rainemak> #info <teleshoes> but my QUESTION is: is this known, is it fixable, is it
16:38:25 <rainemak> #info <teleshoes> perhaps fixed, and will it be deployed before oct17th when my
16:38:27 <rainemak> #info <teleshoes> race is :)?
16:38:36 <rainemak> Oops... Jumped over
16:38:44 <rainemak> #topic The Jolla Ringtone Project: The Missing Pieces—The Musician(s) Behind It and the future (5mins – fingus)
16:38:44 <rainemak> #info <fingus> We’d like to learn more about the Jolla Ringtone Project and its
16:38:44 <rainemak> #info <fingus> fantastic outcome. The presentation at the Jolla Phone Day1
16:38:44 <rainemak> #info <fingus> event was impressive, but one question remained unanswered—and
16:38:44 <rainemak> #info <fingus> the YouTube Shorts doesn’t address it in a satisfactory way
16:38:46 <rainemak> #info <fingus> enough. Why was this particular musician (and band?) chosen?
16:38:48 <rainemak> #info <fingus> Maybe you could tell us this story in an entertaining way. I
16:38:50 <rainemak> #info <fingus> think this is an important question because the ringtones for the
16:38:52 <rainemak> #info <fingus> four different TOH back covers play a significant role in shaping
16:38:54 <rainemak> #info <fingus> the identity of the new Jolla Phone. Perhaps there’s still some
16:38:56 <rainemak> #info <fingus> information about it that hasn’t been shared yet.
16:38:58 <rainemak> #info <fingus>
16:39:00 <rainemak> #info <fingus> In the future, can we expect more TOH back colors and new
16:39:02 <rainemak> #info <fingus> ringtones from this fantastic musician/band?
16:39:04 <rainemak> #info <Jolla> This musician felt like a good match. We’ll get back to this topic – stay tuned.
16:43:02 <rainemak> Now back to to GPS topic
16:43:04 <rainemak> #topic timeline for fix for GPS works-once-only in AAS on JP2 (5mins – teleshoes)
16:43:04 <rainemak> #info <teleshoes> So the bug is: it seems that GPS doesn’t work in any apps that
16:43:04 <rainemak> #info <teleshoes> have location sharing permission with Allow only while using
16:43:04 <rainemak> #info <teleshoes> the app (RaceJoy) instead of Allow all the time (GMaps). this
16:43:04 <rainemak> #info <teleshoes> might be a coincidence. the broken apps get a gps fix at
16:43:05 <rainemak> #info <teleshoes> startup, but then wont update unless i open GMaps and switch
16:43:07 <rainemak> #info <teleshoes> back (and then it gets one more fix).
16:43:09 <rainemak> #info <teleshoes>
16:43:11 <rainemak> #info <teleshoes> but my QUESTION is: is this known, is it fixable, is it
16:43:15 <rainemak> #info <teleshoes> perhaps fixed, and will it be deployed before oct17th when my
16:43:17 <rainemak> #info <teleshoes> race is :)?
16:43:19 <rainemak> #info <Jolla> This could be same as FMI issue (Finnish Meteorological
16:43:21 <rainemak> #info <Jolla> Institute). Needs more investigation. What we
16:43:23 <rainemak> #info <Jolla> can say is that we do not have a fix for this (not yet). Thus, the
16:43:25 <rainemak> #info <Jolla> fix will not be deployed before October 17.
16:43:45 <rainemak> Sounds fixable
16:46:16 <usbee> To my experience enabling hybrid location service improves the location service at some extent.
16:46:58 <usbee> It will give a really vague location but at least it will make apps not crash that are requires some sort of location data. Far from being a good solution but bette than nothing.
16:47:33 <usbee> In my understandings it uses IP location and phone cell location besides GPS.
16:50:29 <rainemak> okey, let's move on
16:50:37 <rainemak> #topic High CPU usage by AAS system_server process (5 mins -- Orologiaio)
16:50:37 <rainemak> #info <Orologiaio> There’s an abnormally high cpu usage by the AAS system_server
16:50:37 <rainemak> #info <Orologiaio> process when AAS is running (see the bug report). I was not
16:50:37 <rainemak> #info <Orologiaio> the one to create the report, but I started noticing this as
16:50:37 <rainemak> #info <Orologiaio> the cause for the occasional battery drain I was seeing with
16:50:38 <rainemak> #info <Orologiaio> Finlayson version .18, and the issue persists also with the
16:50:40 <rainemak> #info <Orologiaio> .20 upgrade. Is the Jolla team aware of this? How can the
16:50:44 <rainemak> #info <Orologiaio> community help to troubleshoot the issue and find a fix?
16:50:46 <rainemak> #link https://forum.sailfishos.org/t/high-cpu-usage-by-system-server-aas/33503/
16:50:48 <rainemak> #info <Jolla> Yes, we are aware of this. We have not managed to reproduce this.
16:50:50 <rainemak> #info <Jolla> We had a "blind" fix proposal, but we don't think it was conclusive
16:50:52 <rainemak> #info <Jolla> whether the fix worked. Thus, it was not merged.
16:51:42 <usbee> In the Futo keyboard topic it was mentioned a similar issue and it was fixed since then. Maybe it's related?
16:53:35 <Orologiaio> @rainemak can we help with logs or something? While attending here, I've been keeping my phone's screen on most of the time, and I'm noticing that if I don't let the screen switch off, the high cpu load does not trigger. But it does soon after I put the phone down.
16:54:20 <rainemak> We could gather logs, when you trigger it
16:54:30 <Orologiaio> maybe unrelated, but I'm also unable to uninstall micro (in order to attempt to remove and reinstall AAS, which solved the issue for some).
16:54:38 <Orologiaio> microG
16:55:00 <Orologiaio> Jolla store says it uninstalled, but it didn't
16:55:13 <rainemak> 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
16:55:15 <Orologiaio> This prevents me from uninstalling AAS as well
16:55:48 <rainemak> Hmm, should be doable via command line
16:55:56 <rainemak> any thoughts abr
16:56:27 <Orologiaio> @rainemak thanks, I'll look into collecting logs. We can also keep troubleshooting this via PM if you (or anyone from Jolla) are available
16:57:57 <rainemak> Perfect, sounds good
16:58:24 <rainemak> #topic Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla)
16:58:48 <Orologiaio> @usbee if you can point me to the exact message in the futo thread it would be appreciated, but I can also search for it myself, in any case thanks for the heads up
16:59:25 <usbee> I'm not sure how to link a specific message from there but it happened relatively recently in the topic.
17:00:05 <usbee> https://forum.sailfishos.org/t/release-futo-keyboard-with-swipe-and-offline-voice-input/32610/335
17:00:41 <Orologiaio> Super, thanks! We can move on, the everyone
17:00:47 <Orologiaio> thanks
17:02:41 <rainemak> let's take the general discussion... I guess we'd have something for that
17:02:46 <rainemak> #topic General discussion (10 mins)
17:02:57 <usbee> Yeah I have one thing I want to address
17:03:06 <rainemak> Jolla Phone Roadshow Stockholm, October 22
17:03:06 <rainemak> #link https://forum.sailfishos.org/t/roadshow-community-meeting-stockholm-oct-22/34246
17:03:09 <rainemak> usbee, go ahead
17:03:54 <Rikudou[m]> Do you plan on making it possible to run daemons in Store apps?
17:04:01 <usbee> So I started to donate to Jolla monthly because I remembered that there was a discussion about moving to a subscriotion based model where people who buys a SFOS phone would have an 1-2 years software support and after that they would have to pay for sunscription to keep receive updates.
17:04:43 <usbee> Now my problem is that the donation isn't reall visible and I started donation because I remembered this discussion and I really in favor of paying for the labour it takes to maintain the system.
17:05:15 <nephros> Rikudou[m]: not exactly, but a first step private binaries: https://github.com/sailfishos/sdk-harbour-rpmvalidator/pull/189
17:05:17 <usbee> I'm not sure if people are aware this option exists.
17:05:22 <rainemak> usbee, it's not quite like thaat
17:06:06 <rainemak> there won't be paid updates at least with the current EU legislation
17:06:38 <rainemak> usbee, what do you mean that your voluntary subscription is not visible?
17:06:40 <usbee> I know it's a voluntarily subscription, sure, it's very clearly worded in the store. But to people know this option they need to visit the store then scroll through the options to see that one. I think the visibility of it is poor. For example KDE does an annual campaing to fundraise.
17:06:42 <extechop[m]> Does Jolla aim at getting OS updates out for this community meeting, it's happened several times now? 😸
17:07:51 <usbee> So without knowing numbers I assume most SFOS are nor even aware that they can donate to Jolla.
17:08:00 <Rikudou[m]> Well, I'm thinking for an app like my Inari Blue Notifier, it would be great if it could be in the store, but without a daemon that's not likely
17:08:03 <usbee> So without knowing numbers I assume most SFOS users are nor even aware that they can donate to Jolla.
17:08:26 <rainemak> usbee, noted that
17:08:27 <usbee> KDE has a simple subtle notification, something similar could be done here too
17:08:39 <rainemak> extechop[m], what do you mean?
17:09:24 <extechop[m]> I looked yesterday, no update. Today, update, to coincide with this meeting. And I believe the same thing happened to me with the previous update too.
17:09:28 <nephros> On a somewhat related note, in case someone wanted to donate a couple of beverages or some such from far away to the Jolla team, what would be a good way to do that?
17:09:33 <rainemak> there are internal reasons as well for pushing updates out
17:10:31 <rainemak> extechop[m], that's coincident I'd say but now that you say it... this would be a good forum to discuss about the update
17:10:42 <rainemak> so we could target Wednesday updates
17:10:49 <CLMA31[m]> Rikudou[m]: Isn't the thing Jolla published, symbiosis(?), suitable for that? Sorry if stupid question....
17:10:57 <mal> that gps bug could be just some issue in how the information which app is active is handled between sailfish side and appsupport
17:10:58 <rainemak> when we are about to publish an update
17:11:44 <Rikudou[m]> CLMA31[m]: Symbiosis makes it possible to run as non-root, but you can't really react to events without a daemon. And Symbiosis has no Sailjail permissions (yet?) meaning it can't be in store either way
17:11:53 <usbee> Btw I want to highlight I use a bluetooth speaker the entire time to play music in the background during this meeting and it works well with an Android app so kudos for that!
17:13:30 <CLMA31[m]> rainemak: Update every Wednesday would be dream!😍but on serious note, Wednesday sounds good. I have much appreciated the friday updates, but if there would be problem, then weekend makes it harder to react for Jolla
17:13:57 <usbee> System76 does a weekly updates for Cosmic and they usually does it on Tuesdays
17:14:19 <usbee> They skip weeks sometimes
17:14:22 <CLMA31[m]> Rikudou[m]: Thank you for explanation!
17:14:29 <rainemak> CLMA31[m], that's the reason why we try to avoid Friday updates
17:15:06 <extechop[m]> By the way, is there a page somewhere tracking the other halves people are putting together and which even could be available to purchase?
17:15:51 <CLMA31[m]> But of course as a user I love to have updates as soon as possible, but as user base grows rapidly, any day between Monday - Wednesday works great
17:15:57 <extechop[m]> (And the SFOS update that I just started on my phone apparently got stuck at the shutting down part)
17:18:13 <rainemak> extechop[m], sorry, I don't understand what your asking
17:18:35 <rainemak> extechop[m], hopefully your device corrected itself
17:18:59 <extechop[m]> (It did, I just had to force the shutdown, but after that things went normally)
17:19:04 <CLMA31[m]> About the front camera dust issue, some have gotten email, others haven't. I assume this is due Jolla being busy and not because all cases have veen handled?
17:19:48 <rainemak> CLMA31[m], work in progress
17:20:15 <extechop[m]> rainemak: what I was trying to ask was, do there seem to be active projects by people to develop TOH or is it in practice all up to Jolla?
17:20:37 <CLMA31[m]> rainemak: Good to hear!
17:21:40 <rainemak> extechop[m], I should ask from Tomin. He has been following TOH development very closely.
17:22:12 <rainemak> are we done for today?
17:22:12 <Rikudou[m]> extechop[m]: There have been some on the forum
17:22:56 <extechop[m]> I guess so?
17:23:18 <CLMA31[m]> Thanks for everyone!
17:23:43 <rainemak> let's schedule next meeting
17:23:52 <rainemak> #topic Next meeting time and date (2 mins)
17:23:52 <rainemak> Proposing Thursday October 29 at 04:00 PM UTC
17:24:44 <extechop[m]> So the usual two-week schedule. Works for me.
17:24:49 <rainemak> LGTM
17:25:03 <rainemak> #info Next meeting will be held on Thursday October 29, 2026 at 04:00pm UTC: 2026-10-29T1600Z
17:25:24 <rainemak> Thank you all! Was a pleasure to host once again.
17:25:29 <rainemak> #endmeeting