Database Info

Cyanogenmod 13 for LG G Pro 2 D838, CM14.1

Other stuffs:
1. Increase volume on older cm13 builds - https://drive.google.com/file/d/0B0LH2ajSZjDpY3JuSm9ERmkyLWs/view?usp=sharing
I also try to fix lineout but not test lineout.
2. Remove black rectangle on incoming call photo in dialer( tested on CM13) - https://drive.google.com/file/d/0B0LH2ajSZjDpeWpwbFdkWFZmMGs/view?usp=sharing
CM14.1 08.12.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://mega.nz/#!IEt2hAwT!d8muFzv47Ot7a8aMWn59wGLdrUWG9iuGWAj4r7JIFuc
i don't test this Rom - only build.
CM13 08.12.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://mega.nz/#!MNNQWABB!tsc_dxAW8_WWvfyVOGflOoQRJjk3l3z6mqMro8_cojQ
Kernel, devtree, cm updates.
i don't test this Rom - only build.
CM14 19.09.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpelFkNE92MVBzVWs/view?usp=sharing
First build, only for testing. Now i don't have device on the hands.
i don't test this Rom - only build.
Small CM14 russian screencast - https://drive.google.com/file/d/0B0LH2ajSZjDpcGNSbmlEdElNZEU/view?usp=sharing
Now i update device sources and add cm 14.1 tree.
Manifest for cm 14.1
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xenius9/android_device_lge_d838" path="device/lge/d838" remote="github" />
<project name="xenius9/android_device_lge_b1w-common" path="device/lge/b1w-common" remote="github" />
<project name="xenius9/proprietary_vendor_lge_b1w" path="vendor/lge" remote="github" />
<project name="xenius9/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" />
<project name="CyanogenMod/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
Old Manifest:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xenius9/android_device_lge_d838" path="device/lge/d838" remote="github" revision="cm-14.0"/>
<project name="xenius9/android_device_lge_b1w-common" path="device/lge/b1w-common" remote="github" revision="cm-14.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.0"/>
<project name="xenius9/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-14.0"/>
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.0"/>
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.0"/>
<project name="xenius9/proprietary_vendor_lge_b1w" path="vendor/lge" remote="github" revision="cm-14.0"/>
</manifest>
CM13 build instruction:
1. Install ubuntu
2. We start with setting up the build environment:
First, start with installing this:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-
utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev
lib32readline-gplv2-dev lib32z1-dev
3. Once that is done, we go about installing JDK-7 since that's the one that works for lollipop
sudo apt-get install openjdk-7-jre
sudo apt-get install openjdk-7-jdk
4. Then we install the Android SDK for some useful stuff:
sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers
android-tools-adbd androidsdk-ddms android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview
5. Once all that is dealt with, we can move on to the repo tool. That's what will get your CM repos syncing:
mkdir -p ~/bin
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
and then, reboot to apply the changes.
Now for the interesting part
Not really, actually.
Time to yank the CM source code.
Create a working directory where you're going to sync all the sources and do the dirty stuff.
For this guide, we'll call the working directory "cm13"
Create the directory by running
mkdir cm13
enter your working directory by typing
cd cm13
6. Inititialize the repo by throwing in:
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
Wait for all the activity in the terminal to cease. And then type in:
repo sync
if needed post user information when promted
while the stuff is downloading, grab a ginger ale, or a cup of coffee and admire your handiwork. If you're the impatient type, find a generous
dose of your favourite sedative, and knock yourself out for a few hours. When you're up again, you'll be faced with one of two things. Either
your repos have synced successfully (yay!), or you get some nasty fetch errors. If it's the latter, then, Voila! You've just faced your first
ever compiling frustration. Take some time out and break a few things, drive the neighbours crazy and then return to the PC and knock in:
repo sync -j1
This should (hopefully) work perfectly as long as you have an internet connection worth paying for. If not, then compiling probably isn't for you
anyway.
7. Once all that stuff's over, create a folder called
local_manifests
in the .repo folder, and then make a new file in that folder called
roomservice.xml
open roomservice.xml using gedit, and add the following:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xenius9/android_device_lge_d838" path="device/lge/d838" remote="github" revision="cm-13.0"/>
<project name="xenius9/android_device_lge_b1w-common" path="device/lge/b1w-common" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0"/>
<project name="xenius9/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-13.0"/>
<project name="xenius9/proprietary_vendor_lge_b1w" path="vendor/lge" remote="github" revision="cm-13.0"/>
</manifest>
Then cd back to your working directory
cd ~/cm13
8. YOU'RE READY TO ROLL!
Finally, to build, type in:
. build/envsetup.sh
brunch d838
9. Wait for the build to compile. Usually takes about 2-3 hours on an okay PC. You'll find your completed build in cm13/out/target/product/d838.
The next time you want to build, run:
make clean
repo sync
. build/envsetup.sh
brunch d838
.. and so on.
Happy Building!
CM13 24.10.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpV1BGVjNycFBwSzg/view?usp=sharing
news: CM updates, kernel updates
i don't test this Rom - only build.
CM13 19.09.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpZFFKaXJ4V0tWems/view?usp=sharing
news: CM updates, kernel and devtree updates
i don't test this Rom - only build.
CM13 24.08.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpTUFGVkRQbGlmb2s/view?usp=sharing
news: CM updates, kernel and devtree updates, possible fix offline charging
i don't test this Rom - only build.
CM13 22.08.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpbGJqVnI5aEpDbDA/view?usp=sharing
news: CM updates, kernel and devtree updates, possible fix some errors
i don't test this Rom - only build.
CM13 18.08.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpZFF6NG50RGwtVjA/view?usp=sharing
news: CM updates, kernel and devtree updates.
i don't test this Rom - only build.
CM13 21.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpS0JFMGdDeGhzUDA/view?usp=sharing
SuperSu Kernel with voltage control for 19-21.07 builds - https://drive.google.com/file/d/0B0LH2ajSZjDpeDA5RTdnSWFBT1k/view?usp=sharing
Kenel with voltage control for 19-21.07 builds - https://drive.google.com/file/d/0B0LH2ajSZjDpSHdxOTExOFRQUEk/view?usp=sharing
news: CM updates, voltage control in kernel.
i test this Rom - boot - ok, calls - ok.
Older builds and info:
CM13 19.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpbmRHN2IxSk5STG8/view?usp=sharing
SuperSu Kernel - https://drive.google.com/file/d/0B0LH2ajSZjDpMVpmd24yXzNuQzg/view?usp=sharing
news: CM updates, cosmetic fix for charging speed, fix wakeup when proximity covered, fix errors in voice and gps config, try to add line_out.
i test this Rom - boot - ok, calls - ok.
CM13 13.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpUGxCSWR3cDFWYkk/view?usp=sharing
news: CM updates, wifi and BT mac from misc partition, increased audio volume, viper4android preinstalled(enable root in dev options and use selinux mode changer for set selinux to permissive), other camera wrapper(from g3) and added 2160p profile for video recording, fixed fstab.
i test this Rom, mac`s reading from misc and set ok for me - no random mac.
CM13 04.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpdmlwMkNzUG5KdkE/view?usp=sharing
news: CM, devtree and kernel updates
i don`t test this Rom, only build(with no errors)
CM13 6.06.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/open?id=0B0LH2ajSZjDpdHRJOXo2OEF2dVE
Advanced ROM (integrated SuperSu, Viper4Android) - https://drive.google.com/file/d/0B0LH2ajSZjDpdVNYODVXTXplOUk/view?usp=sharing
Patched kernel for SuperSu - https://drive.google.com/file/d/0B0LH2ajSZjDpeFNnMGlzTFkwU28/view?usp=sharing
A-GAPPS - see here - http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606 (need internet connection for setup, you must flash gapps immediately after flashing ROM)
news: CM and kernel updates
CM13 26.05.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpWER6dHZpcFl3ZjQ/view?usp=sharing
news: CM and kernel updates, added quickcircle from g4 - for testing.
CM13 25.05.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpTDJBRUFVYVZEekU/view?usp=sharing
news: CM updates, added echo reference to mixer_patchs, fixed double tape to wake -now it`s worked)))
ROM tested - boot normal, sounds play , calls - calling, Double Tap to Wake worked Oooo )))
Patched kernel for SuperSu - https://drive.google.com/file/d/0B0LH2ajSZjDpeTA1OUdUS2JNSVk/view?usp=sharing
For China`s users - all SDCard filesystem types supported, not only fat32
CM13 24.05.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpeDczM1JWeDBrSk0/view?usp=sharing
news: CM updates, kernel updates, mixer_patchs levels up, try to add dt2wake(not tested by me - for devs)
i build this ROM only, not test - no time.
CM13 10.05.2016 build
Advanced ROM (integrated SuperSu, Viper4Android, A-Gapps(you need flash modem and loader if you on kitkat rom now)) - https://drive.google.com/file/d/0B0LH2ajSZjDpNFg0TWJxd1VNamc/view?usp=sharing
Full ROM (for flashing over any ROM)(modem, rpm, kk loader included) - https://drive.google.com/file/d/0B0LH2ajSZjDpc0VETkk3dk5zX3M/view?usp=sharing
Stock ROM (as is, no loaders, modem,etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpYWkyMnVEZXpodzA/view?usp=sharing
Modem and loader only (only modem, rpm and kitkat loader) - https://drive.google.com/file/d/0B0LH2ajSZjDpeXNnRFhFRlFGbHc/view?usp=sharing
Supersu kernel - https://drive.google.com/file/d/0B0LH2ajSZjDpWjBYRW5hcmp3ZUk/view?usp=sharing (flash after you flash Supersu installer)
news: CM updates, some kernel updates, revert mixerpath config
CM13 04.05.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpYmh4bEFCSG1RNEE/view?usp=sharing
Full ROM (for flashing over any ROM)(modem, rpm, kk loader included) - https://drive.google.com/file/d/0B0LH2ajSZjDpNjJoZS1LWFo0QW8/view?usp=sharing
news: CM updates, some devtree and kernel updates, audio policy updates
CM13 29.04.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpMTA1RG45cko4d0U/view?usp=sharing
news: CM updates, some devtree updates
TWRP 3.0.2-0 Recovery (port) for LG G Pro 2:
https://drive.google.com/file/d/0B0LH2ajSZjDpalVsQmpoTDBfTUE/view?usp=sharing
CM13 21.04.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpWnlzVEg5WjZUMk0/view?usp=sharing
news: CM updates, 32 dip navbar
if you want selinux permissive - install supersu and kernel for SuperSU
if you want to use SuperSu, download it from https://download.chainfire.eu/927/SuperSU/RC-SuperSU-v2.70-20160314191951.zip and AFTER you flash SuperSu flash this:
Kernel for SuperSU https://drive.google.com/open?id=0B0LH2ajSZjDpUDYwV2JsOWFGTWM (bumped kernel patched for supersu)
CM13 18.04.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpT2piYVRyeXpOSm8/view?usp=sharing
news: NFC fixed, kernel and devtree updates, possible ir blaster working too.
if you want to use SuperSu, download it from https://download.chainfire.eu/927/SuperSU/RC-SuperSU-v2.70-20160314191951.zip and AFTER you flash SuperSu flash this: https://drive.google.com/file/d/0B0LH2ajSZjDpZGVTeTV1N1pZX3c/view?usp=sharing (bumped kernel patched for supersu)
ROM link - https://drive.google.com/file/d/0B0LH2ajSZjDpZkZDSU5sUzlReFk/view?usp=sharing
FOR KK BOOTLOADER!!!
What's not working: NFC, you tell me)))
What's working: microsd(fat32), charging, camera, bluetooth, GPS, sound, phones, calls, sensors.
How to flash(you need recovery - TWRP is better(marshmallow support)):
1. MAKE BACKUP!!!
2. Push baseband and ROM to sdcard (copy cm13 zip and LP Baseband to sd card)
3. Make WIPE dalvik, data,cache(from recovery)(advanced wipe in twrp)
4. Install lollipop baseband
5. Install ROM
Additional links:
KK Baseband and kernel - https://yadi.sk/d/nVx3rb7MpheN9
LP Baseband and kernel(bumped)+KK bootloader - https://yadi.sk/d/_hz4jdQhpheNn
How to Restore previous ROM:
1. if you have KK based Rom - flash KK Baseband and restore ROM from Recovery
2. if you have LP based Rom - flash LP Baseband and restore ROM from Recovery

hell yeah, it amazing fast ever, testing now on f350s, seems everything good but nfc, will report later.
update: i think this rom can daily use for me live without double tap and nfc/IR, no fc and very fast on f350s.
update 2: few days gone, everthing good battery good no any fc. @xenius9, can you add IR remote in ROM further?
http://forum.xda-developers.com/lg-g3/themes-apps/app-quickremote-port-aosp-t2929146

BUG: double tap screen and nfc.
Testing on d838.

Also testing on D838, for now, only NFC and DT2W doesn't works.

if I'm on KK
i just flash the KK Baseband and kernel then flash your rom???

ares. said:
if I'm on KK
i just flash the KK Baseband and kernel then flash your rom???
Click to expand...
Click to collapse
Flash lollipop baseband and rom.

i just installed it..noob question where can i download gapps for cm13? i tried open gapps its not working when i flash it tnx..what gapps did you use guys? tnx
.i would never imagine we will have a cm13 marshmalow for lg g pro 2! awesome xenius9

pato2015 said:
i just installed it..noob question where can i download gapps for cm13? i tried open gapps its not working when i flash it tnx..what gapps did you use guys? tnx
.i would never imagine we will have a cm13 marshmalow for lg g pro 2! awesome xenius9
Click to expand...
Click to collapse
You can download gapps below
http://opengapps.org/
Sent from my LG-D838 using XDA-Developers mobile app

stevenhehe said:
You can download gapps below
http://opengapps.org/
Sent from my LG-D838 using XDA-Developers mobile app
Click to expand...
Click to collapse
tnx..no wonder it cant install my gapps for 5.0 not 6.01 heheh..downloading gapps for 6.01 now
---------- Post added at 03:41 PM ---------- Previous post was at 03:12 PM ----------
how to turn on root for this cm13 rom... i installed super su..binary cant be updated..im i doing wrong here? sorry as this is my first cm rom

pato2015 said:
tnx..no wonder it cant install my gapps for 5.0 not 6.01 heheh..downloading gapps for 6.01 now
---------- Post added at 03:41 PM ---------- Previous post was at 03:12 PM ----------
how to turn on root for this cm13 rom... i installed super su..binary cant be updated..im i doing wrong here? sorry as this is my first cm rom
Click to expand...
Click to collapse
You can enable root in development option
Sent from my LG-D838 using XDA-Developers mobile app

and lastly anyone tried installing xposed on this?

xposed work perfect.

xenius9 said:
Flash lollipop baseband and rom.
Click to expand...
Click to collapse
Lg camera knock code touch keys white background and small keys plzz
Sent from my LG-D838 using XDA-Developers mobile app

mydoom said:
xposed work perfect.
Click to expand...
Click to collapse
may i ask what xpose version did you use? 80?
---------- Post added at 09:28 PM ---------- Previous post was at 09:22 PM ----------
how did you install super su...everytime i install super su from playstore run binary it fails ...already turn on rooted on developer option..what shall i do tnx

pato2015 said:
and lastly anyone tried installing xposed on this?
Click to expand...
Click to collapse
i am using 81
pato2015 said:
may i ask what xpose version did you use? 80?
---------- Post added at 09:28 PM ---------- Previous post was at 09:22 PM ----------
how did you install super su...everytime i install super su from playstore run binary it fails ...already turn on rooted on developer option..what shall i do tnx
Click to expand...
Click to collapse
gone system>about phone>built number>10 time>develo mode>root access> open

Does cm13 support slimport/hdmi?
Sent from my LG-D838 using XDA-Developers mobile app

When using cm 13 ROM do we need to install super su or we can use the cm built in root app to handle rooting accept deny thing on our phone..?
---------- Post added at 02:12 AM ---------- Previous post was at 02:01 AM ----------
mydoom said:
i am using 81
gone system>about phone>built number>10 time>develo mode>root access> open
Click to expand...
Click to collapse
Thanks care for the link of xpose 81..how did you install? Just install apk alpha 4 and flash 81?
Updated...it works so well with cm 13

Im on LP5.0.1
Should i return to stock 4.4 before start? or i can start now

pato2015 said:
When using cm 13 ROM do we need to install super su or we can use the cm built in root app to handle rooting accept deny thing on our phone..?
---------- Post added at 02:12 AM ---------- Previous post was at 02:01 AM ----------
Thanks care for the link of xpose 81..how did you install? Just install apk alpha 4 and flash 81?
Updated...it works so well with cm 13
Click to expand...
Click to collapse
Why you guys love using xposed?
For me, I had used it several times and it just made my phone lag!
Sent from my LG-D838 using XDA-Developers mobile app

I think you need add kikat bootloader and lolipop baseband to your rom for anyone don't know how to flash it

[ROM][OMS7][Experimental]LineageOS 14.1 with extra open commits

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.
*
*/
This thread is no longer supported or updated! You can maybe still find new builds on my AFH, but no guarantees! I will let the original first post only for information.
Important information:
I made this thread in order to avoid the off topic in the official LineageOS thread by @dianlujitao (http://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850).
The ROM that I propose is an experimental build using the official LineageOS 14.1 commits with some extra stuff that are not yet merged for testing. In order to avoid issues with repopicking, I use my own repos that are forked from the official repos. You can find them at the end of the post.
The commits that are included which are not merged are:
Kernel modification in order to pass SafetyNet CTS check
OMS / Substratum (fully included using n-mr1 tree)
160327 160328 (kernel) --> Postponed
160726 163935 (device)
161956 (OMS extra stuff)
161709 (hardware_cyanogen)
Please be aware that I might be missing some commits, the easiest way is for you to check the repo commits
All new builds will be in LineageOS_OOS4.0.3_OMS. I will keep including basic OMS functionality until issues arrive. At that time, I will remove and stop supporting OMS.
Please be aware that this is for advanced users!
I share all of my building information in order to help the users know what is included and how to reproduce. However, if you share your builds, please quote this thread in order to give the correct credits to the correct persons.
New builds (after 2017/1/15) uses F2FS backported from 4.10 kernel, you may meet compatibility problems such as deadlocks. If you do, flash the modified TWRP from @arter97 or from @dianlujitao and choose "Wipe -> Format Data" to format (not just wipe) your /data partition. This will clean the entire /data partition, including the emulated sdcard, so don't forget to backup your data!. After that, your data partition will be formatted into ext4, if you want to keep using f2fs, just convert fs type normally in TWRP.
It is highly recommended to use the modified TWRP from dianlujtao because the TWRP kernel is the same as the Android kernel, including 4.10 F2FS, which keeps 100% compatibility with LineageOS 14.1. There's no guarantee that other TWRP author will use the right kernel. Btw, NEVER choose the outdated OFFICIAL TWRP, it's out of maintenance!
The following will not be supported here:
Custom kernels
Mods
Xposed
I am not a dev, I only build the ROM. This can be read by the real dev, @dianlujitao. If you find a bug, please attach a logcat. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
F2FS ROMs can have deadlocks or other issues, please use the new TWRP
Some OMS themes apparently don't work, can be linked to missing root for masquerade or substratum app (use SuperSU, not in-built root, uninstall and install Substratum app again)
Built-in root removed by LineageOS, flashable addon exists (https://download.lineageos.org/extras), only needed once apparently
Wifi calling doesn't work after reboot or airplane mode --> Need to toggle the switch in Settings to make it work again
OOS Camera port doesn't work (no postprocessing, low quality photos) --> Use HAL 1 with flashable zip (https://forum.xda-developers.com/showpost.php?p=70983628&postcount=1879)
other stuff
Installation:
Download the zip
Install a compatible Recovery (Modified TWRP)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset unless you want to dirty flash
Flash LineageOS
Optional: Install the Google Apps addon package (if clean flash)
Reboot
Roomservice + Building process
Here is the roomservice.xml of this ROM:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_oneplus_oneplus3" path="device/oneplus/oneplus3" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_kernel_oneplus_msm8996" path="kernel/oneplus/msm8996" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_vendor_nxp-nfc_opensource_Nfc" path="vendor/nxp-nfc/opensource/Nfc" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_vendor_nxp-nfc_opensource_frameworks" path="vendor/nxp-nfc/opensource/frameworks" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci" path="vendor/nxp-nfc/opensource/libnfc-nci" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TeamSubstratum/masquerade" path="packages/apps/masquerade" remote="github" revision="n" />
</manifest>
Here is the rough building process (all the repo updating, repopick conflicts, etc... are not shown):
Use LineageOS roomservice
Cleaning output directory
Sync repo and prepare repopick commands
Repopick open commits from LineageOS
Clean build directory (sometimes necessary)
Generate changelog
Prepare build
Config jack server + start server
Build ROM
Copy zip file to host and cleanup
Kill jack server
Download:
https://www.androidfilehost.com/?a=show&w=files&flid=75317
Version Information
Status: Nightly
Created : 2016-12 -13
Latest build: 2017-03-05
Changelog
Code:
Project name: device/oneplus/oneplus3/
* df7c1db Revert "op3: remove highspeed recording profiles"
* 13e4b5d op3: disable wpa_supplicant log spam
Project name: hardware/qcom/audio-caf/msm8916/
* 1e33348 hal: dolby: Only set C_KEY if ACDB License is enabled.
Project name: vendor/cm/
* 3a03129 OMS: Add masquerade for Substratum OMS themes
Credits
CM team
LineageOS team
Substratum team
@dianlujitao
@ivanich
@siankatabg
@Sultanxda
@miscom
@flo071
@arter97
@piats
@nicesoni_ash
everyone else that helped me
Source Code:
https://github.com/LineageOS
https://github.com/Matssa56

Thanks loved yesterday's build downloading.

Thanks mate, downloading now!

chazey2 said:
Thanks loved yesterday's build downloading.
Click to expand...
Click to collapse
Giocarro said:
Thanks mate, downloading now!
Click to expand...
Click to collapse
Feel free to give me your feedback!

currently, I'm running CM13 on my OP3, want to update to CM14, but I can't find any issue log. What are the current knows issues? Thanks

Good work bud rom is awesome

titan1655 said:
currently, I'm running CM13 on my OP3, want to update to CM14, but I can't find any issue log. What are the current knows issues? Thanks
Click to expand...
Click to collapse
I didn't out any issue log since the build is experimental. For now, the issues are the same as the official nighties without the echo problem.
An issue that can be present concerns the volume, it goes up or down in some apps or when you change the audio of the notifications in some apps, but I didn't experience it yet.
Other than that, there was the dev option that was freezing, but it is apparently fixed, don't know if it was a oneplus3 issue or if it was multi device.
That is about it on my end, didn't take a chance to look at the logs yet. Pleas be aware that this is an experimental build, it has some fixes that are not yet merged in the official CM build, for example the echo and GPS fix.

@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?

Gave this a go, but for me after flashing there were some strange things with the home key not responding that i hadn't had in previous builds. For me the 13th nightly seemed a bit more ineffective than previous so I'm back on the official 12th for now, but will keep an eye on this thread with interest. Thanks for contributing!

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?
Click to expand...
Click to collapse
A tad curious about you mentioning NFC, I noticed there are some issues with NFC on Nougat builds in general and Android Pay, is that something that may have been fixed with the merged caf code?

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?
Click to expand...
Click to collapse
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.
MisterCoolBeans said:
A tad curious about you mentioning NFC, I noticed there are some issues with NFC on Nougat builds in general and Android Pay, is that something that may have been fixed with the merged caf code?
Click to expand...
Click to collapse
The issue was heating and crashing of the NfC with the N blobs, but it has been fixed by merging the new version. I didn't test Android Pay because I don't have it in my country.

matssa said:
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.
The issue was heating and crashing of the NfC with the N blobs, but it has been fixed by merging the new version. I didn't test Android Pay because I don't have it in my country.
Click to expand...
Click to collapse
I'm willing to give it a test! :good: I'll download your build and try it.

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?
Click to expand...
Click to collapse
Just checked the repo to be sure before changing thanks for the heads up!

I'm facing some little issue that become showstopper as they break my daily usage:
1) HOME button long-press to turn OFF the display is not working consistently; most times I have to press it twice to trigger the action;
2) BACK button long-press is not customizable?!? I want it to trigger MENU action, but the option is not present;
3) there's no way to disable capacitive keys while gaming; not a deal breaker for most people I know, but my son yesterday went as far as crying because of false touches on capacitive keys during his brief gaming time.
Well, I guess I'm writing this to show appreciation for Matssa work and to ask whether you guys see any solution to these little but important glitches.

