[ROM][8.1][STABLE] LineageOS 15.1 for P8 Lite

[ROM][8.1][STABLE] LineageOS 15.1 for P8 Lite - P8lite Android Development

Hi,
{
"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"
}
LineageOS 15.1 for Huawei P8 Lite (ALE-L21/23/02) & (CHM-U01/U03)
*** Stable Version ***
About
Code:
[CENTER]LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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. Lineage OS does still include various hardware-specific code, which is also slowly being open-sourced anyway.[/CENTER]
Working
Code:
[CENTER]* Touchscreen
* Adb / Mtp
* Audio
* Boot
* Bluetooth
* Internal/External storage
* Wifi
* NFC
* RIL
* Camera
[/CENTER]
Not Working
Code:
[CENTER]* Sensors (Read 2nd post)[/CENTER]
Installation
Code:
[CENTER]* you must also have this recovery installed
* go to TWRP and do a full wipe (system, data, cache, dalvik/art cache/cust) !
* install LineageOS ROM
* Flash gapps and root (optional)
* reboot system
* Enjoy !!![/CENTER]
Update
Code:
[CENTER]* copy the new update of LineageOS to Internal/External Storage
* reboot device to recovery
* wipe cache & dalvik cache
* install the new update of LineageOS
* reboot to System
* reboot system
* Enjoy !!![/CENTER]
Download
Code:
[CENTER]
[URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P8%20Lite/Oreo/LineageOS-15.1/"]Lineage 15.1[/URL]
LineageOS recovery
[URL="https://opengapps.org/"]Gapps[/URL]
[URL="tiny.cc/latestmagisk"]Magisk[/URL][/CENTER]
Kernel Source: android_kernel_huawei_hi6210sft
Please support my work, it's very important! Thanks
DONATIONS
Regards !

Reserved
FInally Oreo is stable !
Notes:
- Sensors are working but are making system unstable so I decided to disable them for now. You can use an app as workaround for sensors.
- RIL is working for the 90% of the time, if u want it working instead of reboot just shutdown and then boot. It's due to some race conditions I didn't look at it yet.
- Hotspot is working only if you use it from terminal (hostapd) and then enable from settings
- Battery life is like on Nougat but be sure to not invoke logd (doing adb logcat ; logcat ; dmesg ; etc) otherwise multiple logd will start and logspamming draining all the battery even on deepsleep.
If u invoke logd, like I said above, make sure you reboot to restore the default behavior.

thank's for your job?
hi am I in Los 14.1 do I still have to wipe or can I just upgrade to 15?
what does sensors mean?
the magisk connection does not work

Thank you very much! :good:

Dayum, bro. You're amazing. Thanks for all your efforts keeping this device alive!
Sent from my Mi Max 2 using XDA Labs
---------- Post added at 08:45 AM ---------- Previous post was at 08:42 AM ----------
Canna77 said:
thank's for your job?
hi am I in Los 14.1 do I still have to wipe or can I just upgrade to 15?
what does sensors mean?
the magisk connection does not work
Click to expand...
Click to collapse
Well, it means that the gyroscope, proximity and the others are not going to work correctly or even not work at all.
Sent from my Mi Max 2 using XDA Labs

dude I beleve in you, you can do it!
---------- Post added at 04:47 PM ---------- Previous post was at 03:59 PM ----------
also while trying to install it, error 7 and apperantly my device name is " ", basicly nothing, I know how to fix that but why does that happen?

ender1324 said:
dude I beleve in you, you can do it!
---------- Post added at 04:47 PM ---------- Previous post was at 03:59 PM ----------
also while trying to install it, error 7 and apperantly my device name is " ", basicly nothing, I know how to fix that but why does that happen?
Click to expand...
Click to collapse
Remove ota assert

DarkJoker360 said:
Remove ota assert
Click to expand...
Click to collapse
yeah I did that, I am saying just in case its something wrong
edit: ok any idea with what to compress this, if I compress it with mi explorer I just get invalid zip format

ok apperantly I have vendor image mismatch, i need huaweiale-l21 and I have it anyways who cares, RIL IS WORKING, I AM NOT JOKING, basicly it thinks my device is dualsim and my both sim cards are the same (cuz I am singlesim), I got in call, the voice was very high pitched and the other guy couldnt hear me, but when he called me everything was perfect, I can use my mobile data and I swear of god I am single sim (ale-l21), dude you did it! also I did a mustake with compresing my bad (the upper post I fixed it)
moreee edittt: when I restarted even when I called he hears me and I hear him, basicly RIL is working fine on single sim for me, I have no idea why but it also fixed my battery, yeah um ril is working on oreo.... dude thank you sooooo much :laugh: :victory:
UPDATE: well that didnt last long, after a factory reset and gapps the rom saw that I use singlesim and ril stopped working, thats stupid....
UPTADE2: WTH after few restarts the phone started thinking I use dualsim again and it ril started working again, then the phone turns off without reason and starts offline charging, this rom is hell of a mess, also after every restart there was different senario, 1 - no sim in the phone, thinks its single sim, 2 - there is a sim in the phone but no singnal, thinks its single sim, 3 - there are 2 sims in the phone and both are same, thinks it dualsim, this rom is a mess, also it doesnt let me boot in the rom without getting me into offine charging (when its plugged in), the vendor image warning is still there is still there

ender1324 said:
ok apperantly I have vendor image mismatch, i need huaweiale-l21 and I have it anyways who cares, RIL IS WORKING, I AM NOT JOKING, basicly it thinks my device is dualsim and my both sim cards are the same (cuz I am singlesim), I got in call, the voice was very high pitched and the other guy couldnt hear me, but when he called me everything was perfect, I can use my mobile data and I swear of god I am single sim (ale-l21), dude you did it! also I did a mustake with compresing my bad (the upper post I fixed it)
moreee edittt: when I restarted even when I called he hears me and I hear him, basicly RIL is working fine on single sim for me, I have no idea why but it also fixed my battery, yeah um ril is working on oreo.... dude thank you sooooo much :laugh: :victory:
UPDATE: well that didnt last long, after a factory reset and gapps the rom saw that I use singlesim and ril stopped working, thats stupid....
Click to expand...
Click to collapse
This is a good news man !
Unfortunatly I wasn' t ever able to test ril here as my NVMO sim card isn' t recognized even on N.
Gonna investigate more ! Thanks so much

DarkJoker360 said:
This is a good news man !
Unfortunatly I wasn' t ever able to test ril here as my NVMO sim card isn' t recognized even on N.
Gonna investigate more ! Thanks so much
Click to expand...
Click to collapse
yeah it is actually, but it still loops from the senarios (sim/nosignal, nosim/nosignal, 2sim/signal), also I cant really say offline charging is good because when I get in it i need to reboot like 5 times to boot into system without the phone turning off, anyways seems good for now, I am going back to my lineage 14.1 for now, maybe after a update I will test again also any idea why is this vendor warn, also overheating is gone (on rros oreo there was a lot of overheating)

ender1324 said:
yeah it is actually, but it still loops from the senarios (sim/nosignal, nosim/nosignal, 2sim/signal), also I cant really say offline charging is good because when I get in it i need to reboot like 5 times to boot into system without the phone turning off, anyways seems good for now, I am going back to my lineage 14.1 for now, maybe after a update I will test again also any idea why is this vendor warn, also overheating is gone (on rros oreo there was a lot of overheating)
Click to expand...
Click to collapse
Okay thanks for testing and reporting, actually let's ignore that warning

DarkJoker360 said:
Okay thanks for testing and reporting, actually let's ignore that warning
Click to expand...
Click to collapse
sure, also if you cant find any way to get ril working while the rom is thinking the phone its singlesim, wouldnt making the rom always think its dualsim be a solution? if you want me to test something just quote me, I check this forum 6 times daily.. lol also camera wasnt working for me, the stock camera gets stuck on taking pics, footej gets stuck on getting camera info, open camera gets stuck on loading

ender1324 said:
sure, also if you cant find any way to get ril working while the rom is thinking the phone its singlesim, wouldnt making the rom always think its dualsim be a solution? if you want me to test something just quote me, I check this forum 6 times daily.. lol also camera wasnt working for me, the stock camera gets stuck on taking pics, footej gets stuck on getting camera info, open camera gets stuck on loading
Click to expand...
Click to collapse
Well dual sim is one of the reason of rild crash for single sim, my idea is to nuke dual sim support in order to have first single sim base working good. Anyway is dual sim working on my Los 14.1?

DarkJoker360 said:
Well dual sim is one of the reason of rild crash for single sim, my idea is to nuke dual sim support in order to have first single sim base working good. Anyway is dual sim working on my Los 14.1?
Click to expand...
Click to collapse
Noone said it didnt, I assume it did

DarkJoker360 said:
Reserved
Some news about oreo: well as I can see it s pretty hard to have oreo stable as nougat but I won't give up on this, for now here is a test version. I hope to fix something more soon.
Off-charge is working!
Click to expand...
Click to collapse
Why aren't all leftover developers working on this project? NO, WE DON'T WANT 3 OREO BUILD AND ALL OF THEM HAVE FRAGMENTED THINGS WORKING. Lineageos is one of the biggest and best/stable, ALL of you should just work on this rom. You are like 3 devs left... We don't have 3 broken rom

D1stRU3T0R said:
Why aren't all leftover developers working on this project? NO, WE DON'T WANT 3 OREO BUILD AND ALL OF THEM HAVE FRAGMENTED THINGS WORKING. Lineageos is one of the biggest and best/stable, ALL of you should just work on this rom. You are like 3 devs left... We don't have 3 broken rom
Click to expand...
Click to collapse
I guess so, thats somewhere true, if everybody just started working on 1 thing, i guess it will be done even faster

D1stRU3T0R said:
Why aren't all leftover developers working on this project? NO, WE DON'T WANT 3 OREO BUILD AND ALL OF THEM HAVE FRAGMENTED THINGS WORKING. Lineageos is one of the biggest and best/stable, ALL of you should just work on this rom. You are like 3 devs left... We don't have 3 broken rom
Click to expand...
Click to collapse
Well actually I am doing this alone, who is still here? I can' t find someone who is interested on fixing this actually.

DarkJoker360 said:
Well actually I am doing this alone, who is still here? I can' t find someone who is interested on fixing this actually.
Click to expand...
Click to collapse
@Thespartann @Adi5 @XTutorials

DarkJoker360 said:
Well actually I am doing this alone, who is still here? I can' t find someone who is interested on fixing this actually.
Click to expand...
Click to collapse
well wasnt the viperos creator still working on something, he did say he is going to try pie on this dead thing, I doult it will be stable but we will see but if the s3 can boot pie there can be a way this can boot pie, of course they are so different but still if we can get stable oreo on this that would be awesome
---------- Post added at 07:01 PM ---------- Previous post was at 06:57 PM ----------
D1stRU3T0R said:
@Thespartann @Adi5 @XTutorials
Click to expand...
Click to collapse
wait didnt XTutorials give up?

Related

[ROM][UNOFFICIAL] Lineage OS 13 For Obake [22/2/17]

Installing now, will test and report my findings. Thanks for this! Been looking out for a while.
Edit:
So after using this rom for a day, I can say its quite stable for an alpha rom. It's fast, transitions and scrolling are smooth. I had absolutely no freezes, crashes or restarts. With some work, it can be a great rom!

This rom on my maxx is faster than my dt2 on 5.1..1 of course I havent added any apps yet but it is fast as ****

I can't wait to try it out soon. Just waiting to hear more try it out since my phone is a daily driver for work ><

I'm officially using it as my daily. The only thing that doesn't work that bothers me is the flashlight. Video recording actually works fine for me.
Device is a Droid Mini.

bigv5150 said:
This rom on my maxx is faster than my dt2 on 5.1..1 of course I havent added any apps yet but it is fast as ****
Click to expand...
Click to collapse
That is quite an endorsement for the ROM! As soon as the flashlight bug is fixed, I'm flashing!!
Sent from my XT1080 using Tapatalk

No issues so far. Loving it as a daily driver. A third party flashlight app works fine. Stock camera didn't work at first, installed google camera which worked. Then I tried the stock camera again and it works fine, video and all. Weird.
Multi-windows also works fine.
All in all, great job and keep the builds coming.

I couldn't help myself, installing Apps now but yeah, no joke, this thing is smooth... Almost as smooth as my iPhone 6s j/k
Edit: been running for a few hours and it has bogged down a bit with all the Apps I've installed. Still not bad but getting some serious lag with the keyboard as I'm typing this...
Edit2: lag seem to be from BT, I toggled it and everything went back to normal. It was BT'd to my car earlier.
Edit3: loving this ROM! Installed Xposed and Greenify. Battery life so far is pretty good. Will continue to monitor and report back.
Sent from my DROID MAXX using Tapatalk

Bootlooped on a clean flash....just got stuck on the CM logo. Anyone else? DL's are good, TWRP at 2.8.7.0.
Edit: I'm on my third clean flash and it appears to be stuck yet again. I can't get passed the logo. What am I doing wrong? I've re-downloaded, all flashes appear to be successful, I believe my TWRP to be the latest. How long did it sit on the logo? When it's over 10-12 minutes I start over. Should I be changing the system format in TWRP or something? I've flashed all the 5.1.x roms and back to stock a ton, so I must be missing something here that I'm unaware of.

kude87 said:
Bootlooped on a clean flash....just got stuck on the CM logo. Anyone else? DL's are good, TWRP at 2.8.7.0.
Edit: I'm on my third clean flash and it appears to be stuck yet again. I can't get passed the logo. What am I doing wrong? I've re-downloaded, all flashes appear to be successful, I believe my TWRP to be the latest. How long did it sit on the logo? When it's over 10-12 minutes I start over. Should I be changing the system format in TWRP or something? I've flashed all the 5.1.x roms and back to stock a ton, so I must be missing something here that I'm unaware of.
Click to expand...
Click to collapse
All I can think of is your bootloader. What version are you running?
Sent from my iPad using Crapatalk

Johnny Wong said:
All I can think of is your bootloader. What version are you running?
Sent from my iPad using Crapatalk
Click to expand...
Click to collapse
Good call, though I'm not sure what version I need. I'm on 30.BA.

kude87 said:
Good call, though I'm not sure what version I need. I'm on 30.BA.
Click to expand...
Click to collapse
I'm running the bootloader from 4.4.4 SU6-7. Forgot what the bootloader version is exactly. Running battery test right now and don't want to boot into recovery, lol
Sent from my iPad using Crapatalk

Johnny Wong said:
I'm running the bootloader from 4.4.4 SU6-7. Forgot what the bootloader version is exactly. Running battery test right now and don't want to boot into recovery, lol
Sent from my iPad using Crapatalk
Click to expand...
Click to collapse
I'm not sure then. I unlocked way back on 4.4 with sunshine, but I have flashed new versions of 4.4.4 along the way. I know I'm on at least 6-7, and I think I'm on 7-2. I thought if I unlocked ages ago, the bootloader does not update with new flashes? Now I'm just unsure of this all. If someone can chip in with bootloader info for flashing 6.0, that would be great.

kude87 said:
I'm not sure then. I unlocked way back on 4.4 with sunshine, but I have flashed new versions of 4.4.4 along the way. I know I'm on at least 6-7, and I think I'm on 7-2. I thought if I unlocked ages ago, the bootloader does not update with new flashes? Now I'm just unsure of this all. If someone can chip in with bootloader info for flashing 6.0, that would be great.
Click to expand...
Click to collapse
I just checked mine, it is 30.BA. Sorry, back to square one.
Sent from my iPad using Crapatalk

Johnny Wong said:
I just checked mine, it is 30.BA. Sorry, back to square one.
Sent from my iPad using Crapatalk
Click to expand...
Click to collapse
Thanks, I appreciate your help. Gonna be honest, I've never had more issue flashing stuff than I have with my Maxx. Seems there's always an issue, yet I always do it to myself with the want to flash stuff, ha.
Back on stock. If someone has any ideas of why it sticks on the CM logo, I'd be curious to try this again.

Can't thank you enough for this!! Flashing right now and will report back!
---------- Post added at 05:18 PM ---------- Previous post was at 04:51 PM ----------
I am on TWRP 2.8.4.0 and install went super smooth - Droid Mini.
I went ahead and flashed OpenGApss mini package and it was a bad call. Continuous messages popping up on reboot,
Setup Wizard has stopped.
Clock has stopped.
Play services stopped.
lol, read the instructions just now Will re-flash and report back
---------- Post added at 06:11 PM ---------- Previous post was at 05:18 PM ----------
Well, it went fine - had to flash both rom and gapps one after the other without booting (as mentioned in first post). Everything seems to work. I'll report back after trying it out extensively during the next couple of days hopefully. Thank you again

Hey kude, i had the same issue. I know sometimes cm doesn't play well with a clean install. I installed a old snapshot of cm12 from a clean wipe. Then did a factory wipe(data, cache, and dalvik. No system and internal storage wipe) and installed cm13 over that with marshmallow gapps. Booted fine after that.
Its been a few days and I've had no problems. Great rom

appletonpunk said:
Hey kude, i had the same issue. I know sometimes cm doesn't play well with a clean install. I installed a old snapshot of cm12 from a clean wipe. Then did a factory wipe(data, cache, and dalvik. No system and internal storage wipe) and installed cm13 over that with marshmallow gapps. Booted fine after that.
Its been a few days and I've had no problems. Great rom
Click to expand...
Click to collapse
This is good info, thanks! When I have some time to do this, I'll try your method. How's GPS on this new rom? All the 5.1.1 roms had finicky GPS and data hand off quirks for me.

I just wiped everything clean: Dalvik Cache, System, Data, Internal Storage & Cache. Then rebooted in Recovery and plugged in to PC and copied rom and gapps. Flashed both one after the other and rebooted. This went fine!
I'm using Google Maps and GPS seems to be behaving properly. Device is Droid Mini. The Speakerphone during calls and LED issue remains the same as in CM12.1. Speakerphone during the call does not work. It works as a mute button but neither sound goes out nor it gets in. Pressing it back restores the call. Notification LEDs does not work at all.

Yeah notification LED not working in CM 12.1 ..i hope thats working in cm 13. My device droid mini. Thanks Sir...

[Rom] [Hydrogen] CyanogenMod V13.0.1 for MI Max 32Gb

Screenshots

Reserved
Features That I added
> Boot in 30sec
> Fast Charging
> Dolby Included
> Clear audio during calls
> No heat >Multi Language
>Finger print
>0% Battery drop during stand by mode
> Many more

Reserved for feature

Another awesome rome thanks to u! But I would like to ask the same as Mokee if the video (I take alot of photos) is fully working? Because u said everything is working and 2 users reported that Video and GPS is not working..
Anyway thanks for all of your hard work for our amazing device!!

king123321 said:
Another awesome rome thanks to u! But I would like to ask the same as Mokee if the video (I take alot of photos) is fully working? Because u said everything is working and 2 users reported that Video and GPS is not working..
Anyway thanks for all of your hard work for our amazing device!!
Click to expand...
Click to collapse
Video is not working in this rom yet, at least not on my Helium. I flashed the video recording fix and for the past two hours I've tested video recording and it's working. Mobile data works for me on both sims without issues. Everything else seems to work. The on screen navbar is still there and the only way I can figure out how to get rid of it is download GMD Auto Hide Soft Keys from the Play Store to remove it. Adding qemu.hw.mainkeys=1 to the build.prop doesn't work. This is definitely progress though.

ajsmsg78 said:
Video is not working in this rom yet, at least not on my Helium. I flashed the video recording fix and for the past two hours I've tested video recording and it's working. Mobile data works for me on both sims without issues. Everything else seems to work. The on screen navbar is still there and the only way I can figure out how to get rid of it is download GMD Auto Hide Soft Keys from the Play Store to remove it. Adding qemu.hw.mainkeys=1 to the build.prop doesn't work. This is definitely progress though.
Click to expand...
Click to collapse
Leave device to sleep (screen off) for 5 minutes or so and see if video recording brakes... I bet it does.
@Annabathina
Thanks for your work.

ajsmsg78 said:
Video is not working in this rom yet, at least not on my Helium. I flashed the video recording fix and for the past two hours I've tested video recording and it's working. Mobile data works for me on both sims without issues. Everything else seems to work. The on screen navbar is still there and the only way I can figure out how to get rid of it is download GMD Auto Hide Soft Keys from the Play Store to remove it. Adding qemu.hw.mainkeys=1 to the build.prop doesn't work. This is definitely progress though.
Click to expand...
Click to collapse
Hey guys flash xposed
and install " Xperia/AOSP NavBar Buttons "
it will fix

nijel8 said:
Leave device to sleep (screen off) for 5 minutes or so and see if video recording brakes... I bet it does.
@Annabathina
Thanks for your work.
Click to expand...
Click to collapse
::good:

Thanks @Annabathina
Enviado desde mi MI MAX mediante Tapatalk

nijel8 said:
Leave device to sleep (screen off) for 5 minutes or so and see if video recording brakes... I bet it does.
@Annabathina
Thanks for your work.
Click to expand...
Click to collapse
Video recording is still working for me even after the device sleeping overnight. I'll check back tonight and let you know if it's still working.
---------- Post added at 01:32 PM ---------- Previous post was at 12:44 PM ----------
nijel8 said:
Leave device to sleep (screen off) for 5 minutes or so and see if video recording brakes... I bet it does.
@Annabathina
Thanks for your work.
Click to expand...
Click to collapse
Yep it finally stopped working.

ajsmsg78 said:
Video recording is still working for me even after the device sleeping overnight. I'll check back tonight and let you know if it's still working.
---------- Post added at 01:32 PM ---------- Previous post was at 12:44 PM ----------
Yep it finally stopped working.
Click to expand...
Click to collapse
Here is what I see... This rom is based on
@Principles of ...........................for Kernel
Click to expand...
Click to collapse
and that is the exact video recording behavior of all "Principles of..."(the second chinese guy who who still does Mi Max development) roms... I bet wifi/mobile network location works no problem...
The other OP Mokee rom is based on
@zhaochengw ...........................for Kernel
Click to expand...
Click to collapse
and again same behavior of all "zhaochengw"(the first chinese guy who abandoned Mi Max development) roms - video recording and wifi/mobile network location not working at all out of the box.
Tell me if I am wrong...

nice work ... is this rom work on 16gb & 2g ram model

nijel8 said:
Here is what I see... This rom is based on
and that is the exact video recording behavior of all "Principles of..."(the second chinese guy who who still does Mi Max development) roms... I bet wifi/mobile network location works no problem...
The other OP Mokee rom is based on
and again same behavior of all "zhaochengw"(the first chinese guy who abandoned Mi Max development) roms - video recording and wifi/mobile network location not working at all out of the box.
Tell me if I am wrong...
Click to expand...
Click to collapse
You are correct.

In this rom CM is the same as with the RR 5.7.1..... 3G not work for me.
Only work 2G (Edge), as in recent versions CM
APN is correct, that's not the problem.
I attached screenshots to look
In your Mokee rom works fine 3G

Downloading. You're a hero.

Can volte support this rom???
I am using reliance jio volte
Can support volte on this rom???
Plez replay

ajsmsg78 said:
Video is not working in this rom yet, at least not on my Helium. I flashed the video recording fix and for the past two hours I've tested video recording and it's working. Mobile data works for me on both sims without issues. Everything else seems to work. The on screen navbar is still there and the only way I can figure out how to get rid of it is download GMD Auto Hide Soft Keys from the Play Store to remove it. Adding qemu.hw.mainkeys=1 to the build.prop doesn't work. This is definitely progress though.
Click to expand...
Click to collapse
Hello, can you please share the ROM you flashed with files required for helium already included [emoji4]
Sent from my MI MAX using XDA-Developers mobile app

tombassi said:
Hello, can you please share the ROM you flashed with files required for helium already included [emoji4]
Sent from my MI MAX using XDA-Developers mobile app
Click to expand...
Click to collapse
Just take the firmware files from your device and put them in the CM13 rom zip, replacing the ones already in it. Then after you flash the rom, flash the video recording fix. Video recording will work but then stop working a short time after (it records but with choppy audio and skipping video) Restarting the phone fixes the issue until it happens again.

ajsmsg78 said:
Just take the firmware files from your device and put them in the CM13 rom zip, replacing the ones already in it. Then after you flash the rom, flash the video recording fix. Video recording will work but then stop working a short time after (it records but with choppy audio and skipping video) Restarting the phone fixes the issue until it happens again.
Click to expand...
Click to collapse
Thanks for your kind response ,but please how to do that my phone is 64GB version..
Sent from my MI MAX using XDA-Developers mobile app

[ROM][VNS-LX1][6.0.1][UNOFFICIAL] AICP for Huawei P9 Lite

Reserved
WORKING/NOT WORKING
-same as CM

Bugs?

How to delete the fingerprint

Does everything work or are there any bugs?

Raymen03 said:
How to delete the fingerprint
Click to expand...
Click to collapse
Settings > Lockscreen > Fingerprint > *Click on your registered fingerprint in the options* > Delete > *click OK*
Thijs van Hal said:
Does everything work or are there any bugs?
Click to expand...
Click to collapse
Simply put,it has the same bugs as CM(the 2.1MP cam limit and that is that?)

The Marionette said:
Simply put,it has the same bugs as CM(the 2.1MP cam limit and that is that?)
Click to expand...
Click to collapse
How about Bluetooth paring?

Care to elaborate on the difference between this and CM?

Hi,
I have a few questions:
1: Does this work on any P9 Lite variant (i have VNS-L21)?
2: Why is archive so big (almost 700mb)?
3: What Open Gapps package do you recommend to flash?
Tnx
tw1st3d ?

tw1st3d83 said:
Hi,
I have a few questions:
1: Does this work on any P9 Lite variant (i have VNS-L21)?
2: Why is archive so big (almost 700mb)?
3: What Open Gapps package do you recommend to flash?
Tnx
tw1st3d ?
Click to expand...
Click to collapse
1. Yeah,I declared the L"X"1 value to say that it is compatible with both L31 and L21.
2. AICP is "fatter" than CM since it has extra features,so no reason to panic. :silly:
3.I personally use the Pico package and then just install other Google apps which I need. That is the beauty of Open Gapps,you have several options.
Sent from my VNS-LX1 using Tapatalk

The Marionette said:
1. Yeah,I declared the L"X"1 value to say that it is compatible with both L31 and L21.
2. AICP is "fatter" than CM since it has extra features,so no reason to panic. :silly:
3.I personally use the Pico package and then just install other Google apps which I need. That is the beauty of Open Gapps,you have several options.
Click to expand...
Click to collapse
Thanks man for fast answer, the flashing will comence in the morning, i need a straight head for this ?
And sa for archive size i did not panic, just been curious because i had AICP on my galaxy s4 and it was half the size...
AICP rom is one of the best out there and it has sooo much customization options that i almost cry with happyness when i saw this post ?
And one more question: do i use ARM or ARM64 version of gapps?

Huawei P9 Lite have to use ARM64

Potato997 said:
Huawei P9 Lite have to use ARM64
Click to expand...
Click to collapse
Yeah,I thought everyone knew that...
Added it as well to the instructions! xD

@The Marionette thanks for this amazing work. There is some possibility that you can support the VNS-L23 variant? It is practically equal to the L31, with the only differences that do not have NFC support, the bands 4G are different and it has 2GB of RAM. Greetings.

Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...

tw1st3d83 said:
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
Click to expand...
Click to collapse
Someone on the question and answer thread had the same problem. See if any of his answers helps.
Sent from my Huawei P9 Lite using XDA Labs

oss_mosis said:
@The Marionette thanks for this amazing work. There is some possibility that you can support the VNS-L23 variant? It is practically equal to the L31, with the only differences that do not have NFC support, the bands 4G are different and it has 2GB of RAM. Greetings.
Click to expand...
Click to collapse
I have the L21 variant and it works fine for me. If CM works on your device,AICP will work as well.
tw1st3d83 said:
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
Click to expand...
Click to collapse
Did you follow the instructions or did you do it your own way?
Are you coming from stock?
I think everyone needs to be on CM before flashing.
I flashed it exactly like I described and it booted.
The only downside is that the TWRP goes red(thinks the current ROM is stock) and data can't be mounted. I will look into it.
Sent from my VNS-LX1 using Tapatalk

The Marionette said:
I have the L21 variant and it works fine for me. If CM works on your device,AICP will work as well.
Did you follow the instructions or did you do it your own way?
Are you coming from stock?
I think everyone needs to be on CM before flashing.
I flashed it exactly like I described and it booted.
The only downside is that the TWRP goes red(thinks the current ROM is stock) and data can't be mounted. I will look into it.
Sent from my VNS-LX1 using Tapatalk
Click to expand...
Click to collapse
I followed Meticulus instructions first (did all backups and dump) and then i followed your instructions from OP but i come from stock rom, did not try to install Meticulus CM ROM... So now i managed to get past password screen by formating data partition to FAT and then formating it back to ext4 but now when phone boot i get "Decryption unsuccessful" screen and when i click "reset phone" button it reboots in recovery, wipe cache and then boots up back to "Decryption unsuccessful" screen...
I am downloading now Meticulus build to try with that... Will report back soon...
EDIT: I managed to boot AICP!!! By doing this:
First i updated recovery (did not see that Meticulus pushed V2) then i flashed Meticulus CM build but i got "Decryption failed" screen again but this time when i clicked "reset phone" buton the phone just rebooted to TWRP.
Then i did again full harcore wipe and flashed CM with open gapps and the phone booted in to system without problem, from that point i figure that AICP must work now so i rebooted back to TWRP, did another hardcore full wipe, flashed AICP with Open Gapps micro ARM64 version and the phone finaly booted to AICP :happy: :happy: :happy:
Btw i noticed few thing while doing all this... When i first booted CM my SIM card was not recognized but i figured it needs some time to get the signal or wathever but that never hapend and i cheked camera app and in setting of the app i saw that front and back camera was set to full resolution and the photo i took was really in full (13Mpix) resolution... After checking that and few more things i flashed AICP and at first boot my SIM still not working so i figure i will reboot and after second boot the SIM works again but in this ROM front and back camera are set to 2.1mpix (not a problem for me, just saying for ppl to know)...
Now i am going to play with this awesome ROM!
Thanks @The Marionette
EDIT 2: So after few hours of playing with AICP i been forced to go back to stock because my mobile network gone crazy, every 5-10 minutes it disapear and only reboot helps to get connected again and when network disapears the UI get so much lag that is almost unusable...
I can confirm that other things in ROM work as it should, fingerprint, themes, sound bar, navigation bar customization, lcd density, UI animations customizations etc...
Nice work and keep up the good work! ?

So I am running this ROM on my device since yesterday and I really like it. Seems very stable and allows for a lot of modifications.
It drains a lot of battery while listening to music when the device is locked but I also experienced this on the CM ROM.
I am keeping it on my device for now and am looking forward to new updates

Hello @The Marionette,
May I ask you if you plan to update the AICP ROM with the update from CM? Thank you

[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018]

{
"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"
}
LineageOS 14.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am 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
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
NOTES
1) If you've found a bug, please report it along with a logcat.
2) If you experience a random reboot, please share /sys/fs/pstore/console-ramoops.
3) It should work on all models, just like LOS 13.
4) Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
5) I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), 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.
What's working :
Boots
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
RIL (Calls, SMS, Data)
Audio ( Recording and Playback )
Sensors
Fingerprint
Notification LED
FM Radio
GPS
NFC
Hotspot
What's not working / bugs:
Camera is / looks zoomed when recording a video (it seems to be same on stock)
HDR?
IMS/Volte
Requirements
Huawei Nova CAN-L11 (should work on the other models too)
Unlocked bootloader ( here's a guide about how to unlock it)
TWRP. The TWRP made by @Grarak is also working fine. You can find it here.
Click to expand...
Click to collapse
Installation
Starting with January 2018 builds you need Nougat /product partition otherwise you'll get bootloop. To get Nougat product partition, you must install / flash EMUI 5 or restore this TWRP backup of Nougat /product partition (more details here). You don't know how to restore that backup? Check the steps from this post.
Make sure you meet the requirements listed above.
Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 7.1 and pico).
Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
Wipe system, data, cache and dalvik-cache.
Flash the ROM from the directory where you've placed it.
Flash GAPPS (OPTIONALLY).
Reboot.
Click to expand...
Click to collapse
Download
ANDROIDFILEHOST | MEDIAFIRE
Sources
LineageOS: https://github.com/LineageOS
Device: https://github.com/skinzor/android_device_huawei_hwcan
Vendor: https://github.com/skinzor/proprietary_vendor_huawei
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1
Click to expand...
Click to collapse
Donations
You don't have to, but if you like my work and you wish to support the development:
Donate via PayPal:
https://www.paypal.me/Henkate
https://forum.xda-developers.com/donatetome.php?u=4471434
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Credits
@Grarak
@gt_o
@abhishek987
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak, gt_o
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2017-11-13
Last Updated 2018-05-25

