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
And as @praveen
said: lots of issues are hardware specific so Phosh will benefit a lot by getting wider hardware support. I'd say the varying support over devices is what hits us the most atm as the experience differs so much.
2/2
We're following the discussions. Phosh has a recommended (codified) set of apps/services we ship by default and we preferably develop for / contribute to. That is unlikely to change based on a poll. It can change based on good arguments so I hope to learn some of those during the ongoing discussions (and also learn about gaps that people are currently bridging with workarounds or that we missed completely so far).
1/2
@fizzo That's related to the way how we currently handle the touch events (so not OP6 specific) so an issue would be helpful.
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.
@arunmani @suraj_sloth Thanks! That didn't work when I posted it as it was a live stream still. Just wanted to update and saw it's already there 🙏
(I also only noticed during the presentation that @rudraps is on stage too)
Too bad this mastodon instance doesn't allow edits: Gotam's fedi handle is @gauthamx
@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)
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.
@suraj_sloth and Gotam talking about #phosh at OOSC (https://oosc-next.vercel.app/):
@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 ;)