yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ZaneZam:
happy u like it :highfive:, ehm yes this is a classic situation with zzmoove and its restrict sleep settings, and this is also the reason why the "relax" setting exist.

to fix that problem. back then i tried many combinations of settings to nuke these delays but the conclusion was that it can only be completely fixed by not

doing anything restrictive at screen off. so what u can do now is using relax setting (which is btw. almost moderate) or use moderate or any other setting and

give the tunable : "disable_sleep_mode" the value "1" then at once all sleep settings are disabled and u shouldn't have a delay anymore.

but the possible bluetooth "stutterings" etc. might be still present then because that depends on the online cpus at sleep (relax has two cores min to react that).

its as quickly as that explained i hope u get it also quickly done! as said fiddling around with all other settings is waste of time which i already did for u guys

no need to do it again :)
[Galaxy S III Android Development] ZaneZam:
overlooked that, sry (again one :eek:)

ehm well zzmoove is a "sprinter" which tends to peak a lot that's its "nature" so there is a chance u get more higher freq peaks with avarage load. BUT for my experience

mostly when "heating up" happens then the system load is also high. check if your system "hangs" on high load! recently i had such a problem with nova lauchner. my system (actually 2 systems) heated

up w/o any good reason. i found out nova launcher produced a constant mid to high load and zzmoove did it's jop in addition :) but the main reason was that high load of course. beside of all that

if u dont have that problem u might consider to use "moderate" or even "battery" settings which r made to user lower freq most. as a last step if all that doens't help consider to use another governor and see

if it does change anything ;)
[Galaxy S III Android Development] rpdroky:
Thanks allot for the kind replay and thanks to the description i get it now ;)

Cheers :highfive:
[Galaxy S III Android Development] Sourpatchmanx11:
Question

After flashing boeffla kernel, I can use zzmoove governor, but I cant access zzmoove profiles such as extreme battery yank. How do I access more governor profiles?
[Galaxy S III Android Development] andip71:
Why can't you access it? What is the problem?

Andi
[Galaxy S III Android Development] ZaneZam:
answered also in the OP2 thread ;)

and "OP2" is at the same time the "problem" andi as there are no such zzmoove profiles for it yet. :)
[Galaxy S III Android Development] LDAP98:
[MENTION=3279788]ZaneZam[/MENTION]

Great work!

But I wanted to make a suggestion if you have to much free time (like we all):

Did you tough about that for power consumption ist ist better to run 2 cores at a lower freq as 1 at a high freq? I observed that most (also zzmoove) governors first lover freq, then hotplug. Maybe you could add or create a feature which tries to keep a value down witch is the number of cores multiplicated with the number of frequencies but tries to calculate the best power saving.

I don't have the skills to invent such algorithms but Im sure you have.

Best greetings
[Galaxy S III Android Development] ZaneZam:
thanks, but unfortunaltely its the other way around i have too less free time these days hence not much happens here. :)

about your suggestion: can't say it might be a good idea yes but just to lower expectations and to say something i know 1.) keeping frequencies lower with zzmoove

mostly has also very neagtive effects on UI experience so u got lags lags lags which are not nice. 2.) zzmoove is based on the pretty "straight forward" logic

of conservative governor which "doesn't like" to calculate much around before doing anything with scaling especially when it comes to limiting

(which at the end is what u want as the logic normally would scale up more straight and fast and we would stop that) there we again come into the not nice

lag situation. if i state that then because i tried

a lot

