Community meeting on IRC 16th February 2023

Schedule: Thursday 2023-02-16T08:00:00Z   :world_map:   :date:

Topic proposals for the 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.

* Name/IRC nick:
* Open PR URL:

  • Name/IRC nick: lolek
  • Topic: decouple encryption password from phone password
  • Some details about the topic:
    ok we finally have encryption that allow us to use alphanumeric values which is step forward in good direction. Now the only problem is that the same pw is needed twice to start up the phone. Imho this shouldn’t be required and some decoupling is required. I’d like to get information what’s exactly needed for this and if community can help with this?
  • Approx. time needed: 5min
  • Substitute (optional): leave a message if I’m not present.
  • Name/IRC nick: lolek
  • Topic: Bootloader relock
  • Some details about the topic:
    This is something that came out on the previous meeting.
    Thaodan said:

if the bootloader supports user signatures you can relock it with your own key to accept only kernels e.g. from Jolla but Sony phones don’t support that so far.

My question is:
What Jolla can do to change this, and how community can help achieve this?

  • Approx. time needed: 5min
  • Substitute (optional): leave a message if I’m not present
  • Name/IRC nick: lolek
  • Topic:providing a better mechanism in the OS for installing additional
    authentication methods and letting users choose what they prefer.
  • Some details about the topic:
    this is a continuation of:
    Community meeting on IRC 31st March 2022 - #4 by lolek

Also I asked there if Jolla can’t just license BB picture password since BB is gone.
And for this part I’d like to also get an answer and I’m willing to wait for this one as it would probably require contacting with BB.

  • Approx. time needed: 10min
  • Substitute (optional): leave a message if I can’t make it
  • Name/IRC nick: piggz
  • Topic: Enabling VoLTE on community ports
  • Some details about the topic:
    From VoLTE enablers: sources for ports
    With 4.5 SFOS released, I wonder what is the state with VoLTE support. Sounds like Jolla’s implementation is closed source. Any plans to release it? Earlier, we were told that it is too early and no definite answer could be given. Maybe it is the time?

I believe unofficially ported devices could benefit from looking into Jolla’s approach. Right now, I personally, even have no idea where to start digging. And, in principle, time used for duplicating efforts is not very efficiently spent.

In addition, does keeping VoLTE closed give Jolla an advantage over competitors? most other mobile linux distros are using ModemManager, so this seems unlikely, opening up VoLTE would be a great boost to sailfish ports.

If its not possible to open the code, could the compiled packages atleast be put into the adaptation-common repos so that porters can experiment? If there are other device-specific hacks required to enable volte, could these be documented to help porters understand what needs to be written? Would any sony specific packages also be useful on other sony ports?

  • Approx. time needed: 20 minutes
  • Substitute (optional): @rinigus
  • Name/IRC nick: piggz
  • Topic: Qt Upgrade
  • Some details about the topic:
    The time has come again to ask about the potential for a Qt Upgrade in Sailfiish. Qt 5.6 was released almost 7 years ago, and security support ended in 2019. Newer Qt versions not only add useful feature, but bring improved compiler support and support for newer c++ features.
  • Approx. time needed: 30 mins
  • Substitute (optional): @rinigus

Untracked bug reports

ID Comments Additional Information


ID Original
14373 14372
1 Like
  • Name/IRC nick: vlagged[m]
  • Topic: ability to buy/enable Android AppSupport for community ports
  • Some details about the topic:

Compared to the alternatives (anbox of old or waydroid now) Jolla’s AAS is specifically more integrated with SailfishOS and makes “selling” the idea to switch to Sailfish more easy for anyone. Adding the ability to pick any device that has a community port can help with people’s different hardware needs and expectations while still giving a great experience for Android apps. This would also mean that the work for the tight integration with Sailifish OS pays off even more.

Since this is not something that any user could make an assessment of, I would suggest having a similar step to the one that is already in place for enabling Jolla Store access, which is that the porter confirms that the device is working with AAS. What is enabled then is the ability to buy the license that would activate the download for the user that bought it.

For the porter to be able to make this assessment a minimum requirement document would be needed, specifying the e.g. min kernel version, kernel params etc. Waydroid could be used as a similar in spirit “proof of work” for the porter.
Since adding this support may or may not succeed, it would probably mean that the porter would have to have access to give it a try (assuming ‘proof of work’) without costs other than having a set-by-Jolla minimal feature parity (e.g. audio should work, you name it) for the port.
To be able to add this kind of access a possibility would be, when adding the store support for a ported device, to request a “porting enabling” license for the specific device the porter uses for testing so that he can also use the store to install Android AppSupport and debug it.
For debugging, the same level of support as of today for community ports should be enough. If the porting fails, it would be nothing (but time) lost.
If it succeeds, there could be a bunch of new customers for SailfishOS as a platform and for the AppSupport product for each port. And we get more friends to move over here:)

  • Approx. time needed: 10 mins
  • Substitute (optional): b100dian
  • Name/IRC nick: lolek
  • Topic: Moving away from GitHub
  • Some details about the topic:
    Since Microsoft took over GitHub they started to use OSS projects to train their CoPilot product on others code and is making money out of it. The Software Freedom Conservancy organization calls OSS projects to move away from GitHub. I’d like to know if Jolla is aware of this and are there any plans in the future to move away from that platform to somewhere else?
    DeepWeb / Open source developers urged to move away from GitHub after Copilot launch
  • Approx. time needed: 10 min
  • Substitute (optional):
    I expect some conversation between the community members around this topic.
1 Like

Minutes: #sailfishos-meeting: Sailfish OS, open source, collaboration -- 16th February 2023
Minutes (text):
Log: #sailfishos-meeting log