16:01:49 #startmeeting Sailfish OS, open source, collaboration -- 12th February 2026 16:01:49 Meeting started Thu Feb 12 16:01:49 2026 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:49 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:01:49 #info Meeting information and agenda can be found here: 16:01:50 #link https://forum.sailfishos.org/t/27468 16:01:51 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:01:54 #topic Brief introduction (5 min). Please prefix your name/handle with #info 16:02:02 #info Raine Mäkeläinen, Jolla 16:02:20 #info Ruben De Smet - rubdos - community 16:02:41 #info Matti Viljanen, Jolla 16:04:49 hello rubdos[m] and direc85[m] 16:04:50 #Info mettska, User 16:05:06 #info Andrew Branson, Jolla 16:05:07 welcome mettska 16:05:22 o/ 16:05:33 hello Andrew 16:05:35 I realized why I seldom attend. Around this time I usually walk home from work! 16:05:59 rubdos[m], well that explains 16:06:12 We have 2 topics today. Let's try to have an open discussion. 16:06:18 :) 16:07:04 let's start 16:07:11 #topic Will the J2 have HBM (high brightness mode) (5 mins -- MeeGo-Junky) 16:07:19 #info In the region where I live HBM is really essential: 16:07:19 #info On the Xperia 10 V with current 5.0.0.72 beta there is no 16:07:19 #info HBM (at least to my awareness) and this renders the 16:07:19 #info device useless outdoors, meaningful use only indoors 16:07:20 #info possible. The same device with stock Andoid (that has 16:07:21 #info HBM) is a pleasure to use. 16:07:23 #info Also on my Volla Quintus HBM makes a striking difference: 16:07:25 #info with HBM enabled, SFOS shines and the device is useable 16:07:27 #info outdoors. 16:07:29 #info Therefore: is there anything planned about the screen 16:07:31 #info brightness of J2? 16:07:33 #info We cannot yet confirm the HBM but taken into account. HBM 16:07:35 #info should be ~800 nits. We are working on a more technical Forum 16:07:37 #info post. We'll try to cover various questions that have been asked 16:07:39 #info at the Forum and on other channels. Let's try to cover this one 16:07:41 #info in more detail as well. Every day matters when clarifying 16:07:43 #info things. 16:08:57 That rendered weird on Matrix, hmm. Some lines seem to have disappeared. 16:09:17 where is the information that Xperia 10 V has hbm? didn't find anything sysfs at least 16:09:48 then there is this one still open... https://github.com/sailfishos/mce/pull/41 16:10:06 like Simo commented 16:10:07 Display brightness; 16:10:07 bits 0-7 is brightness in percent (0-100) 16:10:07 upper 8 bits is high brightness boost (0-2) 16:10:29 Are you trying to cover "everything" in one forum post? It might be useful to show some details in some atomic increments, while you're writing. Might keep the momentum going a bit more on the pre-order as well 🤔 16:10:50 rubdos[m], surely not all in one 16:11:19 more like frequently asked questions -> then some of them towards product page's FAQ 16:12:37 but also tech details that we have not yet shared 16:12:56 Maybe more for the open discussion part, but having some breadcrumb style "deep dive" blog posts might generate some more traction 16:13:03 but for 3.5mm jack, it still no :-) 16:13:10 either way, looking forward to reading :) 16:13:22 but for 3.5mm jack, it is still no :-) 16:13:56 haha! Pray for some Apt-X "goodness" ;-) 16:14:11 let's move forward 16:14:22 #topic Unreliability of Android apps in secondary user accounts (10 mins -- asked by headlamp_mapper) 16:14:28 #info Installing Android apps on secondary user accounts 16:14:28 #info seems to work correctly at first (they can run in the 16:14:28 #info background and send notifications). When switching 16:14:28 #info users to defaultuser and back to the secondary 16:14:28 #info account, the apps disappear from the app drawer. The 16:14:30 #info apps still work (notifications work and apps can be 16:14:31 #info opened from push notifications). Is this a known bug 16:14:33 #info and can Jolla investigate? 16:15:00 #info First a bit of background. Work on the Sailfish OS multiuser 16:15:01 #info support started around 2020 and back then requirements were such 16:15:01 #info that Android apps won't show up for additional users. Further, 16:15:01 #info some OS features will not be available for additional users. One 16:15:01 #info could think an additional user as a limited user. 16:15:02 #info 16:15:03 #info Application data is stored per user but a Sailfish OS 16:15:05 #info application is installed so that they are shared for all users 16:15:07 #info (as per harbour guidelines). Back in that time also Android apps 16:15:09 #info were shared between all the users. Thus, we needed to "hide" 16:15:11 #info them from the additional users. 16:15:13 #info 16:15:15 #info Less than 2 years ago AppSupport instances were changed to be 16:15:17 #info user specific. After this change we could in theory allow 16:15:21 #info installation of Android for additional users as well. Probably 16:15:23 #info this should be controlled by the device owner (defaultuser). 16:15:25 #info 16:15:27 #info Long story short. It's currently a feature that requires more 16:15:29 #info work. When do we have time to improve it needs more planning. 16:16:06 Like headlamp_mapper commented you kind of can install Android apps for additional users but that is not intentional by design. 16:17:38 the device owner, user id 100000 works in a way device manager allowing or denying features from additional users 16:18:37 currently there are not that many features that you could control but that's the intention 16:21:43 for info, ii wasnt able to figure out the HBM config on my volla to get MCE to trigger it (it does have hbm) 16:24:43 time to move on... I guess this is covered. 16:24:59 #topic Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) 16:27:20 This one was opened by dcaliste (https://github.com/sailfishos/rust/pull/24), but there was already work from Matti (and tiny bit myself) underway in https://github.com/sailfishos/rust/tree/rust-1.89 16:27:41 Would be good to get Rust bumped again, but I heared a Whisper that 1.89 might break Gecko 16:27:56 Any idea on how the timeline could work there? 16:28:08 "would be good" meaning; Whisperfish depends on 1.89 or higher (because of upstream changes at Signal) 16:29:00 it depends on how much things break in gecko 16:29:16 it'd be nice to get that weather PR unstuck 16:29:24 +1 16:29:46 updating the rust crates in gecko is a bit of work if those then need updating also dependencies 16:29:52 In theory, we could do a Rust upgrade to Sailfish OS 5.1 release 16:30:09 we meaning us all 16:30:22 I would not mind being implicated. 16:31:18 let's move to general discussion 16:31:22 #topic General discussion (10 mins) 16:31:25 (but also, I don't know how to proceed or what needs fixing in Rust, for Gecko to be happy) 16:31:28 I need to test how gecko breaks and then we can decide how to move forward 16:31:57 Feel free to ping me if you need patches to rustc. I imagine there might be a few 16:32:11 rust doesn't need fixing, gecko has various rust crates or something in its sources and those often need to be updated when rust is updated 16:33:08 I tried updating some crates in gecko, but it didn't really help. I guess bigger version jumps were needed, and that brings other issues. 16:33:44 yeah, need to also see how esr102 works with the new rust 16:33:48 I should probably read flypig's blog on how to build it, and check myself whether I can get it working under a new rustc... 16:33:55 if only we had gtk3 and fennec 16:35:00 https://github.com/sailfishos/gecko-dev/tree/sailfishos-esr102 is public, so in theory shouldn't be an issue to test it from community side 16:35:06 but I'm not sure whether it'd be good use of my time 16:35:27 piggz[m]: Oh well, but then it's not a "Sailfishy" browser 🤷 16:35:29 just reminder, needs rust-cbindgen update to get that built 16:36:21 Luckily gecko is not that hard to get building, just don't give it too many cores at once :) 16:36:34 ack, https://github.com/sailfishos/rust-cbindgen is a thing and https://github.com/sailfishos/rust-cbindgen/tree/jb62655 seems "up to date"ish 16:37:18 yeah, that 0.26.0 is enough for esr102 16:37:23 piggz[m], guys were playing with gtk -> not sure if they tried running anything yet 16:37:56 maybe abranson knows 16:38:14 and yes, there should be "Sailfishy" browser as well 16:38:31 Day 64 contains the instructions but the site seems to be down: https://www.flypig.co.uk/list?&list_id=903&list=gecko 16:38:57 Newer rust-cbindgen also compiles fine iirc 16:39:28 we just need to get that merged 16:42:29 unlocking that Open Weather would be nice... If anybody able to help there that would be much appreciated 16:43:18 I was able to build and run gedit with the gtk experiment, but it segfaults when touched :) did not debug any further 16:43:38 When building gecko locally, adding MOZ_NOSPAM=1 to rpm-shared.env in the spec file may be needed so the build doesn't stop because of missing notify-send 16:44:52 Keto, oh, nice :-) 16:45:40 If anyone wants to play around with gtk, I know how to build it for sfos. But you'll end up being the gtk guy. 16:46:05 Maybe I should build it on the community obs for brave souls 16:46:14 abranson, let's do that 16:46:47 thumbup.gif 16:46:49 Sounds like abranson is about to be the gtk guy. 16:46:55 ;-) 16:47:21 o no i am not good with glib 16:48:15 it would be interesting to play with that but way too many things to do already 16:49:35 i cant be the gtk guy, im the qt6 guy, which is enough 16:49:55 mal, please try to keep your fingers away :-) 16:49:58 hehe 16:50:03 piggz[m]: sounds like a different side of the same coin :D 16:50:14 I'm happy to be half a Rust guy. :') 16:50:45 Sounds that we could start wrapping up. 16:51:22 I'd say so. Then I'll be walking home from my office now, instead of 50-ish minutes ago. 16:51:36 let's schedule the next then... 16:51:39 #topic Next meeting time and date (2 mins) 16:51:43 it'll be in here soon: 16:51:44 https://build.sailfishos.org/project/show/home:abranson:gtk 16:51:46 Proposing Thursday 26th February at 04:00 PM UTC 16:52:48 +1 16:54:11 👍 16:55:19 #info Next meeting will be held on Thursday 26th February 2026 at 04:00pm UTC: 2026-02-26T1600Z 16:55:28 thank you all! 16:55:48 #endmeeting