yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] taufiqs:
Yes. I am using kernel adiutor. Btw your screen colour settings is amazing. It's like I am using an amoled screen.

Btw, care to explain more about this userspace and cpuquite runnable?
[ONE Android Development] stranostrano:
In kernel adiutor, go to cpu then like cpu governor choose "userspace".

Go down till someting like CPUQuiet. Enable it and downside in "Cpuquiet governor" chose "runnable"
[ONE Android Development] taufiqs:
Umm thanks for the guide. Yes, I know how to change those yet I dont understand how it works.
[ONE Android Development] kalapapa:
You will learn everything here

http://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957/
[ONE Android Development] taufiqs:
Thanks for the link, I'd had read it yet I prefer real user explanation about userspace. It doesnt have tunetable then how to control its behavior then? By script or something?
[ONE Android Development] kalapapa:
The point of the userspace governor is to dynamically scale itself to whatever app it's in. So in a way the app controls how aggressive the CPU will be.
[ONE Android Development] 69gm:
Might be ROM. The other day on Omni nightly, before flashing your kernel, I was muted during a phone call. Might be my face muted me because of the proximity sensor.

EDIT: Confirmed! I flashed Omni nightly with stock kernel and had proximity sensor problem. I made a call, then covered the sensor but the screen remained on. Hope they fix soon. I just reported it to [MENTION=4683552]maxwen[/MENTION] and I know he's the man!
[ONE Android Development] indian84:
Is it only me who is running this amazing kernel on SAOSP? Running beautifully for me so far.
[ONE Android Development] taufiqs:
Count me in bro. Great kernel indeed.

What's your setting ?
[ONE Android Development] stranostrano:
I think that need to be suggest the use of this kernel in respective rom tread or, apart the people that came across this tread, people didn't know about.
[ONE Android Development] indian84:
Using stock.

---------- Post added at 11:51 AM ---------- Previous post was at 11:51 AM ----------

I did already in SAOSP thread.
[ONE Android Development] stranostrano:
I've suggested a settings configuration some posts earlier. Try it and report your opinion.
[ONE Android Development] :
Does anyone know why, any time I flash a custom kernel on Omni, be it Donkey or this one, and with just Omni's default settings the phone starts to terribly lag?

Awesome work dev, thanks for supporting Omni.
[ONE Android Development] stranostrano:
It works well with rom's stock kernel?

Are you running official nightlies?
[ONE Android Development] :
Yes, no issues
[ONE Android Development] kalapapa:
I've had that issue as well. It went very laggy even before I used xposed modules

---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------

One feature I want to have in this kernel is a custom hotplug like bricked, mako, or alucard. That would be amazing

thanks
[ONE Android Development] :
Does it work on CAF Based ROMs? :confused:
[ONE Android Development] indian84:
No. The title says it all. Only Omni/ Omni based ROMs.

Website signature
[ONE Android Development] :
Oh well, okay..Thanks for the info
[ONE Android Development] parvesh:
hi just wan to confirm with which SAOSP version you are using it , is it the early release dated 5th Feb :)
[ONE Android Development] indian84:
Yes. 5th Feb build.

Website signature
[ONE Android Development] stranostrano:
Updated to ver. 1.4 on 16 march 2016 - refer to the OP thread in first post for details and the 2th post for download.

Changed source from herna to Official Omni Nightly.

I've just uploaded the zip files.

The source will be updated as soon as possible!

As always, if you find bugs, please report back.

have fun. ...always!
[ONE Android Development] stranostrano:
Source link updated.

updated on 1st op post also.

Development continues. Stay tuned and ..

Have fun. ...always!
[ONE Android Development] Maestropcxp:
Since ver 1.2 i have lag in general (no smooth like ver 1.2). Is there a way to eliminate the lag?

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] stranostrano:
I didn't noticed lags. What's cpu governor are you using?
[ONE Android Development] robbieast:
Can we plz get voltage control :D
[ONE Android Development] stranostrano:
I'll work on this feature soon.
[ONE Android Development] stranostrano:
Version 1.5 is out.

