@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.
As announced earlier, I started collecting important missing features for daily driving a gnu/linux phone.
You can see the currently identified list here,
https://codema.in/g/D8TO7J5c/tags/librem5 please contribute more.
Use GNU/Linux (not android) as a daily driver already?
Have you tried using and given up?
Are you keen to switch away from #Android to a more sustainable approach to developing an operating system, where collecting maximum personal data is not its driving philosophy?
I've lost my PinePower (https://pine64eu.com/product/pinepower-destkop/) at #FrOSCon2024
It was last seen around around 18:00 at the FOSS on Mobile booth.
lost+found hasn't turned anything up yet.
The spot on my desk where it used to sit feels very empty now,
so please reach out if you stumble upon it ;)
@liw 3071169
My talk "eSIM management on Qualcomm phones" from Sunday at #FrOSCon is now subtitled and ready to watch on my YouTube channel! https://www.youtube.com/watch?v=L8WyIrwg14E
I hope you enjoy and learn something!
@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).
Did you miss a talk at #FrOSCon? Some recordings are already available here: https://media.ccc.de/c/froscon2024 with more to follow
#froscon2024 #froscon19
@linmob @linuxphoneapps just noticed there's a @1peter10 account too which would have been the better @-mention of the presenter, sorry.
Why and how to teach students about F(L)OSS? The recordings of my #FroSCOn talk about this topic are online now:
Abstract and slides live here:
https://programm.froscon.org/2024/events/3130.html
Again, many thanks to all who made #FrOSCon19 possible!
Yesterday I had the chance to give a short #phosh status update in the FOSS on Mobile devroom at #FrOSCon: https://programm.froscon.org/2024/events/3153.html
Slides are at: https://programm.froscon.org/2024/system/event_attachments/attachments/000/000/830/original/phosh-status.pdf
@tzafrir The PinePhone arrived. Thanks a lot!