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.
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.
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.
Speaking as an IT professional, unironically
I wish android didnt just forcibly update itself
LineageOS doesn’t just forcibly update itself
Ah dang, regretting buying a unihertz phone now
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.
Jelly Star. Any recs for how to back up my phone?
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.
A Reddit link was detected in your comment. Here are links to the same location on alternative frontends that protect your privacy.
A Reddit link was detected in your comment. Here are links to the same location on alternative frontends that protect your privacy.
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.
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