[ROM][Official][Nightly] LineageOS 17.1 for OnePlus 3/3T - OnePlus 3 & 3T Cross Device Development

[ROM][Official][Nightly] LineageOS 17.1 for OnePlus 3/3T - OnePlus 3 & 3T Cross Device Development

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 17.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 17.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog:
2019.10.24
Initial release
2019.10.25
Sync latest source
Fix bluetooth
2019.11.20
Sync latest source
Fix wifi display
Ship Snap
Fix vulkan graphics
Pass safetynet
Fix crash of some native services
2019.12.31
Sync latest source
SELiunx working in enforcing mode now
Update kernel to LA.UM.8.6.r1-02900-89xx.0
Update blobs from OOS 9.0.6
Fix suspend when AOD is on
Happy new year!
2020.1.12
Sync latest source
Fix ril of the last build
Update blobs from LA.UM.8.6.r1-02900-89xx.0
Add backuptools
Other trivial fixes
2020.4.2
Official nightlies started
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: Android 10
Version Information
Status: Nightly
Created 2019-10-24
Last Updated 2020-06-26

Any recommendations which gapps to use?

Why not the official ones? https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/

is this with kernel 4.4?

helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
https://github.com/LineageOS/android_kernel_oneplus_msm8996/blob/lineage-17.0/Makefile#L1-L3

helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...

dianlujitao said:
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T.
Click to expand...
Click to collapse
OP needs some changes its for LOS 17 instead of 16 [emoji3][emoji39]
Sent from my ONEPLUS A3003 using Tapatalk

Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.

Master_TC said:
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
Click to expand...
Click to collapse
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
mady51 said:
ya i built it once but it didn't booted. after that didn't spent time on it. may be ill give it another try soon
Click to expand...
Click to collapse
Anyway amazing work @dianlujitao you're one of our heroes ???

Viper The Ripper said:
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
Anyway amazing work @dianlujitao you're one of our heroes ???
Click to expand...
Click to collapse
https://github.com/dianlujitao/android_kernel_oneplus_msm8996 @dianlujitao did bring up a 4.4 kernel but it has issues.

Jus asked because of this

mvalda01 said:
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Click to expand...
Click to collapse
Can you provide more info such as logs, my aptx headset works fine here.

Thanks for the effort,nice rom for nice phone.
From Op3 owner

Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure.
NFC works fine for me, it wound be nice if you could grab related logs.

Well done @dianlujitao!

Thanks for your work @dianlujitao! I'll probably flash next build

@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.

MJPollard said:
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
Click to expand...
Click to collapse
You need to pick - at least - https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/255737 from https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3+status:open, maybe all.
There's a good reason why OP calls it an experimental build instead of alpha or beta... Rebuilding experimental needs skilld and patience...
EDIT:
For the blobs commits (i.e. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/260573 and https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/262330) see also https://github.com/dianlujitao/proprietary_vendor_oneplus/commits/lineage-17.0 .

BillGoss said:
- Digital Wellbeing keeps stopping (logs attached)
Click to expand...
Click to collapse
On some other Android 10 ROM, force stopping, disabling and then re-enabling solved this issue.

Related

[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU]

Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
ROM Information
ROM Target Device: Samsung Galaxy Tab E [SM-T560NU ]
ROM Status: Stable
ROM OS: LineageOS 14.1
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Project Gerrit Review site: https://review.msm8916.com/
Bug reports: https://bugs.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]
Click to expand...
Click to collapse
Download
All Jenkins builds are testing builds, and as such, are likely to be extremely unstable or
unusable.
Code:
[B]All builds:[/B] [url]https://download.msm8916.com/[/url]
[B]Jenkins Builds Builds:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/[/url]
[B]TWRP Builds:[/B] [url]https://jenkins.msm8916.com/job/TWRP_Builds/[/url]
[B]GApps:[/B] [url]http://opengapps.org/?arch=arm&variant=micro&api=7.1[/url]
[B]RSS:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/rssLatest[/url]
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.
* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:
* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
* Download and flash GApps in the same way.
Click to expand...
Click to collapse
How to provide logcats
Under Windows:
Code:
[B]* Install samsung device drivers and then
the adb utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the adb utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your home directory.[/b]
* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.
* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
Features
Code:
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
XDA:DevDB Information
[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU], ROM for the Android General
Contributors
vince2678, deadman96385, minz1
Source Code: https://github.com/Galaxy-MSM8916
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-06-08
Created 2017-02-03
Last Updated 2018-06-24

