Sebastian Krzyszkowiak @dos@librem.one

@mrlakes Calls and SMS are actually what will wake it up just fine! VoIP, IM and other Internet-based stuff won't though (and whether alarms do depends on the OS). The LED indicator will at the moment stay dark while in suspend too.

When suspended, it lasts about 20-22 hours with the modem on.

@mrlakes That's without suspend, I assume? I'd expect it to still have more than 50% left if it was sleeping most of that time.

@wolnoscwkieszeni @mat_hmm Co prawda nie używam pmOS, ale moim daily driverem jest Librem 5 z PureOSem już od kilku lat, więc z tym "nie nadawaniem się" bym nie przesadzał. Może się nie nadaje gdy oczekujesz, że wszystko będzie działać na losowym sprzęcie przy którym sobie z nudów dłubie jedna osoba po kilka godzin w miesiącu 😜

@vincent Though we may consider configuring it out-of-spec anyway if it ends up helping with ERR050384.

@vincent See https://social.librem.one/@dos/115952734691702400

@okias Nice, I was looking for a GNOME equivalent of KDE Itinerary recently but did not stumble upon this.

@Jamoteusz No to jest na komp, ale na moim kompie nie używam GNOME.

@Jamoteusz Ja na telefonie używam Drawing: https://maoschanz.github.io/drawing/

@gitranks I still don't know what these stars are supposed to mean 🤨

@vincent Incidentally, I think attempting to apply the feedback from the gauge series would be a good start! It's self-contained and I haven't touched it for a while so we wouldn't step on each other's feet, as I've been reworking some other stuff for mainlining recently too.

The TPS65982 stuff is very entangled with other drivers, firmware config etc. so I'd leave that one for later.

@vincent Similar story with fuel gauge patches, they need some changes: https://lore.kernel.org/lkml/20220318001048.20922-1-sebastian.krzyszkowiak@puri.sm/

Generally, aside of really recent stuff, things that stay downstream usually have a reason to stay there. Some reasons are easier to get rid of than others though, so I can help point you in their direction.

@vincent These events aren't handled in the upstream driver, so I don't think this patch makes sense there without reworking and upstreaming other patches as well. Also, it's already there in the 6.18 tree: https://source.puri.sm/sebastian.krzyszkowiak/linux-next/-/commit/a2b7faa8e47673f18a002f07517e218cbe39b6a1

There's still feedback to apply from https://lore.kernel.org/lkml/20220317154518.4082046-1-sebastian.krzyszkowiak@puri.sm/ that I have never got around to do so far.

That's why I asked to coordinate ;)

@vincent Yes, feel free to ping me there.

Regarding USB there is https://lore.kernel.org/all/20260316-eth-null-deref-v1-1-07005f33be85@google.com/ - in next but hasn't reached stable trees yet, so you may be missing that.

@florekm Kwestia dokładności licznika Coulomba.

@0xabad1dea There are five nines on the screenshot, I don't see any problem.

Protip: GTK can do hardware video acceleration using V4L2 on e.g. #Librem5, but only if you let it.

Adding "--device=all" to overrides lets it be used in #Flatpak apps that don't specify it in their permissions already, such as #Tuba.

https://github.com/flatpak/flatpak/issues/5524

#mobilelinux #linuxmobile

@opensourceopenmind You'd have to ask Broadmobi to fix that one. We can only consider various workarounds, each with different tradeoffs - but since it's modular, replacing the modem is also on the table.