Sounds exactly the same issues I was facing meaning I can't use as a driver for the moment

New nightly on AFH, first post was updated.
Giocarro said:
I'm facing some little issue that become showstopper as they break my daily usage:
1) HOME button long-press to turn OFF the display is not working consistently; most times I have to press it twice to trigger the action;
2) BACK button long-press is not customizable?!? I want it to trigger MENU action, but the option is not present;
3) there's no way to disable capacitive keys while gaming; not a deal breaker for most people I know, but my son yesterday went as far as crying because of false touches on capacitive keys during his brief gaming time.
Well, I guess I'm writing this to show appreciation for Matssa work and to ask whether you guys see any solution to these little but important glitches.
Click to expand...
Click to collapse
Mmmh got any logs?
For the Home button, I have the same issue, I find some fpc hall errors. @dianlujitao, you can find a log here. Best bet is that we need to wait for the updated hall and blobs from the official OOS N ROM.
For the Back button, apparently it isn't customizable yet, I suppose it is the same issue in the official nightly. If you want to trigger the menu, you can use the recent apps button.
For the disable capacitive keys, this option was never in CM before, I don't think it will appear one day. Did you try with the on-screen navigation bar? I think this disables the capa buttons and they should dissapear while gaming (not sure about that last point). It may be possible to do something like that, but I think in an Xposed module, which is still not possible for Android N :/

