yashsingh1/xdaforums huggingface dataset:
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
You have to look into the source of the power HAL and understand how things works. There's no documentation for that flag. Sometimes, if you check the commit history and find the commit where the change which you're looking for got added, that commit might have a description for the change. I don't know if it's the case for this flag as I haven't looked into it yet.

As a side note, yesterday i've seen other phones (also 8953) supported by lineage which has TARGET_USES_INTERACTION_BOOST enabled too.

Regarding the status of the development, the known issues left are:

- camera saturation

- fingerprint is missing sometimes after a reboot

- SIM card showing up as "####" at mobile network sometimes

- low volume while a bluetooth headset is connected as it was reported (I still haven't got the chance to test myself, especially after the audio changes which I've did)

The freezes caused by libqmi_oem_main was fixed and the audio seems better, at least in my opinion. Also, the reboot which occurs when opening CPU-Z app was fixed thanks to [MENTION=5662620]BadDaemon[/MENTION] who shared his kernel fix from kiwi.

The other (weird) known issues are:

- for some reason, the sound isn't working on other Novas, but it's working when the headphones are plugged in (according to the feedback, the problem was there even on the first build of lineage 14)

- screen isn't working / usable on Novas with JDI screen after some reboots or powering off , but at beginning it's working fine

I'd like to publish a new build when at least the fingerprint's issue and camera saturation are fixed.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Earlier i've did 50 reboots and fingerprint wasn't missing at boot... I'd be glad if someone could share a logcat taken during a boot when fingerprint is missing, also kmsg (cat /dev/kmsg).

I'll take a log every time i reboot to test something, but i still don't know when it'll happen nor if it'll happen again.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Defirence:
Thanks [MENTION=4471434]#Henkate[/MENTION], I'll flash when I have a chance at home after doing a proper backup.

Is it possible in future that we can have an OTA update notifier? It'll be fine to download the image manually and flash via the device, but as I don't ever really use XDA, it would be nice to be notified about updates via a push notification or something of the like.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I'll be aiming for official lineage, so that means OTA updates too. In the worst case, I can provide OTA on unofficial builds.

I haven't provided OTA for lineage 14 because I thought that the XDA thread would have even less attention and less feedbacks.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Defirence:
Ah I see, makes sense. Well, I did attempt flashing the new update, but I soft-bricked my device for a while trying to restore an old backup, if you can please direct me to the forum link for the superuser.zip for the last release you did, my current version is 14.1-20180524-UNOFFICIAL-hwcan, as I did want to test if Titanium works on the backup I restored, when I have some time this weekend I will see about a re-flash to 8.0 and with the new recovery and see if it works, or if I did a dirty flash the last time around and broke some stuff.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I'm sorry for the delayed reply.

I've mentioned the needed TWRP in the first post at requirements, but I understand from your reply that you haven't used that one...

Regarding root on lineage 14, please read 4) at notes in lineage 14 thread. On lineage 15 you can flash addonsu-15.1-arm64-signed.zip from https://download.lineageos.org/extras and then enable it in Settings > System > Developer Options > Root access.

You can also install phh superuser, Magisk or something else, but I won't assist regarding that since lineage provides own root. You can check the specific thread for phh / Magisk.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Defirence:
Hey no problem, I did use the new recovery, I think I need to do the whole process clean again I think, thanks, I'll take a look and use that!
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Cooks_8:
I am using your trees and trying to build another ROM for this phone. I keep running into an error that originates from the hwcan device folder. Here's a shot of what I am running into. It isn't making sense to me why it's happening, I just wanted to see if you ran into the same issue with Lineage. https://hastebin.com/zuxaqebiha.xml

Thanks for any advice/help. Really appreciate the work you have done to get Lineage on this phone.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Please don't quote the first post as that's a big one and it sux to scroll that much. You can quote less, add [HIDE ][ /HIDE] tags (with no space) in the quote or mention my name. It's just an advice, don't get me wrong.

There's no build errors while building lineage apart from the one which I've wrote few pages ago (read more here).

Regarding your RR build errors, unfortunately, I don't have any idea and I'd like to help, but I'm busy with lineage.

Make sure that you have used the right repos and branches (see the first post at sources). I don't know if lineage / RR sources has ipacm / ipanat stuff in their sources as I've never checked before, but i know that the kernel does.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Cooks_8:
Regarding your RR build errors, unfortunately, I don't have any idea and I'd like to help, but I'm busy with lineage.

Make sure that you have used the right repos and branches (see the first post at sources). I don't know if lineage / RR sources has ipacm / ipanat stuff in their sources as I've never checked before, but i know that the kernel does.[/QUOTE]

Yeah I am sorry about the long post. Totally get your busy. I was just wondering if you had pushed the commits that allowed you to build lineage 15.1 to your sources yet? I will check for the ipacm / ipanat items. I am using the oreo branches for the oreo builds. I used to maintain a few devices, but it has been a couple of years. Lots has changed. lol. Thanks for your response, I have a couple more things to check now. Appreciate it.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
I've run into the same build errors you pointed, not sure why though. I tried to build Validus and as it didn't work, I downloaded los 15 and try to build. Same issues. Then my credits on gcp was over xD

so i downloaded everything to my pc and I trying to build los 15 again. Everything is going fine now and I just run into SSR error and fixed it. I have no clue of what I did differently from the time I tried to build it on gcp. So my guess it has something to do with rom sources.

As soon as los 15 get builded (it is building right now), I'll try Validus again
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Cooks_8:
I swapped out data-ipa-cfg-mgr with invisiblek's folder in his essential device tree. Passes through these errors. Stops at an audio error. So I'm going to check the difference between it and henkate's. It is why I asked if the sources were up to date. I think I read it was on git lab but maybe not on github. Thought maybe there was a couple changes missing from that device folder.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Check this post for the audio build error. I assume that's the one you've encountered.

The sources from github are up to date with the first build, but I've forgot to remove that AUDIO_FEATURE_ENABLED_SSR flag from BoardConfig. I didn't had any commit for it on gitlab neither because I was always cherry-picking a commit which fixes the build error (instead removing the flag) and that's why I've forgot to remove it and make a commit for that when I've pushed the sources to github.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
I can't confirm if that solve all our problem with tweaking kernel settings, but go to:

- settings > battery > battery saver and performance

Set your power profile to Power Save (left edge). After I tested this, I saw in Kernel Adiutor that we can tweak things.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
Yes it seems to give back control to CPU frequencies in kernel-control-apps. But still something is wrong. Despite what I tune the govenors to, despite the CPU load <3%, the frequencies do not go down.

So let`s see how the next build behaves.

BTW I have a great tip for all users that users that use one sim in a dual sim capable nova: It highly improves the standby time to completely shut down the 2nd sim! Look for persist.radio.multisim.config=none in the build.prop. Otherwise there is also an app here at xda: [APP] [4.0.3+] [ROOT] MultiSIM Toggle by xenon92
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
The next build won't have any change regarding that and I really dunno if I'll disable that flag considering that's being used on other 8953 phones too. I might make one build for testing purposes, but I dunno when.

Regarding the status of development, I've still got to fix the missing fingerprint and camera saturation. I'm currently working on the fingerprint bug and I have some clues, but gotta test them. I've also worked on sepolicy and it's pretty much done (very close to enforcing), although I'll have to rework it when I'll enable treble.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
i built a bootimage disabling that flag and nothing really changed. It seems a lot more related with power profiles than the flag itself. I'll take a look and I want to test somethings regarding battery life when using this interaction boost and when not.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
You need to build the whole ROM. Would be nice if you'd leave your opinion about using it with and without interaction boost.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
oh i see! I thought it would be only a kernel thing. I'll do it this weekend and I'll try to write tests to it ^^
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
Hmm I don't know if its necessary to play with flag.

We may need to check the apps before:

After unlocking manual control by shifting the slider to most energy saving + applying my scheduler settings (up thresholds, hysteresis, fast ramp down) kernel auditor showed high frequencies. also the great app simple system monitor shows this. If I track the frequencies with cpu-spy the phone shows a good ramp down till 625 MHz. - maybe the reporting to some apps broke with Oreo? Which to trust?

(clear all but CPU spy have a advanced GUI, but under 14.1 also there the frequencies dropped)
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] onewayup99:
bug

huawei nova caz al10.The sound disappears after flashing this rom
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
Hi.I was thinking about updating from LinageOs 14.1 to 15.1,but then i read that i need to install an official version of EMUI 5 before flashing Oreo.To install Nougat i unlocked the Bootloader of an EMUI 4,and i still got the unlock key,but i don't know if it will be usable with the EMUI 5 Bootloader too.Will the key change or not with the update?

Thank in advise and sorry for my bad english.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] zaabolla:
Yes the key change you have to get new one for 7.0
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
The bug is known already.

The reason i've wrote EMUI 5 as requirements is because some parititons gets updated like /product for example, which holds acdbs for audio. You can also backup your phone in TWRP and try to flash lineage 15 even if you were on MM, but i wouldn't recommend that. Either way, you can't brick your phone trying that.

Regarding the unlock key, i know that Huawei requested us to choose EMUI 4 or 5 when getting the key from their website, but i don't think that it matters and it may actually be a sort of feedback for them. I've had only one key on my first Nova (second one too) and it worked on both EMUI versions.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
So i basically can't update to Oreo,from the moment that Huawei doesn't give unlock key anymore.That's sad.

Thank you,Huawei.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] cojocar.andrei:
It did't for me. can-l01. Same key for emui 4.1 or 5, but I wouldn't risk it as no more unlock page. It sucks. Now even the huawei ff does not work anymore... Really sucks, but I'm really happy I got to update to Nougat before this happened... Such a mistake from huawei to close all this, of course I wouldn't buy from them again... Cannot live w/o root and xposed...
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
So i'm not that Hopeless...I'ill try.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] cojocar.andrei:
If you are not bothered with remaining with a locked bootloader on Nougat in case this fails... I also want to specify that the only way I succedded to upgrade was through the huawei ff installed on the phone and with the link to their servers (I was so close to bricking the phone as I tried a couple of methods which didn't work). This doesn't work anymore so take this into consideration as well. It sucks, I know...
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
So,i managed to flash a stock version of EMUI 5 on my phone via dload,and then i tried to unlock the bootloader with the key i already had,and all finished good.Then i flashed TWRP 3.2.1.0 using adb and i obtained root access with magisk.But there's a bigger problem now.When i open TWRP,the recovery asks me a decryption password for data partition,that i don't know.So i tried wiping data with TWRP to avoid that problem,but the operation was unsuccessful.When i turned on my phone again,there was a black screen saying "Encryption Unsuccessful",that forced me to format data,a thing that i can't do.You think i could flash Lineage Os 15 using TWRP without problems or i have to do something else before?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
The TWRP I've built doesn't support decryption for now, so you have to format data in TWRP (format, not wipe). Formatting data will wipe your internal memory. I don't remember the path from TWRP right now, but look in the wipe menu.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
I tried formatting data selectin "Format Data" in the Wipe Menu,but the result is an error.

The log says:"Formatting data using mkfs.f2fs",and the ends with an "ERROR 1-Unable to wipe data-Unable to format to remove encryption".Then it says:"Updating partition details-Failed to mount '/data' (invalid argument)"and the same thing with "/cust".I don't know how to proceed.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
You've mentioned TWRP 3.2.1, but I've provided 3.2.3 which you're supposed to use. Try that one.

Regarding /cust, check this post. If you have error about /product too, then you can get a backup of that partition here.

Theoretically, fastboot-ing cust and product images extracted from UPDATE.app should also work.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
You mean flashing the cust image from the UPDATE.app of the EMUI 5 i've installed?

Anyway, i tried changing the file system of data to EXT4 to avoid the encryption problem,and now it seems to be disappeared.Now i'ill try fixing the cust problem,that seems making Lineage Os 15 bootloping.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Yes, but i don't know if you'll be able to do that. You can try though.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Ekifi:
After three days of work,I finally managed to install Oreo on my phone.I restored the TWRP Backup that you provided,and so resolved the "/cust/" partition problem.Then I tried re-flashing Lineage Os 15.1,and after some seconds it started up.

Thank you for the support and for the work you put in this device.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
Finally got some time to try building again. Running into the exact same error with data-ipa-cfg-mgr
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Did you get that while building LineageOS? o_O
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
Yep. Was a fresh sync, so maybe the LOS team has changed something.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Nope, it isn't that since i didn't have any such issues. I don't get why though. The sources i've pushed to github are the same with the ones from gitlab (i've verified with kdiff3 after i've pushed them) and i've also tried to build with the ones from github like about two weeks ago to confirm that everything is fine and it built fine besides that SSR flag which i've forgot about. It was a successful build but it failed at 99% because i've ran out of free space on Google Cloud Platform (forgot to run make clean in lineage 14 folder or something).

So yeah, i don't get why.

With this occasion, lemme tell y'all that a new buid will come soon. The camera saturation still isn't fixed in the next build, but i'll make sure that will be fixed in the next one. Other issues were fixed and i've also added OTA support. I guess that it won't hurt to have OTA on unofficial builds until i can get official support. In one of my previous posts, i've said:

But after all, official lineage support also means having OTA.

I still got to make a new build to test OTA again.I'd also want to switch to enforcing too, but i'd need to use my phone for a while to make sure that everything is fine.

Regarding treble, i've tested it few days ago by flashing RR GSI, and it didn't boot (not even bootanimation) but i got a log and i know that i still got to do some changes for that.

Regarding Pie (lineage 16), i've booted it two days ago and overall everything seemed fine besides bluetooth, NFC and a (small?) camera issue (basically when i took a pic with Camera2 app, the camera was closing itself and the pic wasn't saved). There was also some lag / glitches while scrolling due blobs. I still got to do things before moving to Pie though, like fixing the camera saturation and fixing TWRP decryption.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
The android.mk files in ipacm and ipanat src folders did not point to msm8953. Got past it when I changed that.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
Please henkate, give me an instruction or rom to try a pie. Having found the vendor folder and the line in build.prop (ro.treble.enabled), I plucked up courage and got flash gsi via fastboot, but it turned out that after a month of using lineage 15.1, I closed frp and I couldn’t flash anything, since the way is to unblock it in the emui settings, but I could not install it, because I don’t want to spend 3GB on one tick in the settings. I can be a tester and send permanent logs
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Cooks_8:
my mistake

No mine was caused by stupid me. I forgot to checkout the lineage-15.1 tree on the kernel and that's why I kept getting that.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
Sorry for my ignorance, but what exactly did you do to fix it.

Never mind, I understand. Problem is I only have one branch of lineage on my build machine. Once I switched those android.mk files I got past that error though. Now having issues with audiopolicymanager libs.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Initially [MENTION=6049555]Cooks_8[/MENTION] said that he's using the Oreo branches for Oreo builds, but now he said that he didn't use the lineage-15.1 branch for kernel...

Please make sure that you're using the correct sources. Again, the sources are mentioned in the first post. I've also just updated the manifest from phone, so check it here. Besides removing the SSR flag from BoardConfig, there's nothing else which has to be done.

Keep me updated.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
I am sure I had the right branches, followed the links in the OP. I deleted all the branches and pulled them again and this time it worked. I am not sure why it was messed up. To do anything I have to run through a VPN and sometimes it times out (network drops), so I suppose something could have been corrupted. Good thing is it built without errors. Was doing it at like 4:30 in the morning :D
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] soul-man71:
I tried to install it on Nova Plus MLA-L11.

I started from emui 5, I Installed twrp for Oreo and flashed with 15. 1 and gapps

without receiving any error.

Anyway when it try to boot it goes on loop, It diplays le lineage os logo animation.

Then I tried to format data using twrp 3.1.1 as suggested on the discussion but it fails the format.

What I have to do, please? :)

I wonder if I should flash a stock firmware, set a password (pin to unlock the screen) and the try to use that pin ad password for the decryption...

UPDATE NOW WORKS!

I've tried several times to format data with 31.1 twrp and finally it worked ;)
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Cooks_8:
I had my vendor and device correct.... When I dug deeper I found that I hadn't checked out the kernel. I got RR built but I have a bug where it doesn't recognize headphones when they get plugged in. And the brightness slider isn't working. Otherwise runs pretty good.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
You can't enable treble just with a line in build.prop lol.

Maybe you didn't have the right kernel source neither, like Cooks_8. Damn, building at that time sounds crazy, but I guess that it isn't a problem with your PC specs :D.

I've told you to make sure that you're using the right sources xD.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
We try our best. Henkate just does it better :D
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
New update

NEW UPDATE - 13/10/2018

EDIT: It looks like I've completely forgot to commit and push a change... Basically, I've switched back to the stock libacdbloader so acdbs gets loaded properly (related to audio). That's the change I've forgot to commit and push. You can wait until tomorrow when I'll publish a new build or flash this zip which I've had in my phone.

I'm really sorry for this.

First, let me remind you again that this is possible thanks to [MENTION=4850735]wangdaning[/MENTION] who helped me to get a new Nova. Thank you!

The download links are in the first post. The github became the main download link now and it'll be used by OTA too since the download speed is better.

The sources were updated accordingly and you can find them on my github (check the first post).

If you choose to install the new update from OTA, it'll automatically reboot to recovery and install it, so basically it's dirty flashing. Keep in mind that quote though.

CHANGELOG

- synced LineageOS sources

- 5 October 2018 security patch

- added OTA support (using lineage's updater)

- fixed the freezes caused by libqmi_oem_main

- fixed the reboot which was occuring when CPU-Z was opened (also the sensorservice's crash)

- fingerprint will no longer be missing at boot

- updated audio configs (and audio flags), media and wifi configs

- enabled QUOTA feature for userdata partition

- addressed many selinux denials (next build will be enforced)

- other misc fixes which you can see at commit history

NOTICE

:

1.

You can read more here: https://source.android.com/devices/storage/faster-stats. As a side note, i didn't had any problem with quota on f2fs until now.

2. OTA will download the flashable zips / updates to internal memory (/data/lineageos_updates), so you'll need to have enough free space for that. I might try to change the path to external sdcard.

Please let me know if you still have this issue with the new build. I haven't tried to debug that problem since i've made audio changes, but if the problem persists even with the new build, i'll try to debug it.