Show more

@turbobob

If you think it's a good idea why not just organize a crowdfunding instead of pushing this in the direction of the Foss Mobile WG?

@FreePietje @debacle @mobian

@awai @gecko @tootbrute @KinmenRisingProject @purism I think this was a bit of a "misunderstanding" between the card vendor and Purism who will look into upstreaming the missing driver bits 😄 (fueled by a takeover of the card vendor by another company)

@zachdecook @cjr @linmob @purism I think there's the wrong term being used in purism's post.

I *think* what is meant is "apps that can connect to your own, self hosted services" rather than forcing you to use "centralized" services from your phone vendor.

I never get tired of posting my phone running on the latest stable kernel. Props to @purism for doing all the hard work to maintain the #librem5 kernel and making it easy for @mobian to use it!

Ever wondered how to *really* declare device compatibility in AppStream MetaInfo files for your app?
I wrote a short-ish blogpost about that!
Things will also become much nicer to use with AppStream 1.0 soon, with more validation and helper tools 🙂
blog.tenstral.net/2023/10/how- #freedesktop #appstream #linux

@ralen @purism I'd say Librem 5 and PinePhone (classic) have the best hw support atm as haptics, leds, cameras, phone calls, etc. all works.

Oneplus 6T will work (and is fast) but has limitations (e.g. no camera support yet, last time I checked audio was flaky).

This is not so much a phosh thing but rather if the hw is supported by Linux at all atm.

So it depends a bit if you want it for tinkering or want it for daily use.

@betaphish @purism The favorite Linux distribution of your choice (Debian, Mobian, pmOS, PureOS, Fedora) will ship it. Install that and you should have an option to select phosh. Supported devices can be found for e.g. pmOS and Mobian at wiki.postmarketos.org/wiki/Dev and wiki.debian.org/Mobian/Devices

@rmader @mort @cassidy @cas
whatever (hopefully) ends up in the kernel we need a way to provide the information via userspace too for
- overrides / non dt-devices
- tests (where you e.g. want to check phosh's layouting for different notch positions)

That's why it ended up in gmobile (gitlab.gnome.org/World/Phosh/g). If it comes from DT or viia drm properties too we'll pick it up there as well for compositors and shells to make use of it.

@goatwildernesscollective @eliasr It should be finished in a matter of seconds. Note that you're installing unstable software on your device for *development* purposes.
If you feel uncomfortable debugging and fixing issues I'd recommend to stick to the released versions. Like Debian sid it usually is pretty stable but it *can* break on you.

This weeks update mentions the Q3 LinuxPhoneApp update which I had missed before: linuxphoneapps.org/blog/new-li

Adding new apps to LinuxPhoneApp is easy and can be done by everyone. It's a good chance to help to improve the ecosystem. 📱

I've added gitlab.gnome.org/World/Phosh/p 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).

For the moment having not placing UI elements in the notch area (like the clock) already helps a lot.

We could have the compositor () just avoid the notch but we want the app to have a say there (as depending on screen content) it might want to use that area.

@cassidy @mort When running just add the notch info to and you're done.

For fullscreen apps this needs Wayland protocol support. This is work in progress (but the compositor already uses the same info).

A gnome-shell extension could just pick up the same info.

See phosh.mobi/posts/notch-support

@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).

Show more
image/svg+xml Librem Chat image/svg+xml