added OndemandPlus cpufreq governor and SIOPLUS, FIOPS and ZEN I/O scheduler.

Have fun. ...always!
[ONE Android Development] kalapapa:
Hey since it's based off omni nightly and not omnisaber kernel does that mean f2fs is supported
[ONE Android Development] :
F2FS is not included in Omni nightly.
[ONE Android Development] kalapapa:
Dang

Can the dev add f2fs support using commits from Omnisaber kernel

That's be amazing
[ONE Android Development] stranostrano:
Here it is

https://www.androidfilehost.com/?fid=24459283995301872

Try it and report back if you'll find some bugs.

I'm continuing with developments!
[ONE Android Development] stranostrano:
Hi all. Version 1.6 is out.

Have fun. ...always!
[ONE Android Development] mada1991:
Many thanks for your work... it's great...

I'll wait voltage control with impatience...

Many many thank...
[ONE Android Development] stranostrano:
I'm testing 1.7 ver with voltage control implemented and some other feature and a reworked "lowmemorykiller". Just a little time to test it and if it work good I'll update to 1.7.

Give me just a little time more.

Have fun. ...always!
[ONE Android Development] stranostrano:
Version 1.7 is out.

Added Voltage Control and Simple_gpu_algorithm

Have fun ...always!
[ONE Android Development] mada1991:
I'm trying for now many many thanks
[ONE Android Development] stranostrano:
Please feedback
[ONE Android Development] mada1991:
Let me try it for a day....;)
[ONE Android Development] mada1991:
I've noticed if I leave set msm-adrenal-tz as gpu governor the GPU doesn't use anymore the 200 MHz freq... It always stays at 330 MHz even when the device is completely idle...

And if I set cpubw_hwmon all crash and I have to restart the phone...
[ONE Android Development] stranostrano:
I've noticed the issue and I'll investigate.

Thank you
[ONE Android Development] stranostrano:
Hi mada1991 and thanks for your feedback.

Regarding the gpu freq that stay to 330 MHz, is related to SimpleGpuAlgorithm. If you deselect it, msm_adreno_tz scale down to 200 MHz. If you want enable SimpleGpuAlgorithm and want the 200 MHz you have to use "simple_ondemand" that is a [MENTION=3332811]faux123[/MENTION] governor based on msm_adreno_tz.

Regarding the "cpubw_hwmon" issue, I can confirm that it freeze OPO. This issue is present on other device too and I think it's related to some error of DDR management on Krait devices.

Anyway, strictly to my Kernel, I can confirm that this happen also on at least 1.6 version. I'm removing it in ver. 1.7.1 that I'll release soon.

Ciao

Have fun ...always!
[ONE Android Development] webore:
I don't know why but I can't turn WiFi on with this .

Running omni latest build .
[ONE Android Development] stranostrano:
No problems here with wifi.

Which version are you on?
[ONE Android Development] webore:
yes I noticed that no one else had this problem.

I will try again with your new kernel.
[ONE Android Development] mada1991:
It isn't a big deal for me about cpubw_hwmon...

It was just a trying...;)

About the frequency "issue" I've tried with and without "SimpleGpuAlgorithm" but in kernel audior with opened just that and without touching anything... 330 MHz is always shown...

So I've switched to simpleondemand that It should be more battery friendly than the other... And for me it should be better because I don't play...

Grazie mille

Ciao

Me too no problem with wifi works fine...

Try clean cache and flash last version again...
[ONE Android Development] stranostrano:
Hi, if you don't touch anything, it stay to 330 but if you touch the screen it goes to 200.

Anyway this governor have this problem from the origin and we can't modify because of "tz" (trust zone). I suggest you simple ondemand.

Have fun ...always!
[ONE Android Development] mada1991:
Yes yes...

I've already switched to that:)