to bring in more automation into the scaling logic (mostly to let zzmoove more scale in the mid

range of frequencies which it doesn't do that much - thats a con yes) but ended up with not wanted effects. now the wheels i put in which take

a bit care of that do that in a more "manual" way which found a better fitting to the whole governor structure and which at the end did what they should with

minimal impact to the ui. i finally come to the conclusion that this governor can't do automation well because of its "straightness". to put in more we

would have to include also more checks and timers which run in parallel which means more complexity but then we also can use other governors as a base.

as there are many good ones around which do that out of the box already. beside of all that we r talking about old stuff like "hotplugging" which i think is a dying technique.

Im also saying all that because the good old 1.0-beta8 version of zzmoove will be closed with a 1.0 stable tag soon and with that beeing so i will stop adding features

to it and go on with the the "Big Little Edition" which is "the future" of zzmoove and which has no hotplugging included anymore. ok that now even mutated to a little

insight of what's coming next in near future :)
[Galaxy S III Android Development] Frenzi2012:
i9300 overheat

They found some combination so the i9300 does not overheat and does not have lags?

When using it for 10 minutes with the screen on?
[Galaxy S III Android Development] ZaneZam:
who is "they"? [emoji4]

OK I try to extrapolate : u mean if there is a setting which doesn't make your phone hot? hmm it strongly depends on what u r doing at screen on but I would suggest you try the "battery" (maybe the yank one as this one might have the most less lags) settings or even the game setting which has the temperature tripping included which should avoid "overheating".

beside of that my experience is if there is overheat= system has a high load. zzmoove just uses high frequency more often then other govs if load is high. so maybe u also can check your system load if there is something using much load. thinking about media service using 100% load after start for some time and so on. just one hint in addition why that "overheating" can happen.

if nothing helps then as a last suggestion I even would recommend another governor. zzmoove isn't that much a "allrounder" [emoji6]
[Galaxy S III Android Development] elsaedy:
please sir...i hope to port this amazing boeffla kernel for note2 n7100...i think i9300 and n7100 have same cheap...thanks
[Galaxy S III Android Development] andip71:
Cross-post, you did the same in another thread.

The answer will be the same here: no.

Andi
[Galaxy S III Android Development] jlb1959.01:
it is very hard to find updated kernel for lg3 vs985,that carry zz ,and that's a shame,,a great governor!!!..
[Galaxy S III Android Development] mrpascal:
Hey [MENTION=3279788]ZaneZam[/MENTION] i want to add in cpufreq_zzmoove_profiles.h in my kernel

but i don't know where to add it & in which folder

can u please help me ?

And

can i add this governor to J7 prime G610F ?
[Galaxy S III Android Development] dkionline:
I wonder, if there is hope to get cpufreq_zzmoove_profiles.h support in bLE-develop-k4xx [MENTION=3279788]ZaneZam[/MENTION]

Governor works on EMUI8 so far.
[Galaxy S III Android Development] ZaneZam:
Seems Possible

what the heck, i missed that too.... sry! :o

check out what i write below it applies here too (if u didn't find it by yourself meanwhile which might be the case after that time *gg*).

hi,

ehm quick hint: for example take the latest used boeffla kernel sources which is for the OnePlus 5T (or others of course, but with boeffla i know it's working well ;) )

and compare following 3 files (be sure u use a "neutral" stock branch otherwise u have diffs because of boeffla changes):

https://github.com/OnePlusOSS/andro...neplus/QC8998_N_7.1/drivers/cpufreq/cpufreq.c

https://github.com/OnePlusOSS/andro...8998_N_7.1/drivers/cpufreq/cpufreq_governor.h

https://github.com/OnePlusOSS/andro..._N_7.1/drivers/cpufreq/cpufreq_conservative.c

in your case for example with (here too check the branch to be as stock as possible):

https://github.com/Huawei-Dev/android_kernel_honor_bkl/blob/master/drivers/cpufreq/cpufreq.c

https://github.com/Huawei-Dev/andro...lob/master/drivers/cpufreq/cpufreq_governor.h

https://github.com/Huawei-Dev/andro...master/drivers/cpufreq/cpufreq_conservative.c

if the files are the same or very similar (difficult to say how much) then u can even use the latest zzmoove bLE sources 1:1 (which i think is the case in this exact example, but don't take my statement as 100% true as i dind't check in particular it just seems to me like so, u would have to a check yourself again)

so the answer would be: source-wise it seems like it's easy doable (if i took the right sources *g*). if it's finally working can only be said after implementing and testing, tho.

if anyone want's to try here another hint: as said i know that the boeffla kernel implementations are working well so i suggest to take these as an example. with all the possible patches available but this actually needs another close eye of course, but anyway it's a good point to start with lord boefflas way to put it into source. ;)

[MENTION=7349820]mrpascal[/MENTION] the header file just has to be in the same dir as the .c file which is normally in /drivers/cpufreq

but this file firstly needs SoC specific adaption and secondly has no function in bLE (which is the version u would need as i checked quickly -> compare boeffla source with this : https://github.com/Exynos7870/android_kernel_samsung_exynos7870/tree/lineage-15.1/drivers/cpufreq ;) ) because there is no profile support yet and also not much "wheels" to adjust.

i take this as a possibility to short inform: it doesn't seem to but i still plan to port over the remaining meaningful options from "legacy" to bLE version of zzmoove, i just need to have time and power to do it so bear with me plz :)
[Galaxy S III Android Development] RFrancis:
Hello, why is hot plugging a dying technique and where can I read more about the up to date way of achieving balanced performance/battery.
[Galaxy S III Android Development] STAticKY:
Yep no flickering on any colour as long as its setup to stay on 40... Its when you have it set to dynamically switch from 40-60 that you get that flickering..

TP.
[Galaxy S III Android Development] davtse:
I am using a dark theme. Even then a clean black and white theme could stand to benefit from lower fps in terms of battery savings
[Galaxy S III Android Development] Yank555:
If switching occurs too often (aka. flickering), set kickin_delays higher (like 1000) and it will not switch all the time, that's what it's good for. The value is a number of samples, so depends on you sampling rate how long that is.

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6d-beta1 (Linux 3.0.83) powered Galaxy S3 i9300
[Galaxy S III Android Development] dhirend_6d:
0.5.1b is just killer. The earlier versions before 0.5 were also good but not as good as this. The new hotplug logic and scaling function doing wonders I guess. Its ultra smooth and slick. Hell I am not even using touchboost now and its working great. :) :)
[Galaxy S III Android Development] ThePureHeart:
Really? Haha, congrats!

What did you change for the governor settings?

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Android Development] dhirend_6d:
I didn t change anything. I am using zzmoove with optimized profile.

