[KERNEL][P9][8.0+] ECOKernel 2020

[daspyki]

Hello. Will this work on my honor 8? I tried flashing the kernel but the device was not starting up.

 

[Bumo Gaming]

Hello. Will this work on my honor 8? I tried flashing the kernel but the device was not starting up.

No, it's just for the P9. They may have the same hardware, but the kernels are build a bit different.

---------- Post added at 12:57 AM ---------- Previous post was at 12:52 AM ----------

Although for b535 changing Governors work, I cannot change Min Freq (I choose 470 MHz but it always defaults to 807 MHz for big)

Btw, which Governors could be useful to save battery - mainly while screen locked.
Eg, Conservative for LITTLE?

Smartmax is a good governor for powersaving when the screen is of. Maybe try that one.

 

[Rampire]

Thanks to this Kernel I've been able to get deep sleep on my P9 with Omni Pie, however I've noticed that whenever the network changes (turning off data, turning on WiFi, switching to airplane mode), the phone stops going into deep sleep.

 

[zgfg]

Smartmax is a good governor for powersaving when the screen is of. Maybe try that one.

Smartmax for both big and LITTLE?

 

[udamster]

Although for b535 changing Governors work, I cannot change Min Freq (I choose 470 MHz but it always defaults to 807 MHz for big)

Btw, which Governors could be useful to save battery - mainly while screen locked.
Eg, Conservative for LITTLE?

I had the same issue with minimum frequency in Kernel Aduitor and it worked all of a sudden and I set 480Mhz as minimum for Big.


My setup is blu_active for LITTLE and interactive_pro for BIG. I tried power save and conservative for LITTLE but the UI became a bit choppy so this was the best I got without sacrificing the fluidity of the UI. Battery drain it's a bit unpredictable some days I get like 1-2% charge drop over 6 hours when screen is off (when I sleep) other days I get about 5% drop. One thing I've noticed is battery drop overnight is less when I charge it 100% and let it drain.

 

[zgfg]

I had the same issue with minimum frequency in Kernel Aduitor and it worked all of a sudden and I set 480Mhz as minimum for Big.


My setup is blu_active for LITTLE and interactive_pro for BIG. I tried power save and conservative for LITTLE but the UI became a bit choppy so this was the best I got without sacrificing the fluidity of the UI. Battery drain it's a bit unpredictable some days I get like 1-2% charge drop over 6 hours when screen is off (when I sleep) other days I get about 5% drop. One thing I've noticed is battery drop overnight is less when I charge it 100% and let it drain.

You get battery saving wirh blue_active instead of default interactive for LITTLE. Isn't blue_active more to somewhat boost performances
https://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957

 

[udamster]

You get battery saving wirh blue_active instead of default interactive for LITTLE. Isn't blue_active more to somewhat boost performances
https://www.google.hr/amp/s/forum.x...f-to-date-guide-cpu-governors-o-t3048957/amp/

This was using those settings. I think I read somewhere blu active is a more efficient form of interactive. Can't remember where. But switching to blue active made the UI bit more fluid than with options like Power save, conservative and smart max. At least for me

 

[NervReaper]

it's possible to add alucard governor?

 

[dkionline]

Hello. Will this work on my honor 8? I tried flashing the kernel but the device was not starting up.

ask @hackslash there: https://forum.xda-developers.com/honor-8/development/kernel-chihayafuru-kernel-v0-1-honor-8-t3839904

Thanks to this Kernel I've been able to get deep sleep on my P9 with Omni Pie, however I've noticed that whenever the network changes (turning off data, turning on WiFi, switching to airplane mode), the phone stops going into deep sleep.

Im aware of this. Switching between Pie and Oreo for Kernel.

it's possible to add alucard governor?

I tested it on beginning, had 20+ governor, but half failed and alucard too. Will check again after testing, but i think, it reboots anyway after issue.

 

[saentis]

I'm running the Omn Pie alpha 2 (openkirin) with this kernel on my P9, and am having lots of problems with push notifications. At least Threema and Whatsapp are affected, which both to some extent use GCM/FCM. Messages only come through when I open the respective app. I did all the usual fixes (disable battery optimization, enable background data). Is it possible that this is related to the Kernel? If yes, are there any settings I can tweak?

Thx!

 

[dkionline]

I'm running the Omn Pie alpha 2 (openkirin) with this kernel on my P9, and am having lots of problems with push notifications. At least Threema and Whatsapp are affected, which both to some extent use GCM/FCM. Messages only come through when I open the respective app. I did all the usual fixes (disable battery optimization, enable background data). Is it possible that this is related to the Kernel? If yes, are there any settings I can tweak?
Thx!