Many thanks always
[ONE Android Development] stranostrano:
Ver 1.7.2 is out.

- Moved get_cpu_idle_time() to cpufreq.c to align Omni source to current standard, updated and adapted to "get_cpu_idle_time()" change, all cpu governors, added Alucard hotplug and Alucard, Intelliactive and Intellidemand Cpu Governors and updated some source code.

Please feed back

Have fun ...Always
[ONE Android Development] robbieast:
Wow awesome job! Ty for the update
[ONE Android Development] robbieast:
Hmmm kernel is very laggy
[ONE Android Development] stranostrano:
Confirmed, it's laggy. I didn't realized because of the Kernel Auditor that set my own configuration. I've tried without applying custom configuration and it's very laggy. I'm working on it. I hope I'll soon update an improved version.
[ONE Android Development] stranostrano:
Updated to ver. 1.7.3

Thanks to robbieast for his feedback.

1.7.2 results laggy. Now I think it's good.

Anyway, for your info, I want to share my Kernel Adiutor set up.

CPU - Alucard, MPS enabled, CpuQuit enabled and runnable, cpuboost 20ms, sync thre. 1190, I.I. 350 ms, IBF 1497

Hotplug alucard enabled, samp. rate 35%

GPU msm_adreno_tz with simple_gpu_alg enabled

I/O sched deadline

Entropy 4096 4096

Try and report, please

Have fun. ...always!
[ONE Android Development] mada1991:
Which are the difference among the three setting of CPU quit?

Runneble

Load stats

Rq stats

Thanks for all...
[ONE Android Development] stranostrano:
Hi mada1991,

(from the source info)

The Cpuquiet implements pluggable policies for forcing cpu cores into a quiescent state. Appropriate policies will save power without hurting performance.

For what I've undestand, "runnable" evaluate the scheduler queue to decide which cluster/cores to use and scale the number of CPUs online depending on the number of runnable threads.

"stats" uses load status to hotplug cpus. I think that it's similar to the old "balanced" cpuquiet governor and I consider that load_stats is not batteryfriendly because by default load balancing is set to the most aggressive setting but it's just my think and I can be wrong. Luckily, load_stats and rq_stats are written from [MENTION=4683552]maxwen[/MENTION], one of a great coders of OMNI rom and we can ask him for more detailed info.

Obviously "runnable" it's just the cpuquiet governor that I use and suggest to you but surely you can try "load" or "rq" and report back your impressions.

Have fun. ...always!
[ONE Android Development] mada1991:
Many thanks... I've just asked to you because U've chosen in your configuration that particular setting...

Now I'm trying Runneble...

I'll let you know...
[ONE Android Development] stranostrano:
28 april 2016 - updated a reworked 1.7.3 version.

Added again "power_suspend" feature.

It seems lags are gone.

I suggest this setup from kernel auditor

CPU:

max cpu 1728; governor Alucard; Multicore pow/sav enabled; Cpuquiet on - runnable; cpuboost 0ms; sync thres. 652MHz; Inp. Int. 10ms;Inp. boot freq 883MHz;

HOTPLUG: Alucard (default setup)

GPU: max gpu freq 462MHz; min gpu freq 330MHz; governor "Simple_ondemand"; Simple Gpu alg. ON; laziness 1; ramp thresold 7;

Entropy r/w 4096

Misc Control: Power suspend mode "Autosleep";

try and report, please.

Have fun. ...always!
[ONE Android Development] robbieast:
With default settings is lag gone as well or only with your settings
[ONE Android Development] stranostrano:
sorry robbiest, I had the flu.

The lags problem are present in 1.7.3. I need to review the source code because till the 1.6 ( and 1.7.0 also) there is no lag's.

Today I'll start from the 1.6 source and I try to understand what happened.

Stay on 1.6 ver. for now.

have fun. ...always!
[ONE Android Development] stranostrano:
02 May - Ver. 1.8.0 released.

