Sebastian Krzyszkowiak @dos@librem.one

@harshad Seems like I've been living your younger self's dream my whole life; first with Neo Freerunner, then Nokia N900 and now Librem 5 😄

I don't understand why people still call Android or iOS phones "smartphones". The tech's baseline has moved forward (even basic "feature phones" do stuff like Web browsing these days after all), but in its essence this market segment is more similar to old cameraphones rather than PDAs.

@silmeth https://github.com/Bismuth-Forge/bismuth/pull/490 ?

@silmeth Just try to find the reason, KWin scripting is pretty straightforward.

@silmeth Even after years of using it I find Librem 5's 5.7" screen to be tad too big already, and PinePhone's 5.9" is stepping one foot into "comically big" 😫

TIL: It's surprisingly hard to design a board for such a simple schematic that will be cheap to manufacture 😫

@blake There is no separate "mobile version" of PureOS - it's the same OS as what runs on laptops, built from the same repos (early versions had a repo overlay, but that's gone for years now). And while we often worked with and do love our pmOS pals (there's plenty of cross-pollination between various distros there on multiple levels), I really don't think it's a fair characterization of how the OS was built 😂

@blake > a variant of PureOS, which is itself built on Ubuntu and PostmarketOS (which makes Linux available for phones)

Neither of that is true; PureOS is built on Debian.

@SceNtriC Przypomniało mi się, jak wcześniej tego samego dnia co grali w Opolu prezentowali klasyki Perfectu we Wrocławiu 😁
https://youtube.com/watch?v=EktMCAZPLmQ

@gnuntoo @thegnuguy In the strict sense: no, not really. However, there's nothing that would prevent efficient periodic wake-ups to check for those - but we need to build a proper infrastructure for that first and then use it across apps.

Had to update my userChrome.css for the new version of #Firefox a bit - the necessary changes turned out to be trivial, but it still managed to nerd-snipe me into making the whole thing a bit more robust 😅

@lina > Kao the Kangaroo: Round 2

Ah, I see you are a person of culture as well.

@greytheearthling It's not "just the battery", but you may be able to boot it with a charged one. Something's physically wrong with the power path, the red LED would blink without any assistance from software or even CPU if it was actually getting powered.

The "codes" are chips, the first one is USB-C controller and the second is battery charger. Either one of them is broken, or the USB-C socket went bad. There's still a chance the battery power path is intact.

@greytheearthling Check the voltage on the battery +/- pads, if it's flat then maybe it could still boot once you get it charged externally - but I'm afraid something is really broken there, either TPS65982 or BQ25895 :/

@greytheearthling Take the battery out and try plugging it in with various power sources (USB-C PD, USB-A to C cable) and both USB-C plug orientations. Wait a few seconds after plugging in and look for any signs of life from the indicator LED.

@sigmasternchen @ptrc @psykose Both are used in different contexts (contributing patches vs. merging between maintainer trees)

@sigmasternchen @ptrc @psykose ...and that's exactly how pull requests are being used on Linux mailing lists.

@thegnuguy You can use system suspend which makes it last about 20 hours (at expense of not waking up on network events such as IM messages; only calls and SMS).