Weekly GNU-like #MobileLinux Update (40/2023): #Phosh 0.32.0, #UbuntuTouch Q&A, #SailfishOS Community News and more!
@rmader @mort @cassidy It's not in device tree yet https://lore.kernel.org/dri-devel/f8747f99-0695-5be0-841f-4f72ba5d5da3@connolly.tech/
I've added https://gitlab.gnome.org/World/Phosh/phoc/-/issues/341 as that looks like a simple thing to add (and we have the information in the compositor already to draw the notch area for debugging purposes).
@kosmosghost @purism Phosh is using a lot of GNOME technologies and we consider us part of the GNOME community/ecosystem but phosh doesn't use gnome-shell so its extensions won't work. There's extension points for e.g. lockscreen plugins though (and more planned for e.g. quick settings).
phosh 0.32.0 is out 🚀📱:
More fixes in #phosh and #phoc ➕ allows to reorder lock screen plugins (thanks gauthamx@mastodon.world) ➕ improvements in phosh-osk-stub's virtual-keyboard mode in non US layouts (e.g. for electron apps) and initial #varnam support for Malayalam.
Check out the full release notes at https://phosh.mobi/releases/rel-0.32.0/
#librem5 @purism #gnome #linux #mobile #gtk #LinuxMobile #MobileLinux
@QuadRadical in my simplistic world view phosh is part of the gnome mobile effort. Nitpicking aside: If you mean if it also runs under the gnome-shell fork for mobile: it should, it's a regular GTK/adwaita app.
Sources are at https://gitlab.gnome.org/guidog/phosh-ev/
Next thing needed is a "stop charging" button as some charging stations don't allow for that either 😞 . The data leaking involved here is also concerning but as it is sent out no matter what, let's at least make it usable via #FreeSoftware too.
Had the need to charge an all electric Kia recently and guess what: both the charging stations app and the vendor's app are proprietary so how would I know when charging finished?
Turns out people around #HomeAssistant figured out the vendor API so I could use that to have a small app to monitor the charging status on my #Librem5 running #phosh
@krzym @devrtz @copyrights @zeroday Librem 5 ist locker schnell genug für Waydroid, siehe https://forums.puri.sm/t/anyone-successfully-run-waydroid-on-librem-5/16757/130
Problem bei Waydroid ist eher:
- derzeit generell kein Bluetooth support
- die proprietären Apps laufen nicht auf gerooteteten Telefonen
Von daher ist der Anwendungsfall in er Praxis stark eingeschränkt.
I had already disabled automatic HighContrast in #phosh but the last days were so ☀️ that I flipped it on again.
Thankfully this doesn't need any `gsettings set sm.puri.phosh automatic-high-contrast true` anymore but can be done conveniently in the mobile-setting's sensor panel added by @devrtz in 0.29.0.
#ExtremeProgramming principle: Accepted Responsibility
"Responsibility cannot be assigned; it can only be accepted. If someone tries to give you responsibility, only you can decide if you are responsible or if you aren’t."
Beck, Kent; Andres, Cynthia. Extreme Programming Explained: Embrace Change (p. 63).
AKA why developers/engineers should be signing up for work OVER being assigned work
@eliasr I assume at a later point there will be calls for upgrade and alpha / beta testing.
@eliasr You can check the issues tagged crimson in PureOS bug tracker and see if something sparks your interest but I'd say most things need a spare device to test on (there's little things left that can sensibly be done in e.g. a VM).
@eliasr I don't think anybody is doing the backporting to byzantium atm. Crimson has recent packages (but I wouldn't recommend Crimson for every day phone usage yet). For experiments `l5-fetch-next phosh` gives you current phosh (+next patches) on byzantium (that's what I'm using to run recent phosh on my daily device).