Fixed all lags (thanks to robbiest to report it), removed junk cpu governors, updated Alucard hotplug, added MSM hotplug, Added Adreno Idler and updated "Powersuspend" feature plus a lot of code review (my fault). Now all seems gone right.

Please feed back.

Have fun. ...always!
[ONE Android Development] mada1991:
Many thanks I'm trying it...

Do you have some suggestion for the settings?
[ONE Android Development] stranostrano:
Hi mada1991,

my setup, using Kernel adiutor, is:

CPU:

max freq 1728MHz, smartmax, Multicore power sav. enabled, cpuquiet on - runnable, cpu boost interval "0", sync thres. 652MHz, Input interval 10 ms, input boost freq 1036MHz

MSM hotplug enabled min/max cpu online 1/4, Cpus boosted 2, max core screen off 1, boost lock 1500, down lock 1000, update rate 30, fast lane 90, offline load 0, io is busy ON

GPU

governor msm-adreno-tz, simple Gpu Alg. on, laziness 2, ramp thres. 7, Adreno idler on, down diff. 10, idle wait 15, workload 7.

I/O Sched "zen", read-ahead 1024

Entropy on, r/w

MISC CTRL:

Powersuspend Autosleep, network Highspeed.

If you want more smooth at cost of battery, select "userspace" as CPU freq gov.

Please feedback.

Have fun. ...always!
[ONE Android Development] stranostrano:
Hi all, I've uploaded a 1.9 pre release with fsync on/off toggle and Voltage Control. If someone want to try out you can download it here

Have fun. ...always!
[ONE Android Development] mada1991:
Many thanks for sharing your setting...

I've a couple of question about them...

I Know (correct me if I'm wrong please) CPU Quiet is a CPU HotPlug why do you keep active that and MSM together? I've read that it's better active just one...

Second One...

In smartmax there is already implemented the mechanism of input bust... Why do you force it?

Thanks in advance

I have a littel request;)

in future if You have time could you add the wakelock control feature?

in any case 1.8 works very well

ciauuuu
[ONE Android Development] stranostrano:
Hi mada1991,

yes CPUquiet is a Tegra derived hotplug trimmed by Faux, I think, and probably in theory they didn't have to be enabled together but I've noticed a minor cpu activity (see it in cpu section of KA) enabling togheter.

Related to Smartmax, the governor default value (see smartmax msm8974 section in cpufreq_smartmax.c in source) for TOUCH_POKE_FREQ is set to 1497MHz and I set to a minor value 1036MHz for battery friendly reasons. But, obviously is my personal preference and you can get rid of it!

Have fun. ...always!
[ONE Android Development] mada1991:
I'll try to enable both of the them together and I'll report...

I'm curious;)

About the question related to smartmax I know that the TOUCH_POKE_FREQ is set by default to higher value than yours but with my very little experience the INPUT BOOST FREQ is more useful for governor without this mechanism already integrated like Smartmax...

You can save a little bit more of battery with the same smoothness...

If you wanna try to set the parameter of smartmax to 1036 MHz and disable the other...

Ciauuu
[ONE Android Development] stranostrano:
Did you mean in source?
[ONE Android Development] mada1991:
What do you mean with the post in quote?

Sorry[emoji29]
[ONE Android Development] stranostrano:
I mean if you are referring to set 1036 in the source code of smartmax cpufreq or setting it in Kernel Adiutor.

Anyway I've asked to maxwen (the autor of smartmax gov) if my way of thinking is right and he says that theoretically I'm right. That just loose a bit of responsibility in touch event but he didn't think that the saving battery amount is considerable.
[ONE Android Development] mada1991:
No my point wasn't change the source of SmartMax but to set the frequency in Kernel Audior of the touch poke freq inside the tuning menu of Smartmax governor instead of set INPUT BOOST FREQ....

always in kernel audior...
[ONE Android Development] stranostrano:
Ah ok! I'll try it
[ONE Android Development] mada1991:
I've been trying Runneble for a couple of days as you suggested and I can confirm the phone it's smooth as before with a little bit of more battery...

