yashsingh1/xdaforums huggingface dataset:
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
Like the speakers, for the micro the mixer_path_mtp.XML could offer a workaround. Personally I have no idea where to adjust because there are several micro's listed.

Actually, if the standard los15.1 gains in the XML do not suit well (los speaker, low micro), I have no idea where else, on a lower level, the android sound is controlled.

btw: There had been in old custom kernels (not huawei) patches, which allow control via apps like kernel audiutor. But since henkate is the only dev (thaaaaaanks) for our device, I see his arguments to do not apply any kernel patches. If I would like to see undervolting ;). But I know from other dev's/phones that one waste some time to implement this. remember, on other phones, there had been several people just for a ROM and several people working on a kernel. It's just a miracle(!) that henkate drive this device just alone.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] cojocar.andrei:
I also would like to see undervolting. It helps a lot with the battery (also some newer cpu governors would be nice) ...

Thanks,
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I'm sorry, but i don't have time right now to reply to the last 2-3 replies.

[MENTION=4850735]wangdaning[/MENTION] and others who tried to build but encountered build error, you should remove or comment out the following line in BoardConfig:

AUDIO_FEATURE_ENABLED_SSR := true

The build error should've been something like:

fatal error: 'surround_rec_interface.h' file not found

I'm really sorry, but i've completely forgot about that. I've just remembered about it now when i was checking audio flags.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
I played with oreo :) Maybe you (dear Henkate) need help with treble?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
[MENTION=4471434]#Henkate[/MENTION] No worries, you pushed out a good build, us noobs should learn to troubleshoot ourselves :D
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] R0mi4:
Good afternoon! From the very beginning of the possession of this smartphone wanted to install LOS, but it all ended with a non-working sensor and a black screen. as it turned out this problem only in JDI screens. on your advice put the driver from another phone with a pure android and JDI screen, but it did not help.

I managed to use LOS 15.1 a bit, I really liked it, especially the changes with the sound in the headphones, the volume margin was added. for me this is a very important change.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
Treble ,treble!!
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I've made some changes and seems to be better, but I'm not sure if it's same on stock. I've recorded a video on stock to see the sound produced by microphone, but it didn't seemed that loud nor good neither, at least in my opinion.

Thank you for your last words!

Undervolting / overclocking would never be on my list. First of all, I don't have any knowledge about them and I wouldn't spend time for such thing. Secondly, undervolting / overclocking might've been useful for old phones, but I wouldn't see the point in doing that for newer phones which already has nice battery backup and performance, and if someone would do that I can bet that it would be a placebo or it would just give better benchmark results or there wouldn't be any significant improvements in the daily usage.

Also, this kind of stuff doesn't go well with official LineageOS.

See the answer to GNUDroid above.

Any help would be welcome, but treble isn't a priority. There's issues which must be fixed and sepolicy must be enforced firstly.

Someone can always make a pull request to my github repos if he wants to.

Well, that might be true in a way, but I'm still responsible for breaking the builds and it might be too challenging for beginners xD.

I know that I've told someone before in the lineage 14 thread that if I'll get Nova again I'll look into it or something like that, but I'm busy with the current issues and I can't really solve the problems so fast, especially since I lack knowledge, but I've always tried my best. I'll take a look at it someday, just like at the other issues.

You say that you've managed to use lineage 15 a bit, but I don't understand that at all. Does that mean that you no longer have a black screen with the JDI screen?

You can always do it on your own.

