Lineage OS

879 readers

1 users here now

Lineage OS

lineageos.org | Wiki

GitHub

IRC | Unofficial Matrix room | Discord

Twitter | Facebook

Other LineageOS communities on Lemmy

founded 3 years ago

MODERATORS

testman@lemmy.ml

Is there a good starting guide to build LOS for an unsupported phone? (lemmy.ml)

submitted 8 months ago by velox_vulnus@lemmy.ml to c/lineageos@lemmy.ml

9 comments fedilink hide all child comments

I have a realme 5 Pro. Honestly, the current state of officially and unofficially supported custom ROM for rmx1971 suck. PixelExperience was the last decent half-decent ROM for my device - it had some battery issues. DerpFest, crDroid and EvolutionX are all terrible for me - because I never wanted those "fancy" settings in the first place.

Right now, I'm on DerpFest, and honestly, it's terrible. The desktop and wallpaper engine is broken, the theming is all over the place and some of the contents are out of the screen. Honestly, I want something that is as close to the stock ROM, is lightweight, and gives life to older devices. LOS seems to be a good ROM, at least from the YouTube videos I've seen.

How should I go about creating a build for my device? And what should I care about while building? And how can I make my build official later on? What about the kernel? Can it be updated beyond the version that's it at right now?

top 9 comments

sorted by: hot top controversial new old

[–] j4k3@lemmy.world 7 points 8 months ago (1 children)

Kernels for android are supplied by google in a stripped down form. The manufacturer supplies the kernel modules in binary form at the last possible moment. Without the source code for those binaries, you're working backwards trying to build software dependencies for the orphaned kernel at the time the last available kernel was built by someone with the binary. It is a unique mess for every model of a device. Orphan kernels are the mechanism used to steal ownership and deprecate devices.

[–] possiblylinux127@lemmy.zip 2 points 8 months ago

Just a quick clarification, it is the manufacturer of the platform (Soc) that is responsible for the terrible code. Blame Qualcomm

[–] LiveLM@lemmy.zip 2 points 8 months ago* (last edited 8 months ago) (1 children)

The fact that there's other custom ROMs already available for the device is a great starting point. I'd try asking the maintainers of the current ROMs for some pointers.

[–] velox_vulnus@lemmy.ml 4 points 8 months ago* (last edited 8 months ago) (2 children)

I wish I wasn't exaggerating, but they're (folks in Telegram for my particular device) not the most friendly bunch. This is why I was looking for a generic tutorial to try my own hands on.

[–] LiveLM@lemmy.zip 3 points 8 months ago

Huh, I wish I could say your experience wasn't the norm :/

[–] 7heo@lemmy.ml 2 points 8 months ago

Yeah, their friendliness is the only reason I have not tried once in over a decade.

Toxicity kills software.

[–] possiblylinux127@lemmy.zip 2 points 8 months ago (1 children)

What kernel version is it on?

[–] velox_vulnus@lemmy.ml 2 points 8 months ago (1 children)

It's somewhere in the 4.9.x range.

[–] possiblylinux127@lemmy.zip 1 points 8 months ago

You shouldn't have any kernel issues then