Probably some use cases for “regular” users. Someone mentioned music production, though that’s probably more professional than hobby.

To my understanding, you mostly need real time performance for specialty cases where timing is absolutely critical. So I guess if you were building custom drones or custom control boards for drones, you could use real time Linux for that now since the timing could be guaranteed.

Doesn’t say, but I am curious. They said their workarounds broke other workarounds which caused a lot of implementation delay, but I’m not sure what the actual compromise was to address all that.

Answer probably lies somewhere in the kernel maintainer’s mailing list, I’d imagine. Just not equipped to search for it right at the moment.

Security tip: Never post your home address on social media.

Lol, yeah.

The Slashdot article that led me to the original was slanted to say “legacy IT” equipment was the cause and had the distinct subtext that had they been using cloud for everything, they would have been fine.

Nope, this is 100% failure to provision and secure equipment correctly. And cloud doesn’t mean anything for security, especially given how many sensitive files have been left in wide-open, publicly accessible S3 buckets.

Further, while only licensed device makers are permitted to modify Google’s AndroidTV, any device maker is free to make changes to open source versions. That leaves open the possibility that the devices were infected in the supply chain and were already compromised by the time they were purchased by the end user.

It’s ArsTechnica, so I wouldn’t think they’re intentionally spreading FUD around FOSS, but that bit did live a bad taste in my mouth.

I realize it said “major Android skins” but really wish there would have been some love shown to LineageOS’s AOSP + Trebuchet.

Most of the rooting processes these days is done via unlocking the bootloader and patching the boot image with Magisk. I’ve never had luck with any of the “one click” root tools, and they just seem to install junk on the device. So I would avoid those even as a last resort.

I would start with the Motorola e4 you have there and seeing if you’re even able to unlock the bootloader on it. If so, you will have your foot in the door, so to speak, and can at least try your luck luck with a GSI version of a newer Android.

If any of them are retail models (ones that were sold through a carrier), they may not be bootloader unlockable without jumping through a lot of hoops. That usually involves converting it to the OEM firmware and then enabling bootloader unlock (varies by device/manufacturer).

The Samsung Galaxy J7 had previous support for Lineage, but not that exact model number. You may still find the instructions useful (perhaps supplement those with XDA) and use them as a starting point. That might be a carrier model, and perhaps you can convert it to an OEM model (which have different model numbers) and go from there.

TIL HTC still makes phones.

Used to love their devices then they just kind of…disappeared.

Thanks. (hands you two slips of gold-pressed latinum). I haven’t had a chance to look into that yet (been playing around with Kodi and the Emby add-on), so you may have saved me some time/research effort.

Yeah, I think I just tried the older one “EmbyCon” and it just loads an empty repo.

“Emby for Kodo NextGen” seems to be the “new” one and is currently syncing my library on my test box.

Yeah, Kodi seems to be the leading contender.

With the emby for Kodi addon

How old is that add-on and howe well does it work? I was exploring Kodi at one point in the past (never got past planning stage) and was looking to see if there was a plugin to integrate Emby but couldn’t find one (there’s nothing really special about it’s streams, they just need to be requested the right way).

I may give that a try. I do like the idea of a unified interface versus a controller for the UI and a separate controller/webapp for Emby.

Yeah, I currently boot straight into OpenBox -> Firefox Fullscreen -> Emby right now, and everything’s controlled from a second Emby session on my phone. I’d keep that, but I’d also want to be able to easily navigate the “desktop” part. Someone else mentioned BigScreen, but I’ve never had a good experience with KDE in general, so I’m hesitant. May still try it out, though.

I’ve used Plasma off and on for years, and every time I just regretted it. Can’t point to one particular issue that ruined it, it was just a lot of little annoyances over a long period of time (mostly with multi-monitor setup and the panels glitching out all the time). So “BugScreen” sounds about right, lol.

That said, this would be more of an “appliance” configuration so I may give it a shot and keep Kodi as a fallback.

Looks like Kodi it is, lol. Which is fine, I guess. I should be able to customize it and remove the unneeded options.

My current setup only really runs Emby and Snapcast, so I haven’t had to deal with any kind of launcher. It just boots into Openbox, launches FF full screen, and loads Emby. I’m aiming to add some new features to the new build since it’s more capable than the old Core2 Duo laptop I dug out of the basement lol.

If you are still experiencing issues, consider using Organic Maps in the meantime 😀

Made the switch a few weeks ago after learning about it here, and I don’t think I could ever go back to Google Maps. Street and satellite view are nice, but I am quickly realizing how much I don’t really need them (if OM has sat view, I haven’t found the option to enable/download those layers). It’s just so nice that the actual map part of the software is the focus rather than all the clutter Google’s thrown into theirs

!meshtastic@mander.xyz

If it ever happens, absolutely :)

Oh, yeah, I just like the T-Deck form factor. Was going to use Meshtastic as the base but the ESP32 itself would be the messenger (e.g. wouldn’t need the phone).

As long as it’ll still accept a charge and isn’t a spicy pillow, yeah, absolutely. I’ve never had great luck soldering onto those little pads but it’s certainly doable (though I’ll admit my soldering skills aren’t the greatest).

I’ve been wanting to play with Meshtastic for a while and was looking at using something like the LilyGo T-Deck with its blackberry-like keyboard to make cool little off-grid messengers for camping/hiking trips.

Is this for your Meshtastic board (from your other post)? If so, that’s a great up-cycle and should work well with the onboard charging.

I have a few I’ve saved for similar purpose, but I’m not sure about shipping them.

Like someone else said maybe check with vape shops / dispensaries in your area to see if they collect them for recycling.