Changelog
25 May 2018
* security patch level 5 May 2018
The development has been resumed and is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
Click to expand...
Click to collapse
15 February 2018
Read this small, but important F.A.Q.
* synced Lineage sources
* security patch level 5 February 2018
* switched to enforcing selinux
Click to expand...
Click to collapse
25 January 2018
ROM
* synced Lineage sources
* security patch level 05.01.2018
* fixed in-call volume slider, mic/sound recorder (it's louder now) thanks to @gt_o. Read more here.
* updated audio configs to B382 and synced few audio props with stock ones
* show "HUAWEI NOVA" instead "Android" when phone is plugged to PC
* removed substratum support.
* added two blobs to fix two errors in logcat
* added the missing device_qcom_common (i don't know how i haven't noticed that till now lol). Now there are 5 profiles: powersave, efficiency, balanced (default), quick and performance. This can be configured at battery settings. As an idea, the powersave profile seems to turn off 3 cores (the cores doesn't seems to turn on when there is a high load though), while the performace one sets all cores to 2ghz. The power hal being used is the one of msm8937, which is also an octa core CPU. This is defined in the power hal's makefile on Lineage's repo (if the processor is msm8953, use the power hal of msm8937). I recommend it to keep the balanced profile (which is enabled by default), but it's up to you.
Kernel
* merged stock kernel source into the CAF one (tag LA.UM.5.6.r1-01300-89xx.0 as this one semeed to be the closest to stock, but also based on the Adreno log)
* got rid of many drivers from Huawei. You can see the commits here. Thanks to @gt_o, huawei's bootfail monitor (HWBFM) has also been removed. Although HWBFM was disabled till now, it was better to get rid of it, to get a cleaner kernel, but also being easier to merge the stock source into CAF.
* cpuset updates (also in ramdisk)
* added WireGuard support, thanks to @zx2c4. WEBSITE | XDA
* removed fsync/crc toggles as it's better to not mess with them
Click to expand...
Click to collapse
9 December 2017
ROM
* synced Lineage sources
* added Substratum support
* fixed blinking mode of notification light
* allow minimum brightness 1 (it was 4 before)
* possibly fixed the power usage reported by bluetooth ( i can't test right now as phone is charging and can;t reset the battery stats)
* Reverted this commit (more details there)
Kernel
* fixed hotspot
* cleaned ramdisk
Click to expand...
Click to collapse
25 November 2017
ROM
* security patch 6 November 2017
* fixed signal icon on 3G (it isnt empty / gray anymore)
* fixed flac audio playback
* updated media configs to N B382
* hide sRGB toggle in developer options
* increased the number of voice call steps from 5 to 8, and media volume steps
from 15 to 20
* increased the handset volume from the default (84) to 88 to improve UX with voice calls
* added ext4 support for /data
* added f2fs support for /cache
* added glove mode (Settings > Display > High touch sensitivity)
* from now on, Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
Kernel
* fixed logd/klogd issue (the high cpu usage)
* disabled HUAWEI_DEBUG_MODE config
* added DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
* added USB HID gadget support
* CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
* FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
Click to expand...
Click to collapse
13 November 2017
* initial release
Click to expand...
Click to collapse

Reserved

Dowloanding ^^
As soon as I can, I'll report back =)

Thank You #Henkate for keeping Nova alive!

Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!

Works fine here, thanks a lot for the hard work !!!

Will give it a shot this weekend. I am a teacher and students are doing mid term exams this week, so I kind of need my phone.

For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/

To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
GertFromTheWell said:
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Click to expand...
Click to collapse
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
Vinnom said:
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
Click to expand...
Click to collapse
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.

#Henkate said:
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
Click to expand...
Click to collapse
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk

Vinnom said:
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
I see.
I have the second error too, after flashing the ROM. I haven't checked why, but it doesn't seems to affect anything.
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.

#Henkate said:
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
Click to expand...
Click to collapse
@Vinnom
Here you go. Install it from recovery.

I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.

sk8buoy said:
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
Click to expand...
Click to collapse
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:

icutzo said:
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
Click to expand...
Click to collapse
Nope, this bug is gone now. When I'm on LTE the icon don't show LTE (it show only the signal strength) but data works fine.

I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful

Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !

Vinnom said:
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Click to expand...
Click to collapse
The recovery logs looks fine. I see that you have also installed Magisk and a Titanium Backup zip. Just to be clear, you have tried to install it without anything else too?
1) Did you wait about 5 mins ( although i dont think that much time is required)?
2) Can you take a kernel log too?
Run the following command, while booting (let it run few seconds after you think that you have got bootloop):
Code:
adb shell "cat /dev/kmsg"
I cant find anything wrong in logcat neither. I think the stock kernel may not be compatible with your model, so i will need to use the kernel source for your model or compare the two sources and import changes from CAZ-TL10 source into the one im using now.
The stock kernel source which is being used right now is CAZ_NG_EMUI5.0_opensource. According to Huawei`s website, it is meant for:
HUAWEI Nova,HUAWEI Nova Plus, CAN-L10, L11, MLA-L01,L11,L12,L13, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
When i search for "CAZ" on their website, i find nothing. But there seems to be:
Cannes-AL10_TL10 HUAWEI nova, Cannes-AL10, TL10, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
Perhaps thats the right one for CAZ-TL10 too?

imkoma said:
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Click to expand...
Click to collapse
Thank you too for your words!
By the way, its Henkate. You can also call me Robert .
1) When exactly camera is stopping and how? I didnt encounter this on my CAN-L11
2) What kind of issues does have front camera? My Nova`s front camera got damaged / broken when my Nova has been damaged, therefore i cant use it nor test it.
3) Regarding the cores, ive wrote at "notes" in first post:
The first thing you want to do after first reboot is to install a file manager and rename /system/bin/logd to "logd.bak" and reboot. You have to do this in order to get rid of the high CPU load. Consider this a workaround until the issue gets solved. Note that this breaks logcat, so you'll have to rename it back to "logd" and reboot to be able to take a logcat.
Click to expand...
Click to collapse
Would be nice if you could share a logcat regarding 1) and 2).