Reserved
Changelog
NOTE: gtesqltespr (SM-T377P) builds have been disabled until someone steps up for testing to resolve the issue in recent builds.
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added KeyDisabler. For devices with touch keys controlled separately
from the touch screen, this means that the virtual Nav Bar
can be enabled in the Settings. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
app(s) should be gone. [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Both cameras should now be working [/B]
Code:
[B][U]01/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] LineageOS updater can reboot to recovery properly.[/B]
Code:
[B][U]11/03/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
T377PSPT2BPJ1 (6.0.1) to T377PVPU1AOJ5 (5.1.1)[/B]
Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Decreased minimal scaling freq. to 200Mhz.
The previous scaling frequency minimum of 800Mhz was pretty high,
and could quickly cook your phone and kill power on mobile devices.
Lowering to 200Mhz should significantly extend batery life
on the stock scheduler. [/B]
[B][U]12/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.9_rb1.11 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated kernel source [ to LA.BR.1.2.9_rb1.11 ] [/B]
[B][U]06/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed to a new kernel source [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored device trees [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Monthly security fixes from Google [/B]
There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.
Code:
[B][U]29/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Switched to LineageOS sources. [/B]
[B][U]20/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Made some substantial changes to our build
infrastructure, which should make my life substantially easier
and using Jenkins and all a more pleasant experience. [/B]
[B][U]17/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Reboot bug should be fixed [/B]
[COLOR="RoyalBlue"][B]gtesqltespr[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Wifi should be working (build >= 4) [/B]
Code:
[B][U]16/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.7_rb1.7 ] [/B]
Code:
[B][U]15/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Started builds for SM-T377P [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added KSM and ZRAM. These have to be enabled manually by
setting "ro.config.ksm" and "ro.config.zram" in the build.prop to true. [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Set maximum cpu frequency to 1209Mhz [/B]
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Rear camera is working [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] LiveDisplay feature is working [/B]
Code:
[B][U]11/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
T560NUUEU1BPI3 (6.0.1) to T560NUUEU1AOK1 (5.1.1)[/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Audio and wifi now work proper. [/B]
Code:
[B][U]08/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created forum thread [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] First build completed. [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None [/B]

nice work! maybe this would work on the t377p

That good ... there is the possibility of cooking something for the T560: C

I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3

I'm aware of the bug. For now, you'll have to flash the latest CyanogenModRecovery to update the device until twrp works proper.

I'm hoping you might know what I need to do here, but I installed a theme recently and it worked fine. But I ended up having to redo my tablet for a different reason, and ever since then whenever I try to use the same theme my system UI fails.

Finally custom rom for our device. :good: Can we hope to see CM13 on T560 also?

ElsaReyes said:
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
Click to expand...
Click to collapse
You can try the recoveries below, fully tested and working.
https://forum.xda-developers.com/showthread.php?t=3302935

gapps
hey guys does this require gapps?

You can install Gapps after flashing the rom, Yes.

im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?

42o247 said:
im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?
Click to expand...
Click to collapse
wont work needs another kernel

parrotgeek1 said:
wont work needs another kernel
Click to expand...
Click to collapse
cool cool. good to know.

ElsaReyes said:
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
Click to expand...
Click to collapse
The reboot issue for recovery is now fixed.

i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo
ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device

42o247 said:
i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo
ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device
Click to expand...
Click to collapse
A lot of things would not work, for example, the touchscreen. As similar as devices may seem there will still be hardware differences between variants and I don't recommend cross flashing.

Just flashed the 1/15 build and everything went well. I'm in the process of setting my Sm-t560nu up. I will report back after I'm finished. Thanks a lot for this Rom.

vince2678 said:
The reboot issue for recovery is now fixed.
Click to expand...
Click to collapse
Awesome. Thank you for all your work on this. Downloading the build now. :3
And just to keep you updated, it might not be in the newest build but I tried playing some of the videos I have saved on my sd card last night, and while the audio moves along just fine, the video plays all choppy and slow.

Hello, i'm glad to see a rom for TAB E, great work, but if you have time pls do something for T560, many users will be happy to see a CM on theyr tablets imcluding me, thanks allot for any answers
Sent from my SM-G935F using XDA-Developers Legacy app

[EOL][ROM][SDCLANG-6][microg-ready][OMS Service Mode]NLOS-15.1 - 20190208

NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. This build is optimized for oneplus3t - it will flash and run on a oneplus3, because it's an unified build, but it's optimized for 3t!
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Oreo) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
NLOS doesn't require any mods to work with @Arnova8G2's GoogleCamera Mod (more details in S4turno's thread ). Just install the modded Gcam - no need to flash twrp-front-fix-oreo-op3-3t.zip, nor to use the magisk module.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty isn't void: we are on an oneplus device.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 15.1 builds for oneplus3 and onepluy3t. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps larger then opengapps-nano)
First time flashing NLOS 15.1 on your device, or coming from another ROM:
Backup your current ROM and make sure you have backups of your data you want to keep.
Download the ROM below in the downloads section.
Download current MindTheGapps for arm64. If you insist on using gapps, don't use a package larger then nano.
Download and flash twrp-3.2.3-0!
Download and flash latest OxygenOS Oreo firmware.
Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://forum.xda-developers.com/on...1-20180223-t3754855/post75688089#post75688089 - NOT recommended!
Wipe system, data and caches.
Flash NLOS.
Flash Google Apps. If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Optional: flash Magisk (if you need root)
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery (if necesarry flash the firmware zip recommended by the release notes) and flash the updated NLOS zip - don't forget to wipe dalvik and cache. Settings, apps and even google apps are preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/15.1/
Build 20190208
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 8 Feb 2019, 14:09:19 CET / 8 Feb 2019, 13:09:19 UTC):
Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo
drivers: video: mdss: Fix direct references to HZ — celtare21
drivers: ipa: Fix direct references to HZ — Humberto Borba
drivers: platform: gsi: Fix direct references to HZ — Humberto Borba
drivers: hwmon: Fix direct references to HZ — Humberto Borba
drivers: i2c: Fix direct references to HZ — Humberto Borba
Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx
msm: kgsl: Remove POPP — Sultan Alsawaf
current.pick.sh: O_asb_2019-02. — Nvertigo
current.pick.sh: introduce a safer repopick. — Nvertigo
op3/t: nfc: advertise support for extended length NFC — Paul Keith
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20190127
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 27 Jan 2019, 13:01:40 CET / 27 Jan 2019, 12:01:40 UTC):
current.pick.sh: force picking abandoned battery customisation commits (220407, 220422, 219299) — Nvertigo
op3: Restore better load balancing after boot — Thomas Shum
WG: squash WireGuard-0.0.20190123. — Nvertigo
Merge tag 'v3.18.133' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp
Thread for official twrp
Google Apps:
MindTheGapps-8.1.0-arm64-20180223_195845.zip
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-15.1 (If you want to build this rom yourself, consult the file named README, it's outdated, but still helpfull)
Aytex, who made all of the banners on this post.
team-exynos5420 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
The microG Team
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
@Arnova8G2 for his GoggleCamera port.
@S4turno for this great thread on GoggleCamera Mods.
@knpk13 for debugging this OP.
Substratum Dev Team
@danieldmm for opening my eyes for the obvious...
@mcdachpappe for helping me with additional notification slider options.
...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-15.1, ROM for the OnePlus 3
Contributors
nvertigo67, dianlujitao
Source Code: https://github.com/nvertigo/local_manifest/tree/nlos-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: latest
Based On: LineageOS 15.1
Version Information
Status: Stable
Created 2018-12-04
Last Updated 2018-12-04

Known Issues
fixed: NLOS can't initially encrypt f2fs data partitions (though ext4 is working flawlessly).
fixed: NLOS can't change the encryption passphrase for f2fs/ext4 data partitions (though ext4 is working flawlessly).
fixed: adb and mtp doesn't work out of the box. Workaround:
put in QS-tile "adb over network"
disable wifi
enable "adb over network" with the added tile (tile shows 0.0.0.0)
connect usb cable
an expandable notification shows up
expand it, tap it and select "file transfer": voila.
If you've run through the above adb and mtp are working fine - even trough reboots... automagicaly...
If secure boot password, pin or pattern is set: LiveDisplay's Settings show color profile as "Standrad" after a reboot, though the configuered LiveDisplay's color profile is correctly aplied.
Notification lights have hickups.
fixed: With no substratum themes applied and dark mode enabled the qs edit page is in stealth mode (white text on white background). For reference see: https://forum.xda-developers.com/ap...um-support-t3606400/post76619564#post76619564

Where has "keep wifi on during sleep"?
Sadly this isn't working anymore.
The maker of betterbatterystats offers also a tool to accomblish this task and much more:
betterwifionoff
When switching from lineage-14.1 to lineage-15.1 I found idle bat usage doubled: what has been 0.4 % per hour on nougat increased on oreo to 0.8 to 1.0 % per hour.
On n I've always used "only if charging" for "keep wifi on during sleep", but the access to this setting has been vanished by google. So I exprimented with wifi conf file, kernel driver and wakelock blocking on kernel level. Nothing really solved the adsitional idle drain.
I'm still surprised, what I found while searching settings (cli): the setting "wifi_sleep_policy" is still there! Google has just droped the access via Settings->Network&Internet->Wi-Fi and makes "Always" the default , but the setting is still available and is working like on n.
Value: Function
0: Never
1: only when plugged in
2: Always
To get restore my n setting (keep wifi on while sleep only when plugged in), I only need to connect via adb (I prefer adb over network, but it works as well with usb), and issue this command:
Code:
adb shell settings put global wifi_sleep_policy 1
After spending endless hours on kernel and debugging, this simple command brought back 0.4%/h idle bat usage.

How To: format data with f2fs with current official TWRP
Current twrp (3.2.1-0) can't change the data fs to f2fs. The reason for this breakage is, that twrp expects a mkfs.f2fs command that knows "-r size" as cli-option, but the image is shipped with a version that doesn't know about "-r".
To get data formated as f2fs with space for the encryption footer, you just need to follow these simple steps:
Download attached mkfs-f2fs.zip.
Unzip and place the contained mkfs.f2fs in /sdcard/Download.
Boot to current twrp-3.2.1-0.
In twrp:
Home-Screen->Advanced->Terminal
Code:
cp -vi /sdcard/Download/mkfs.f2fs /tmp
chmod 0755 /tmp/mkfs.f2fs
/tmp/mkfs.f2fs -t 0 -r 16384 /dev/block/bootdevice/by-name/userdata #for the lazy, if on op3/t can use /dev/block/sda15
flash rom (or use the installed rom, which is factory reseted by formating data), reboot t system amd encrypt your device.
The mkfs.f2fs binary is taken from the original twrp-3.2.1-0. This will only work for 64-bit devices:
Code:
file mkfs.f2fs
mkfs.f2fs: ELF 64-bit LSB pie executable ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /sbin/linker64, BuildID[md5/uuid]=46b5f32d88973c91f79744258599a19a, stripped

stuff.

UPDATE
Build 20180225
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta03 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk — Nvertigo
Bring back busybox. — Nvertigo
Switch kernel branch to linux-stable/nlos-15.1. — Nvertigo
Merge tag 'v3.18.96' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!

set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.

With the version from 18th February the setup wizard is working, if you are going for a fresh installation.

vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
crian said:
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
Click to expand...
Click to collapse
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).

nvertigo67 said:
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
Click to expand...
Click to collapse
Will this work on op3 too?

Aasresh said:
Will this work on op3 too?
Click to expand...
Click to collapse
Most propably: yes.
I don't have my hands on a 3, and I made it my self a rule to only build and push for devices I have my hands on. That's why I stay in 3t forum though it's essentially an unified build. On the other hand: whenever a setting can be tuned for either for sd820 or sd821, I go for sd821. Other then that, NLOS should work on both models, and I try my best to give you support here.

Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
Nope

doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.

OMS service mode
TheGatorade said:
Can't wait for rootless OMS patch
This rom looking good, surprisingly stable for a beta
Click to expand...
Click to collapse
Stay tuned. Need to cleanup the sources and make a clean build.

nvertigo67 said:
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
Click to expand...
Click to collapse
Gotcha. Good to know that plain LOS is just as good with battery life. Thank you

For people having trouble with gapps try flashing the rom then complete the setup wizard then flash gapps.
Worked for me.

UPDATE (OMS Service Mode)
Build 20180226
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta04 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
OMS Service Mode is still work in progress. Sometimes you need to activate a theme once again after "compile&activate". Some themes (i.e. flux - though it's working flawlessly) refuses to deactivate, but flashing /sdcard/substratum/SubstratumRescue.zip removes all activated overlays. Rebooting is sometimes neccessary. Wiping caches and dalvik may be a good idea, too. SwiftDark and Flux seem to work otherwise.
Special thanx to @danieldmm for helping me out of my brainlock with pointing me to https://substratum.review/ . Without his help I would be still searching for commits currently not meeged... ...that would have taken looooong.... *lol*
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
OMS Service Mode: https://substratum.review/#/q/branch:o+(status:merged+OR+status:open) and https://github.com/nvertigo/android_frameworks_base/commit/e5cc87691ea4ba482914adee36821243fe39f7b4
op3: Use exfat-nofuse — dianlujitao
Merge remote-tracking branch 'lneageos/lineage-15.1' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
EDIT:
HOTFIX:
Set sepolicy temporary to permissive, if you want to deactivate an overlay.

Dirty flashed nlos-15.1 20180226 over 20180225 cause some bugs.
Op3T boots but few seconds after the screen becomes black and the phone reboot to recovery.
Revert to 20180225.

[ROM][official] AICP 13.1 - o8.1 - amami

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD in 2012 and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the ROM has always been based on AOKP. Since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (Lineage) we are now Lineage based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the Lineage team will if it concerns their code base. This ROM isn't Lineage supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: http://dwnld.aicp-rom.com
Official builds will be deleted from our servers every month due to maintenance services. We advise everyone to keep at least the latest or best working build on their device as a backup. Maybe copy it to a cloud service or USB too.
Test builds Version 13.1
Download link: https://basketbuild.com/devs/SpiritCroc/amami/AICP-o8.1
Google Apps
http://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico
Full Changelog link: http://dwnld.aicp-rom.com
Alternative: Check the inbuilt changelog (Settings/AICP Extras/About/Changelog)
- Offline charging when connected to PC leads to reboots
- You tell...
What should be working:
- Boots
- Display
- Sound
- WiFi
- GPS
- sdcard
- phone functionality
- mobile data
- bluetooth
- timekeep
- led
- flashlight
- camera
- FMRadio
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
0. Real recovery is recommended, it has been reported though that FOTA recovery might work too. There are issues with reboot to recovery with some recoveries (the TWRP linked here seems to work fine for me)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 should not require flash on every dirty flash.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use other recoveries and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source: https://github.com/AICP/kernel_sony_msm8974/tree/o8.1
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
rcstar6696
SuperLamic
AdrianDC
115ek
All the other contributors to sony msm8974 platform
ROM OS Version: 8.1.x Oreo
Kernel: Linux 3.4
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 13.1 Amami, ROM for the Sony Xperia Z1 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: No Longer Updated
Created 2018-02-26
Last Updated 2020-10-18

Reserved
Device-specific changelog for test builds:
(for complete ROM changelog, see AICP gerrit or ROM inbuilt changelog)
20180908_1022
- Fix connection to some mobile data networks
20180825_1523
- Upstream update
- Performance profiles
20180723_0816
- Fix mem sleep
- Other minor improvements
20180605_1939
- sdcardfs: fix space leak
20180516_0928
- sepolicy update
20180514_0941
- Minor fixes from upstream
20180507_2103
- Video recording fully fixed
20180506_0926
- Added exFAT support
20180428_0921
- Green stripe in video recording fixed
- Preferred network type should be working, connecting to network might be slow
20180411_1920
- Enforcing sepolicy
20180407_1320
- Fix issues with some displays
20180326_1629
- ANT+ added back
- Preferred network type fixed
20180321_1035
- Fix AudioFX crashes
20180319_0808
- Fix repeated NFC crashes
- Fix video recording (remaining issue: green stripe on edge on recordings)
20180302_1718
- Fix wrong hardware key settings showing
- Fix front camera crash
- Fix screenrecord and other possible media issues
20180228_1748
- Fix some background services
- Add Snap Camera, which has working back camera
Warning: switching to front camera will make it crash and you'll have to clear its data to use it again!
20180228_1042
- Timekeep working again
- Mobile internet fixed (now it takes a little longer to detect the SIM card though, so be patient after booting up your device)
- GPS fixed (probably)

Great to hear that there are people working on 8.1.
I just fixed wifi on lineage 15.1.
Some hours ago I tested your build quickly. These things were working at first glance.
wifi
rotation
LED
backlight (even with sensor)
flashlight
Keep up your work :good:

Good news, I finally managed to get mobile internet working, will try to provide a build with more fixes later

SpiritCroc said:
Good news, I finally managed to get mobile internet working, will try to provide a build with more fixes later
Click to expand...
Click to collapse
Really good news! Thank You!

New update (20180228_1042) is out!
Changelog:
- Timekeep working again
- Mobile internet fixed (now it takes a little longer to detect the SIM card though, so be patient after booting up your device)
- GPS fixed (probably)
Remaining issues:
- Inbuilt camera app not working
- Video recording broken
- Sepolicy
- Potentially everything that hasn't been tested yet, please report issues that aren't listed!
Enjoy!

Firmware liked!

Opinion
I also found some bugs. Sometimes when you lock the screen, it may not turn on the power button. And if you support it, the screen turns on. And also slows down in some areas of the animation.
My verdict: the Firmware is very good, but there are shortcomings. Please do not give up and continue to make new builds for us, because if you give up, no one will care about our phone. Thanks! :good:

I uploaded another build (20180228_1748) with some fixes and added a reserved post for changelog.
Latest build fixes some background services and adds Snap camera, which has working back but broken front camera. Switching to front camera will make it crash and you'll have to clear its data to use it again!

lovely

@SpiritCroc : thanks for your efforts on this! Have been quite amazed with my old trusty z1c on your AICP 12.1 builds and managing 10+ days idling on one charge with a new battery. I hope AICP 13. will help returning my z1c to being my daily driver.
Do you or AICP in general also keep your eyes out on possibly supporting zx2c4 's WireGuard (zx2c4 instructions) into your future builds? Have been very pleased using this on all my linux systems.
Also, I just flashed AICP-o8.1_amami_20180228_1748.zip with LineageOS' 14.1 addonsu-arm-signed.zip (2017-06-21) and this got me working root in ADB. Haven't tested apps yet though.
Code:
$ adb shell
amami:/ $ whoami
shell
amami:/ $ su -
amami:/ # whoami
root

cntmagistus said:
Do you or AICP in general also keep your eyes out on possibly supporting zx2c4 's WireGuard (zx2c4 instructions) into your future builds? Have been very pleased using this on all my linux systems.
Click to expand...
Click to collapse
Currently not planned
cntmagistus said:
Also, I just flashed AICP-o8.1_amami_20180228_1748.zip with LineageOS' 14.1 addonsu-arm-signed.zip (2017-06-21) and this got me working root in ADB. Haven't tested apps yet though.
Click to expand...
Click to collapse
Here you can get lineage su for oreo (I have't tested it):
https://androidfilehost.com/?w=files&flid=243911
I wouldn't recommend using 14.1 su addon on oreo

cntmagistus said:
@SpiritCroc : thanks for your efforts on this! Have been quite amazed with my old trusty z1c on your AICP 12.1 builds and managing 10+ days idling on one charge with a new battery. I hope AICP 13. will help returning my z1c to being my daily driver.
Do you or AICP in general also keep your eyes out on possibly supporting zx2c4 's WireGuard (zx2c4 instructions) into your future builds? Have been very pleased using this on all my linux systems.
Also, I just flashed AICP-o8.1_amami_20180228_1748.zip with LineageOS' 14.1 addonsu-arm-signed.zip (2017-06-21) and this got me working root in ADB. Haven't tested apps yet though.
Code:
$ adb shell
amami:/ $ whoami
shell
amami:/ $ su -
amami:/ # whoami
root
Click to expand...
Click to collapse
Root access in ADB is also possible without flashing the addon. Just enable root access --> ADB only in developer options.
Then the following results:
Code:
$ adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting adbd as root
$ adb shell
amami:/ #
amami:/ # whoami
root
Don't know if you know that

Update (20180302_1718):
- Fix wrong hardware key settings showing
- Fix front camera crash
- Fix screenrecord and other possible media issues

115ek said:
Root access in ADB is also possible without flashing the addon. Just enable root access --> ADB only in developer options....
Don't know if you know that
Click to expand...
Click to collapse
Oops, I should have figured that. Nevermind, thanks, you're right indeed!
@SpiritCroc Thanks for the info!

How was the battery drain in AICP 12.1? I'm coming from @munjeni's Lineage 14.1. And there the battery last some days. (Without doing much...)
Now the battery gets empty very fast, at least for me (on two different Z1C's...).
I'm looking for a good app to log the drainage and wakelocks. Are there any good (free) suggestions?

Battery drain with AICP 12.1 was very low/good. Got 10+ days (estimated), idle in flight mode. Never actually used it much as development stopped in favor of 13.1 so not a real usage number. With AICP-o8.1_amami_20180302_1718.zip I get ~48 hours according to battery estimations.

Tested this ROM and works fine. If you want Sony Based Camera in this rom, just download the port. It's for Nougat, but works with Oreo. (Video recording not working, but the developer is going to fix this issue). Also, you can flash Sony Apps Enabler, and you can install Sony Xperia Apps.
Camera: https://forum.xda-developers.com/cr...port-stock-camera-nougat-roms-t3628791/page49
Sony Apps Enabler: https://forum.xda-developers.com/an...-sony-apps-enabler-install-sony-apps-t3590477
Edit: Can't access to the Recovery. Orange LED appear , and after 5 second the phone is restarting.

I also tested the rom a little bit and so far so very good.
Bugs I found:
- video recording shows an error message
- sepolicy: when I set it to strict, I got the message that Magisk closed. After restart I have not got the message again. Maybe because of the question for superUser access.
@roland080: I can enter recovery via hardware button and via advanced start options(enabled in developer settings).

I am on aicp 12.1 . The ROM is great. Can I switch to this ROM with my kernel and twrp that is running on 12.1 and just flash the zip and gapps?

[ROM][OFFICIAL][kirin][10] LineageOS 17.1

oh btw you might want to use this TWRP for flashing my builds.

LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
I didn't expect you here mr Luk. I'm gonna test it when I will be at home. I'm glad that Kirin got such a developer

Problem Resolved.
Problem Resolved.

AlexDaBoii said:
Hello! So I tried to install a custom rom called Lineage OS, version 17.1 unofficial for my SOny Xperia 10 through TWRP custom recovery. I then tried installing the GApps and then rebooted the system. Then it came up with a prompt saying that the OS was corrupted and then to factory reset it. I did just that, and then LineageOS booted up just fine. However no Google Apps could be seen. I then tried to boot in to TWRP custom recovery, however it came up with the LineageOS recovery instead. I then tried to flash TWRP and managed to get it up and running, but when I rebnooted the phone, it just brought me in a boot loop.
I tried for hours to fix it and the I finally managed to flash TWRP again, however all of my save files were gone. I then tried to flash the Stock ROM for the Xperia 10 to the "system" folder and then my device powered off. I tried to power it on again and then it came up with a prompt saying "Your device is corrupt. It can't be trusted and will not boot. Powering off in 5 sec.". I got really freaked out at this point and did not know what to do. I know that I am an idiot for doing this, but if there is any fix at all for this that anybody can tell me, then I would be very thankful.
Click to expand...
Click to collapse
If you join irc I may be able to help you:
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev

Flawless on I3123 so far. Really appreciate the work on this device.

Has somebody tried this on I3113?
Are all components working fine?

xXqepXx said:
Has somebody tried this on I3113?
Are all components working fine?
Click to expand...
Click to collapse
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.

LuK1337 said:
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.
Click to expand...
Click to collapse
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!

thesandroid said:
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!
Click to expand...
Click to collapse
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).

What gapps do you recommend? I have an i3113 and after i flashed opengapps, i always get this weird "Android setup isn't responding" "System UI Keeps crashing" thing. What can i do?

LuK1337 said:
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).
Click to expand...
Click to collapse
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.

thesandroid said:
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.
Click to expand...
Click to collapse
Yeah that doesn't sound fun. Not going to bother.
On a sidenote, next build will fix Netflix Widevine L1.

Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.

zzz00072 said:
Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.
Click to expand...
Click to collapse
You build it exactly the same you'd be building an official device.

Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
LuK1337 said:
You build it exactly the same you'd be building an official device.
Click to expand...
Click to collapse

After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
zzz00072 said:
Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse

zzz00072 said:
After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
Click to expand...
Click to collapse
hint: themuppets.

Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
LuK1337 said:
hint: themuppets.
Click to expand...
Click to collapse

zzz00072 said:
Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
Click to expand...
Click to collapse
Yikes, you're doing so much stupid stuff...
Msg me on irc if you want it done anytime soon.

[ROM] [UNOFFICIAL] LineageOS 14.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]

Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- BACKUP, BACKUP, BACKUP, All will be WIPED!
2 - Unlock bootloader instructions here
3 - Flash the new mandatory TWRP Recovery
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package "ARM" > "7.1" > "Pico" or "Nano" visit OpenGAPPS
Working:
It Boots
Storages
Wifi
Audio
Charging
Offline Charging
Video decoding / Playback (i.e.: Youtube) up to 720p
Sensor: magnetometer: akm8963
Bluetooth (basic functions, pairing, file transfer, a2dp (Audio))
GPS - GNSS
DRM Widevine : For Netflix, Amazon Prime, etc
Front Camera: mt9m114_mipi_raw
Front camera: GC0339_RAW
ZRAM swap ( LZ4 )
etc ....
NOT Working:
Rear Camera: a5142_mipi_raw
Sensors: accelerometer (autorotation)
You tell me
Special Thanks
OMNI Rom
LineageOS
DerTeufel1980 & fire855 ( my Team mates from M.A.D)
GPL Compliance:
GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
ASUS ME173x device for LineageOS 12.1 & LineageOS 13 - GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
github.com
GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1
ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1 - GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / ...
github.com
--> "asus_n" branchs

FAQ
Small FAQ:
Q: How can i Unlock the Bootloader?
A: Instructions for Unlocking the Bootloader can be found here
Q: After locking the screen, the screen is all black, and /or flickering and I'm forced to reboot, how can I fix this?
A: If you have this issue, then your device uses the second screen/lcm hardware revision
( the lgld070wx3_dsi_vdo ), please use the second kernel.zip for this variant, it'll be added an second kernel . zip for people with this variant, on the download section with the ROM release
Q: how to flash this second kernel for the new hardware variant ?
A: After flashing the ROM, flash the second kernel afterwards
Q: Where are the Developer Options?
A: Go to Settings>About Tablet, and tap 7 times on the Build Number
Q: How can i enable the Advance Restart?
A: in the developer options, you can enable it there
Q: How can i change the WebView implementation?
A: in the developer options.
Q: How can i root this rom?
A: you can use Magisk
Magisk: v.23
note: Magisk builds v24.x and v25.x do NOT work / Not fully tested
Q: Do i really need to update recovery?
A: YES
--> If you already have Lineage13 TWRP release, your OK
Q: I can't flash this Rom on recovery "X Y Z" why?
A: You need to update your recovery to TWRP
Q: how to work with twrp?
A: in the first time TWRP boots, it'll ask if you want to allow modifications, slide to YES
Q: how to wipe and flash in twrp?
A: Go "mount" and mount "system"
then go "wipe" > and wipe dalvik / cache / data / System
Q: How can i flash the new recovery?
A: If you already have an custom recovery installed:
Download the new TWRP recovery zip
flash the new recovery
reboot to recovery again, TWRP should be now installed
If you don't have any custom recovery installed:
- You can extract the "recovery.img" from the .zip
- Open an terminal
- Boot to fastboot mode, and type:
Code:
fastboot flash recovery recovery.img
then reboot:
Code:
fastboot reboot
Q: I Love your work, how can i thank you?
A: You can press the "Thanks" button, and if you wish, you can pay me a beer
..

Changelogs
Build 20220808
First Release
Build 20220820
Fix Advance reboot Menu (removed: reboot bootloader, isn't used)
ZRAM: Increase disk size to 768MB (recommended for 1GB Ram devices)
ZRAM: Boost performance: Actually enable LZ4 compression ( inline with current kernel)
ART: Update flags (Drop old flags, Drop uneeded dex2oat, force dex2oat not to use swap file ,etc)
Enable Pinner Service: pinning files into memory, boot oat, services dex (Improves system performance)
Removed LOW RAM flag:
- Device tree & kernel has been greatly optimized
- We finnaly have working ZRAM swap since los 13, working great
- There's no need to cripple the device out of useful features like MultiUser
Fix GPS
Fix DRM Widevine : For Netflix, Amazon Prime, etc
Fix Bluetooth (basic functions, pairing, file transfer)
- Bluetooth a2dp (Audio) is still broken (work in progress)
Fix Front Camera: mt9m114_mipi_raw / GC0339_RAW ( photos )
Some optimizations done at frameworks
Build 20220911
Fix Bluetooth a2dp (Audio)
Removed Useless LineageOS apps for more free RAM
WLAN: Update blobs from MediaTek ALPS N1
LCM: lgld070wx3_dsi_vdo: Fix flickering on resume, discharge ESD properly
Improved System Animations
Fix FWB SysUI / StatusBar, power leak
Fix FWB ArraySet crash
Fix FWB backup schedule system_server crash
Fix FWB batterySendBroadcast not synchronized issue
Fix FWB SystemUI FC due to Google Assistant
Fix FWB hwui: skip empty frame
Fix FWB system server crash caused by CME in usage stats
Fix FWB batterySendBroadcast not synchronized issue
Fix FWB PackageManagerService user CE data failed
Downloads
TWRP 3.1.1
TWRP_3.1.1_ME173X.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20220911
https://www.androidfilehost.com/?fid=14871746926876822197
If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220911
https://www.androidfilehost.com/?fid=14871746926876822201
Older Builds
Build 20220808
https://www.androidfilehost.com/?fid=15664248565197201611If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220808
https://www.androidfilehost.com/?fid=15664248565197201606
Build 20220820
https://www.androidfilehost.com/?fid=15664248565197206369
If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220820
https://www.androidfilehost.com/?fid=15664248565197206372

The year is 2082. Society as we know it has collapsed and the world is but a nuclear wasteland. I haven't seen or talked to another human in weeks. Food is scarce and shelter is hard to come by... But life lingers on, even if just for a while longer, nature tries to heal itself with the little sunlight that manages to reach the ground through the dense clouds of soot. Last night I heard screams coming from the forest of dead pine trees, east of the abandoned glass factory. I'm not sure if they were human screams or the calls of an alternate, but I'm not eager to find out... I must hurry and head north, this place is no longer safe. To add insult to injury, I broke my only weapon while I was trying to cut down a few tree branches to light a fire... until I find materials to fix it, my possessions are my pet dog Alex, an half eaten can of beans and my ME173X running Android 69 with the latest security updates.

I'm waiting for the continuation and publication of this work in the form of a book.

Haha
This made my day
Cheers

superdragonpt said:
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- BACKUP, BACKUP, BACKUP, All will be WIPED!
2 - Unlock bootloader instructions here
3 - Flash the new mandatory TWRP Recovery
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package "ARM" > "7.1" > "Pico" or "Nano" visit OpenGAPPS
Working:
It Boots
Storages
Wifi
Audio
Charging
Offline Charging
Video decoding / Playback (i.e.: Youtube) up to 720p
Sensor: magnetometer: akm8963
etc ....
NOT Working:
Bluetooth
GPS - GNSS
DRM Widevine : For Netflix, Amazon Prime, etc
Front Camera: mt9m114_mipi_raw
Front camera: GC0339_RAW
Rear Camera: a5142_mipi_raw
Sensors: accelerometer (autorotation)
You tell me
Special Thanks
OMNI Rom
LineageOS
DerTeufel1980 & fire855 ( my Team mates from M.A.D)
GPL Compliance:
GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
ASUS ME173x device for LineageOS 12.1 & LineageOS 13 - GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
github.com
GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1
ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1 - GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / ...
github.com
--> "asus_n" branchs
Click to expand...
Click to collapse
This is great! Thank you so much! I never expected so much support for this tablet...
Unfortunately, I really need GPS so I have to wait for another build...

Thank you very much for providing builds for this tablet! The 13 build really helped us a lot, as our 2-year-old could watch downloaded Peppa Pig episodes from Netflix during long vacation drives. Although I did had to download a previous major version of the Netflix APK to get it to work on Android 6.
As this version doesn't have Widevine DRM, Netflix won't work, I guess. The current version of Netflix from the app store needs at least Android 7, so it would be nice if this new build would also support that in the future. Is it possible to flash that somehow, or would you need to compile that during build-time? If so, it that planned, or are there any technical difficulties regarding that?

New Build is up
Build 20220820
Fix Advance reboot Menu (removed: reboot bootloader, isn't used)
ZRAM: Increase disk size to 768MB (recommended for 1GB Ram devices)
ZRAM: Boost performance: Actually enable LZ4 compression ( inline with current kernel)
ART: Update flags (Drop old flags, Drop uneeded dex2oat, force dex2oat not to use swap file ,etc)
Enable Pinner Service: pinning files into memory, boot oat, services dex (Improves system performance)
Removed LOW RAM flag:
- Device tree & kernel has been greatly optimized
- We finnaly have working ZRAM swap since los 13, working great
- There's no need to cripple the device out of useful features like MultiUser
Fix GPS
Fix DRM Widevine : For Netflix, Amazon Prime, etc
Fix Bluetooth (basic functions, pairing, file transfer)
- Bluetooth a2dp (Audio) is still broken (work in progress)
Fix Front Camera: mt9m114_mipi_raw / GC0339_RAW ( photos )
Some optimizations done at frameworks
cheers

Which Lineage version is the fastest?

bravur said:
Which Lineage version is the fastest?
Click to expand...
Click to collapse
Lineage !4 is on-pair with LOS13.
Lineage14 is currently the best if you ask me

New Build is up
Build 20220911
Fix Bluetooth a2dp (Audio)
Removed Useless LineageOS apps for more free RAM
WLAN: Update blobs from MediaTek ALPS N1
LCM: lgld070wx3_dsi_vdo: Fix flickering on resume, discharge ESD properly
Improved System Animations
Fix FWB SysUI / StatusBar, power leak
Fix FWB ArraySet crash
Fix FWB backup schedule system_server crash
Fix FWB batterySendBroadcast not synchronized issue
Fix FWB SystemUI FC due to Google Assistant
Fix FWB hwui: skip empty frame
Fix FWB system server crash caused by CME in usage stats
Fix FWB batterySendBroadcast not synchronized issue
Fix FWB PackageManagerService user CE data failed

First of all: thank you so much for giving us Andoid 7 for this old thing!
I just found out that Adaway won't install from F-Droid:
Error installing AdAway
Parsing apk file failed! Maybe minSdk of apk is lower than current Sdk? Look into logcat for more specific warnings of Android's PackageParser.

My observations of LG kernel up to 20220911
- battery charging VERY slow
- rotation sensor not working
- camera not working
- fast stock, slow with GAPPS
Maybe these are already on the todo list. Great to have A7 on this still usable tablet.
Cheers

pimisen said:
First of all: thank you so much for giving us Andoid 7 for this old thing!
I just found out that Adaway won't install from F-Droid:
Error installing AdAway
Parsing apk file failed! Maybe minSdk of apk is lower than current Sdk? Look into logcat for more specific warnings of Android's PackageParser.
Click to expand...
Click to collapse
Yup that's normal, im also an user of it
see here: https://github.com/AdAway/AdAway
"For devices older than Android 8 Oreo, use the version 4 of AdAway."
Get the last version here:
Releases · AdAway/AdAway
AdAway is a free and open source ad blocker for Android. - AdAway/AdAway
github.com
Version 4.3.6 > on Assets download " AdAway-4.3.6-200726.apk "
cheers

tweakradje said:
My observations of LG kernel up to 20220911
- battery charging VERY slow
- rotation sensor not working
- camera not working
- fast stock, slow with GAPPS
Maybe these are already on the todo list. Great to have A7 on this still usable tablet.
Cheers
Click to expand...
Click to collapse
hi
rotation sensor not working :
Yeah this is stated on the "not working" status " > Sensors: accelerometer (autorotation)"
I could never fixed this sensor on my kernel
battery charging VERY slow
The device can be very picky with chargers, with the stock charger it can charge up to 1.2 AMP @ 5v
fast stock, slow with GAPPS
Yeah GAPPS really have an huge impact on devices, it runs really smooth without GAPPS installed
Google sucks
camera not working
This is very nice report ( Thanks ) every single user that reported me the front camera isn't working has an device with the LG screen...
I just bought my third ASUS ME173X and got it yesterday ( since my kid broke the second one .. )
unfortunately all my tablets have the same nt35521 Screen ( really hopping to grab an LG variant ) for testing :/
cheers

How can I find out, what screen our tablet has?

Plz help! I can't root this rom, can you give a manual or something? I've tryed everything

sus ඞ
This is with the tablet plugged into the wall 24/7, sometimes it gets tired and stops charging
Don't mind the second pic, that's just it being used as a wireless monitor

bravur said:
How can I find out, what screen our tablet has?
Click to expand...
Click to collapse
You need to be running any of stock firmware with root rights.
There's many apps that facilitate the task like "deviceinfohw" , give the app root on settings, and on the main page it'll show you what LCM you device has.

Database Info

welcome