No OC. No ABB. No touchboost. Drain is also pretty good. This is what I got. Its pretty good.
[Galaxy S III Android Development] ThePureHeart:
[MENTION=3279788]ZaneZam[/MENTION]

Is there anywhere I can find zzmoove profiles?

Googy-Max uses STweaks but there are no profile so I was hoping you would know maybe? :D

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Android Development] ZaneZam:
hi,

well all i can provide are some init scripts from boeffla kernel. there are 4 settings available: zzmoove prototype (=hardcoded defaults) battery/optimized/performance. "profiles" as mentioned in form of init scripts which normally have to take place in /etc/init.d folder. but u could also run them with the app "tasker" if u know how that works or even simpler with "SManager" which can also do the jop for u on every boot. i think it might be a good idea to put them all together with a little description on the OP. yeah i think i will do that but i'm very busy atm so it can take a little bit. ;)
[Galaxy S III Android Development] ThePureHeart:
No problem - I look forward to it :D

It would actually be very useful so we can test and then find our own improvements.

Thank you for bothering :) :)

Sent from ThePureHeart's I9300 Boss Edition
[Galaxy S III Android Development] d4nrc:
Yank555 kernel + zzmoove in one word: AMAZING.

Thank you!
[Galaxy S III Android Development] davtse:
Very impressed. Check out the smooth curve. I would normally be getting sharp drops with screen on use. This is with lcdfreq limited to 40hz.:thumbup:

Before anyone asks, yes I'm using an extended battery, but even with the extended battery, this kind of usage is pretty insane.
[Galaxy S III Android Development] ZaneZam:
Version 0.6 released!

Hi guys,

the new version 0.6 is out of beta so

check it out: http://xdaforums.com/showthread.php?t=2326544

and enjoy! :)

regards

ZZ
[Galaxy S III Android Development] MIKEMON:
Well, yeah but how to insert cores boeffla new governor??
[Galaxy S III Android Development] ZaneZam:
Hi misacek,

I have little bit troubles to understand what u exactly mean :) but there is nothing special to do for boeffla kernel as the default core setting is 4. the new support for more/less cores should just help developers to implement the governor on non-4 core systems easier. ;)
[Galaxy S III Android Development] habylab:
Any kernels supporting this yet?!
[Galaxy S III Android Development] ZaneZam:
Hi habylab,

Hehe I saw your posts around

thanks for spreading the release info! :)

I guess temaseks and perkas shark kernel will have it first as they obviously just made some announcements ;)
[Galaxy S III Android Development] habylab:
Awesome, I'll have to try Shark then! Not on AOSP as I'm going to a festival so need a decent camera ;)
[Galaxy S III Android Development] N1m0Y:
Good work:)
[Galaxy S III Android Development] nelsonw:
Zam, why u added 8 cores support in this kernel, it's only for the S3 that have 4 cores. Or this is a base for/from other kernels?
[Galaxy S III Android Development] sakindia123:
the 8-core part will be activated only if the developer sets MAX_CORES as 8,otherwise that part won't be compiled :)
[Galaxy S III Android Development] Yank555:
Might I also add, this is not a kernel, this is a governor, which is the small part of the kernel that controls CPUs, and one of the goals of many of the changes we made in 0.6 are to make zzmoove portable to as many devices as possible, hence the :

- 2, 4, 8 core support

- scaling based on system freq. table

JP.
[Galaxy S III Android Development] habylab:
This is true. Governor has always been a place where I feel the S3 can hugely benefit from constant work - and now we have it with zzmoove!
[Galaxy S III Android Development] Perka:
I have updated shark with latest zzmoove :)

