fury

joined 1 year ago
[–] fury@lemmy.world 13 points 3 months ago

Give it a few more years. At this rate, by 2028, the entire back of the phone will be camera bump and you'll be able to lay it down on a flat surface at last.

[–] fury@lemmy.world 2 points 3 months ago

I did, and it didn't work either. :(

[–] fury@lemmy.world 3 points 3 months ago (3 children)

I'm looking for one that works well on Android Automotive. So far I couldn't get OsmAnd to show the Android Auto UI on the full OS, or integrate with the home page (split screen music / maps), and none of the others I tried in F-droid worked at all. I need something because I'm tired of using my phone, and I don't have Google services on my tablet (flashed with a custom build of Lineage / Android Automotive OS).

It would be nice to have an open source version of the big screen systems they're putting in the newest cars...

[–] fury@lemmy.world 4 points 3 months ago

Imagine something as outlandish as user serviceable infotainment systems. Like they used to have in the old days. I'm hanging on by a thread to my basic 2014 car which still has a double DIN slot I can put my own system into...some day

[–] fury@lemmy.world 3 points 3 months ago (1 children)

The company that didn't see the 3G sunset coming, I would think. I know auto moves slow, but damn...4G was out for what, 4-5 years before development likely started on the 2019 model year?

[–] fury@lemmy.world 22 points 3 months ago (8 children)

How is the 3G sunset not solvable by just swapping out a modem module for an LTE or 5G one and maybe installing some new modem firmware? A lot of cars are running a Linux kernel under the hood, so I'd think it's pretty well swap and go

[–] fury@lemmy.world 17 points 4 months ago (1 children)

Windows 3.1 did have a BSOD. It wasn't always fatal, you could try to hit enter to go back to Windows, but most of the time it wasn't really recoverable, Windows often wouldn't work right afterwards.

I ran into them all the time in 3.11 on our 486 which had some faulty RAM (the BSOD would even be scrambled). If we could get back to Windows after that, it'd just be in a zombie state where moving the mouse around would paint stuff over whatever was left on screen, and wouldn't respond to clicks or keypresses.

Fun times.

[–] fury@lemmy.world 21 points 4 months ago (1 children)

Regrets aplenty after some of the things I've drank, but none of them are about Debian.

[–] fury@lemmy.world 58 points 5 months ago (8 children)

How do these things not have unbrickable A/B firmware partitions by now? Even I have that on a $2 microcontroller. Self-test doesn't pass after an update? Instant automatic rollback to the previous working partition.

[–] fury@lemmy.world 13 points 6 months ago (1 children)

I'd love to comply, but unfortunately the last time I tried Windows 11, my Ethernet and WiFi quit working and I had to roll back ¯\_(ツ)_/¯ how do you screw up something as basic and necessary as the internet connection?

[–] fury@lemmy.world 3 points 8 months ago

A little slower by today's standards, but if your needs are light, it'll do the job. Keep in mind it only has a gigglebyte of RAM, so its capacity for running things may be limited, especially as docker applications go (since they bring a copy of each dependency). You won't be able to run something as large as GitLab or Nextcloud, but a smattering of small apps should be within its capabilities

[–] fury@lemmy.world 4 points 8 months ago (2 children)

The thing with using the "latest" tag is you might get lucky and nothing bad happens (the apps are pretty stable, fault tolerant, and/or backward compatible), but you also might get unlucky and a container update does break something (think a 1.x going to 2.x one day). Without pinning the container to a specific version, you might have an outage suddenly due to that container becoming incompatible with one of your other applications. I've seen this happen a number of times. One example is a frontend (UI) container that updates to no longer be compatible with older versions of the backend and crashes as a result.

If all your apps are pretty much standalone and you trust them to update properly every time a new version of the container is downloaded, then you may never run into the problems that make people say "never use latest". But just keep an eye out for something like that to happen at some point. You'll save yourself some time if you have records of what versions are running when everything's working, and take regular backups of all their data.

view more: next ›