07:05:52 <rainemak> #startmeeting Sailfish OS, open source, collaboration -- 22nd May 2025
07:05:52 <sailbot> Meeting started Thu May 22 07:05:52 2025 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:05:52 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
07:05:58 <rainemak> #info Meeting information and agenda can be found here:
07:05:58 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-22nd-may-2025/23148
07:05:58 <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.
07:06:01 <rainemak> #topic Brief introduction (5 min). Please prefix your name/handle with #info
07:06:19 <rainemak> #info <Fingus> #info Niels S., Community
07:06:19 <rainemak> #info <ExTechOp> #info Otto Mäkelä,
07:06:19 <rainemak> #info <direc85[m]> #info Matti Viljanen, Jolla
07:06:19 <rainemak> #info <ExTechOp> #info Otto Mäkelä, community
07:06:19 <rainemak> #info <piesalad[m]> #info tfinn, Community
07:06:20 <rainemak> #info  <flypig> #info David Llewellyn-Jones, community
07:06:22 <rainemak> #info  <rainemak> community leading 4-2
07:06:39 <rainemak> Two topics today. In addition, two weeks ago we agreed to have a roadmap checkpoint
07:06:39 <rainemak> today. Next roadmap checkpoint will be 19th June. I'll try to remind ourselves on
07:06:39 <rainemak> the next community meeting.
07:06:47 <rainemak> #topic Sailfish OS roadmap checkpoint (10 mins -- rainemak)
07:07:00 <rainemak> #info Previous roadmap checkpoint 24th April community meeting.
07:07:00 <rainemak> #info An update from there as a textual update.
07:07:06 <rainemak> #info <Jolla> Following bigger update items that we have on the roadmap.
07:07:06 <rainemak> #info <Jolla> Good part of these will likely land to Sailfish OS 5.1.
07:07:06 <rainemak> #info <Jolla> Items are not in priority order:
07:07:06 <rainemak> #info <Jolla> systemd
07:07:06 <rainemak> #info <Jolla> pulseaudio - fixes needed for bluetooth
07:07:08 <rainemak> #info <Jolla> python - ready for 5.1
07:07:09 <rainemak> #info <Jolla> rpm
07:07:11 <rainemak> #info <Jolla> openssl
07:07:13 <rainemak> #info <Jolla> gcc
07:07:15 <rainemak> #info <Jolla> esr102
07:07:17 <rainemak> #info <Jolla> glibc - integrated to 5.1
07:07:19 <rainemak> #info <Jolla> glib2 - integrated to 5.1
07:07:21 <rainemak> #info <Jolla> lvm   - integrated to 5.1
07:07:23 <rainemak> #info <Jolla> and tons of other updates.
07:07:25 <rainemak> #info Sailfish OS 5.1 branching somewhere summer time frame
07:07:27 <rainemak> #info or right after summer break. After branching, we’d need
07:07:31 <rainemak> #info a month or two for ironing out issues that are blocking
07:07:33 <rainemak> #info the release.
07:07:35 <rainemak> #info Gecko sailfishos-esr102 related branches will be availble for
07:07:37 <rainemak> #info each related repository: gecko-dev, embedlite-components,
07:07:39 <rainemak> #info qtmozembed, sailfish-components-webview, sailfish-browser.
07:07:45 <rainemak> #info Gecko's submodule points to mal's fork. During development patches
07:07:45 <rainemak> #info are applied to git tree. You may see force pushes on these development
07:07:47 <rainemak> #info branches - be warned. No branches yet for qtmozembed and sailfish-components-webview.
07:07:49 <rainemak> #link https://github.com/sailfishos/gecko-dev/tree/sailfishos-esr102
07:07:51 <rainemak> #link https://github.com/mlehtima/gecko-dev-mirror/commits/sailfishos-esr102/
07:07:53 <rainemak> #link https://github.com/sailfishos/embedlite-components/tree/sailfishos-esr102
07:07:55 <rainemak> #link https://github.com/sailfishos/qtmozembed/tree/sailfishos-esr102
07:07:57 <rainemak> #link https://github.com/sailfishos/sailfish-components-webview/tree/sailfishos-esr102
07:08:01 <rainemak> #link https://github.com/sailfishos/sailfish-browser/tree/sailfishos-esr102
07:09:42 <flypig> Thanks for sharing these gecko branches; that's really exciting to see.
07:10:22 <rainemak> Builds fine but not rendering yet. We'll try to get WebRendering pipeline working.
07:10:23 <dodoradio[m]> has there been anything you can share on the open sourcing of components?
07:10:27 <flypig> Great work from mal.
07:10:34 <rainemak> flypig, yeap
07:11:21 <flypig> Maybe it's not a topic for now, but I'm very curious to hear more about WebRender progress.
07:12:16 <rainemak> dodoradio[m], not really. Steadily progressing.
07:13:00 <rainemak> flypig, we could have WebRender update as a topic for the next meeting or the next community newsletter
07:13:19 <rainemak> maybe it's a topic more for the community meeting
07:13:26 <dodoradio[m]> ok, that's still good to hear, and the transparency about planned component updates is really appreciated!
07:13:41 <rainemak> dodoradio[m], thanks
07:13:56 <flypig> rainemak, that would be great. I can submit a topic for the meeting if that would be appropriate?
07:14:35 <rainemak> flypig, yes sure, please do
07:14:53 <flypig> 👍 (thumbsup)
07:15:00 <rainemak> next one is a topic from Fingus
07:15:03 <rainemak> #topic Percentage display of Jolla C2 battery (10 mins -- Fingus)
07:15:12 <rainemak> #info <Fingus> The battery calibration of the percentage display on the Jolla C2
07:15:12 <rainemak> #info <Fingus> has a strange mapping/positive shifting. While the system shows
07:15:12 <rainemak> #info <Fingus> 100% battery at “end” of charging, it sometimes continues to charge
07:15:12 <rainemak> #info <Fingus> at 400mA and decreasing for 10-30 minutes until its really “full”
07:15:12 <rainemak> #info <Fingus> - the System recognized that correctly then. When the
07:15:14 <rainemak> #info <Fingus> battery-level falls below 20%, it drops very quickly (only a few
07:15:15 <rainemak> #info <Fingus> minutes remain). The voltage of the battery is then 3.6 volts or
07:15:17 <rainemak> #info <Fingus> lower, which indicates a miscalibration. Here in the forum, there
07:15:19 <rainemak> #info <Fingus> are already some who have also observed and reported this. I do
07:15:21 <rainemak> #info <Fingus> not consider this to be a hardware fault, as the battery voltages
07:15:23 <rainemak> #info <Fingus> are within the permissible parameters. I could imagine it is
07:15:25 <rainemak> #info <Fingus> defined in the device adaptation. Is there a way for you to easily
07:15:27 <rainemak> #info <Fingus> change this mapping? Or its up to Reeder to change it in the
07:15:31 <rainemak> #info <Fingus> Firmware/Driver?
07:15:33 <rainemak> #info <Jolla> Internal bug report filed regarding this as well. Maybe something
07:15:35 <rainemak> #info <Jolla> wrong in the calibration. Needs more investigation.
07:15:38 <rainemak> #info <Jolla> Both nephros and affe_null posted good pointers to the forum.
07:15:39 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-22nd-may-2025/23148/3
07:15:41 <rainemak> #link https://forum.sailfishos.org/t/community-meeting-on-22nd-may-2025/23148/4
07:16:35 <Fingus> I would like to add: Observation on my Jolla C2: If the display currently shows 20% battery level, it actually corresponds to a true 5% battery level at the lower end of the battery discharge. At the upper end, when 100% is displayed, it is more like a real 96% battery level, as approximately 140mAh (3,5% of the 4000mAh battery-capacity) are often still being charged into the battery before the charging c
07:17:11 <Fingus> This inaccurate battery display caused issues for some Jolla C2 users during setup (the device shut down during encryption). By now, security mechanisms have been implemented via an update (the battery level must have a minimum charge, and the charger must be connected). Nevertheless, it would be less confusing if a 20% battery display meant more than 5 minutes of runtime, as is common with other smartpho
07:18:04 <Fingus> In my case, I don't consider it a hardware issue, as I can get 1.5 to 2 days of use on a single charge with normal usage before needing to recharge which is really great.
07:18:23 <rainemak> We are hearing you Fingus and very good analysis
07:18:48 <Fingus> Thanks for tracking it
07:19:32 <rainemak> I'm also very glad about of the low power consumption but I'm still charging like daily -- old habits die hard
07:19:45 <rainemak> s/about//
07:20:09 <Fingus> Yeah, it will increase the battery life i guess
07:20:45 <direc85[m]> The battery life is very good for me as well, and I too keep the battery quite well charged. I don't think I even noticed about the sudden power-off until I read about it on the forum.
07:21:09 <rainemak> And it's good to enable that "Battery ageing protection"
07:21:36 <rainemak> ^ like stop charging at 90%
07:22:01 <Fingus> direct85: I suspect many people charge the battery when it is still above 20%.
07:22:29 <rainemak> 3mins to go
07:22:33 <direc85[m]> I typically have the phone connected via USB, so the treshold is nice to have.
07:23:27 <direc85[m]> Fingus: My anxiety starts to kick in at around 30% :)
07:23:55 <nephros_> Batterybuddy charger connected detection is wonky though. It can detect "Charging=yes + Charger not connected" sometimes.
07:24:02 <Fingus> direct85: For me its 25% and under
07:25:09 <rainemak> let's move on
07:25:12 <rainemak> #topic When the video recording in Jolla Camera will be added for C2??? (5 mins -- Valorsogueriero97)
07:25:18 <rainemak> #info <Valorsogueriero97> I think, have read that the C2 can’t yet natively record
07:25:18 <rainemak> #info <Valorsogueriero97> video, and it’s pretty… absurd. When this will be
07:25:18 <rainemak> #info <Valorsogueriero97> fixed? When we will have complete hw support for the
07:25:18 <rainemak> #info <Valorsogueriero97> C2? Otherwise I am not buying it :slight_smile:
07:25:40 <rainemak> #info <Jolla> Getting video recording working requires that we're able to
07:25:40 <rainemak> #info <Jolla> swap from Camera 1 to Camera 2 API. Unfortunately, Camera 2 API
07:25:40 <rainemak> #info <Jolla> is not yet there. Worth noting that Camera 2 API is developed
07:25:40 <rainemak> #info <Jolla> jointly with the Sailfish OS community and you have
07:25:40 <rainemak> #info <Jolla> been pushing it forward very well -- we just do not have hands
07:25:42 <rainemak> #info <Jolla> for everything. That said, Camera 2 API is not necessarily too
07:25:43 <rainemak> #info <Jolla> far away given that there are no surprises. It's ready when it
07:25:45 <rainemak> #info <Jolla> is ready.
07:25:47 <rainemak> #link https://github.com/sailfishos/droidmedia/issues?q=is%3Aissue%20state%3Aopen%20label%3Acamera2
07:26:17 <direc85[m]> nephros: Hm, they are separately tracked values iirc. Feel free to file a bug about it :)
07:26:44 <Fingus> I'm using OpenCamera within App-Support do record Videos. I can choose there Camera API 2.0, is that real working?
07:26:54 <rainemak> let's continue battery discussion in the general if something left
07:28:29 <Fingus> In many Sony smartphones I have used, the percentage increase up to 99% is consistent, and then the last 1% takes a very long time. 100% corresponds to the status of being fully charged, and no charging current flows into the battery anymore.
07:28:48 <rainemak> Usually it goes so that same resources are shared between developing different features, one could ask whether you'd like to have updated browser engine or Camera 2 API. These kind of things we need to prioritize. It should go without saying that also within context of esr102 development we'd like to develop that with you together.
07:29:06 <Fingus> Maybe this behavior could be adapted for the Jolla C2.
07:29:47 <rainemak> let's continue battery discussion in the general discussion at the end
07:30:00 <Fingus> ok
07:30:35 <rainemak> #topic Open PR discussion (5 mins -- asked by Jolla)
07:31:08 <rainemak> anybody?
07:34:45 <flypig> It was great to see all the PR progress in the repository roundup last week.
07:35:08 <rainemak> yeap, surely it was a longer time frame
07:35:33 <rainemak> let's move to general discussion and back to battery :-)
07:35:34 <rainemak> #topic General discussion (15 mins)
07:36:08 <rainemak> Very likely most of you noticed already... but
07:36:08 <rainemak> #info Jolla C2 kernel available in GitHub’s Sailfish OS Adaptation Repositories
07:36:08 <rainemak> #link https://forum.sailfishos.org/t/jolla-c2-kernel-available-in-githubs-sailfish-os-adaptation-repositories/23249
07:37:01 <nephros_> Seeing the pulseaudio update on the roadmap: has a move to pipewire been considered or looked into ever?
07:38:11 <rainemak> nephros_, has been looked at point. It's a bigger effort as there are a lot of resource policies that are quite mobile specific
07:38:37 <rainemak> nephros_, the last time we checked none of those existed
07:38:53 <nephros_> rainemak: that's precisely what I have been wondering - can the policystuff maybe be repplaced by wireplumber schripting.
07:40:37 <rainemak> nephros_, maybe, I don't know
07:41:13 <rainemak> Fingus, direc85[m] : did you had still something on the battery levels that you'd like to discuss
07:42:00 <Fingus> rainemak: From my side, everything has been said.
07:42:08 <nephros_> ok thanks for the answer (but do look into it again once Mozilla gets to the release where it uses it vo video)
07:42:13 <nephros_> *for
07:42:48 <direc85[m]> rainemak: Nothing more to add from me
07:42:51 <rainemak> nephros_, thanks
07:43:06 <rainemak> we'll try to remember that
07:43:37 <dcaliste> rainemak, thanks for the pointer on the kernel sources and adaptation repos for C2.
07:44:24 <rainemak> dcaliste, you're welcome
07:46:06 <rainemak> if there you have interest to contribute to esr102, we're all open
07:46:42 <rainemak> if you have interest to contribute to esr102, we're all open
07:47:37 <dcaliste> How is the process for esr102 different from what flypig published in his blog series ? I mean to build from the repos…
07:47:58 <rainemak> Something similar to flypig's esr91 diary would be awesome -- I still cannot get how did you flypig managed to do it
07:48:49 <rainemak> dcaliste, I think that getting esr102 building was a smoother ride when comparing to esr91
07:49:43 <rainemak> dcaliste, but similar steps as with esr91 are waiting for us
07:50:13 <flypig> There's a rust update required, if I saw correctly? Is that easy to handle with the SDK?
07:50:22 <dcaliste> Great, I may give it a try then, if I find enough time for it !
07:50:50 <rainemak> mal commented something about rust-cbindgen at point but I don't recall others
07:51:52 <direc85[m]> Rust 1.75 can build up to Firefox 123, so we're covered for a while: https://firefox-source-docs.mozilla.org/writing-rust-code/update-policy.html#schedule
07:52:40 <flypig> I guess this was the change I was thinking of (from the roundup): https://github.com/sailfishos/gecko-dev/pull/173
07:53:08 <rainemak> Yeap
07:53:14 <direc85[m]> flypig, you were faster to find that :)
07:53:17 <flypig> But the change is on the gecko side, so not making the build more complex; that was my mistake.
07:53:34 <rainemak> no worry
07:53:46 <rainemak> shall we schedule next meeting...
07:53:52 <rainemak> #topic Next meeting time and date (2 mins)
07:54:00 <flypig> direc85[m] :D I went via dcaliste's report in the newsletter!
07:54:19 <rainemak> flypig, that's so handy at time
07:54:26 <rainemak> s
07:54:27 <flypig> Absolutely!
07:54:38 <rainemak> Proposing Thursday 5th June at 07:00am UTC
07:54:46 <rainemak> the usual interval
07:54:56 <flypig> Looks good!
07:55:02 <ExTechOp> Works4me
07:55:58 <Fingus> Thank you for this great meeting, by the way, it was my first!
07:55:58 <rainemak> settled
07:56:26 <rainemak> Fingus, ah, I didn't realize as you're active at the forum
07:56:33 <flypig> Great contributions Fingus; glad you're here!
07:56:33 <rainemak> Fingus, nice to have you here
07:56:46 <rainemak> flypig, +1
07:57:07 <rainemak> #info Next meeting will be held on Thursday 5th June 2025 at 07:00am UTC: 2025-06-05T0700Z
07:57:09 <ExTechOp> Thank you, everyone!
07:57:14 <Fingus> rainemak: These meetings have a different quality in real-time.
07:57:33 <rainemak> Thank you everybody! Fingus please join in two weeks as well.
07:57:46 <Fingus> rainemak: i try to do so
07:57:52 <rainemak> Great!
07:58:08 <flypig> Thanks rainemak for the great hosting!
07:58:30 <rainemak> #endmeeting