@projectmoon Only after I had these issues. I'm starting to get messages through now. There is no read confirmation from what I can tell. I now have it were the chat has disappeared as the last thing I sent was an image. I have to use contacts to find chat. The invisible messages I got before this are stuck as unread on the appbar

@PhAndersson said: (Volla Quintus upgraded to 24.04-1.3 from 20.04/OTA-12). obexd is not started by default, that's strange. What's the output of systemctl --user cat obex and systemctl --user status obex (obviously do this after a phone restart)

@PerlMax said: Sorry for the long post. aaarg, sorry, one point again There is no problem here

A new Alpha is out: Download here: https://git.brennoflavio.com.br/brennoflavio/greenline/releases Github mirror: https://github.com/brennoflavio/greenline/releases Changelog: Render and allow saving contact array messages (the ones when you send 2 or more contacts in the same message) Allow sending reactions. Open the reaction page and you'll see reaction emojis in the bottom Allow archiving chats locally, so they don't appear in the main page Render unsupported messages, so you know they arrived. In terms of message support, there's no plans to support further message types, most of the remaining ones are business oriented and very specific like pools and broadcast messages. Add infrastructure to support translations Progress torwards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

@brenno.almeida said: @projectmoon @amaurydbz we just got the patches released in original Futify. Would you mind checking if the updated store version works for you? Thanks I'm still logged in to regular Futify from long ago. I played a song this morning and it worked. But then I did a search for a playlist, and played it. But it would go through each song for 2 seconds, without actually buffering or playing it.

@Ida_ Thank you very much! Unfortunately, at the moment, this does not help me understand what happens on 24.04-2.x

@dl8aax said: @Vlad-Nirky said: Could you give some more details about the database to be backed up? Which application is it for? I'm creating the database with: var db = LocalStorage.openDatabaseSync("MienImmen", "1.0", "", 1000000); Because there's also important data, I want to back up the database and import it to my PC. Swapping the database is less error-prone than exporting and importing individual tables. There are approximately 40 tables. App databases are stored under the app namespace, e.g if your app is called "abd.xyz", you should either find it in ~/.local/share/abd.xyz or under ./config/abd.xyz

@gpatel-fr I guess, when all will be ready, that Ratchanan will give the go to use QT6 in clickable with the next framework as he did for 24.04.

@naz.r Merezhyvo works normally with my volla 22 on 24.04-2.x daily . Thanks. The browser can be too open from the OpenStore without crashing.

@PerlMax it's on Telegram according to https://open-store.io/submit

@pparent Agreed, and i will follow your attempt closely

@kugiigi clickable works fine on UT now. Install clickable snap and docker snap connect some.slots and you're off to the races.

@Moem thank you so much, it is very new, I created it, I wish you best of luck as well

@AdFundum no problem! the process is basically 3 steps: verify image/PATH copy to lss wallpaper directory (so user can see the background in lss), this is optional if you don't care about the user being able to reset the background from lss its not necessary but still useful as a place the user wont casually delete unless they want the wallpaper gone. send the correct dbus calls to set URI (from new PATH of step 2) then call update on two services via dbus calls. EDIT: i think, or its close to that its been a month since i touched the background code in wallpaper.cpp

I've published the new revision (0.1.8) with the following improvements: -Fix layout problem coming from changes upstream -Improve ContentHub handling -Improve call icons layout I should also not crash on 24.04-2.x, although it will probably not be usable yet, as for now it seems that On-Screen-Keyboard does not work on any XWayland app. I will try to investigate more about that soon. I next revision I will try to add an option to configure scaling with fine grain, and few improvements/fixes in the UI.