Thx zanezam.
[Galaxy S III Android Development] habylab:
And the winner is...!
[Galaxy S III Android Development] Yank555:
Hmmm ;)

Taken from my repo just now :

Publicly available :

I know, it's unfair :D

BTW, 1.6d and 3.4d kernels are out since.

JP.
[Galaxy S III Android Development] Pantherx12:
Using in temaseks kernel works fantastic thank you very much.
[Galaxy S III Android Development] nelsonw:
Yeah. Silly me. Sorry for that dumb question.
[Galaxy S III Android Development] PacketJ:
I'm back to zzmoove because of this using temasek's kernel. Good job zane, so far so good!
[Galaxy S III Android Development] nelsonw:
Any TW kernel updated with this Gov?
[Galaxy S III Android Development] ZaneZam:
Soon it will be in boeffla kernel too ;)
[Galaxy S III Android Development] Yank555:
Last of my 5 kernels is compiling, i9300 has been available since this morning (it's 16:24 here now), both Sammy 4.1.2 and CM10.1 and CM10. i9305 for now only CM10.1, Sammy 4.1.2 is the one compiling.

JP.
[Galaxy S III Android Development] psndna88:
Agni pureSTOCK v2.3.1 has it now !

sent from I9300 Ultimarom v13 + AGNi pureSTOCK v2.3.1
[Galaxy S III Android Development] N1m0Y:
Help.

How do I set 2 cores (default is 4)?

Where do I put the macro MAX_CORES? Within the script?

Edit: http://xdaforums.com/showthread.php?p=43578971

OK;)

Thanks:)

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S III Android Development] romskii:
after some days with zzmove 0.6 i have to say really great work. Now this governor is on it's best way :cool:

very stable and battery life is very good. Low drain while use.
[Galaxy S III Android Development] ayoubij:
I've been using pegasusq governor all my life and now I tried zzmove 0.6 and I must say it is wonderful !! Good Job [MENTION=3279788]ZaneZam[/MENTION] and [MENTION=2033478]Yank555[/MENTION] and wish you all the luck in the future.

Just a small question to all, where can I find some custom profiles? I am using temasek kernel, it has some zzmove predefined profiles, but neither one of them touch LCD freq and such stuff. Is there a thread for other users custom profiles?

Btw when using the battery profile, there is some delay when pressing the home button to get the recent apps page. What variable to change to fix this delay? (on performance it is instant)
[Galaxy S III Android Development] temasek:
Either

1. Use the zzmoove as it is or

2. Manually tweak the tunables or

3. Use the predefined profiles and manually tweak the tunables.
[Galaxy S III Android Development] Yank555:
This is the profile I use, dunno if it will improve the delay for recent apps, it's aimed at "snappy when possible, but mostly battery-friendly" :

CPU governor set to zzmoove.
Touchboost enabled at 500MHz.
CPU max. frequency set to 1.6GHz.
zzmoove - yank-battery profile :
zzmoove - sampling rate set to 180000.
zzmoove - sampling down factor set to 1.
zzmoove - up threshold set to 80.
zzmoove - down threshold set to 40.
zzmoove - ignore nice load set to 0.
zzmoove - frequency step set to 10.
zzmoove - smooth up set to 65.
zzmoove - up threshold hotplug1 set to 70.
zzmoove - up threshold hotplug2 set to 80.
zzmoove - up threshold hotplug3 set to 98.
zzmoove - down threshold hotplug1 set to 55.
zzmoove - down threshold hotplug2 set to 65.
zzmoove - down threshold hotplug3 set to 75.
zzmoove - sampling rate sleep multiplier set to 4.
zzmoove - up threshold sleep set to 98.
zzmoove - down threshold sleep set to 55.
zzmoove - CPU step for standby set to 1.
zzmoove - smooth up sleep set to 100.
zzmoove - hotplug sleep set to 1.
zzmoove - yank-battery profile applied.
zzmoove - CPU freq. max for standby set to 600MHz.
zzmoove - 1 step up/down fast scaling enabled.
zzmoove - 4 steps up/down fast scaling for standby enabled.
zzmoove - early demand enabled.
zzmoove - early demand threshold set to 50.

JP.
[Galaxy S III Android Development] ayoubij:
Thanks temasek im currently trying to do #3 you listed :p also thanks for including this in your kernel ;)

I will try to add some of yanks tweaks hoping for snappy and good battery life :good:

Thanks both of you :D
[Galaxy S III Android Development] temasek:
The zzmoove profiles were direct extracts from Andip71 github. There maybe changes to zzmoove 0.6 tunables so I'll probably will look deeper into the tunables soon.