PS: last 3-4 days I've been busy with mainly doing researches about improving myself (e.g. workout stuff and such). I didn't had time at all and I didn't feel at all that I want to use the PC. Tomorrow (and maybe today too) I'll continue what I was doing (I'm trying to fix the freezes caused by libqmi_oem_main).
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
You can always do it on your own.

If I were as cool a developer as you, I would. But I'm an ordinary user who prays for the developer. New firmware on the treble you want to touch, but it's impossible. I tried to figure out how to do it myself, but there are no instructions on the Internet. I asked for help from other people, but everyone is busy with their devices. As I understand it, we need to move the vendor partition to the root of the system and create a special recovery. But the vendor section was already at the root. Are these the first steps to treble or symlink? Also recovery can mount the vendor section, but do not delete, do not flash gsi. I'm already confused and will wait for you. I can also use my device for tests, I like frequent rom shifts. Thank you in advance
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
You've previously asked me if I need help with treble and then you've said:

That message sounds to me like "do it now!!" or "I want it now!!", so I've responded you accordingly...
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
Excuse me, I did not want to show an aggressive request, it's just that our communication is complicated by different languages ​​and that it's hard to convey emotions on the letter. I'm just keen on the idea of ​​treble, it's incredible. First, when I bought nova 2 months ago, I was very upset to learn that oreo will not. And then you, it was joyful news. I waited, I was afraid that something would happen to you, counted the days and my nerves could not stand it. I did not have anything wrong and agressive in your address, I apologize again. I saw how the only developer left the development because of aggressive users, and I do not want to repeat. Then I had to sell a smartphone. It was sad

---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------

My google translate is broken
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
[MENTION=4806022]Henkate[/MENTION]: We are soooo happy. You are a one-man show.

Everyone (including me) should stay quite. But I think it's just because all are so excited. and everybody has his own focus on a perfect ROM. and maybe we all are too optimistic after your dramatic break through recently.

please, please take your time! this is just a hobby.

and even if you would quit, nobody of us (since we did not contributed help/code/guides) will ever would have the right to be disappointed.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Well, next time try to write more words when you translate so maybe it'll make more sense what you're trying to say, maybe Google Translate will translate better. Even if you didn't meant to be "aggressive" as you've said, I think you've still meant it as a request. Anyway, would be nice if you won't repeat it again. I hope that Google Translate won't **** it up and you end up understanding something wrong lol.

To y'all, if someone else will make a similar post like the famous "volte plz", then I'll ignore it.

You need to understand that I'm a normal guy just like y'all, that I have a life too and that I'm not a pro dev. Making requests like "volte plz" or "treble plz" won't help in any way.

Nah, nobody should stay quiet. It's actually pretty nice to have an active community, but not one who says "volte plz" :D. For example, I really appreciate your previous posts where you've talked about your mixer_path "experiments", where you've shared your ideas and even the modified file.

Would be really nice if there would be contributors too. When there's two or more people working together, then it becomes easier. For example, it was really fun to work together with [MENTION=5418262]gt_o[/MENTION] back then (lineage 14 days). Although we both were beginners (even now I still consider myself a beginner / newbie compared to pro devs), we've did stuff together (like fixing the high CPU load usage on the stock kernel) and learnt new things together. I'm missing that days.

I don't know why you've mentioned quitting, but I'm planning to support Nova as long as I own it. Once I get a job, that may change though.

Shall we get back to development now? :D
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
Did you found the bug about the high frequencies?

I wonder if they are kernel related or by some new power profiles which came with Oreo, e.g. influence by perf folder in /system/vendor/etc, powerhint.xml file in /system/vendor/etc, pnp.xml file in /system/vendor/etc (not present for us nova)

first 2 i deleted, but it doesn't fix the behaviour, and also setring freqiencies in kernel audiotor still behaves strange (min freq. often Pops up to 1,6 MHz).
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I haven't worked on that yet. I'm currently trying to fix the freezes regarding libqmi_oem_main and notification led. I'm not moving to another issue until I fix this one.

The problem with libqmi_oem_main is that it isn't finding the socket which it needs to connect to and I can try to add qmuxd as it seems it's the one which is supposed to create the socket needed for libqmi_oem_main.

The other solution would be to hex-edit it, so that it won't try to connect to that socket. At boot it's failing to connect to that socket, then it's giving up on trying to connect and notification led gets enabled. I dunno if there would be any downside to this workaround, but the led seems to work fine even if libqmi_oem_main fails to connect to the socket.

Did anyone experience the problem with missing fingerprint again? I think it only happened once to me and that was at the beginning. I've done many reboots until now to test things and as far as I remember, it didn't happen anymore.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
I have this every time I try to flash modules from magisk, it gives an error magisk_merge.img and when I turn it on, the print disappears. Revive through the terminal
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
For me fingerprint never failed.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
It happened to me when I let my phone completely discharge. When I booted it, fingerprint was lost. Then I rebooted and it was working again.

EDIT:

Just to report:

1 - I can't confirm low incall volume.

2 - I confirm kernel odd behaviour

3 - As already mentioned, I faced the fingerprint not working

I can't think of another issue I faced.

About the kernel, stock emui kernel behaved like this too. I remember that I already tested and faced this.

I did a clean install. I really suggest that, if you're coming from a nougat rom, to do the same. Major updates like that, to avoid any bug that doesn't relates to the build itself, should always be pristine.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] alexsakhnov:
[MENTION=4471434]Henkate[/MENTION], Great work, thank you very much for this build! Have been using this ROM for a weak, almost everything works fine.