bay91 said:
Sounds exactly the same issues I was facing meaning I can't use as a driver for the moment
Click to expand...
Click to collapse
What issues do you have? Do you have the same issues with the official nightly without the extra blobs? If so, can you please give us some logs?

matssa said:
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.
Click to expand...
Click to collapse
If "Developer settings" works in your build then you using old blobs.

ivanich said:
If "Developer settings" works in your build then you using old blobs.
Click to expand...
Click to collapse
How can it be possible??? Why, WHYYYY??? WHYYYYYYYYYY?? Where do you think I may have gone wrong? In the building process? I know the commits have been taking into account since the GPS is working, it wasn't on the CM official.
EDIT///
Furthermore, when checking github, a "hax" was found by Scott Hart by removing the OEM unlock and another stuff, and it was made in android_packages_apps_Settings, which isn't touched by the commit from @dianlujitao, correct? So if my guess is correct, we should have the same issue on CM official and unofficial, even with the new blobs, what I saw from the post is that @dianlujitao didn't ship lksecapp in his build: "Nice catch, maybe OEM unlock, as I didn't ship lksecapp in my experimental build".
If you use your own experimental build, do you have the same issue?

matssa said:
How can it be possible??? Why, WHYYYY??? WHYYYYYYYYYY?? Where do you think I may have gone wrong? In the building process? I know the commits have been taking into account since the GPS is working, it wasn't on the CM official.
Click to expand...
Click to collapse
cd to your BUILD_DIR/vendor/oneplus
and show output of
Code:
git status
and
Code:
git log -n 3
Official builds doesn't have this issue because using old blobs.
I have issue with Dev options only with new blobs.

