New blogpost about creating bit-by-bit reproducible images with mkosi(!)
https://vdwaa.nl/mkosi-reproducible-arch-images.html
#archlinux #systemd #mkosi
One thing that bugged me is that we had no way in #phosh to present only the available OSK layouts to the user to pick from. This led to confusion as users configured a layout which then would not be available later on. phosh-osk-stub can now provide that information to mobile settings (and it will be simple to add support for e.g. squeekboard if it dumps out the relevant information).
Thanks to #libadwaita and #GTK4's list models such things are fun to add.
For #Erlang folks, Rebar3 just got version 3.24.0 released, which has some bug fixes, a bunch of internal maintenance, and also turns on rich compiler error messages by default: https://github.com/erlang/rebar3/releases/tag/3.24.0
postmarketOS in 2024-08 --- the next installment of our monthly blog post is out!
Highlights:
* We will move to a self-hosted GitLab instance!
* Thinking about hosting SoC communities there, too
* Pixel 3a has been promoted to community, and it has somewhat working camera
* Firmware compression using zstd
* Proof of concept of VoLTE (4G calls) for SDM845
* PinePhone callaudiod drop-in replacement
* Proper PAM in SSH
* 7 new device ports
* So many events!
https://postmarketos.org/blog/2024/08/25/pmOS-update-2024-08/
llibphosh-rs 0.0.2 is up at https://crates.io/crates/libphosh . Thanks to @me for making it compatible with #phosh 0.41 .
This is hopefully the first release 🐸 can use out of the box.
@agx @suraj_sloth for the lazy, this link with timestamp that takes you directly to Phosh talk :) - https://www.youtube.com/watch?v=dDZJ1d-n2xg&t=6711
(We also have Rudra there)
@suraj_sloth and Gotam talking about #phosh at OOSC (https://oosc-next.vercel.app/):
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 ;)
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!
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
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!