It's definitely better...

Instead activing together CPU QUIET and MSM HOTPLUG has produced (at least for me) a strong battery drain...

Thank you very much for the first suggestion...
[ONE Android Development] stranostrano:
Hi,

new version 2.0 is out.

Added Fsync on/off toggle and Slim and OndemandPlus cpu governors. Some other little update to code.

Please feedback!

Have fun. ...always!
[ONE Android Development] stranostrano:
Hi all,

I'm working on future ver. 2.1. In the meanwhile I've included some feature like GPU OC/UC 657/27MHz and toggleable CRC control setting CRC disabled at boot (it might boost kernel and app removing software CRC).

here the alpha version. Please tell me what do you think about.

Have fun. ...always!
[ONE Android Development] stranostrano:
Hi all,

I've released version 2.1 of my kernel.

Added GPU overclock to 657MHz and idle to 27MHz.

Disabled software CRC at boot and introduced toggle to re-enable and added awake CPU schedule workqueues toggle. Others optimization to code including "more sanity checking" for USB cdc-acm.

Please, feedback.

Have fun. ...always!
[ONE Android Development] mada1991:
Many many thanks I'll try it...

Great work...
[ONE Android Development] kalapapa:
Thanks for the update

Running smooth as usual with my own setup

Just curious, I remember somebody else in another thread writing that GPU over clock is cosmetic as it is configured in the trust zone which cannot be modified. so is it worth keeping?

Source: http://xdaforums.com/showpost.php?p=64706351&postcount=7465
[ONE Android Development] stranostrano:
Adreno idler enabled will force the trust zone algorithm almost on idle. On max freq I didn't see differences.
[ONE Android Development] kalapapa:
[MENTION=862741]stranostrano[/MENTION]

on latest slimsaber release, doing a clean flash resulted in bootloop when trying to boot up with your kernel. I even tried to flash rom and gapps and boot up, then went back to twrp and flashed kernel without wiping cache and then tried booting but it still would bootloop. Any ideas?

Never mind I figured out my issues were due to supersu v2.74. If you want to use any omni custom kernel, use supersu v2.72 or lower because for some reason the latest one is giving me bootloops
[ONE Android Development] mada1991:
I've just clean flashed last omnirom with last supersu with custom kernel and it works normally
[ONE Android Development] stranostrano:
That's good. I'm working on a new different project that take all my free time but I'll still develop kernel in future. Actual version of kernel are working rock solid (imho) then we can stay with it for a little bit more.

Stay tuned and ...have fun. ...always!
[ONE Android Development] stranostrano:
hi,

ver. 2.2 is out. Nothing revolutionary, just added zzmoove cpu governor and patched some bugfix to code.

have fun. ...always
[ONE Android Development] kalapapa:
Thanks for the update

If you have time could you please add bricked hot plugging

Thanks
[ONE Android Development] stranostrano:
I'll try to push in next release.
[ONE Android Development] stranostrano:
hi [MENTION=6440862]aaqibismail[/MENTION],

try this "bricked_hotplug" alpha version and report back if it's good. If it work, i'll move bricked hotplug to "hotplug" dir in source, i'll recompile it and I'll release as official.

have fun. ...always!
[ONE Android Development] kalapapa:
Hi thanks for latest version

Unfortunately I am unable currently to test it for various reasons. I'll try testing as soon as possible, but I can't promise when I will. Sorry
[ONE Android Development] stranostrano:
Sure. It's for everyone.
[ONE Android Development] stranostrano:
Some news. I'm on "2.2_bh_alpha" ver. from about 7/8 hours and all seem fine.

If someone else can test it and report, it would be usefull.

Have fun. ..always!

Inviato dal mio A0001
[ONE Android Development] kodora:
Hey strano, just flashed your kernel on my 1+1 with slimsaber omni. I decided to try your kernel because you just implemented zzmoove which is the governor that suits me better. I have been configuring all to my taste and just noticed that you didn't implemented zzmoove's hotplug. Are you planning on doing it?

