Conversation
Notices
-
Embed this notice
@ezio I did that for a while years ago, back when it was CyanogenMod. :blobfoxgoogly:
-
Embed this notice
@tk @ezio totally forgot it was called CyanogenMod, that thing sucked so bad lol all the Android ROMs back then were buggy as hell with weird issues like cameras never working because of weird proprietary drivers, core apps just crashing for unknown reasons, etc.
-
Embed this notice
@ezio Looks like my current phone can run LineageOS. :blobfoxowo:
-
Embed this notice
@feld @ezio @tk they still have tons of issues, mostly thanks to proprietary apps (especially banking) doing all sorts of checks that won't work on regular LineageOS and other Roms by default both due to the developers of the Roms being fags as well as the schizophrenic apps.
One example from the ROM side:
LineageOS tags all their builds as debug builds instead of release (as per the screenshot included of my outdated phone) which makes it not trustworthy to the apps.
Apps side:
They will try their best to poke around and make sure you don't have root access, especially through regular boot image patching such as done with Magisk. One of the ways around this is to literally patch Android root access into your kernel with KernelSU.
-
Embed this notice
@feld @ezio @tk forgot to mention, the fix to the LineageOS thing is, just like the root one, building the entire thing from source yourself just to remove the gay debug tag in the build name. Just the source code itself is 300G. The build *will* crash if you don't have at least 32GB of RAM and equal amounts of swap.
-
Embed this notice
@getimiskon @ezio @tk phones suck anyway
-
Embed this notice
@tk i've been doing that since that time as well (back in 2016). Missing those times, with its mods and all that stuff. Today's lineage os feels kind of locked down imo.
@ezio
-
Embed this notice
@tk @ezio tbh Cyanogenmod was better than LineageOS, far more features
also, Android itself wasn't as dogshit back then