No, never. Check app settings + notifications for that.

 

[zgfg]

Smartmax is a good governor for powersaving when the screen is off. Maybe try that one.

I had the same issue with minimum frequency in Kernel Aduitor...

My setup is blu_active for LITTLE and interactive_pro for BIG. I tried power save and conservative for LITTLE but the UI became a bit choppy so this was the best I got without sacrificing the fluidity of the UI. Battery drain it's a bit unpredictable...

I changed the kernel manager to EXKernel Manager and then it worked fine.

Tested for several days the following combinations of governors
- big: interactive_pro, interactive
- LITTLE: smartmax, interactive, blu_active

With smartmax, fluidity is little worse than by default interactive - meaning eg choppy scrolling or (much easier to observe) uncomfortable text editing due to late reactions.
With blu_active fluidity is better than by default - but one must concentrate hard to observe small differences in faster touch reactions

Corresponding battery consumption results were not consistent and distinctive enough for a verdict beyond a statistical margine

Under Phone manager / Launch, Kernel Adiutor must be manually given Auto launch and Secondary launch permissions.
Still, sometimes upon (re)boot, Kernel Adiutor did not apply requested On boot changes - I had to disable and re-enable CPU / On boot option in Kernel Adiutor and reboot to enforce* the chosen governors

This also affected battery consumption tests because I became aware too late that default governors were running again instead of my intended ones.
Didn't test with the paid EX Kernel Manager to conclude if intermittent failures to apply custom governors were due to Kernel Adiutor or the kernel itself

PS: Do not lower Min Frequency for BIG (from default 807 to 470 MHz) - it will undoubtedly negatively affect fluid scrolling (initial 470 MHz is not enough for instant scrolling in eg browser, just after screen unlock or after a few seconds of idle)

 

[udamster]

@zgfg on EXKernel Manager, the bug on Kernel Aduitor is not present. You can change both clusters to what ever available and settings can be made to apply with boot.

 

[zgfg]

I

@zgfg on EXKernel Manager, the bug on Kernel Aduitor is not present. You can change both clusters to what ever available and settings can be made to apply with boot.

Thanks, using now EX Kernel Manager, it works - few comments:

- With Battery monitoring enabled I had annoying notification that EX drains battery, hence disabled monitoring battery (using GSAM Battery Monitor anyway)

- In Phone Manager, Launch, EX must be moved to manual with all three options (Auto and Secondary launch, Background) enabled.
Third option (Background) seems unnecessary (CPU changes must be applied on boot) but without, when I didn't unlock the phone (PIN) quickly upon booting, EX failed to apply changes

PS: Now using blu_active for both big and LITTLE.
Fluudity is ok although I'm not sure how it reflects the battery (better or worse - anyhow, but minimally)
Reason: I was monitoring in live how CPU frequencies scale up/down and it seems that blue_active scales down faster than default interactive (also faster than interactive_pro) when load scales down.
When load scales up, all three scale up practically immediate

 

[Hermanos01]

This work on RROSB3?

 

[dkionline]

This work on RROSB3?

It should, yes.

 

[daspyki]

ask hackslash there: https://forum.xda-developers.com/honor-8/development/kernel-chihayafuru-kernel-v0-1-honor-8-t3839904
Im aware of this. Switching between Pie and Oreo for Kernel.

Well i'm already using his kernel and the deep sleep issue was still persistent. So i was wondering if this kernel would fix the issue.

 

[zgfg]

Well i'm already using his kernel and the deep sleep issue was still persistent. So i was wondering if this kernel would fix the issue.

That kernel from @hackslash is also good for P9 Oreo?

 

[Tecalote]

That kernel from @hackslash is also good for P9 Oreo?

OP of that Thread:
"Compatibility with either EMUI and other ROMs is not guaranteed. However, this doesn't mean I won't support them. If you face a bug or issue, please report it here and I'll happily take a look at it."

 

[zgfg]

OP of that Thread:
"Compatibility with either EMUI and other ROMs is not guaranteed. However, this doesn't mean I won't support them. If you face a bug or issue, please report it here and I'll happily take a look at it."

Ok, flashed chihayafuru-v0.45-sec-sep
(since EVA-AL10c00b535 is September security patch) from
https://forum.xda-developers.com/honor-8/development/kernel-chihayafuru-kernel-v0-1-honor-8-t3839904

It's for Honor 8 Oreo, but it works on P9 with b535.
Less number of governors, see screenshots