[ROM][8.1][UNOFFICIAL][MP260&TP260] LineageOS 15.1 for LG K20 Plus

{
"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:
[COLOR="red"]Your warranty is now void.[/COLOR]
I am 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 me for messing up your device, I will laugh at you.
Learn to Google.
WARNING: THIS ROM IS NOT FOR DAILY USAGE, IT'S ONLY A ALPHA AND A FEW THINGS ARE BROKEN. ALSO, IT'S POSSIBLE THAT YOU WON'T BE ABLE TO RESTORE A NANDROID BACKUP AFTER FLASH THIS ROM. FLASH AT OWN RISK!
/* What’s working */
Audio
Bootanimation
Brightness Level
Bluetooth
Microphone
MTP
Wi-Fi
Sensors
SD Card
Screen Casting
Camera/Camcorder
Flashlight
Wi-Fi hotspot
/* What’s not working */
The Fingerprint sensor is not yet implemented into my builds
APN needs set to IPv4/IPv6 to support full data capabilities for T-Mobile/MetroPCS
VoLTE isn't working
Wifi MAC address is not properly set
Double Tap 2 Wake on devices with a Synaptics display (which is about half of the LG K20 Plus devices)
Formatting /data as F2FS limits the partition to only 4GB so definitely avoid doing that for now
Please let me know if there are issues so i can update this list and work towards making it shorter than it already is.
Install Instructions1. Download ROM from the link below.
(This ROM is a 64bit ROM please install the 64bit PBRP from the Official PBRP thread unless you have an old 64bit capable recovery)
2. Wipe dalvik/cache/data/factory reset. (also delete the /Android folder from your external SD card, this can be done in PBRP under advanced/file manager)
3. Flash the rom in recovery.
4. Flash OpenGApps in recovery. (Make sure to choose 8.1 ARM64)
5. Reboot device.
Error 255 when flashing 64bit roms is because you are running 32bit twrp. Try PBRP in the Official PBRP thread
To fix fp enrollment on my builds or stock will require you to either delete the enrolled fingerprint(s) before clean install or switching to/from stock, alternatively you can root the device, use a root file explorer to navigate to the /persist-lg/ partition and delete the goodix folder. (FP is currently not implemented into my Oreo builds and will take time to shim to work, I however will be keeping this bit here for those who decide to revert back to stock or to my Nougat builds)
Downloads
DOWNLOAD
If you are happy with my work, please donate to help me keep this project going.
https://www.paypal.me/travisholt92
Thank You! :victory:
XDA:DevDB Information
LineageOS 15.1, ROM for the LG K20 Plus
Contributors
Travisholt92,
Deadman96385 (helped to provide bandwidth and the Q6 Stock Oreo kernel which my Oreo+ builds and this project utilize),
33bca (For his work on the Redmi 4A/5A, my device/vendor trees for Oreo/Pie are forks of his trees from [url]https://github.com/redmidevs trimmed/reworked to best support our LG devices, without his work this project would likely have taken ALOT longer with alot more bugs) [/URL]
Source Code: [url]https://github.com/LG-SD4XX/android_kernel_lge_sd4xx-common/[/URL]
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.18.120
Based On: LineageOS
Version Information
Status: Beta
Created 2019-02-05
Last Updated 2019-01-31

Changelogs:
2-6-2019
Fixed reboot recovery and 2D gaming issues

Travis, Try this Apn_Conf I had way more stable data and ip6
https://www.dropbox.com/s/3xramb2cbkq7gas/apns-conf.xml?dl=0

New build is up with reboot to recovery and 2D gaming fixed

Aw man.
Good to see the official thread take off!

@Travisholt92 unless I'm doing something wrong when trying to play a couple games (Idle Hero's being one) it won't allow me to play Via data it won't connect unless I'm on Wi-Fi? I can get a log but just wanted to let you know also if anyone wants what seems to help data a bit including faster switches from 3g to lte after calls try flashing this
https://www.dropbox.com/s/rak3v7mc6it4vqm/Apn_and_More.zip?dl=0
Also cleaned up build.prop and added some tweaks to it
---------- Post added at 05:51 AM ---------- Previous post was at 05:44 AM ----------
Also posted in your 7.1.2 thread that Magisk 16.0 doesn't freeze up

hawknest said:
@Travisholt92 unless I'm doing something wrong when trying to play a couple games (Idle Hero's being one) it won't allow me to play Via data it won't connect unless I'm on Wi-Fi? I can get a log but just wanted to let you know also if anyone wants what seems to help data a bit including faster switches from 3g to lte after calls try flashing this
https://www.dropbox.com/s/rak3v7mc6it4vqm/Apn_and_More.zip?dl=0
Also cleaned up build.prop and added some tweaks to it
---------- Post added at 05:51 AM ---------- Previous post was at 05:44 AM ----------
Also posted in your 7.1.2 thread that Magisk 16.0 doesn't freeze up
Click to expand...
Click to collapse
Yeah that data issue is related to ipv6 not allowing full network connectivity. Change that to ipv4/ipv6 in your APN and you'll be golden. It's something kernel related preventing full IPv6 connectivity. I'll check out your build.prop tweaks though. I plan to change the built-in APNs to address that issue until I can get that issue resolved. I probably won't work on debugging that until Pie since its not quite a high priority issue.

I installed the mentioned game just to make sure that was the issue. Loaded up just fine over LTE with ipv4 enabled

Dirty flashing from a previous Oreo build to 2/7 will likely result in a bootloop if you had magisk installed. You will need to reflash magisk and possibly gapps to resolve this issue. Its because I changed the filesystem type for certain partitions from ext4 to f2fs for a slight performance boost.

Travisholt92 said:
Dirty flashing from a previous Oreo build to 2/7 will likely result in a bootloop if you had magisk installed. You will need to reflash magisk and possibly gapps to resolve this issue. Its because I changed the filesystem type for certain partitions from ext4 to f2fs for a slight performance boost.
Click to expand...
Click to collapse
Lol, sure after I find out the hard way

hawknest said:
Lol, sure after I find out the hard way
Click to expand...
Click to collapse
Sorry about that lol
I'm going to revert those changes since they were personal preference but the change won't affect users that had issues installing the most recent build.

I am not sure what's up, I've flashed 2/9 a bunch and just bootlooping.. Clean install and fresh magisk flash
EDIT: Tried a few more times and no go.. I'll wait for the revert

I'm starting to think people don't know this thread exists yet

hawknest said:
I am not sure what's up, I've flashed 2/9 a bunch and just bootlooping.. Clean install and fresh magisk flash
EDIT: Tried a few more times and no go.. I'll wait for the revert
Click to expand...
Click to collapse
Revert build is up under the same name as yesterdays build with yesterdays build renamed to the proper date. It will work with ext4 and f2fs now. Its likely your issue was from cache being formatted as EXT4 which yesterdays build didn't support, today's does.