[ROM] Unofficial LineageOS 15.1 [OPM7.181205.001] for ZTE Blade S6 (P839F30)

Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 15.1 for the ZTE Blade S6 aka P839f30.
This is the first beta release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable nano).
Please check this prop!
Click to expand...
Click to collapse
Changelog:
16.10.2019 - 2nd stable release:
los security patch level 05.10.
merge upstream kernel from oppo devices
kernel version 3.10.108
30.08.2019 - 1st stable release:
los security patch level 05.08.
use sdcard fs now
updated fs drivers
updated wifi driver
fix line-out, you can use it now
use deep-buffer for audio playback
23.12.2018 - 2nd beta release:
los security patch level 05.12.
cpu min freq. 200MHz, min cpu 0
correct modem and wcnss symlinks.
11.12.2018 - first beta release:
los security patch level 05.11.
standard features working.
Click to expand...
Click to collapse
Downloads
second stable release - 16.10.2019:
Google Drive or here.
first stable release - 30.08.2019:
Google Drive or here.
second beta release - 23.12.2018:
Google Drive or here.
first beta release - 11.12.2018:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: There is no weather provider available to download for los-15.1 - what to do now?
A: Search for it here on xda or see this post or use this download link.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
XDA:DevDB Information
Unofficial LineageOS 15.1 [OPM7.181205.001] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS 15.1
Version Information
Status: Stable
Current Stable Version: OPM7.181205.001
Stable Release Date: 2019-08-30
Current Beta Version: OPM7.181205.001
Beta Release Date: 2018-12-23
Created 2018-12-11
Last Updated 2019-10-16

