Unofficial builds vs. /e/OS maintenance

Hi,

A few days ago I did my first official build of /e/OS compiled from source for my battered Samsung SM-A520F (a5y17lte). A huge leap for myself, a small step for mankind. :slight_smile:

I followed the advice of user rust in this forum (a huge “thank you” note for his precious help) and built the v2.3-r branch of /e/OS.

What does this mean for the future of my unofficial build ? Let’s say I decided to relaunch a build in a couple months. Will the v2.3-r branch have integrated some improvements like bug fixes ? And if so, for how long ?

Cheers,

Niki

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

1 Like

thre will be no change in /e/ R branch anymore…

i think you can help there :

with your powerfull machine :

it can be wrong if you use Docker as i believe it clean builds intermediate elements after each utilisation,
you may have to build straight for multiple device

1 Like

Not v2.3-r that is the last of the line. Android 11 (R) is no longer supported by /e/OS.

When considering what one can build next consult the Release | tags page Tags · e / os / 🚀 Releases · GitLab.

If I search for v1-r it does not appear till page 3 as

v2.3-r
584ffa80 · Update v1-r manifest · 5 months ago

For s, t, u a search of v1-x will show where this tag points when you are planning what tag / branch to use.

But I now see the device tree for a5y17lte does run to Lineage-19 GitHub - LineageOS/android_device_samsung_a5y17lte so you may well be able to try v1-s.

1 Like