I want to confirm the issue with in-call volume slider, the volume can't be changed. Is it possible to fix it?

However the in-call volume level is high enough (even too high for me).
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] R0mi4:
Dear Henkata Thank you for your great work! you do a great job and extend the life of our smartphone and even make it better! You're a big lad!

I can tell you more about the problem with the JDI screen, maybe the problem lies on the surface and the solution will be simple.

I installed all the possible versions of LOS and on all versions one picture.

After the first run, LOS everything works fine, the screen shows and responds, the problem starts after several reboots or on / off the smartphone.

It looks like this: do some reboots or (on / off) and at one point the smartphone turns on and does not respond to touch, the sensor does not work. then the backlight goes into sleep mode and the larger screen does not show the picture, when unlocking it is seen that the backlight is working, but the screen is black. Only you can hear the sound of locking and pressing the volume keys.

It will be very cool if you can somehow solve this problem, the owners

JDI screens will honor you as a god)))
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] ddementiev:
Thanks for the good firmware. Found a bug preventing from using the phone. When the Bluetooth headset is connected, the call sound goes only to the headset, and the speaker of the smartphone is silent. As a result, the call is not heard, and I miss it.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vignesh_K:
Have you changed to f2fs file system? I don't think this bug occurs on ext4.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] AssasinAkindinov:
I have a problem with magisk_merge.img, very rarely modules are put, even f2fs loopback bug workaround does not help. I think this is due to dirty flash rom, tomorrow flash is clean and I will test

Will linageOS 15.1 work on ext4? If so, how to put it?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Yesterday I've just experienced it again. I think I'll need to do about 10-20 reboots to make sure that's fixed lol.

I knew that you've wrote about this during lineage 14 days too, but it was different as you've said that min/max frequencies were changing all the time and I've replied you this. I don't remember if we've talked about it further back then.

Regarding the min frequency being stuck at 1689 Mhz, it seems to be related to the board config TARGET_USES_INTERACTION_BOOST which I've enabled same as mido. I've checked a bit their thread and people reported the same "problem" and one of them said about that flag. I haven't looked into it before, but my guess was that would be related to the ramdisk (init.qcom.post_boot.sh) which was updated from CAF. It seems that my guess was wrong though. I'll check the power HAL source and try to understand what's exactly doing, but I might not be able to. The flag name is pretty self explanatory though.

I can disable this flag, but to be honest, phone is smoother and battery is good too. I can test without it too though.

The in-call volume slider is fixed in the next build. I've basically broke it myself when I've switched to Oreo acdbloader blob and it failed to load our acdbs. Once I've switched back to the stock acdbloader, the acdbs loaded successfully and I've noticed that the in-call volume slider works too. It was same on lineage 14.

That's weird lol.

I have a bluetooth headset and I'll test when's possible. It would help if you'd share a logcat too.

Yes, it will work on ext4. You can format /data to ext4 from TWRP.

Just a quick update regarding this. I've seen the same problem yesterday, but now my network/SIM provider seems to be recognized and showed properly. So, it's not a bug related to Chinese SIM card. Either way, it's on my bugs list since the day you've shared me the logcat.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
Yep, you're right! I mistook it xD I'm also not sure we talked further about it. Either way, both things are not really an issue, rather an annoyance. Because if we want to play and tweak settings, it's not possible. But as you said, phone is smooth and battery is good, so no rush.

I tried to build LOS 15 and Validus (using the rest of my credits on GCP xD) but I faced some issues (both presented same issues), but I didn't have the time to try to debug or talk with you about it. Past two weeks were really rushy on work (applying exams and grading students - [MENTION=4850735]wangdaning[/MENTION] already been there for sure xD) I think I'll have some time to go back to building again in the next weeks ^^
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
hmm a poll about the flag? i mean with old los 14.1 and clever Scheduler tuning (fast up, fast down) i bot the same smothness but i could use the phone 2-3 days with intermediate charging. now the accu is down to 55 % from wakup till bed. I prefer to choose what I want. maybe others also?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] 廖帅翔:
This rom have some bugs?:confused:
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
check known issues on the OP.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] OmTatSat:
If i have in-call volume slider problem on lineage 14 maybe it is releated to acdbloader too? How can i fix it?