The end of the year is coming and some will have a christmas feast before. So this is a small christmas gift for you - LineageOS 15.1 aka Oreo for our phone. Have fun with it.
In my opinion it is better than nougat.

Thanks!!!
Tested and no issues found
Great Rom:good:

Files error
There is an issue with files or smth. Some apps can't get the files (all permissions are given)

d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
Check if your build.prop has "ro.sys.sdcardfs=false" or check with terminal or adb shell:
Code:
getprop ro.sys.sdcardfs
it has to be false.
I have read about some problems with that and found it not to be working at the moment, so I disabled it.

d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
It´s true, with other file manager different from the stock (Root explorer / ES Explorer) I cann't see the files in storage.

lightwars said:
Check if your build.prop has "ro.sys.sdcardfs=false"
Click to expand...
Click to collapse
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)

d.alvick said:
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
Click to expand...
Click to collapse
Great that it could be resolved so fast. I will check, why the prop got not in or overwritten. For the second thing: I didn't know that, this is an android oreo thing?

lightwars said:
this is an android oreo thing?
Click to expand...
Click to collapse
Very similar error was in old LineageOS or miui builds for our device or in both of them, I don't quite remember. Tried it again just now, playback is fine... Maybe it depends on device's mood or smth with charging, but I can't repeat it