hawknest said:
I'm starting to think people don't know this thread exists yet
Click to expand...
Click to collapse
Me too lol. Once I get a new screen I'll get a YouTube video up with a side by side comparison between lineage 15.1 and stock. Should make for a very enlightening video.

Travisholt92 said:
Sorry about that lol
I'm going to revert those changes since they were personal preference but the change won't affect users that had issues installing the most recent build.
Click to expand...
Click to collapse
imma slap it on an give it a whirl ... uhhh...any way you could mix in magisk like with RR .. i can flash a backup...maybe
just wondering? i can take no for an answer
and i canT find the LIKE button.....serious
i've looked over the OP 10+ times...

Cyconumnum said:
imma slap it on an give it a whirl ... uhhh...any way you could mix in magisk like with RR .. i can flash a backup...maybe
just wondering? i can take no for an answer
and i canT find the LIKE button.....serious
i've looked over the OP 10+ times...
Click to expand...
Click to collapse
I can but won't for users who for some reason prefer SU, but magisk installer is baked into PBRP so close enough right? Lol also a new build is being uploaded now with overall performance improvements. Maybe I'm just crazy but even networking seems faster on 2/08. Should be up in about an hour. I'm off to bed now. Enjoy the super fluid 2/8 build.
Its a thumbs up lol

Going to need help testing something that everyone wants ??

hawknest said:
Going to need help testing something that everyone wants ??
Click to expand...
Click to collapse
Obviously I'm up for it. Lol.

reboot to recovery :good:
just flashed the 2/8 build 20-30 minutes ago, all is great so far.

Database Develop

welcome