Don't want to jump on lineage 15 before camera saturation problem is fixed, because it is main desired new future for me in lineage 15 and i have a lot of xposed modules and i think not all of them work properly on Oreo so jump to lineage 15 may be not easy. So i would glad to know are there any news about the camera saturation fix?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
probably a clean flash of the latest build of los 14 will fix your problem as it was solved sometime ago.

About camera, I would say that is best to wait him tell rather than be asking if this or that issue was solved or if there is any news about it. Henkate always updates us about ROM development ☺️ sure, there is another way to be kept up to date if you really need news before he tells us: you can check on his github page and see what commits he did. That way, you can see how development are going :)
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] OmTatSat:
Clean flash - a lot of pain to get it right settings in a lot of apps((( and i don't really sure is it will help(( maybe i face this issue because i have G9 plus (tl10)?

about github commits this is great idea!) can you please show link to right plase where i can see latest changes? because link i have found have outdated commits 18 days ago(( https://github.com/OmTatSat/android_device_huawei_hwcan/commits/lineage-15.1
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] fmarx1:
I have to say, battery life on this build is fantastic! I've gotten 6h of screen on time over 24h. With Nougat I barely got 4h.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] ddementiev:
Below is the logcat for bug with bluetooth headsets

https://drive.google.com/file/d/1e_O1YeH_jH45m8BG3Y2IWtnfE74brISp/view?usp=sharing

Additionally about bluetooth. Smartphone with your firmware has significantly lower volume in the Bluetooth headset than the my other smartphone. Sometimes the volume is not enough.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
Clean flash sure takes time, but you left a nougat ROM to a oreo one. This isn't just a normal update. Sure we can't tell for sure if it will solve your problem, but how can we say that your error were caused by a build problem? When we report issues, it is the best that we isolate the possible causes. When you report after a dirty flash, we can't tell for sure from where the error came. So, that way, we may be reporting things that doesn't come directly from build.

Well, that being said, did you flashed the product backup that Henkate shared with us on los 14 thread? If no, try that. That may help you.

about github, it seems you shared a fork you did from his github page. Check OP. Doesn't forget that he is a normal human and have a life. So don't blame him if there isn't any update for days, because he is doing his best ;)

EDIT

about the model, I have a CAZ-TL10 and I didn't face this issue. In-call volume is sound and clear for me
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] OmTatSat:
I think i had recovered product backup, but just to make sure, i recovered it again, but nothing changed((

"Check OP" OP what this mean?

i think this is right place to watch commits? https://github.com/skinzor/android_device_huawei_hwcan/commits/lineage-15.1

i never ever have any blame minds about #Henkate, only appreciating minds. :)

thank you for your help!
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
To be honest, I don't know.

The volume slider was fixed on lineage 14 in 25th January 2018 build, so I don't get how it's still there. Maybe some selinux denial is showing up, but I doubt.

Anyway, it's fixed on lineage 15 in the next build. Regarding camera saturation, it's still not fixed.

Thank you for your feedback! My SOT varies between 8-10h according to my usage and I'm also gapps free xD. In my opinion, it seems better than lineage 14's battery backup too.

Thank you!

I've still didn't test my bluetooth headset, so your log definitely helps. As I've said before, I've already did some audio changes, so it might be different in the next build.

He meant that you should check the first post for the sources.

Since lineage 15, I'm doing the changes on gitlab (private) until I push them to github, so you can't track my progress. Maybe I'll change that and push directly to github as I was doing with lineage 14.

I've uploaded screenshots with the commits I've did until now. See here. I still got to do the commit which fixed the freezes caused by libqmi_oem_main at boot.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
Do you have a thread about the flag target_uses _interaction_boost I want to verify if it's really hardcoaded. For me it does not make sense to completely (nearly 2 freq. steps) disable CPU scaling. If one wants, why not simply choose performance gov. Et voilar! Or use interactive and push touchboost to long times or simply set the slider in settings from balanced to performance. ...Yes battery is OK. but why degrade battery (also lifetime concerning charge cycles) if one would easily could get +33%-40% more lifetime without any felt performance degradation?

Hopefully this flag is not hard coded. I was not able to find right threads via google.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] OmTatSat:
i don't see any messages(

this is great!)

thank you for reply

thank you for screenshots, it would be great if we can see progress directly and not disturb you