Even if you do not participate, topics tend to generate discussion. I want to see discussion happening. Thus, Iām proposing that weād use 10mins as minimum topic duration. Maximum 6 topics a week. Weāll continue with the extended 90 mins meeting duration.
Jolla to check action points from the previous meeting. We agreed today that weāll start to follow up action points on each meeting.
Add your name/nick using the template below to suggest a topic.
Indicate how much time youāll need so we can time-box the meeting accordingly.
Please be as thorough as you can with your question/topic.
If you canāt make the meeting please ask and name a substitute.
It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here and get responses that way.
We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isnāt clear enough it will be postponed. Also: always ask for more time than you anticipate your topic needs!
Please have your topics ready at least 3 days before the meeting so we can prepare good answers. Topics announced afterwards will be postponed to the next meeting.
Template for topic proposal: (post your topic proposals as comments to this forum topic).
Name/IRC nick:
Topic:
Some details about the topic:
Approx. time needed:
Substitute (optional):
Open Pull Requests:
If you have, or know of, a pull request thatās been open for at least 3 weeks, but which you think deserves attention, please add a comment using the template below and weāll consider it during the next meeting.
Topic: AppSupport on other community ports (particularly on the Xperia 1 and 5 IV)
Some details about the topic: Following what was mentioned in the previous community meeting regarding the Xperia 10 IV and V, I wondered if there were any plans to extend that to other well-supported ports (like on @rinigusās Nagara ports). If so, I understand the team may be busy with the JP2026 among other things, but may we have an estimate of when we will have it?
Approx. time needed: 5 mins
Substitute (optional): I will try to be online for the meeting, but Iām not sure
Some details about the topic: To build Whisperfish, we often require a version of Rust and LLVM that leads the version provided by Jolla. I build and host these packages on my home server, such that our CI system can build them, and the resulting RPMs end up on OpenRepos. Iād like to offer Whisperfish on Chum, however. This means weād need to compile Rust/LLVM on Chum, such that I can build-depend on them. However, Rust builds through an sb2 shim, which means that the actual rustc and cargo dependencies need to be available in the tooling and even in the chroot. See our Dockerfile for exact prereqs. As far as I understand, this is not currently possible to specify in OBS. More context at Show home:rubdos:whisperfish / Rust - SailfishOS Open Build Service and Show home:rubdos:whisperfish / llvm - SailfishOS Open Build Service. Would it be possible to get some help to get this going? Iām not entirely sure whether I can hack this in myself, or whether I need Jollaās or the communityās help on this.
Approx. time needed: 10 min
Substitute (optional): (@direc85, if heās available, but a kind ping from anyone would be helpful as a reminder)
Topic: Murray and Zambezi community ports - what are the next steps for AppSupport?
Some details about the topic: We are all very excited at the announcement from the previous community meeting regarding Jollaās confirmation that AppSupport for the community ports for Xperia 10IV and V is still on the cards. As the port maintainer, I would like to know what is required of me to ensure that AppSupport for this port can be delivered to users as soon as possible. Initial testing from users shows the existing AppSupport binaries do not work out of the box currently. Given we know community ports have been able to run AppSupport binaries in the past (see: Nagara) is this a port-specific problem (eg. something I havenāt done right like kernel configs), or a Jolla-side problem (AppSupport binaries need updating to be compatible with Android 15 base)? Is there a preferred way to open a line of dialogue on this topic between myself / any other willing community developer(s) and Jolla so that we can work towards a functioning solution? Noting that I live on the wrong side of the world (GMT+10) and have a day job.
Approx. time needed: 10 minutes?
Substitute (optional): Any present community developers / Murray or Zambezi users. As usual I cannot attend due to timezones.
Topic: Official Xperia 10 IV/V Jolla Ports: Latest internal tests based on which blobs, how far from feature complete, can we help get it done?
Some details about the topic: I know that some community ports are being developped. Nevertheless, I am personally very keep on offical ports, especially as I prefer to entrust @jolla for coding such sensitive software.
A company is a liability.
Therefore I wished to know how far did went the latest tests @mal and @jolla did with the 10 V. About a year ago @mal mentionned camera and audio finally working against āālatest blobsāā, that fingerprint was to be skipped, and that VoLTE had new configs that came along with the new blobs and that it was now a hard nut to crackā¦
I wish to know which ālatestā blobs specifically were used back then, and how much work is still missing (sure giving up on fingerprint, thatās a given) to get it all mostly set up (only volte left to work on?). Could community help crack this nut, if you share with us the exact piece of work still needed to be achieved?
Would be so lovely to get the last push for that official Xperia port .
Topic: Sound/microphone issue with audio/video recordings.
Some details about the topic: sound in audio and video recordings is very bad, details get lost. This may be related to a possible noise cancellation process what is good for calls, but very bad for recordings with camera or audiorecorder. See some more details in the linked thread below.
Whatās the reason for that, is there a possible solution that can be implemented like disabeling noise cancellation (if thatās the reason) for recordings, maybe even with a toggle in camera and audiorecorder or their settings?
Approx. time needed: 5 min
Substitute (optional): none, Iāll try to be there - but the main interest is getting an answer on this as the function may have heavily bad impact on the experience for new users
Topic:The Jolla phone 2026 screen may not have a software problem.
Some details about the topic:Hello, this issue was also discussed on August 20, but the exact cause still hadnāt been properly investigated. After that meeting, some people opened new threads, and we came across some interesting information.
Some people who bought the Jolla Phone 2026 were able to pass every screen color test without any issues at all. However, others experienced problems regardless of which color test they ran. Some described it as looking like a āMexico filter,ā while others saw a shadowy green tint appearing over black areas, or shading near the very top of the screen with orange and red colors.
At first, before we had this kind of evidence, most people thought the issue was software-related. But now that some users experience it while others donāt experience it at all, it has made the issue even more interesting and raised more questions.
Has any further investigation been done on this? At this point, it doesnāt really seem like a software-related issue anymore.
Topic: Camera Quality and resolution of new Jolla Phone
Some details about the topic:
The forum starts to discuss about the capabilities and problems with the camera. One point is the resolution of pictures taken with the native SFOS camera that just seems to use half of the possible resolution compared to Advanced Camera or even Android camera apps.
SFOS has a max of 4096 with both back cameras, while Advanced Camera has a max 4096 and 8192 for the different back cameras.
Front camera resoltion is a little bit more then double with Advanced camera compared to SFOS stock camera.
Also the max video resolution is 1440 in all apps - but as the camera module is/was also used in Sonyās Xperia Range (if we got that right) and capable of recording 4k videos even with an Xperia 10 III it should be possible to do 4k videos on the much better hardware of the new Jolla Phone too.
Some dome concrete questions:
Why does the SFOS camera app not use the max resolution for the main (1.0) camera?
Is the Jolla Phone capable to take 4K videos from the hardware side (especially camera modules and processor)? If yes, what must be done to enable this?
We had filters on other devices (that were still in Xperia 10 III but not working) and now are completely missing on the new Jolla Phone. Are there plans to bring that feature back with a future update?
Several people notice a fisheye effect especially with the (0.5) camera in 4:3. Listening to some people this is caused by the picture processing. Is there a plan to improve that (maybe with Camera API 2 (if Iām right even the new Jolla Phone still uses API 1)?
Approx. time needed: 5 min.
Substitute (optional): none; I try to be there - but primary want to hint Jolla to those topics and am curious fir answersā¦
.