Community meeting on 6th November 2025

[bundyo]

More likely they will sell AAS licenses for the official community port at lower price.

[dcaliste]

As I mentioned during the meeting, I’m trying different ways to add more backends to the note application, now that it is open source. The native backend is a SQLite database which works great for the application itself. The idea is to add concurrent backends that would allow to synchronise part of the notes. Like for the calendar application, I keep the local-only backend and I’ve modified the note application to display either the local notes, or notes originating from other providers.

I’ve implemented a file storage backend, that allows to display files from given directories as notes (modify, delete or create new files within the note application). The files themselves can still be modified outside the note application with a text editor or synchronised by webDAV or git with a server.

This is proposed in this pull request and currently under an early stage of review. It’s more to test the possibility of various backend and may not be accepted as a change in the application, or under an improved form. But it’s usable and I’m eager to hear also feedback on the usability, implementation, interest… I’ve compiled a version of my branch on OBS for those who would like to test, as suggested by @pherjung during the meeting. I’ve not yet created the setting to add looked up directories. It should be done on commad line like:

dconf write /sailfish/notes/directory_list "[['/home/defaultuser/Documents/Recettes']]"

It’s a list that can contain several directories. There are currently some limitations in the implementation:

• it’s not limiting the size of the files when displaying the content as notes. Don’t try with large text files of several MB.
• it’s not guessing the file content, so binary files will display garbage.
• on contrary to the native notes, the file as notes are sorted by modification dates, so modifying a note will promote it to the first position.
• colours are persistent only when selected by the user, otherwise they are taken randomly from a pool of colours.

Some screenshots:

Some more details about the implementation are discussed in the pull request.

Edit: I forgot an important notice, it required to modify the storage logic to add concurrent backends. It may negatively impact the behaviour for the native notes. Don’t forget to make a copy of the database before using the modified application version. The location for the note database is:

~/.local/share/com.jolla/notes/QML/OfflineStorage/Databases

[bananaMixer]

The pherjung’s question and the Jolla’s answer made me think to a similar project I stumbled upon randomly: GitHub - catacombing/catacomb: A Wayland Mobile Compositor

I didn’t test it and I am not familiar with compositor and such things. I am not sure that it could be of any use, but in this experimental PoC phase, looking at all possibilities could help to choose the right direction.

---

Thanks for all the good news and the hard work, both from Jolla and the community.

[rainemak]

First things first, we’re thinking different kind of approaches for Xperia 10 IV / 10 V. We did not say that we will change the direction on how the port should be done. That said, Xperia 10 IV / 10 V could well be the first officially supported community port which would have commercial components available including AppSupport – but that community port does not exists yet.

[Systematics]

First of all, it was a great read of the community meeting. Thank you!

I can only speak for myself and my experiences. I know, that many other people are flashing and successfully running community ports on their phones. And I am super happy about it.

Unfortunately, I have had bad experiences with using community ports. I bricked my Volla X in the past.

Even though I see the challenges that Jolla needs to address with the Sony Xperia IV/V (fingerprint, camera), I would prefer to obtain the image or build from Jolla themselves. This way, I like to know the source of the image. In Jolla’s case I know the legal entity behind it. Again, I really appreciate what community members like Piggz are doing with their effort, and I try to support them through donations. I trust them. But I would still like the option to get an official image from Jolla. Even with the fact that their builds are lacking of features like the encryption key is not bound to the lock key (unlock the device).

[yusssufff]

I completely agree with you @Systematics .

Official Jolla port is so very important to me for all the reasons you nicely stated.