Guido Günther @agx@librem.one

@kirschner For #LinuxMobile phones there's #Railway : https://mobile.schmidhuberj.de/railway

Maybe it would be useful if the apps could display the QR Code?

@okias Nah, I'm just standing on the shoulders of giants here (but thanks!). 😄

@eliasr @devrtz …and we need the DBus activation in chatty for push notifications too.

@eliasr as chatty and calls run as daemon on session startup: so should it be slow for large call histories / room lists we can tweak that by preloading those. @devrtz already optimized that in calls a while back by only loading parts of the history. So basically startup was seemingly slow (although the app was already up) because calls/chatty didn't notify the rest of the system with a valid token

@eliasr Both were running in the background already but the activation token to tell the compositor: hey, I'm here and should get focus (because phosh said so) was lost in the phosh -> spawns calls -> spawned calls instance notifies "calls daemon" that a window should be shown (and then quits) chain of events. By switching to DBus activation we remove the intermediate calls instance, the token gets passed and the compositor knows that calls is up (same for chatty).

It's the small things: If you've been bothered with #calls and #chatty seemingly starting up slowly in #phosh (while most other apps startup fast): I've posted MRs to fix this in chatty and calls (which then also prompted a small fix in phosh). Here's a quick demo of calls before and after the change:

MRs:
- calls: https://gitlab.gnome.org/GNOME/calls/-/merge_requests/760
- chatty: https://gitlab.gnome.org/World/Chatty/-/merge_requests/1432

@Blort That's the thing, with the current rope we have we can just take what the text input gives us so we'll need to improve this per toolkit. It works very well for most cases though, that's why I might end up enabling it and work from there.

@person @antonok The alt text for the image says Onplus 6

@devrtz and myself debugged this a little and it turned out that his devices didn't have a proper channel list set. This can be done via s.th. like

`+CSCB: 0, "0-65535",""'`

(or the #ModemManager SetChannels API we added for that)

@NGIZero

@pavel Hope you all stay safe and dry.

@NGIZero Yeah, happy it worked out! Now we can look at adding all those details to make it nice.

@devrtz @NGIZero This is expected if your device gets unsolicited messages via QMI (rather than AT). Which is one of the next things on the list after initial support lands.It's a relatively minor change code wise, I have a branch for this already but want to keep the initial MR as small as possible so we can land the app facing APIs and thus cut the problem in two halves that can be worked on independently).

@nivea @devrtz @NGIZero You need the merge requests for ModemManager and Phosh. Without these you'll not see any CBMs. Note the *upcoming* in my post 😃