Unofficial builds vs. /e/OS maintenance

[piero]

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

i think you can help there :

@piero

As developpement on some devices has been dropped,

the /e/ management decided to qualify those dropped devices as “legacy devices”.
But since the latest builds released by the /e/foundation for “legacy devices” are currently unavailables,

.

my intentions here are :

1. collecting available dev builds from users personnal archives, contact me if you still have have some old builds from /e/ stored
   *. on your PC ! in your Download folder, or into the snap easy-installer folder
   *. on your phone ! in your Dowload folder, or in the /data/lineageos_updates location, (boot to TWRP to find them even temporary : fastboot boot twrp.img or use a file manager with root permission, or use adb shell root through recovery with adb pull command)
2. initiate a collection here !
   (one can post it using https://upload.disroot.org/, and i will upload it to the /e/OS Legacy Builds server thanks to the sourceforge project.
3. make LEGACY builds for missing devices where UNOFFICIAL builds don’t already exist or are outdated… (help is welcome as it take hours…)

with your powerfull machine :

@piero

on my poor 30€ computer ( an i5(2500) 4-core 3,300 Ghz, with 16 Gb RAM DDR3 1333 Mhz and SATA 3 Gbit/s BUS ) it took 4h00 to 5h30 from the first build of a serie of devices sharing the same kernel, then 1h00 to 2h00 for the others builds of the serie…

@piero

now that you builded for a5y17lte, your build for a7y17lte will take 25% of time to build compared to the first one…

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