[ROM] [UNOFFICIAL] [7.1] [Nougat] [NIGHTLY] Lineage OS 14.1 for Nexus 4

[chenshaoju]

The Build is down...
And LOS has no longer actively maintained Nexus 4...
https://www.lineageos.org/Changelog-9/
EDIT:LineageOS always welcome to join maintainer ,Can you join LOS maintainer ?

 

[accuphase]

The Build is down...
And LOS has no longer actively maintained Nexus 4...
https://www.lineageos.org/Changelog-9/
EDIT:LineageOS always welcome to join maintainer ,Can you join LOS maintainer ?

+1 @milaq will you save mako's future?? Would be great!

 

[milaq]

The Build is down...

fixed the nightly builds.
they should be up for download again soon.

 

[milaq]

[MENTION=1594835]
about cherry picks
https://github.com/milaq/android/blob/cm-14.1/cherry-picks.sh
no longer exists
is it
https://github.com/milaq/android/tree/cm-14.1/patches
now?

That's correct.
Every change is getting reflected in https://github.com/milaq/android/tree/cm-14.1/

Edit: To clarify the automated build process (outline):
* Pull latest upstream sources
* Apply local manifest(https://github.com/milaq/android/blob/cm-14.1/local_manifest.xml)
* Apply patches (https://github.com/milaq/android/tree/cm-14.1/patches)
* Start build
* Publish build

[MENTION=1594835]
Are your builds fully compatible with Lineage 14.1 official people may flash each back and forth? ( I presume that is true, but asking for clarification )

Yes, builds are fully compatible.

 

[accuphase]

@milaq
Thx for the new build!

What's the reason for 35mb less download size compare with further builds?

 

[chenshaoju]

fixed the nightly builds.
they should be up for download again soon.

Thank you!

 

[Pac-Man]

That's correct.
Every change is getting reflected in https://github.com/milaq/android/tree/cm-14.1/

Edit: To clarify the automated build process (outline):
* Pull latest upstream sources
* Apply local manifest(https://github.com/milaq/android/blob/cm-14.1/local_manifest.xml)
* Apply patches (https://github.com/milaq/android/tree/cm-14.1/patches)
* Start build
* Publish build



Yes, builds are fully compatible.

Maybe I should learn the way you patch and build LineageOS to try and make my own builds, thank you so much!

 

[phkhphk]

thanks for the last rom

fantastic :good:

 

[Has_anDroid]

magisk module safety net not work quanta kernel v21 magisk hide su error suhide ?

 

[Pac-Man]

@milaq
Thx for the new build!

What's the reason for 35mb less download size compare with further builds?

According to the local_manifest.xml:

<!-- Remove cyngn.com endorsed stuff -->
<remove-project name="LineageOS/android_packages_apps_Eleven"/>
<remove-project name="LineageOS/android_packages_apps_Snap"/>
  
<!-- We don't use the default updatechannel -->
<remove-project name="LineageOS/android_packages_apps_CMUpdater"/>

It removes some stuff, so it's correct it has 35MB less

 

[nefescalanadam]

magisk module safety net not work quanta kernel v21 magisk hide su error suhide ?

Yeah i have this problem on official and unofficial LOS 14.1

 

[accuphase]

According to the local_manifest.xml:



It removes some stuff, so it's correct it has 35MB less

... and changing Gello to Jelly makes smaller builds

 

[Has_anDroid]

Yeah i have this problem on official and unofficial LOS 14.1

pixel navbar flash ? work ?

 

[xenomorph150]

fixed the nightly builds.
they should be up for download again soon.

You Sir, are awesome! :victory:

 

[*Jonny*]

This version did not work with f2fs :/ on Official was fine...

 

[Pac-Man]

This version did not work with f2fs :/ on Official was fine...

This rom is compiled from official sources, so... I really doubt it doesn't work...

 

[[email protected]]

The caffeine quick settings tile doesn't work I click on it and nothing happens except it lights up no choice of length of time
I am on 5-24-17 build

 

[Pac-Man]

The caffeine quick settings tile doesn't work I click on it and nothing happens except it lights up no choice of length of time
I am on 5-24-17 build

Assuming your date format is MM-DD-YYYY, I use the 05-20-17 build. Caffeine toggle just lights up and that's it. You can stare at your screen without worring about getting it off in the minutes you set up.

It works perfectly, I use it a lot during the day.

---------- Post added at 15:26 ---------- Previous post was at 15:24 ----------

Yeah i have this problem on official and unofficial LOS 14.1

"su" binary is already hidden, as far as the latest blog at LineageOS's blog states (link to the post).

Kernel su-hide to address an important vulnerabilty

It has been claimed that the Privacy Guard implementation of ‘su’ has security vulnerabilities even when disabled. In other words, the mere presence of the su binary is enough to compromise the device.

Unfortunately, the person who reported this vulnerabilty refuses to disclose its exact nature, nor could we make sure to properly fix this exact issue. The next best solution is to ensure that su is only accessible when enabled in the Settings app and keep su disabled when it’s not in use.

We’ve created a kernel patch that hides the existence of su from all processes except root and system when the su daemon is not running (root needs access so that init can start the su daemon, and system needs access in order to populate the root access settings appropriately).
[...]

 

[goosnarrggh]

Assuming your date format is MM-DD-YYYY, I use the 05-20-17 build. Caffeine toggle just lights up and that's it. You can stare at your screen without worring about getting it off in the minutes you set up.

It works perfectly, I use it a lot during the day.

---------- Post added at 15:26 ---------- Previous post was at 15:24 ----------



"su" binary is already hidden, as far as the latest blog at LineageOS's blog states (url removed due to posting guidelines).

That change just went live with the new official nightly (weekly?) that was published yesterday.

They didn't do it for the typical reason (to trick SafetyNet into thinking the device is running an unmodified stock OS), but rather because of the security vulnerability noted in the blog post. If this change happens to cause some devices to pass SafetyNet checks as a result, then that's a happy side-effect.

 

[Pac-Man]

That change just went live with the new official nightly (weekly?) that was published yesterday.

They didn't do it for the typical reason (to trick SafetyNet into thinking the device is running an unmodified stock OS), but rather because of the security vulnerability noted in the blog post. If this change happens to cause some devices to pass SafetyNet checks as a result, then that's a happy side-effect.

In fact the Magisk developer said that doing that doesn't prevent the vuln (he said so by the IRC channel).