/e/OS on Samsung Galaxy J5 2017

What’s wrong with the roomservice.xml I provided ? It doesn’t work ?

Yours not. For lineageos 16 I do need to change 15.1 everywhere w/ 16.0 ?

you will need complete new LOS16 sources.You can’t use los15 sources for los16 build. It’s like mounting a VW Golf door on a Merceds

I know this, this point is not an issue w/ my Gbps fiber - just one hour d/l. But I’d be happy to get the remaining parts of roomservice.xml to attempt my build. Any hint on either :

  • Provide me with the content or…
  • Tell me how to retrieve it

Thanks :slight_smile:

No you can’t just change “lineage-15.1” by “lineage-16.0”. You have to build for Oreo since there is no LineageOS 16.0 thread on xda.
If you give me the link to a working LineageOS 16.0 thread, we will see.

I found this ROM for the phone, cannot guarantee it’s working :

Would it be sufficient ?

PS : just for my information what is xda ?

XDA is the site to visit for Lineage or other custom ROM’s …they have a lot of other info as well.

No, we need to know where it comes from to found the sources used. And yes we don’t know if it works, so forget Pie.

XDA is a developper forum. If you are looking for an unofficial LineageOS, that’s where you will find it.

it comes from him https://forum.xda-developers.com/member.php?u=8353520

I tried w/ Lineage 16.0 and it failed miserably, but it also fails w/ Lineage 15.1 - soooo which would be better ? 15.1 or 16.0 ?

BTW the GitHub repo mentioned above is bluedogerino

@Anonyme could you pls try to explain that he can’t try LOS16, because he has no LOS16 device / kernel sources ?? It seems I can’t

Sorry my bad - I understand your point. But as I cannot build either w/ 15.1 it’s disturbing. :frowning:

You probably can build for Oreo, something is just wrong in your build environment.

First, try to build for an officially supported device by /e/ and LineageOS on Oreo to see if it works by following the documentation :
https://doc.e.foundation/how-tos/build-e
Or manually with the help of this script :

(Start from scratch, it helps)

Personally I prefer to build without docker.

With 'build is failing ’ or something else, no one can help. What kind of error we have to know

EDIT: paste you log here and we can have a look https://del.dog/

The error messages I got are above. I will copy / paste a complete log to make things clearer.

PS : sorry for my noob behaviour but I’m actually lost since there are things for both 15.1 and 16.0, and none of them seem to be official. This phone seems to be very poorly supported by LineageOS as of now. See https://dietrichschroff.blogspot.com/2020/05/my-samsung-galaxy-j5-2017-aka-j5y17lte.html

exynos builds are a pain. I have tried for 3 different Samsung devices and all where failing.

Thanks anyway for your support and sorry if I look stubborn, this is due to my lack of understanding for this world which is rather new to me. (I know docker and so on, phone flashing not exactly :wink: )

I hate docker. It’s unflexible. I’m always build the good old way with breakfast / lunch / brunch :slight_smile:

And it’s a security bug by itself (actually I’m more investigating in DevOps / Security than phones :smiley: ) - the only pro of Docker is that it enables you to have a clean working environment in our case (and for microservices as well when you need to pop up instances quickly - but this is another topic).

EDIT : could this one help ?

If you are talking about this error, it’s clear.

vendor/samsung/exynos7870-common/exynos7870-common-vendor.mk

is missing.
check you sources folder ‘vendor/samsung/exynos7870-common’ if it is available

EDIT: These sources are NOT in the manifest. So you have to add them