[ROM][LineageOS14.1][Nougat][Android 7.1.2] NightOwl 20180824

[BernardG]

How to build

Hello Bauner,

Thanks a lot for your work. It works fine on my galaxy note (despite some slowness from time to time).

For my personal experience, I would like to be able to build the port you have done. I had a look at your github (found the kernel and was almost able to build it (I am missing the initramfs)) but I have more issues to identify the other repositories.
Have you already done a simple how to build and if yes, would you agree to share it? Or would you recommand a starting point?

Thanks in advance for you help and thanks again for your work and time.

 

[bauner]

Hello Bauner,

Thanks a lot for your work. It works fine on my galaxy note (despite some slowness from time to time).

For my personal experience, I would like to be able to build the port you have done. I had a look at your github (found the kernel and was almost able to build it (I am missing the initramfs)) but I have more issues to identify the other repositories.
Have you already done a simple how to build and if yes, would you agree to share it? Or would you recommand a starting point?

Thanks in advance for you help and thanks again for your work and time.

The initramfs gets created if you build the bootimage inside the full lineage source.
If you want to build the kernel standalone (without the lineage source) you need to have an existing initramfs (Ask me if you need it) and adjust the path to it in kernelsrc/usr/n7000_initramfs.list and kernelsrc/arch/arm/configs/lineageos_n7000_defconfig

To build the full rom you need to do this steps

mkdir romdir
cd romdir
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
mkdir .repo/local_manifests

then copy the following to .repo/local_manifests/n7000.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="LineageOS/android_build" />
  <project name="bauner/cm-android_build" path="build" remote="github" revision="cm-14.1" />
  <project name="bauner/cm-android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="cm-14.1" />
  <project name="bauner/cm-android_device_samsung_n7000" path="device/samsung/n7000" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<remove-project name="LineageOS/android_external_toybox" />
  <project name="bauner/cm-android_external_toybox" path="external/toybox" remote="github" revision="cm-14.1" />
<remove-project name="LineageOS/android_frameworks_base" />
  <project name="bauner/cm-android_frameworks_base" path="frameworks/base" remote="github" revision="cm-14.1" />
  <project name="bauner/cm-android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
  <project name="bauner/android_kernel_samsung_tw_n7000" path="kernel/samsung/tw_n7000" remote="github" revision="cm-14.1" />
  <project name="LineageOS/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-14.1" />
 <remove-project name="LineageOS/android_packages_apps_Settings" />
    <project path="packages/apps/Settings" name="bauner/cm-android_packages_apps_Settings" revision="cm-14.1" />
<remove-project name="LineageOS/android_system_vold" />
  <project name="bauner/cm-android_system_vold" path="system/vold" remote="github" revision="cm-14.1" />
<remove-project name="LineageOS/android_vendor_cm" />
  <project name="bauner/cm-android_vendor_cm" path="vendor/cm" remote="github" revision="cm-14.1" />
  <project name="bauner/cm-proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1" />
  <project name="bauner/OTAUpdates" path="packages/apps/OTAUpdates" revision="aosp" />
</manifest>

then

 repo sync

to download the source

 

[BernardG]

Thanks a lot. I am going to have a try.
Regards.

 

[BernardG]

One more question: which lunch target are you using to make your build?

Thanks, Bernard.

EDIT: I guess it is n7000, but I am facing some compilation issues. I will come back to you if I can't solve them.

 

[bauner]

One more question: which lunch target are you using to make your build?

Thanks, Bernard.

EDIT: I guess it is n7000, but I am facing some compilation issues. I will come back to you if I can't solve them.

it is lineage_n7000-userdebug

Which build problems do you have?

Currently it will not build with ninja.
You can disable ninja by adding

export USE_NINJA=false

to your ~/.bashrc

 

[BernardG]

it is lineage_n7000-userdebug

Which build problems do you have?

Currently it will not build with ninja.
You can disable ninja by adding

export USE_NINJA=false

to your ~/.bashrc

My main problem is that this lunch target does not appear in my lunch menu. Anyway, I can select it, but then I don't have any Makefile at root directory. So I created one (by including the one from build/core/main.mk, (not sure I can do that)). But it does not want to compile due to some missing files.
All these issues, let me think that the repo are not correctly sync even if it looks (no errror after a sync).

I am doing another repo sync but it takes time due to the fact I don't have a fast internet access.

 

[bauner]

The LineageOS 14.1 20180318 Rom is finish

Changes:

* Updated lineage sources
* March security patches

 

[asusgarb]

I have Google Play service consuming a crazy battery life amount, even with privacy Guard enabled. On my other devices I have magisk as root. It has a module that enables battery optimization for it.