There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is

d.alvick said:
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
Click to expand...
Click to collapse
These are no bugs! There wont be an impact in performance. Go and look for a device tree which defines msm8939... The platforms msm8ôô916 and msm8939 aren't that different. Even qualcomm defines the values like this, have a look at the CAF. Some vendors habe a common device tree for both platforms, for example asus.
And the last thing the Hardware is 64bit, but the Software is 32bit,changing to armeabi-v8 will not make the Software be 64bit.

Works great so far. Thank you
PS: could unbrick my phone

Update in the OP. new beta release.

2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?

d.alvick said:
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
Click to expand...
Click to collapse
I try to answer your question, but I haven't any insight views or infos, should I could be barely wrong... Over time GApps have gotten more permissions ands task and also more GApps have been published. I think at first there was the syncing of contacts, calendar and sorts of thinks, than the geolocation services. Now we have backups or storage expansion through GApps and also tracking of your fitness, reading out sensor data of your phone. And maybe other sorts of thing, which should make your experience with a smartphone better, but also consums energy.
To emphasizes your feelings about GApps I attach a screenshot of my phone, you can see how often the google service triggers and alarm or wakeup in a span of some hours, roughly speaken every minute.
I stumbled across LKT, which should give you more screen on time. I have used it, but found mixed results. I also think that the battery optimization of 15.1 needs some time, but I could be also wrong.
At the moment I use the naptime app to get more usage, I'm afraid to say this will only help your device last longer, when not used in my opinion.

Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?

MouZ124 said:
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
Click to expand...
Click to collapse
Hi,
have you run the factory reset command from within the android settings menu?
So the device only boots the recovery, even if you select to start the system within TWRP, right?
In the TWRP terminal or from the adb shell with su permission you can try to reset all flags in the misc partition like so:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
You can also back the partition beforehand to be sure, nothing breaks.

