54
submitted 4 months ago by Owl@hexbear.net to c/technology@hexbear.net

Just because the internet of things was two hype cycles ago doesn't mean we can't still dunk on it.

you are viewing a single comment's thread
view the rest of the comments
[-] CarbonScored@hexbear.net 9 points 4 months ago

Speaking as an IT professional, unironically this

[-] Dessa@hexbear.net 7 points 4 months ago

I wish android didnt just forcibly update itself

[-] sovietknuckles@hexbear.net 5 points 4 months ago

LineageOS doesn't just forcibly update itself

[-] Dessa@hexbear.net 3 points 4 months ago

Ah dang, regretting buying a unihertz phone now

[-] sovietknuckles@hexbear.net 1 points 4 months ago* (last edited 4 months ago)

Which Unihertz phone? People have reported successfully running LineageOS on Jelly Star and Jelly 2. The builds they're using were updated within the past month, and are maintained by a recognized contributor.

Warning: On every device I've installed LineageOS (6 of them so far), I've accidentally soft-bricked it and had to restore it before doing it correctly. So back everything up that you don't want to lose.

[-] Dessa@hexbear.net 2 points 4 months ago

Jelly Star. Any recs for how to back up my phone?

[-] sovietknuckles@hexbear.net 1 points 4 months ago* (last edited 4 months ago)

Probably using TWRP. Note that the backup is only good for before you switch to LineageOS. After you're on LineageOS, you'll need to make a new backup.

[-] HexReplyBot@hexbear.net 1 points 4 months ago

A Reddit link was detected in your comment. Here are links to the same location on alternative frontends that protect your privacy.

[-] HexReplyBot@hexbear.net 1 points 4 months ago

A Reddit link was detected in your comment. Here are links to the same location on alternative frontends that protect your privacy.

[-] hexaflexagonbear@hexbear.net 3 points 4 months ago

We were using a fork we customuzed of an open source package (we will merge our additions but the team wants us to wait until they're done with a major revision). At some point another upstream package made a fundamental change that broke everything. So we learned the hard way to have upper bounds on all required package version numbers lol. That was such a pain to investigate.

[-] CarbonScored@hexbear.net 2 points 4 months ago* (last edited 4 months ago)

Lol, sounds like the work I would do at my job. But absolutely! This is why there should always be a >= and <= version requirement on dependencies.

Dooown with needless updates no-fun-allowed

this post was submitted on 09 Jul 2024
54 points (100.0% liked)

technology

23313 readers
138 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 4 years ago
MODERATORS