/e/OS on Samsung Galaxy J5 2017

Anonyme · June 28, 2020, 6:51pm

Be careful, it’s local_manifests and not local_manifest

Sadly I don’t know (yet) how to make a non-lineageos source working. I didn’t see it wasn’t made for lineageos when I made the roomservice.

harvey186 · June 28, 2020, 7:52pm

From my side of view, trying to adjust this sources makes no sense. It’s wasted time. Better searching for los sources or searching for a los rom and using that sources

Manoj · June 28, 2020, 11:26pm

Off topic: I wanted to appreciate the efforts being put in by @julek to first request a device and then attempt to build it himself. Also thanks to @harvey186 and @Anonyme who are helping him out in his efforts. A community is only as strong or as good as the support or contributions of its users.

Anonyme · June 29, 2020, 2:29pm

Hi, do you know why my build for manta has started even if there is no “lineage_manta.mk” file please ? It’s just “lineage.mk”.

harvey186 · June 29, 2020, 3:21pm

I can’t believe, because all files are for AOSP and are full against lineage rules. Product name, … everything is wrong. I never was able to start a build with such sources

As you can see in the above error message, the build script is looking for a product lineage_deviceName
product "lineage_j5y17lte

And in your sources the product name is AOSP_manta. I really don’t know, why your build is starting

Anonyme · June 29, 2020, 3:41pm

Unknown was only building for LineageOS supported devices.
manta is officially only for Marshmallow but as you have already seen, there is a Nougat branch.

I think Unknown used this ‘normally not working’ branch to build the [UNOFFICIAL BUILD] Google Nexus 10 (manta)

I will publish the build once it’s done and see if it’s working for somebody.

harvey186 · June 29, 2020, 3:47pm

yes, he has build everything ‘blind’.

i have tried building for manta and it was always failing. hope your build will Finish successful

EDIT: OK, the lineage.mk contains the right Product Name
PRODUCT_NAME := lineage_manta

It seems that aosp_manta.mk isn’t needed for LOS builds

harvey186 · June 29, 2020, 3:52pm

have you seen the PRODUCT_PROPERTY_OVERRIDES := \

github.com

LineageOS/android_device_samsung_manta/blob/cm-14.1/full_manta.mk

# Copyright (C) 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

#
# This file is the build configuration for a full Android
# build for manta hardware. This cleanly combines a set of
# device-specific aspects (drivers) with a device-agnostic
# product configuration (apps). Except for a few implementation
# details, it only fundamentally contains two inherit-product

This file has been truncated. show original

Anonyme · June 29, 2020, 4:00pm

No, what’s wrong with that ?

harvey186 · June 29, 2020, 4:02pm

It’s changing the DNS to goolag DNS

Anonyme · June 29, 2020, 4:03pm

Even after the /e/ build is done ? (I guess yes, if not you wouldn’t have care)

harvey186 · June 29, 2020, 4:05pm

I don’t know what comes first, but I think device definitions are more important. But you can check after build in build.prob

julek · June 29, 2020, 4:37pm

Looks like there are already unofficial images for my phone :
https://androidfilehost.com/?fid=1395089523397917811

They were built against Pie (which is consistent with my observations for Pie conformity).

The guy’s git repo is there : https://github.com/bosniandoge

This one looks particularly interesting : https://github.com/bosniandoge/vendor-j5y17lte

Dunno obviously if his builds work, but it could be a good starting point (if we find out how to build the thing) don’t you think so ? (Won’t be available tonight for building as I’m also reading books but tomorrow I’ll have some spare time)

harvey186 · June 29, 2020, 4:53pm

I would start with this manifest

github.com

bosniandoge/local_manifests/blob/lineage-16.0/j5xnlte

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

  

  <remote  name="Galaxy-MSM8916"
           fetch="https://github.com"
           review="review.msm8916.com"
           revision="lineage-16.0" />

  <remove-project name="platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9" />

  <!-- Samsung Hardware Repo -->
  <project path="hardware/samsung" name="Exodusnick/android_hardware_samsung_j5xnlte" remote="github" revision="lineage-16.0" />
  <!-- Samsung MSM8916 Common Repos -->
  <project path="device/samsung/qcom-common" name="Exodusnick/android_device_samsung_qcom-common_j5xnlte" remote="github" revision="lineage-16.0" />
  <project path="device/samsung/msm8916-common" name="Exodusnick/android_device_samsung_msm8916-common" remote="github" revision="lineage-16.0" />
  <!-- (J510FN - j5xnlte) -->
  <project path="device/samsung/j5x-common" name="Exodusnick/android_device_samsung_j5x-common" remote="github" revision="lineage-16.0" /> 
  <project path="device/samsung/j5xnlte" name="Exodusnick/android_device_samsung_j5xnlte" remote="github" revision="pie" />

This file has been truncated. show original

julek · June 29, 2020, 5:31pm

This one won’t work - it is not for j5y17lte - my phone is a J530F with an Exynos CPU, not a Qualcomm

harvey186 · June 29, 2020, 6:47pm

Oh, bad. Have you found a fitting manifest in this chaos github repo?

piero · June 29, 2020, 7:27pm

j5lte is for F500F (2015) snapdragon
j5nlte is for J500FN (2015) snapdragon
j5xnlte is for J510FN (2016) exymos
j5y17lte is for J530F (2017) exymos

Anonyme · June 29, 2020, 7:32pm

Could you please try with the following roomservice please ? The previous github repo doesn’t belong to the publier of the xda thread, but I found the good one so I hope it will work. There is no “lineage_j5y17lte.mk” though, we will see.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="nailyk-fr/android_device_samsung_j5y17lte" path="device/samsung/j5y17lte" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_device_samsung_exynos7870-common" path="device/samsung/exynos7870-common" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_kernel_samsung_exynos7870" path="kernel/samsung/exynos7870" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" revision="lineage-15.1" />
  <project name="nailyk-fr/android_hardware_samsung_slsi-cm_exynos7870" path="hardware/samsung_slsi-cm/exynos7870" remote="github" revision="lineage-15.1" />
  <project name="LineageOS/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" revision="lineage-15.1" />
  <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.1" />
</manifest>

harvey186 · June 29, 2020, 8:06pm

That’s also los15. I thought it should be a los16 build ??

Anonyme · June 29, 2020, 8:17pm

I don’t see any Los 16 topic on xda, and only 1 LOS 16 build on androidfilehost, we don’t know if it’s working or not.