16:08:59 #startmeeting Sailfish OS, open source, collaboration -- 21st May 2026 16:08:59 Meeting started Thu May 21 16:08:59 2026 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:08:59 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:08:59 #info Meeting information and agenda can be found here: 16:08:59 #link https://forum.sailfishos.org/t/29498 16:08:59 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:08:59 #topic Brief introduction (5 min). Please prefix your name/handle with #info 16:09:07 #info Raine Mäkeläinen, Jolla 16:09:25 #info CLMA31, community 16:09:32 #info Anton Thomasson, community 16:09:38 Thijs Janssen, community 16:10:13 #info Pami Ketolainen, Jolla 16:12:50 #info Andrew Branson, Jolla 16:12:55 #topic Tracking of non-resolved Community Meeting topics 16:12:55 #action Community task board 16:12:55 #link https://forum.sailfishos.org/t/community-meeting-on-23rd-april-2026/29030/3 16:12:55 #action Jolla to update regarding recommended charging cables and chargers. 16:12:56 #link https://forum.sailfishos.org/t/community-meeting-on-7th-may-2026/29253/2 16:12:57 #info No actions taken yet regarding community task board nor charger / cables. 16:13:24 Pushed one question to next meeting. 16:13:35 Let's get going 16:13:37 #topic General question regarding the timeline of 5.1 and AAS bluetooth support (5 mins -- CLMA31) 16:13:37 #info Firstly, sorry for very late topic, but I thought that maybe 16:13:37 #info this subject could be answered even without preparation. I 16:13:37 #info don’t want to rush things, but I’m interested to know what 16:13:37 #info does the timelines of 5.1 and AAS bluetooth releases look 16:13:39 #info like? 5.1 has sounded like it will land soon, but can the 16:13:41 #info bluetooth support for AAS side also be released at the same 16:13:43 #info time? 16:13:45 #info Yes, Sailfish OS 5.1 is looking good. The first version of the 16:13:47 #info Bluetooth for AppSupport can be considered as beta and will be 16:13:49 #info delivered first via Jolla Store. This way you can easily also 16:13:51 #info uninstall. Later on down the road, Bluetooth for AppSupport 16:13:53 #info should be integrated to the AppSupport itself. 16:13:57 #info 16:13:59 #info We are targetting to release it next week. 16:14:38 Next week for both? 16:14:49 We are targetting to release it next week. == Sailfish OS 5.1 16:14:49 Or only for 5.1? 16:15:09 Thanks for clarification, any timeline guess for Bluetooth? 16:15:13 AppSupport opens to Store more or less same time 16:15:29 Great to hear! 16:16:10 No further question, but I want to thank you for doing the developer early access! 16:17:23 Let's move on 16:17:28 #topic Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) 16:17:28 #info Open PRs raised by nephros 16:17:28 #link https://github.com/sailfishos/ncurses/pull/3/ 16:17:28 #link https://github.com/sailfishos/readline/pull/3 16:19:22 Thank you for raising PRs before hand 16:23:29 let's move on 16:23:38 #topic General discussion (15 mins) 16:23:38 #info Jolla Phone update - The Other Half spec 16:23:38 #link https://forum.sailfishos.org/t/29701 16:23:38 #info Please note that any details at the TOH spec page are still under development and subject to change without notice. 16:26:04 Wow great job! Good that community has a little bit time to tinker :) 16:26:28 Indeed very ice to see. Hope STL files follow soon. 16:26:56 We'll push more content as get them ready 16:27:14 Nice to see. 16:27:30 How does the Jolla phone generally look like? 16:28:30 Can the TOH power input function as an UPS, as in allowing swapping the main battery with another one? 16:28:32 Looks and feels awesome! 16:28:52 Can't wait it! 16:29:10 Dante_, nope 16:29:33 Dante_: Battery would be behind any normal-sized TOH anyway. 16:29:51 attah, correct 16:30:37 Looking forward to July 8th. Hopefully with a printed TOH. No ideas yet, but I like printing and electronics, so hopefully an idea will come to me. 16:30:40 I guess you could clamp something just over the pins. I don't think phone hardware really likes having its battery removed when it's switched on though 16:31:19 One could design a TOH with a battery hole perhaps? 16:31:24 I wouldn't try switching a battery when the phone is connected to a charger either! 16:31:32 which I guess is the same thing 16:31:53 Within your internal testing, has the location improvements in 5.1 allow you to get approximate location lock even inside the building? Meaning probably mostly the Beacon 16:31:56 But still, the phone has to support live battery removal 16:32:12 A charger could supply more than 1A though. 16:32:29 CLMA31[m]: i've got a sfos stumbler in the works to gather data for beacondb! 16:32:58 ThijssjihT, that could a hole for tap to pay i.e. for your credit card 16:33:33 ThijssjihT: Has to? 16:34:06 abr: I have also used android phone to collect data for that :) 16:34:25 ThijssjihT, why do you think so? 16:34:36 I mean, if you would want a TOH to supply power to be able to remove the battery as suggested. In that it would have to. 16:35:02 In that case yes 16:35:40 I really don't care about battery removal. As long as I can replace the battery when it has gone old and bad I am very happy. 16:35:55 It would have to; but may well not. 16:36:02 who would have thought that such a thing would ever be considered a privilege 16:36:56 indeed 16:36:57 attah, it takes a bit that we publish STLs -- the first version at least. 16:37:22 Before july 8th? 16:37:36 of course 16:37:43 Could Jolla provide STEP files so those would be easier to modify? 16:37:47 maybe even during next week 16:38:03 I'm not sure about the formmat 16:38:04 One would think that they by definition must exist to produce the phone - if in another format and for another process 16:38:31 but you have to be sure they won't change again... 16:38:42 or else there'll be some pissed off toh makers 16:39:01 For sure 16:39:04 Have to wait and see 16:39:39 Though i think an early unoptimized version with appropriate disclaimer is a good middle ground 16:39:59 abr, it's about communication. if there are changes expected, then we'll communicate that... and so on. 16:40:14 attah, we're thinking the same 16:40:28 :) 16:40:45 yeah but people will still start building things anyway. i would. 16:40:57 I sort of even see some 3d printing afficionado PR:ing an improvement 16:41:24 Would not surprise me with this cool community 16:42:02 I think we are ready to schedule a next meeting 16:42:24 #topic Next meeting time and date (2 mins) 16:42:24 Proposing Thursday 4th June at 04:00 PM UTC 16:42:24 #info Next meeting will be held on Thursday 4th June 2026 at 04:00pm UTC: 2026-06-04T1600Z 16:42:44 oops, too many lines copied :-) 16:43:04 in two weeks and same time 16:43:07 Well decided 16:43:17 Normal two week interwall, sounds good 16:43:31 that's it then 16:43:38 settled 16:43:43 Sounds good. 16:43:44 thank you all! 16:43:51 Thank you! 16:43:57 #endmeeting