Guido Günther @agx@librem.one

@eliasr @janvlug @z3ntu yes, https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1095

@martijnbraam @janvlug @z3ntu somewhat similar yes, it's simpler though as those are r/o (whereas the messaging interface can also compose sms), part matching is also somewhat different, and there's a replacement feature to replace outdated alerts.

Today was cell broadcast test day in NL. @janvlug and @z3ntu thankfully captured Modemmanager logs. Piped that into my MM testcase and could parse it out all right:

> NL-Alert 04-12-2023 12:00: TESTBERICHT. De overheid waarschuwt je tijdens noodsituaties via NL-Alert. Je leest dan wat je moet doen en waar je meer informatie kan vinden. *** TEST MESSAGE Netherlands Government Public Warning System. No action required.

Next up message assembly and exposing it on DBus.

#ModemManager #phosh

@martijnbraam 🤩 Seems were making progress after all

#phosh

@Fosstonaut Maybe we can get someone motivated enough to look at this 😄 - it shouldn't block on me.

See also https://github.com/ranfdev/Notify

@janet @cas I don't follow openstore (ubuntu touch's app store). But there's multiple ones on flathub: https://flathub.org/apps/search?q=youtube and there's also apps like stream (https://linuxphoneapps.org/apps/sm.puri.stream/) that interface with invidious rather than youtube to avoid the tracking.

@cas time to leave Android behind and switch to a #LinuxMobile phone?

@linmob @FOSSingularity@strangeobject.space Yes, adding `StartupNotify` is the whole thing in the desktop file. The application then also needs to signal activation (basically started up) using the xdg-activation Wayland protocol (or for older things gtk-shell or _NET_STARTUP_INFO for x11). When you use a toolkit (e.g. GTK) this happens automatically,

In case you have splash screens not hiding soon enough then either your app doesn't send the signal or the GTK use by phosh itself lacks https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5628.

@linmob @FOSSingularity@strangeobject.space I don't see any context shown here.

phoc bits: https://gitlab.gnome.org/World/Phosh/phoc/-/merge_requests/506

gtk: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6582

mobile-settings: https://gitlab.gnome.org/guidog/phosh-mobile-settings/-/merge_requests/82

Rudra's work on managing favorites: https://gitlab.gnome.org/guidog/phosh-mobile-settings/-/merge_requests/73

It's the small things. @rudraps@mastodon.social is working on a mobile-settings feature that requires touch drag and drop in a GtkFlowBox. That didn't work and as it turns out we need two small fixes in #phoc and a small fix in #gtk . With that we can also reorder OnScrenKeyboard shortcuts that way:

#phosh

@pwithnall …and there's one more thing: people might just not feel up to the task and don't want to step into the spotlight. Learning on the project is extremely hard if the project is undermaintained and a bit dated already.

Hence "starting your own project for educational purposes" where you can make your own mistakes in a corner of the internet might feel like the safer choice.

A welcoming community can mitigate that a lot.

@pwithnall I tried both ways and it's not that clear to me.

Often the reason why starting out new is that people have *tried* to fix the old app and patches bitrotted unreviewed.

In that case it's either maintaining and modernizing a fork of the old app (with unclear outcome) or doing s.th. in your favorite lang and libs along your lines of thinking.

That can be a *big* motivation for volunteer work. (Making it more tolerable to live with less polish).

@rmader I have looking at GTKs new hw offloading on my list, it currently just keeps slipping. Filed https://gitlab.gnome.org/guidog/livi/-/issues/5 to make that more obvious. (wouldn't only benefit the Librem 5 but also the mnt reform and MobileLinux in general).

@tbernard @rmader Interesting! livi (https://gitlab.gnome.org/guidog/livi) used the older ones as a baseline. Time for me to catch up.

@ebassi I guess that means: Happy birthday 🎁

If you're not developing for phosh or phoc you can ignore this and the above entirely.

Background is that check_import_dmabuf in wlr_linux_dmabuf_v1.c picks the wrong node for it's validation (https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3757) so we have to help it a little bit for the time being.