I know on this ROM it's impossible to use SuperSU, but is it possible to use magisk? Or is there some trick to make its usage possible?

Sent from my Samsung SM-P605 using XDA Labs

 

[Watanabe_You]

I have Google Play service consuming a crazy battery life amount, even with privacy Guard enabled. On my other devices I have magisk as root. It has a module that enables battery optimization for it.

I know on this ROM it's impossible to use SuperSU, but is it possible to use magisk? Or is there some trick to make its usage possible?

Nope. Magisk requires a newer kernel code + format that is impossible for the Note 1.

 

[martinwunderli]

Hi
I just installed LineageOS 14.1 20180318 Rom and the corresponding apps. Absolutely amazing and a very big thanks for your work! (Hint: Maybe write in the howto of the first page that while the PhilZ kernel is flashed using Odin, the 2nd one is flashed via Recovery Mode and therefore should also be copied to the sdcard).

Cheers
Martin

 

[clod22]

The LineageOS 14.1 20180318 Rom is finish

Changes:

* Updated lineage sources
* March security patches

Thank for your great work. All the best.

 

[bowtie81]

will the android go be implemented into custom roms, android go which is made for older hardware to run smoother? Will there ever be oreo developed? I wonder what is least resource hungry? Anyway, I am very pleased with this rom.

 

[Surya Chandra]

i am unable to get root it is only giving root access to adb but not apps (option not present in developer options) pls help me.

 

[asusgarb]

i am unable to get root it is only giving root access to adb but not apps (option not present in developer options) pls help me.

You have to flash the addonsu-14.1 that you find here: https://download.lineageos.org/extras

Sent from my Samsung SM-P605 using XDA Labs

 

[BernardG]

it is lineage_n7000-userdebug

Which build problems do you have?

Currently it will not build with ninja.
You can disable ninja by adding

export USE_NINJA=false

to your ~/.bashrc

Hello Bauner,

I finally succeeded to build with some workarounds.
Here they are:
1) repo sync then create n7000.xml and then repo sync again
2) Do not do ./extract_files.sh
3) lunch lineage_n7000-userdebug
4) make acp
5) make full/path/to/boot.img
6) make all
7) brunch n7000 (to get the final zip)

1) is needed because at least one file is else missing (Makefile at root dir)
2) Else create issue with module libUMP
4) acp is missing else during the main compilation.
5) is needed because else I have a circular dependency in the makefiles between boot.img and kernel. I could not find why.

I will try to solve these issues if I can.

I did not test yet the image generated, but I hope it is working.

 

[Surya Chandra]

You have to flash the addonsu-14.1 that you find here: https://download.lineageos.org/extras

Sent from my Samsung SM-P605 using XDA Labs

It is working. thanks:good:

 

[bauner]

Hello Bauner,

I finally succeeded to build with some workarounds.
Here they are:
1) repo sync then create n7000.xml and then repo sync again
2) Do not do ./extract_files.sh
3) lunch lineage_n7000-userdebug
4) make acp
5) make full/path/to/boot.img
6) make all
7) brunch n7000 (to get the final zip)

1) is needed because at least one file is else missing (Makefile at root dir)
2) Else create issue with module libUMP
4) acp is missing else during the main compilation.
5) is needed because else I have a circular dependency in the makefiles between boot.img and kernel. I could not find why.

I will try to solve these issues if I can.

I did not test yet the image generated, but I hope it is working.

5) should be fixed with the workaround

export USE_NINJA=false

 

[BernardG]

5) should be fixed with the workaround

export USE_NINJA=false

It did not work for me. I had always set USE_NINJA to false since you told me but the circular dependency error was always here.
I will try to investigate when I have time.

 

[leodrums]

Alguién tiene alguna explicaciön?

I installed the nougat on my galaxy note 1 n7000 can someone explain me why ?:
1- the fastest discharge battery, 2 - heat the equipment
3 - the wifi is disconnected after using it
4 - the multimedia volume is heard lower (it is at the top of volume configuration).
I'm from Peru in South America and thank you.

 

[IronRoo]

I installed the nougat on my galaxy note 1 n7000 can someone explain me why ?:
1- the fastest discharge battery, 2 - heat the equipment
3 - the wifi is disconnected after using it
4 - the multimedia volume is heard lower (it is at the top of volume configuration).
I'm from Peru in South America and thank you.

1) hard to say, probably an app that is not compatible, or you restored apps data that cause conflict with newer ROM (always best not to restore app data when moving to a new ROM like nougat)
3) I think you are talking about "doze" feature on newer Android version, design to save power, phone will doze for periods but then reconnect to check for msgs etc.
4) not sure mine is fine.