Hello lightwars,
thank you for your answer
lightwars said:
have you run the factory reset command from within the android settings menu?
Click to expand...
Click to collapse
No, the Device starts automatically into TWRP after Lineage OS 15.1 has the Boot-Loop
lightwars said:
So the device only boots the recovery, even if you select to start the system within TWRP, right?
Click to expand...
Click to collapse
Yes, i can select Reboot - System, then i see the ZTE-Logo with vibration and then start the TWRP short after this Logo...
If i tipped this Command in the TWRP terminal it shows an Error:
Code:
dd: can't open '/sys/block/bootdevice/by-name/misc' : No such file or directory
I try to go back to the old Partition-Layout and try to flash CM12.1, stock-rom B15 (modifide for TWRP), LineageOS 15... nothing works
I try TWRP 3.0.2 and TWRP 3.2.3
I try to flash CM12.1 with other Kernels with is Modified for CM12.1 from the other thread but it fails too...
What else could I do?
Screen if i install a zip

Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden

MouZ124 said:
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
Click to expand...
Click to collapse
Sorry, my bad. It is not in sys, it is dev so this is the correct command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

[ROM] [UNOFFICIAL] LineageOS 15.1 for Shield Tablet OMX | Camera working

{
"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"
}
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_nvidia_device_shield-common
https://github.com/Scavenger-87/android_device_nvidia_shieldtablet
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.10.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 18.10.2021

Scavenger87 said:
View attachment 5308899
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_device_nvidia
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.5.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 14.05.2021
Click to expand...
Click to collapse
Thank You for breathing new life into this great little tablet!

Thanks for keep this device alive!

Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.

Thank you very much and nice job Scavenger for keeping our tablet up and running!

Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?

@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.

marrol said:
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
Click to expand...
Click to collapse
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.

ogremalfeitor said:
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
Click to expand...
Click to collapse
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.

Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1

summerstyle said:
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
Click to expand...
Click to collapse
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong

ogremalfeitor said:
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Click to expand...
Click to collapse
Maybe we have to patch boot.img from NVidia Stock Recovery 5.2 and flash this one?

ogremalfeitor said:
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
Click to expand...
Click to collapse
This is a separate blob update. What for do we need this?

marrol said:
Maybe we have to patch boot.img from NVidia Stock Firmware 5.2 and flash this one?
Click to expand...
Click to collapse
That's not it. The boot.img is unique to every ROM. It contains the kernel and the initial ramdisk (initrd, if you're interested in details search for that and there are a lot of interesting articles explaining the boot process of Linux and derivates like Android).
I know magisk modifies the initrd to sort of "inject" itself during that early boot process, but it doesn't make the system hang with other ROMs, hence before assuming it's a bug in magisk I'd like to know if anyone has any idea or if the ROM is missing anything that could cause this?

marrol said:
This is a separate blob update. What for do we need this?
Click to expand...
Click to collapse
I believe it has to do with outdated bootloaders, which will be the case for people who never used recent stock firmwares, and it's there should you have problems (but don't confuse bootloader with boot partition or boot.img that I mentioned in another post). I think the script in the Zip detects it when you flash in twrp and gives an error if necessary but please correct me if I'm wrong.

I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.

Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.

Hi everyone after a little vacation and some testing out of your reported issues this is what i found out so far:
Hworangg said:
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Click to expand...
Click to collapse
I installed that game on a Tablet with LOS 14.1 and LOS 15.1 and in both cases the Game crashes because it run out of memory. I did a quick test on my Rom with adding ro.config.low_ram=true to the build.prop which activate the Go Version of Android and decreased the usage of Ram this way .
The Game runs but it started to get really sluggish after around 30 seconds.
It seems this Game just needs more than the 2GB Ram this device can offer.
ogremalfeitor said:
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
Click to expand...
Click to collapse
After trying to flash many Versions of Magisk starting by 21.4 over 22.0 and the actual 23.0 via the TWRP Recovery Version (9.5.0_9-0) i mentioned in the Start Thread and trying to flash it with the Magisk App i also wasnt able to install Sucessfully Magisk without running into a Bootlop which is really a Bummer.
I dont know why this happends and i check my Kernel Logs i pulled with TWRP but for the moment we have to use the SU Addon by LOS.
Maybe it has something to do with that my build is signed with a personal key i will check that out.
summerstyle said:
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Click to expand...
Click to collapse
Thats just the Blob File that needs to be flashed when the Bootloader isnt updated to the latest Version (4.00.2016.04)
ogremalfeitor said:
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Click to expand...
Click to collapse
On some rare ocassions you get those same green artefacts on videos like you get with the LOS 16.0 Rom but at least in my case it happends once a week or so and it seems it have something to do with memory managment again.
My guess is that the tegra drivers arent working really well with Android Versions above Nougat (7.0) and this leads to a memory leak but like i said its just a guess by me maybe @Steel01 can say more about that.
I try to optimize the memory management in the future builds if possible.

Hi Everybody
I think its time to give you a little update of my work on this build
After i got a good example of the problems with the ram management of this device i was looking for a solution last few days and i began testing with the Android Go Settings as i mentioned in the last Thread.
With that settings i was able to start that Game mentioned by @Hworangg and i even was able to play it a bit as you can see on one of the added Screenshots below. But you could also see this Game is a real RAM Hog with needing up to 484MB at the last session i played but it is kinda playable you just have to stay in that Game and turn off every notification as it might crashes otherwise. Speaking of crashes while the GO Settings really helping on reduce the usage of Ram by the System itself and let the device take more Memory Pressure it also leads to freezes where you often have to Hard Reset the Tablet because it seems to not close the Main App when its in a Out of Memory Situation. This is something i have to invest more time and research even after i played a lot with the Dalvik VM Settings.
I also found out that my Personal Key Signature is the reason that the install of Magisk is leading to a Bootloop. Here i also have to figure out why this is happen and if its even possible to install Magisk on a Signed Custom Rom as you change out the BOOT.img on this Device to achieve that and it seems the Magisk installer isnt able to resign the File with my Key.
TLDR:
I was able to set up my Build to use the optimized Android GO Settings to withstand more Memory Pressure so that Games like COC and heavy Browsing Sessions with lots of Tabs and Sites with a lot of Pictures doesn't crash that soon but it lead in both cases to a freeze of the whole Device.
The Magisk installer does not work when i sign my build with my own key.
For this Reason i decided to release a another Build for you to test with this Settings as a Nightly Release before i release my next Regular Build when the next Security Patch is out
You find it here : Nightly Build and i´m curious about your opinion.

