Building a5y17lte from docker fails with "Can't detect the android version"

I’m trying to build the Oreo-based version of /e/ using these instructions.

I enter this command:

docker run
-v “/home/rhombus/Documents/Samsung_Galaxy_A5/e_build/src:/srv/src:delegated”
-v “/home/rhombus/Documents/Samsung_Galaxy_A5/e_build/zips:/srv/zips:delegated”
-v “/home/rhombus/Documents/Samsung_Galaxy_A5/e_build/logs:/srv/logs:delegated”
-v “/home/rhombus/Documents/Samsung_Galaxy_A5/e_build/ccache:/srv/ccache:delegated”
-e “BRANCH_NAME=v1-oreo”
-e “DEVICE_LIST=a5y17lte”
-e “CUSTOM_PACKAGES=‘MuPDF GmsCore GsfProxy FakeStore Mail BlissLauncher BlissIconPack MozillaNlpBackend OpenWeatherMapWeatherProvider AccountManager MagicEarth OpenCamera eDrive Weather Notes Tasks NominatimNlpBackend Light DroidGuard OpenKeychain Message Browser BrowserWebView Apps LibreOfficeViewer’”
-e “SIGNATURE_SPOOFING=restricted”
-e “OTA_URL=
-e “REPO=

I immediately get this output:

Set cache size limit to 50.0 GB

[Sun Nov 17 17:19:58 UTC 2019] Branch: v1-oreo
[Sun Nov 17 17:19:58 UTC 2019] Devices: a5y17lte,
[Sun Nov 17 17:19:58 UTC 2019] (Re)initializing branch repository
[Sun Nov 17 17:19:59 UTC 2019] Copying ‘/srv/local_manifests/*.xml’ to ‘.repo/local_manifests/’
[Sun Nov 17 17:19:59 UTC 2019] Use branch lineage-15.1 on
[Sun Nov 17 17:19:59 UTC 2019] Syncing branch repository
sed: can’t read build/core/ No such file or directory
sed: can’t read build/core/ No such file or directory
sed: can’t read build/core/ No such file or directory
[Sun Nov 17 17:19:59 UTC 2019] Can’t detect the android version

I don’t know what name or filesystem space the error is being triggered in, so I don’t know how to start troubleshooting this. Where should I expect to find ‘build/core/’? And where is this sed command being executed?

Also, why is it setting the cache size limit to 50GB when I’ve specified 100G? (I also tried 100GB, no effect).

I know there is already an unofficial build for this (Oreo-based /e/ on Samsung Galaxy A5), but I want to build this myself until there is a community supported version.

Try this way. Your device is unsupported by lineage, that’s why this way fits better

My device IS supported by lineage:

Than try this way. There you can change alot. The cache size for example

Are the oreo sources all still available at lineage git ?

Thanks. Unfortunately that script is for Ubuntu. (I’m running Gentoo).

Is there no generic, distro-independent way to build /e/?

(Really, there should be a community-supported version of /e/ based on Oreo by now…)

It makes no difference, it also works on debian. Remove the first lines and that’s it


It’s los16, that’s pie. You need for oreo los 15.1

There is a branch for 15.1.

Oh, sorry, your are right. There is 15.1

I would use the script and branch 16

So, am I right in suspecting that this docker build approach is broken? So many people have problems with it, I wonder why anyone bothers.

So, Pie. But then I will need a Pie baseband. The phone had Oreo installed on it. I would rather not have to scour the Internet for dodgy ROMs to get it to work.

I’m using always script, becayse I can cange things. I have run a build today for sailfish pie and it works without any error

It’s your decision …

Where do I find the script, exactly? Is it official? Is it in a git repo?

Please see my post 20 minutes before.
You have seen it and you has answered the gentoo comment.

It’s a user script. Not an e-foundation script.

For anybody else who might need it, the script is in a git repo here.

1 Like

That’s the git of the user which has created it. I don’t see a benefit of a script in github. It’s the sane as in forum