Guido Günther @agx@librem.one

@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 😃

@stefan Komplett neu nicht, aber noch nicht gemerged: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1095

Today was "Bundesweiter Warntag" in Germany so a good point in time to test #ModemManager's & #phosh's upcoming #cellbroadcast support 🚨 .

The sounds emitted by #feedbackd are only stubs (and you don' t hear the haptic in the video but I promise it's there 😃).

There's three messages because the CBMs are sent out on three different channels.

Thanks @NGIZero for supporting my work on this!

#LinuxMobile

@stefan @fsfe könnt ihr hier vielleicht helfen?

And here's what we could do for copy. Put that into an extra MR for now so we can check whether it's predictive enough for the user what is being copied (while the paste bits from above can already land for 0.42).

Note that this is orthogonal to what an app/UI toolkit offers for copy/paste (via context menus or drag handles) already.

#phosh

Copy / paste can be fiddly on mobile. I opened an MR today to make the paste part a bit easier in phosh-osk-stub (another old branch finally cleaned up into a (hopefully) mergeable state):

#phosh #gtk #LinuxMobile

@me Good news: Fractal (and other clients) don't need to use feedbackd directly. They just needs to set the `im.received` `category` on the notification: (https://specifications.freedesktop.org/notification-spec/latest/categories.html) and #phosh handles the details.

This is supported by about all notification client libs (libnotify, glib/gio (https://docs.gtk.org/gio/method.Notification.set_category.html)

Maybe file an issue with Fractal for that? Given that Fractal uses glib/gio it's a one line change.

@craftyguy @newbyte I assume the crash is in qemu-user-static ? This is o.k. to debug as you can run the built static binary right from your built qemu tree. When debugging the reverse (a arm64 binary crashing on amd64) QEMU_STRACE was very useful: https://www.qemu.org/docs/master/user/main.html