Flashed the nightly onto a freshly wiped K1 along with opengapps and Magisk 23 using patched boot, no problems there. Video playback - Netflix played about as well as it could with level 3 widevine, with Jellyfin no obvious visual problems streaming 1080p over lan. Got hard freezes when running memory heavy apps (firefox, manga reader, 3d unity games) but it was expected.
Ended up downgrading back to factory stock Lollipop as the memory management is best there, even better than stock Nougat. But will keep an eye on your builds because the K1 could still be a great little tablet if the memory issues in newer versions of Android was fixed. Thank you for your hard work

[ROM][12L][UNOFFICIAL][libra] LineageOS 19.1

Important information:
This thread is for LineageOS 19.1 opensource builds for Mi 4C/4S. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
Permissive
Data Usage
Encryption
VoLTE (may fix)
Installation:
If you are on the stock OS, you will first need to unlock, then you need a custom recovery. You can get the recommended TWRP here.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on libra
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
AndroidFileHost
Changelog:
Changes for libra
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to Tipz Team
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@WJXXBSH, @TipzRickyCheung, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required:
Based On: LineageOS

Reserved

Nice... Longlast libra....

New Update!
20220518
Changelog:
Fixed DT2W
Added support for Dirac audio enhancement
Added support for Ambient Display
Added support for Edge Tap
Improved power consumption estimation
Download

If I only write to the system and gapps, then I can boot normally.
If magisk are written, the system cannot be boot on and restarts in a loop.

Correctly installed Rom Lineage 19 and MindTheGapps in xiaWRomi MI4C with 2Gb of storage. I have the TWRP Orange-Fox and the F2FS partition, I formatted the data and did a zip installation lineage-19.1-20220518-UNOFFICIAL-libra, deleted in system/system/fonts Notosans CJK in case there was not enough space to install MindTheGapps-12.1 .0-arm64-20220416_174313.zip.
Everything worked fine, after setting up the Google account.
Don't install Magics, because someone said it was incompatible.
If I find any error, I'll tell you about it. Thank you very much
Edit:I just installed Magisk v25.0 working perfectly.
Edit: After using it for two days with internet, Sygic, Google Maps, iGo and it works fine. The problems that I detect are: some unexpected restart, some delay on the unlock screen. The GPS connection is not precise, but it was already with the previous ROMs and the battery is fine.
Thank you very much for keeping MI 4c alive

thanks a lot

Hi @tipzrickycheung,
Thank you for the ROM.
I use Mi4c, 3GB RAM. I flashed recommended Firmware before I clean flash your ROM. What I've noticed is that the phone is getting quite hot when not much loaded. Also there are issues with Bluthooth. It happens each time I connect to Hi-Fi system and then I can't do much on the phone, it freezes. I have to restart it.

lousido said:
Correctly installed Rom Lineage 19 and MindTheGapps in xiaWRomi MI4C with 2Gb of storage. I have the TWRP Orange-Fox and the F2FS partition, I formatted the data and did a zip installation lineage-19.1-20220518-UNOFFICIAL-libra, deleted in system/system/fonts Notosans CJK in case there was not enough space to install MindTheGapps-12.1 .0-arm64-20220416_174313.zip.
Everything worked fine, after setting up the Google account.
Don't install Magics, because someone said it was incompatible.
If I find any error, I'll tell you about it. Thank you very much
Edit:I just installed Magisk v25.0 working perfectly.
Edit: After using it for two days with internet, Sygic, Google Maps, iGo and it works fine. The problems that I detect are: some unexpected restart, some delay on the unlock screen. The GPS connection is not precise, but it was already with the previous ROMs and the battery is fine.
Thank you very much for keeping MI 4c alive
Click to expand...
Click to collapse
Hi,
can you please help me with some installation instructions step by step?
I have downloaded everything and i prepared but i don't want to miss any essential step.
Thank you for your help.

AngelTudorache said:
Hi,
can you please help me with some installation instructions step by step?
I have downloaded everything and i prepared but i don't want to miss any essential step.
Thank you for your help.
Click to expand...
Click to collapse
I am not an expert to make a tutorial, my way of proceeding is: trial and error.
The process is the same that we use to install other previous ROMs.
My experiments are always with a device that I don't need, so if it doesn't work the first time, I try again ?????
If you have any specific problem, you can comment on it and we will try to find a solution.
Cheer up and good luck

Now i have TWRP installed and MIUI 9.5.2.0 (NXKCNFA) running on my device.
What should be the next step? To boot into TWRP and wipe the phone? Than i should copy the LineageOS 19.1 on the phone?

In this link you have instructions on how to do it.
Luck
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com

In this link you have instructions on how to do it.
Luck
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com

Do anybody know where to post kernel related questions? I've just got to the point of building the nethunter kernel tree for libra, but I can not boot the anykernel it generates. I know I'm missing parameters, but nethunter documentation is not helping, at all...