Thanks for you work.
[ONE Android Development] kalapapa:
Normally it should be implemented when you add the governor. Use kernel adiutor and turn off all hot plugging and switch to zzmove governor from another governor. Check to see if some of the tunables pop ip
[ONE Android Development] kodora:
Well, that's what I've done (not my first rodeo here.. ;) ) but none of the tunables showed up. I'm using kernel adiutor modded.
[ONE Android Development] kalapapa:
Well I guess we'll have to wait for [MENTION=862741]stranostrano[/MENTION] to implement it
[ONE Android Development] stranostrano:
Hi kodora,

What do you mean about zzmoove?

You have to disable all hotplug and in kernel adiutor, select cpu zzmoove, and in "cpu governor tunable" you make your mods according to [MENTION=3279788]ZaneZam[/MENTION] zzmoove http://xdaforums.com/galaxy-s3/development/info-cpu-governor-zzmoove-t2326544op post here.

I've reviewed my source and zzmoove cpu governor and zzmoove profile are updated to ver 1 beta8.

Could you be more detailed?

Thank you for your report.

Have fun. ...always

Inviato dal mio A0001
[ONE Android Development] kodora:
Hey [MENTION=862741]stranostrano[/MENTION], zzmoove is a governor that has its own hotplug. The tunables for these hotplug can be found in "sys/devices/system/cpu/cpufreq/zzmoove/" and edited on the cpu tunables section in any kernel app (like kernel adiutor). You can check the screenshot I attached that show some of this values on other kernel available on the forum.
[ONE Android Development] stranostrano:
Hey [MENTION=2207256]kodora[/MENTION], that's exactly what I'm talking about and this is the screenshot of my kernel adiutor

Inviato dal mio A0001
[ONE Android Development] kodora:
I think you aren't understanding me (or I am not understanding you.. lol), what I am saying is that those hotplug tunables that allow tweaking zzmoove hotplug don't show up in kernel adiutor and are not present in the folder where these values should be (sys/devices/system/cpu/cpufreq/zzmoove /". At least I don't see them in my kernel adiutor tunables section (the screenshot I posted is from another kernel).
[ONE Android Development] stranostrano:
Hi [MENTION=2207256]kodora[/MENTION],

could you check which version of zzmoove is in your screenshot?

The commits pushed from zanezam is completely ported in my source but effectively I can't find the "hotplug" section in mine kernel adiutor.

I dunno if is related to the version or I need to enable hotplug in some place (defconfig I think).

I want to collect some more info before to contact zanezam for a suggestion.

Thank you and have fun. ...always!

Inviato dal mio A0001
[ONE Android Development] stranostrano:
[MENTION=2207256]kodora[/MENTION],

sorry you're right.

the ver. 1.0 beta8 have the hotplug function disabled. I'm working on re enable the hotplug function and soon I'll update a fixed version.

Thank you for your report.

Have fun. ...always!
[ONE Android Development] stranostrano:
Hi all,

version 2.2.1 is out.

- Updated zzmoove cpu governor to re-enabling native hotplug functionality (thanks to [MENTION=2207256]kodora[/MENTION] for reporting issue).

- Added "Bricked hotplug" (MSM MPDecision hotplug) from [MENTION=4195844]show-p1984[/MENTION].

As always, you can find downloadable zip in 2nd OP post.

Have fun. ...always!
[ONE Android Development] mada1991:
Many thanks

I'm trying...

This kernel is amazing...

Really many many compliments...
[ONE Android Development] kodora:
Hey [MENTION=862741]stranostrano[/MENTION], thanks for the quick update even before I could answer! :D

Will flash ASAP and the report if any issue arise.
[ONE Android Development] Traace:
I would really like to try this Kernel on SlimSaber, [MENTION=862741]stranostrano[/MENTION] could u please add F2FS support?