Lazy Kernel for OP5/T - 10/27/2020

DeadRod

Senior Member
Dec 25, 2014
1,124
753
143
Riyadh, KSA
github.com
So yeah, I'm sorry about being inactive for days when it comes to the forum as well as the long wait for the next version's arrival. I just recently passed my college's aptitude test (and passed yay), and now I'm back to working on it again. So far these are the changes (test builds version X):

- Upstreamed 4.4.220
- Updated weeb base
- Staged dynamic stune boost based on input
- New dynamic underclock (depends on DSBoost)
- Scheduler tweaks
- Memory management tweaks
- Removed CIB and Devfreq boost
- Removed stune assist
- Disabled PPP support (unnecessary)
- Removed noop
- Set CDG and fq qdisc as default
- Disabled more logging and debuging stuff
- and more that I may had forgotten...

I'm still fixing instabilities with the new integrations as I am really just a newbie or an amateur when it comes to coding. Nevertheless, I enjoy it and I do want to learn more. :))

About the TG group, I'm still thinking about it XD

Anyways, good day! :good:
 

Ritwik Rahman

Senior Member
Dec 30, 2017
142
56
0
23
Dhaka
www.facebook.com
Yes it does support various kernel managers? I use Franco Kernel Manager. Although I'm still thinking of a way for everyone to at least have some control with the underclock and stuff. I can't assure though that I'll be able to do it in the next version.
Flashed the x33 test version it is very laggy, stutters a lot (maybe due to underclocks)...
The x28 was better in smoothness and performance.

Coming from latest weeb custom regression2 r34, Lazy x28 had less drain. But charging was a lot slower which was fixed in weeb from r30 builds after I tested and reported about it in Weeb chats.

But new Lazy x33 is a No-No situation here. If you're using weeb as base, r34 is a complete package with faster charging and smoothness.

And the overall spaker sound is also way less in Lazy kernel.

Um just sharing my reports as i want Lazy kernel to grow at its best. Perdon me if um wrong.
 
Last edited:
  • Like
Reactions: djporti1973

dogukan.uck

Member
Jul 7, 2015
9
0
0
last week i tried this kernel.cant remember which build it was but battery life was amazing.sometimes apps lagged and system froze for couple of seconds.so iwill wait until that issue is gone.
 

DeadRod

Senior Member
Dec 25, 2014
1,124
753
143
Riyadh, KSA
github.com
Flashed the x33 test version it is very laggy, stutters a lot (maybe due to underclocks)...
The x28 was better in smoothness and performance.

Coming from latest weeb custom regression2 r34, Lazy x28 had less drain. But charging was a lot slower which was fixed in weeb from r30 builds after I tested and reported about it in Weeb chats.

But new Lazy x33 is a No-No situation here. If you're using weeb as base, r34 is a complete package with faster charging and smoothness.

And the overall spaker sound is also way less in Lazy kernel.

Um just sharing my reports as i want Lazy kernel to grow at its best. Perdon me if um wrong.
Sorry about that XD. Try v40, it should have both underclock and stune boost working, with low jitters.

EDIT: Underclock was broken at that version.
 
Last edited:

djporti1973

Senior Member
Jun 10, 2013
77
32
0
astillero
The kerne lazy test l is a bit lagey. In my opinion the best kernel for pixel rom is V5. But it is my opinion, I insist. I have not tried in other ROMs since the pixel with V5 works perfect

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
 

DeadRod

Senior Member
Dec 25, 2014
1,124
753
143
Riyadh, KSA
github.com
The kerne lazy test l is a bit lagey. In my opinion the best kernel for pixel rom is V5. But it is my opinion, I insist. I have not tried in other ROMs since the pixel with V5 works perfect

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
Huh, that's strange, I have a more smoother experience with the new test builds. Try the latest one and change top-app sched_boost value with a kernel manager, it'll change the dynamic stune boost on input value. The default is 2 (not shown in kernel manager since it's hardcoded to the kernel and it triggers if sched_boost is equal to zero). You could also disable it (input dsboost) by putting -1 to the sched_boost value.

EDIT: It could be because of the change with timer frequency and pelt half-life. I'll try to bring it back with version 56 and I'll see if the battery doesn't drain a lot.
 
Last edited: