Sebastian Krzyszkowiak @dos@librem.one

@nina_kali_nina @elly @Remiberry My phone has 3GB RAM and while I do sometimes think it would be handy to have a bit more, it's usually triggered by things like compiling Rust codebases on it, so it's not exactly an essential need 😂

@okennedy Not sure what "it" you refer to, but if irregular red LED blinking stops once you set a lower input current limit in sysfs manually then yes, that's what it is.

This is now going to happen automatically using BQ25895's ICO feature, which apparently works better when VINDPM is set correctly 😜

The #Librem5 has properly detected chargers using BC1.2, Type-C and PD signaling for years now, but it struggled with sources that couldn't actually provide the advertised current (which could happen with buggy chargers/docks, broken or poorly made cables etc.). It would attempt to draw power, drop below voltage threshold, disconnect, and then do it all again once the voltage went back up to a good level in an endless loop. Good news: this behavior is about to be gone 😁 #mobilelinux #linuxmobile

@cassidy @firefoxnightly Something like... XULRunner? 🤔

@schratze musical creatures 🎶 😺

@valpackett > making sure wakeups don't turn the display on xD

That'll get us, like, 90% there usability-wise already 😜 AFAIR gnome-settings-daemon simply turns it on unconditionally on resume from system suspend.

It's nothing new and has even been proposed for upstreaming years ago, but I wasn't aware until now. Apparently it broke some iMX7 platforms, but could still be something worth having downstream.

NXP has published their 6.18-based kernel tree and while browsing it I have noticed that they apparently found a way to support custom horizontal strides with mxsfb (by using some undocumented leftover IP for EPDC panels that imx8mq doesn't support). This may be interesting as it potentially opens a way to use linear PE in #etnaviv with the #Librem5's internal screen, so the GPU could render directly to the scanout surface without having to resolve its tiled buffer to linear afterwards. #imx8mq

@seachdamh @wariat @mason @emill1984 U mnie nie, nano nie ma 😥

@emill1984 @wariat Ktoś Ci sprzedał wybrakowanego KWrite'a/Kate'a, zażądałbym zwrotu pieniędzy.

@Oleksii Made me check when I flashed PureOS on my phone. Looks like it's a bit older 😁

2021-02-11 08:58:42.687823321 +0100

@mrlakes Recent versions of GNOME Online Accounts have generic CalDAV support; older ones can be made to work by choosing the Nextcloud option: https://semanticlab.net/sysadmin/linux/Gnome-Todo-and-CalDAV-servers/

@frandavid100

@frandavid100 This has worked for me for years and still does.

Despite of its enormous codebase it wasn't that hard to look around and find relevant stuff - the GTK layer is fairly thin. The hardest part was to compile it, but running distcc on a Steam Deck sped it up well 😄

We still need to:
- emit pointercancel when the browser takes the touch gesture over
- not change scrolling targets during scrolling just because a new one "flew" onto the cursor/finger
- have some thresholds to differentiate between vertical and horizontal scrolling

All my #WebKit merge requests have been merged. Now #WebKitGTK supports touch PointerEvent API, touch point coordinates are fractional, synthesized mouse events are unbroken and both WebKitGTK and WPE WebKit handle pointer capture and release according to the spec. This should considerably improve compatibility of #Epiphany (#GNOME Web) with touch interfaces.

There are still some more things to fix in there, maybe someone in #mobilelinux #linuxmobile community would like to give it a try?

@datenwolf Fun fact - you can write a protocol to offload graphics operations over Wayland too, and you'll instantly get about the same adoption of it as that part of X11 has today 😁

With things like QtQuick being basically a big scene-graph canvas to draw you won't get much further than that anyway.

@datenwolf @newbyte @mirabilos @jzb The truth is - these toolkits used to work the way you describe and they have been reworked since for good reasons, which is why we can now do or think about doing things like multi-GPU with GPU hot-(un)plug, split render/display nodes, modifiers, zero-copy, desktop effects (incl. accessibility ones) and lots of other stuff that software from 90s simply did not have to concern itself with.

@datenwolf @newbyte @mirabilos @jzb So now you're saying that to reap the benefits of "old-school graphics system" you need to constrain yourself to very specific bits of software from the past? How is that different to this theoretical non-composited Wayland setup, which could actually be maintainable if anyone cared? What happened to "give the benefits to all applications, without extra effort"? 🤔