Sebastian Krzyszkowiak @dos@librem.one

@hackaday No movies either, but I do have some live concerts on DVD and I keep a USB drive around to be able to rip whatever lands in my hands 😁

@hackaday Vast majority of the music I usually listen to and plenty enough of yet unread books not to worry about it :)

@opensourceopenmind @bhyoram @chesterdott Right. WebkitGTK did use WPE as well until fairly recently though, but I'm not sure for what exactly.

@bhyoram @opensourceopenmind @chesterdott > Kumo is a UI written around Safari's WebKit browser engine, so they should be comparable in behavior and performance.

So just like Epiphany, which I've been using for years on my phone?

@catsalad IF TRUE

@queserasera ...universal income

@pavel FYI I played a bit with the M4 core in the last days and the obstacles have moved a bit :)

I can make it continue running in suspend now and fixing interrupt issues is just a matter of not registering GPIO interrupt handlers in Zephyr's dt. Now it needs to stop consuming more power than when the system isn't suspended at all 😂

I'm optimistic that it's possible though. There's plenty of things described in AN13400 that we don't do ATM.

@richardwonka @janvlug That claim relates to another (though similar) product, not to the Librem 5.

Me: So, dear GitHub container repository, I need a version of this image from May 2023.

GitHub: Here is the list of 55 tags "published about 2 years ago"!

@pavel You can upload and launch code via remoteproc interface (/sys/class/remoteproc/remoteproc0)

There's an example code that blinks a LED in Zephyr: https://source.puri.sm/angus.ainslie/zephyr/-/tree/librem5

AFAIR the current obstacle to overcome is to make it continue running while suspended. It seems to do some weird things to interrupts too.

That's all I can think of on the spot. Of course there's still the camera and GPU stuff, but these would need their own dedicated threads 😂 Feel free to hit me up if you want to hack on some of these things, I could likely offer some help and guidance.

#mobilelinux #linuxmobile #librem5 #linuxsmartphones

iio-sensor-proxy still needs some work in order to be able to use the compass: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/316

There's also a hall sensor which needs to be exposed to the userspace in some appropriate way: https://source.puri.sm/Librem5/linux/-/merge_requests/638

We're still missing a way to control the notification LED while the phone is suspended. There's a lightweight Cortex-M4 core that can keep running in suspend and some proof-of-concepts have been made to utilize it in the past, but nothing has been properly integrated so far.

The audio codec has a quite powerful DSP that can perform frequency linearisation based on speaker's and microphone's impulse response - but it needs to be fed with configuration parameters.

Speaking of audio, since there are two microphones - one on the top and one of the bottom of the phone, they could be utilized for noise cancellation. Right now only the bottom one is used for calls.

The touchscreen supports a low-power mode in which it can recognize some predefined gestures. It could be used to wake up the phone by, for example, double tapping the screen. Right now it just gets its power shut down as soon as the screen is blanked.

The GNSS module has an internal flash that can be used to autonomously store traces, letting the phone suspend and save plenty of power. It can also wake the phone up with geofencing. Right now you need to configure it manually with NMEA commands though, as there's no high-level infra to use at all.

There's also AGNSS to speed fixes up. I wrote a script to generate almanac/ephemeris data, but you need to run it manually and it could be improved with SBAS and GLONASS: https://source.puri.sm/-/snippets/1207