@letterus @agx One more thing: a possible feature that could be added to phoc to make platforms like PinePhone faster even with software rendering is to render everything in smaller resolution and then upscale while displaying. This will of course make everything blurry or pixelated, but should make it very snappy even with underpowered hardware.
@letterus @agx Possibly. GTK4's GPU rendering isn't well optimized for mobile platforms, but it already got pretty usable in GTK 4.2. There will still be some work needed in order to keep slow GPU-rendered clients from making the whole compositor slow (like https://github.com/swaywm/wlroots/issues/3026), so there's no single silver bullet, but we'll get there eventually ;)
@letterus @agx Most of apps you're likely to run under phosh (and also phosh itself) is still based on GTK3, and GTK3 is purely software rendered - PinePhone's slow memory bandwidth is a huge bottleneck there. It is noticeably snappier on the Librem 5 since its RAM is significantly faster.
One thing to check is whether arm64 optimizations are enabled in pixman build used by your distro, there is a patch that's not merged upstream that can make it a bit faster overall.
phosh 0.13.0 is out 🚀 :
https://gitlab.gnome.org/World/Phosh/phosh/-/tags/v0.13.0
Improved call handling when shell is locked, lockscreen notifications, high contrast theme support and much more. Check the release notes.
@gamey @maximiliano No way, Megapixels reaches directly to V4L2 media request API, which is as low-level as it gets (maybe aside of reimplementing the drivers in user space)
@maximiliano > ASHPD
I *knew* that this acronym feels weirdly familiar, but I'm a bit ashamed that I didn't realize why until I read the README.
@chrichri I wish! I have no idea how to build it with F-Droid's build system (it's a cmake project that embeds gradle). It is in my own repo though: https://dosowisko.net/fdroid/repo/
@ssafar You are about 11 years late, mate: https://github.com/paulfertser/fso-el
@ruff It doesn't even request any permissions. It's an Allegro game - one big OpenGL context, audio output, touch input and just enough Java glue to get multiplatform C code going, there's nothing more there.
@the_tech_beast It does not - it was just the rendering of system UI etc.
The whole CPU usage "test" wasn't very useful since it mostly showed how much CPU the terminal uses to render changing htop content (and terminals that do their drawing on the GPU will obviously show less CPU usage there)
@linmob This one and Navit were a go-to navigation apps on the N900 :)
The GNOME Mobile Q&A starts in half an hour (14:00 UTC)!
We'll have many of the core people behind various pieces of the stack, including @agx, @KekunPlazas, @exalm, @dos, and myself.
Join here: https://meet.gnome.org/ale-u66-xf7-kic
If you're interested in GNOME Mobile development, adaptive apps, and the future of the GNOME platform join our virtual Q&A later this week!
We'll have many of the core people behind various pieces of the stack, including @agx, @KekunPlazas, @exalm, @dos, and myself.
Thursday, July 29
14:00 UTC
meet.gnome.org/ale-z3p-pjq-kkn
phosh 0.12.1 is out 🚀 : https://source.puri.sm/Librem5/phosh/-/releases/v0.12.1
This mostly brings the bug fixes by @dos and yours truly into a release, updates translations and also no longer claims the accelerometer when automatic rotation is off (making iio-sensor-proxy sleep a lot more, helps 🔋) .
Just published Google lawsuit evidence indicates that like always retained users' location data, even if disabled in user interface, to the extent that its own employees flashed LineageOS on their phones to avoid tracking. Full thread on https://twitter.com/jason_kint/status/1398353211220807682
Hi, I'm dos. ~80 silly FLOSS games, open smartphones, terrible music. 50% of @holypangolin; 100% of dosowisko.net. he/him/any. I don't receive DMs.