Guido Günther @agx@librem.one

@janvlug @eliasr @devrtz

Yup, better not do that (`dpkg --force-depends` would work to remove system chatty temporarily but it'll get pulled back in on updates).

Another option is to move away /etc/xdg/autostart/sm.puri.Chatty-daemon.desktop when running the flatpak (which AFAIK does not get autostarted on boot so you might not get new SMS).

Chatty is tightly integrated into the system on phones, I think the flatpak is currently more of a demo for systems where it's not running yet.

@docRekd @eliasr It took us a long time to make Linux work on PC, servers and laptops either but it grows device by device and if you include the Halium based devices there's quiet a few already. It will just be the new normal at some point.

@eliasr @janvlug @devrtz I would even uninstall the system chatty as otherwise two processes try to take SMS out of the Modem. (and after uninstalling make sure there's no process running).

@janvlug @devrtz Looks like you had the system instance still running (starting chatty would then just activate that one).

@suraj_sloth and Gotam talking about #phosh at OOSC (https://oosc-next.vercel.app/):

https://www.youtube.com/watch?v=dDZJ1d-n2xg

@janvlug @devrtz We don't get much feedback from flatpak users (as Chatty is usually recent in most distros) but see e.g. https://gitlab.gnome.org/World/Chatty/-/issues/913 . So in case you try it feedback in that issue we be welcome.

@praveen Might make sense to also update the Phosh screenshots at some point. The ones here are a bit out of date. Let me know when I can help with that.

@liw 3071169

@stefan Via matrix (die Debian Channels sind z.B. gebridged) in Chatty?

@praveen Can we do some sort of "tagging" like in gitlab so there could be "Librem5", "PinePhone" labels to help people figure out if it will help their device?

@praveen Nice initiative and focusing on one distro and UI makes sense (and happy to see #phosh made it in 🙂 ).

At FrOSCon (https://programm.froscon.org/2024/events/3178.html) however we saw (again) that lots of issues affecting
daily drivability for users are device specific (modem data and call stability, gps availability, sensor support, camera sensor support). I thus wonder if the scope is still too broad and one should look at "per device" funds as well?

While memory is still fresh I summed up my gist from helping to organize/run this years #FOSSOnMobile devroom at #FrOSCon: (https://honk.sigxcpu.org/con/A_short_look_back_at_the_FOSS_on_Mobile_Devroom_at_FrOSCon_2024.html) in the hope that we can do another one next year (and there'd be people interested to participate again).

#LinuxMobile

Thanks! Hopefully we'll have a devroom again next year.

@linmob @linuxphoneapps just noticed there's a @1peter10 account too which would have been the better @-mention of the presenter, sorry.