Buy ZaneZam a beer if u love him. :)

... I meant his zzmoove :D

Edit : Btw if u manage to find a set of tunables that u find worth keeping then let me know and I'll make it a predefined profile named after u. :)
[Galaxy S III Android Development] ayoubij:
Yes I think there is one value called "CPU step for standby set to 1 " thank yank posted but I did not find it in stweaks (may be named different though)

Btw temasek, yank's profile is very similar to your currentl profile called "battery" but is snappier than battery, I think because he enables fast scaling. Check it out and maybe you can call it after Yank :p

EDIT: is it possible that u add a slot called custom and that we can set it to whatever you want? The reason I ask, is that if we want to change between profiles, but in a tweaked way. :)
[Galaxy S III Android Development] temasek:
As I said, I the predefined profiles for zzmoove in my kernel are extracts from Andip. I can anytime add more profiles when necessary. Just give me what u think are good set of values and I'll test it. If ok then it's good for profile.
[Galaxy S III Android Development] ZaneZam:
hehe thx tema :)

btw. no changes to the settings from andi's repo yet! JP did some fine tuning into the "saving battery" direction, so his ones might be the new battery values, will see.. i am currently testing slightly other values in addition also in saving bat direction and also working very fine for now. i previously stated that i will put all the settings to the op with a little description, will do this definitely but time is something i do not have much atm. so it could take a bit ;)
[Galaxy S III Android Development] ayoubij:
Ok will test yank's values for a day or two and give my impressions :) But till now running smooth. Will test for battery life :)
[Galaxy S III Android Development] temasek:
Ok

When u feel ready and good just let me know and post me your stweaks profile.

I call it Yankzzmoove
[Galaxy S III Android Development] kofe:
Yank555 here is the file that u requested in temasek's thread.

Hope this helps u.

I did what u said. After the phone froze i rebooted using power button, and then copied the file u told me to. So here it is.

LE1: sorry, i mentioned the wrong guy. :) Sorry ZaneZam.

It is for [MENTION=2033478]Yank555[/MENTION]

LE2: i flashed your kernel, and the phone does not boot. I was on temasek's ROM v108. Flashed this kernel and after the Samsung Galaxy S3 appears the screen goes black and won;t boot or anything. Booted in recovery, flashed temasek's rom again and temasek latest kernel and it is all fine...
[Galaxy S III Android Development] zeli9:
I've been testing yank's latest kernel with zzmoove and must say I'm very impressed, overnight drain with wi-fi off was 0.4%/h (and that's on a rather poor signal -91dBm), I never saw such numbers before. Also snappy and minimal battery drain! Amazing work from Yank and ZaneZam! Also happy to hear tema will include yank's profile into his kernel so that more people can check it out. Seems zzmoove is really the cutting-edge governor these days! :)

============

Battery Info

============

Level lost [%]: Bat.: -4% (88% to 84%) [0.4%/h]

Voltage lost [mV]: (4123-4079) [4.5%/h]

===========

Other Usage

===========

Deep Sleep (): 9 h 13 m 16 s (33196 s) Ratio: 94.7%

Awake (): 30 m 26 s (1826 s) Ratio: 5.2%

Screen On (): 5 m 57 s (357 s) Ratio: 1.0%

No Data Connection (): 25 s (25 s) Ratio: 0.1%

No or Unknown Signal (): 25 s (25 s) Ratio: 0.1%

Moderate Signal (): 1 m 52 s (112 s) Ratio: 0.3%

Good Signal (): 7 s (7 s) Ratio: 0.0%

Screen dark (): (0 s) Ratio: 0.0%

Screen dimmed (): 5 m 56 s (356 s) Ratio: 1.0%

=========
[Galaxy S III Android Development] Yank555:
You flashed the kernel for Samsung ROMs ;) Yoi need to use 1.6d.

I'll have a look at the logs.

JP.

Sent from my SlimBean 7 / Yank555.lu CM10.1 kernel v1.6e-beta1 (Linux 3.0.86) powered Galaxy S3 i9300

Edit :

Checked the log, unfortunately it only shows the boot, nothing from before the freeze, damn, I had some hopes here... :(

Thanx for trying !!

JP.
[Galaxy S III Android Development] kofe:
Lol, i was pretty sure i was flashing the right kernel. :)

Sorry for the log... Someone told me something about adb logging, but i don;t have any idea how to do that.

Think u can teach me how?

LE: flashed the other kernel for aosp, and it gives me bootloop... :(