[KERNEL] Ares-Kernel {KlteXXX}

[Trey n]

I have the same issue and solved it by downloading a kernel auditer mod and enabled per govner control and cpu 2 3 4 were on performance instead of zzmove, I switched them to zzmove and now it's working like it should so far

Sent from my klte using XDA Labs

 

[Latako]

Same as the others.
First core changes frequencies, other 3 stay at max (performance).
Same behavior switching hotplugs.

KLTE (w8)

I'm not getting any app crashes that I had with prior version though.

Big thanks for this!

 

[blikkk]

Perfect!
Ares 1.3
AnTuTu benchmark, stresstest OK.
Firefox not crash.
All core variable: Offline-2841MHz (OK)

Max clock: 2841MHz
CPU Governor: interactive
Voltage:
670 680 690
700 710 720
730 740 760
770 800 810
840 880 940
980 1010 1040
1120 1170 freez
freez freez

AnTuTu score:
interactive governor: 68106
performance governor: 63363 (WTF?)

 

[Trey n]

Same as the others.
First core changes frequencies, other 3 stay at max (performance).
Same behavior switching hotplugs.

KLTE (w8)

I'm not getting any app crashes that I had with prior version though.

Big thanks for this!

Mine are doing the same thing

Sent from my klte using XDA Labs

 

[The~Skater~187]

Odd. I will look into out tonight and see if I can simulate.

Sent from my kltespr using Tapatalk

 

[Ibuprophen]

Odd. I will look into out tonight and see if I can simulate. Sent from my kltespr using Tapatalk

I do see a few items on the Repo that optimizes the first CPU without the remaining CPU's being set that ends up defaulting (in a way) to their maximum capacity.

I hope I had explained this okay via text...


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

 

[ToCatchATiger]

Just to be thorough, I tried clean flashing over a fresh install of Havoc as well as installing over beta 1.1 and the behavior stayed the same

 

[Ibuprophen]

Just to be thorough, I tried clean flashing over a fresh install of Havoc as well as installing over beta 1.1 and the behavior stayed the same

This is plausible...

Depending upon the specific device, there's a handful of areas within the kernel that speak to each other. If one item calls out for one or more of the CPU's to be set at a specific frequency but, one or more of the others aren't specified accordingly, it will max them out in a default way since there's no real direction provided.

This is a very good Kernel development that requires feedback like yours in order for the developer to make the required adjustments.


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

 

[The~Skater~187]

After some playing around last night, I was able to replicate the mentioned core behavior by doing a full clean install ( must of had something left from testing that didin't get over written ).
So since I ended up with today off, I will be investigating the issue to find the cause.

Edit: I think I figured it out. May have an update for you guys in a but.

 

[The~Skater~187]

Beta-v1.3 is live:
Link is in the op
See changelog for details

 

[Ibuprophen]

Beta-v1.3 is live:
Link is in the op
See changelog for details

Thanks a bunch for your hard work My Friend!


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

 

[The~Skater~187]

Thanks a bunch for your hard work My Friend!

Just an FYI regarding the recent Changelog...

It looks like you hadn't formatted the Size and Color appropriately as reflected below:

*revert: disabled "CAF" cpu policy save code (Fixed cores not scaling properly)
*MSM Limiter updated​

You had quoted the 2 "Black" & "3" when the specific quotes shouldn't be there like the following:

COLOR=BLACK
SIZE=3

Example:

*revert: disabled "CAF" cpu policy save code (Fixed cores not scaling properly)
*MSM Limiter updated​

Just wanted to let you know. [emoji106]


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

All fixed. Thanks for catching that.[emoji106]

Sent from my kltespr using Tapatalk

 

[ToCatchATiger]

Beta-v1.3 is live:
Link is in the op
See changelog for details

Everything looks good now! Thanks again and looking forward to future updates

 

[Latako]

Working great here.
Havoc Pie, KLTE(w8), smartpack kernel manager (cleared data)

I did reflash the rom to restore default kernel prior to flashing yours. (Not sure if this is needed, I usually do this)

Only thing I came across was thermal switches. But it still works, just use vdd, or intellithermal.

By default, smartpack kernel manager sees both core control, vdd restrictions on.
I enabled vdd only, rebooted, and it was the only one active.
I enabled core control only, rebooted, both core control and vdd restrictions were active.
I enabled intellithermal only, rebooted and it was the only one active.

Core control can't stick to itself.



Thanks for doing this for us

 

[The~Skater~187]

Working great here.
Havoc Pie, KLTE(w8), smartpack kernel manager (cleared data)

I did reflash the rom to restore default kernel prior to flashing yours. (Not sure if this is needed, I usually do this)

Only thing I came across was thermal switches. But it still works, just use vdd, or intellithermal.

By default, smartpack kernel manager sees both core control, vdd restrictions on.
I enabled vdd only, rebooted, and it was the only one active.
I enabled core control only, rebooted, both core control and vdd restrictions were active.
I enabled intellithermal only, rebooted and it was the only one active.

Core control can't stick to itself.



Thanks for doing this for us

Odd, upon initialization of the kernel, core control should be the only thing active.

Sent from my kltespr using Tapatalk

 

[blikkk]

Update

Perfect!
Ares 1.3
AnTuTu benchmark, stresstest OK.
Firefox not crash.
All core variable: Offline-2841MHz (OK)

Max clock: 2841MHz
CPU Governor: interactive
Voltage:
670 680 690
700 710 720
730 740 760
770 800 810
840 880 940
980 1010 1040
1120 1170 freez
freez freez

AnTuTu score:
interactive governor: 68106
performance governor: 63363 (WTF?)

Big Thanks dear Development!

 

[Latako]

Odd, upon initialization of the kernel, core control should be the only thing active.

Might be me.

Will do a wipe later tonight.(will update after i do)

Thanks

Edit: same after clean install

Clean install through twrp by factory reset, then advanced wipe caches/system/data

Installed Havoc pie march 11th
Installed gapps mini march 12th
Installed magisk 18.1
Installed Ares 1.3
Cleared caches, reboot.
Let it restore my account/apps
Installed smartpack kernel manager

Unfortunately, same thing.

But if its just me no worries, I can use vdd restriction or intellithermal with no issue.


Everything is peachy my friend

 

[Ibuprophen]

I'm just curious as to the new kernel release...

How has it been performing when flashed over the previous kernel as opposed to flashing on a fresh firmware installation?

I'm just wondering since some issues might be likely to be experienced when flashing over the previous release as opposed to flashing after a fresh firmware installation.

I hope I had stated the above okay via text...


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

 

[lollipop]

I'm just curious as to the new kernel release...

How has it been performing when flashed over the previous kernel as opposed to flashing on a fresh firmware installation?

I'm just wondering since some issues might be likely to be experienced when flashing over the previous release as opposed to flashing after a fresh firmware installation.

I hope I had stated the above okay via text...


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

flashed over beta v1.2
no problem so far

 

[ToCatchATiger]

I'm just curious as to the new kernel release...

How has it been performing when flashed over the previous kernel as opposed to flashing on a fresh firmware installation?

I'm just wondering since some issues might be likely to be experienced when flashing over the previous release as opposed to flashing after a fresh firmware installation.

I hope I had stated the above okay via text...


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

I like to avoid "dirty flashing" when updating kernels, I have had it cause issues in the past... I always follow the same procedure: flashing the magisk-patched stock boot.img from whatever ROM I'm running, then flashing the kernel .zip, then wipe cache/dalvik