yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ZaneZam:
Unfortunately that will not happen so very soon as yank555 has to take care of some family issues. Dunno when he is back :(

But I just had an idea regarding this problem, will PM u when I am on PC!
[Galaxy S III Android Development] fusionjack:
is it enough to just change the MAX_CORE to 2? or there is same part of codes need to be changed for dual core?
[Galaxy S III Android Development] ZaneZam:
no max_cores macro is only for the new flexible scaling/hotplugging methods. and yes for the legacy mode there are changes necessary as stated in source

so no support for 2 core systems in legacy mode atm ;)
[Galaxy S III Android Development] fusionjack:
no, what i meant is that i have integrated this governor into cm based kernel for i9100 (dual core) and i changed only the macro from 4 to 2.

i wonder if there is anything else that needs to be done for dual core.

i have already used this governor (v0.7) and it seems working fine. :)

i'm asking this just want to make sure whether i set up this governor correctly for dual core. :p
[Galaxy S III Android Development] eskriminal:
have you had a look at the adaptation done by a dev for dorimanx? they changed sources quite a bit I think
[Galaxy S III Android Development] fusionjack:
afaik, at time i integrated this governor, the changes in dorimanx or kangbang (cannot remember anymore) was to adapt the freq table which don't need anymore since v0.6. (correct me if i'm wrong)

edit: thanks for reminding me to take a look into dorimanx github. :)
[Galaxy S III Android Development] eskriminal:
not sure, can't remember what alucard did at the time, but always good to check eh? np fusion, any time
[Galaxy S III Android Development] ZaneZam:
yeah u do not have to change anything in the source since 0.6. just put the amount of cores in max_cores macro, that's it. this macro is just for disabling/enabling the corresponding hotplug tuneables ;) u can even put in 8 cores here and the right amount of cores will still be automatically detected by the governor! but then u will have 8 hotplug up/down freq and 8 load threshold tuneables for just 2 cores. ;)

Btw. the possible scaling frequencies will also always be detected automatically on versions >0.6 even if the scaling table is "inverted", so also no need to change anything here.

now all this applies ONLY to the updated scaling/hotplug logic NOT to the "new" legacy mode as this mode was taken directly from version 0.4 (enhanced with some little tweaks) and on that version 0.4 there was no auto detection at all hence only support for 4cores/scaling range (and steps) from S3 and similar devices ;) I included that mode because i heard of some people (S3 users) which had better experience with the scaling/hotplugging logic of 0.4 version and at the end its just an option for them. disable it put in the 2 cores in max_cores macro for your system and have fun with the new logic (hopefully *g*)
[Galaxy S III Android Development] fusionjack:
cool, nice explanation zane!

i'm still green regarding governor settings, that's why i just use the default setting and imo this default setting is already good enough for me. :p

keep up the good work. ;)
[Galaxy S III Android Development] ZaneZam:
ZZMoove v0.7b released!

Hi Guys,

again a new Version :D

enjoy!

ZZ
[Galaxy S III Android Development] N1m0Y:
:eek:

:D:thumbup::beer::)

Spoiler content hidden.

Inviato dal mio supermuletto :tank:
[Galaxy S III Android Development] Shahan_mik3:
Using v0.7b from past one hour...smooth and silky :D
[Galaxy S III Android Development] AndroidGX:
Fantastic job mate, I confirm that v0.7b works now perfectly on my stock kernel ! :good:

Very nice find ;)

See you laters :highfive:
[Galaxy S III Android Development] ZaneZam:
Great! Glad it works now! :)
[Galaxy S III Android Development] Choristav:
I love zzmoove with yank's settings.
[Galaxy S III Android Development] ZaneZam:
ZZMoove Version 0.7c released!

Hi Folks,

just pushed the v0.7c to the repo!

no big changes and the last one for 0.7 :)

scope for 0.8 in the OP!

have fun!

ZZ
[Galaxy S III Android Development] MIKEMON:
Hello, everyone, it would be better less load on,, GPU, and then everything was very good.

gov.co best I've had ...
[Galaxy S III Android Development] AndroidGX:
Thanks for your hard work mate :good:

Currently compiling my v2.7 kernel just for your governor :p

'laters ! ;)
[Galaxy S III Android Development] MIKEMON:
Very good, thanks ZaneZam ..
[Galaxy S III Android Development] temasek:
Temasek kernel will include the awesome zzmoove 0.7c

ETA 5 mins
[Galaxy S III Android Development] JustArchi:
As always excellent work ZZ :).
[Galaxy S III Android Development] longntt105:
this kernel can use for rom glance 2.3 ? plez help me
[Galaxy S III Android Development] petros70:
It's worked on 4.2.2?
[Galaxy S III Android Development] bgn9000:
Interesting topic, I am challenging my own thoughts with this governor.

Good job ;)
[Galaxy S III Android Development] petros70:
Zanezam this mod it's work on 4.2.2 roms
[Galaxy S III Android Development] eskriminal:
1.of course it does, it's a CPU governor not a tweak

2. don't bump your posts, especially in under a day
[Galaxy S III Android Development] francescozanghetta:
Many thanks for your great work.

is there any way to delay the kick in of freq_limit_sleep?

thanks in advance
[Galaxy S III Android Development] ZaneZam:
thx..

no not yet, why would u need that if i may ask?
[Galaxy S III Android Development] francescozanghetta:
I think (my personal opinion ;) ) it would be great because in that way the freq_limit_sleep can be applyed just after touch wake delay time. I think that they should work one (freq_limit_sleep) after the other one( touch to wake).

Just a suggestion to make the logic more harmonic
[Galaxy S III Android Development] ZaneZam:
thx interesting will think about it but first i have to fix some bugs :fingers-crossed:
[Galaxy S III Android Development] bgn9000:
I am releasing a new version of my kernel (shun S3) with 0.7c with Yank profiles. Very nice results.

I have one issue about up threshold hotplug freq if equal to max frequency (core stuck to this frequency).

Trying to enhance my own governor with your nice job ;)
[Galaxy S III Android Development] ZaneZam:
nice to hear that, thx :)

regarding the issue i will take a look, did'nt set such high vaules yet :)

i'm currently bugfixing araound a little bit so if i find something i will of course

fix that by the way..
[Galaxy S III Android Development] ZaneZam:
ZZMoove Governor 0.7d released!

Well Mr. never say "the last one"! :D

sorry guys but i have to throw out an additional bugfix release and now i

hope

that this is the last one for 0.7 :)

Enjoy!

it would be nice to hear from the guys that had problems with any tuneables

if setting "their" value-combinations works now. thx! :fingers-crossed:
[Galaxy S III Android Development] AndroidGX:
You made the same mistake as me, never promise! :D;)

v0.7d added into LiteGX kernel, and just released v3.1 with it :good:

thanks for your work mate :)

Cheers'
[Galaxy S III Android Development] andip71:
Boeffla-Kernel will follow tomorrow

Hi,

Boeffla-Kernel will be distributed in version 3.1-beta3 tomorrow (if all goes well until then) with zzmoove 0.7d.

Thanks ZaneZam for fixing the tunables stuff together, so now it works as expected :good:

Andi
[Galaxy S III Android Development] davtse:
Hey ZZ,

Is this the issue I PMed you about? If so, super excited :p

As always, absolutely marvellous work. Will report back if the problem is fixed soon! :good:
[Galaxy S III Android Development] MIKEMON:
Big thanks ZaneZam, great work, I hope that boeffla kernel will be super.
[Galaxy S III Android Development] ZaneZam:
Thx andy perfect! allways a pleasure to work with u and to make it work for u :D

looking forward to your beta3 and the new app version!
[Galaxy S III Android Development] ZaneZam:
thank u!

well i'm not certain, it's more a fix for the one [MENTION=3487382]bgn9000[/MENTION] reported, but would be of course great if it fixes your problem

in addition! ;)
[Galaxy S III Android Development] habylab:
I think a limit on sleep state depending on call status would work super well, if possible. My phone freezes otherwise.
[Galaxy S III Android Development] ZaneZam:
really? u mean if your phone sleeps and a call is coming in?

never had that on stock roms/boeffla but have u ever tried one of the following :

lower sampling_rate for example to a half of the currently used one

or lower sampling_rate_sleep_multiplier from 4 to 2?

in addition you can try to set fast_scaling_sleep to 2 or higher and/or

lower up_threshold_sleep to 85 or lower and/or set freq_limit_sleep to 800mhz or higher

one of these or all of them might help on your system... which is? rom? kernel?
[Galaxy S III Android Development] omek07:
ZaneZam

can i ask you if we can do something ???

When the phone is on standby its going on deep sleep i think...

When i push the power button the screen open after 1 - 2 seconds . Can we fix this ???

thank you
[Galaxy S III Android Development] bgn9000:
Issue fixed (now up threshold hotplug freq at max frequency is no more a sticky freq for 3 cores)
[Galaxy S III Android Development] 7wajahat7:
Running boeffla 3.1 beta 3 and using zzmoove extreme battery yank governor. phone freezes multiple times and there are alot of random reebots. anybody else facing it?
[Galaxy S III Android Development] bgn9000:
No such issues with shun battery profile (edit: Yank555 extreme battery settings).

[MENTION=5357006]Zumclub[/MENTION] profile added with a lot of tuning tests within.
[Galaxy S III Android Development] Yank555:
Extreme settings may induce lags, but freezes and reboots are not very likely...

Have you tested the same settings a clean fresh system ?

JP.

Sent from my SlimBean 8 / Yank555.lu CM10.1 kernel v1.6f-beta9 (Linux 3.0.94) powered Galaxy S3 i9300
[Galaxy S III Android Development] andrewfung888:
Hi!

i used boeffla 3.1 beta 3 with zzmoove.0.7d yank battery for one day only.

Phone is very smooth and no lag but i don't play game.

Battery life idle the best ever. 0.2%/Hr

Thanks Zanezam and Yank.:thumbup:

http://db.tt/Pyr5A4Fl

I found one issue was that the setting freq_limit_sleep is 700, the freq in sleep should be max. 700. But seems like the other way round and is min. 700 now. :confused:
[Galaxy S III Android Development] ZaneZam:
yeah indeed sooner or later the phones goes (hopefully!) into deepsleep, thats right :)

it's a good question if "we" can do anything against that because that behaving doesn't change if u switch for example to pegasusq!

at least on my phone currently with XXEMH1 stock rom installed (and i know it was also on all previous roms). sorry but that seems not governor related from my sight.

great thx for confirming!

also great thx again for confirming :)

Well as JP stated (btw. very nice to see u back here my friend!) it's very unlikely that the governor is the cause. i must say even when

testing veeery buggy alpha versions (one example: one time i managed to turn off all available cores lol) the system allways stayed stable

and i had never such problems. most of that freeze/reboot issues are coming from "uving". maybe forgot to reset uv settings?

just a little guess.. but yes again as JP stated a clean fresh system would be a good base for further testing.
[Galaxy S III Android Development] ZaneZam:
thank u! :)

min 700? that's strange it works here as expected like before and i didn't change anything regarding freq limit in new versions. hmm anyone else got this?
[Galaxy S III Android Development] andrewfung888:
Yes, very strange. You can see from my bbs log.

CPU States

==========

1.4 GHz (): 10 s 0.0%

1.3 GHz (): 0.0%

1.2 GHz (): 0.0%

1.1 GHz (): 0.0%

1 GHz (): 1 m 25 s 0.3%

900 MHz (): 0.0%

800 MHz (): 1 m 56 s 0.4%

700 MHz (): 3 m 31 s 0.7%

600 MHz (): 12 s 0.0%

500 MHz (): 11 s 0.0%

400 MHz (): 10 s 0.0%

300 MHz (): 7 s 0.0%

200 MHz (): 15 s 0.0%

Deep Sleep (): 8 h 28 m 56 s 98.4%

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

It is not really min 700. But most of the time is 700-1.1g during screen off.

:)
[Galaxy S III Android Development] ZaneZam:
looks quite normal to me, these are the peaks to freq_limit_sleep (=700mhz) and some other freq such as 800mhz and 1ghz (hardware wakeup frequencies - no hardlimit with governor possible unfortunately so u can see them) i guess u got the 700mhz when the phone is doing something at suspend (background activities such as email sync etc.) and was woken up for that. and/or the amount of time after disabling the display.. it needs a bit till the phone goes to deep sleep but the limit is active right after the displays goes off. so that might also be included

in that stat the time between display off and deep sleep. ;)
[Galaxy S III Android Development] andrewfung888:
Thanks, now i understand.

I think that is the behavior of zzmoove. In Pegasusq, i got most freq in 200 and 800 in idle. That's why i think more should be found in 200M.:)
[Galaxy S III Android Development] MIKEMON:
very good work, thank you very much

---------- Post added at 07:16 PM ---------- Previous post was at 07:09 PM ----------

@ ZaneZam, please do not describe different zzmoove gov. / Battery and other extreme /

in the fiber boeffla kernel?

Thank you very much, enough users asking ..: Zmatený:
[Galaxy S III Android Development] habylab:
Could someone quickly clarify Legacy mode? Does the disable in Googy Max mean the old method ("legacy") is used, and disable means a newer method?

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Galaxy S III Android Development] Yank555:
Pretty much that ;)

Legacy mode, if compiled into the kernel that is and the switch is enabled, will use the zzmoove 0.3/0.4 logics, as implied in the OP :

JP.
[Galaxy S III Android Development] ZaneZam:
hi misacek, thanks man!

u surely try your best but its always a kind of challenge to understand. (no offence) :)

to you want me to explain the different settings in boeffla or shouldn't i? u inverted your request (if it is one *g*) but

"enough users asking" implies that i should. am i right? ok will wait till u reply and maybe clarify a bit then

we'll get there sooner or later :)

thx JP my friend for putting this in one sentence ;)

now my usually slightly longer version :D

yes habylab exactly!

enabled = use old (legacy) method with fixed included scaling table and old hotplugging logic, disabled = use new (since v0.5) scaling/hotplugging method which is improved and "lighter". I implemented that legacy mode because of some users which

reported better battery life with < 0.5 versions of zzmoove. well, i dunno (no long term test from my side) if that makes any big

difference in recent versions but just try it if u want and report ;)
[Galaxy S III Android Development] MIKEMON:
Yes, a lot of users boefffla core inquire?
[Galaxy S III Android Development] ZaneZam:
OK will try to put that together in detail as promised on one of the starting posts when I have time. and that's the point unfortunately I've got very little atm. ;)

but here just a "quick" explanation:

nomen est omen:

"battery"

the first battery setting was based on conservative gov max battery settings I picked up somewhere some time ago and has the main task to save battery as much as possible but at the same time keep the system most of the time lag free. yanks battery and battery extreme should squeeze out a little bit more and at the same time "balance" the battery setting in addition due to the Hotplug freq thresholds (which also are balancing all other settings now)

"optimized"

is based on old battery setting and was made to nuke some little lags on older roms (and with older zzmoove versions). a bit more aggresive than battery but with similar behaving. unintentional it tuned into a "middle thing" between bat and performance.

speaking of "performance"

that "ferrari" setting was based on conservative max power setting I picked up somewhere some time ago and was made to bring u max performance as fast "as possible" but on the other hand keeps pretty quiet on "idle" times to still save same battery.

that's it roughly. ;)

but honesty I must say that these settings where just quick adapted every time to new zzmoove versions. so there is surely some more potential in every setting and maybe some of them can even be dropped completely, we will see..

zzmoove "grew up" faster than its settings and there is more to come so it still will take a bit till we have a really settled down set of settings :)

well a little exception are the yank settings now as JP did some maticolous researching with them and the good results when using it are proving that! :) so if u ask about a suggestion I must say that these are my favorites now ;)

cheers

ZZ
[Galaxy S III Android Development] hisee:
I tied battery profile and balance profile but i didnt notice any changes got same battery life
[Galaxy S III Android Development] Antidote03:
Sorry for the dumb question :rolleyes: can i or how i can add ZZMoove Governor to leaked Android 4.2.2

i just see the basic profiles pegasusq , powersave , performance , etc i want add ZZMoove Governer :confused:
[Galaxy S III Android Development] Yank555:
You can't, as it has to be included in the kernel and there are no (and most likely never will be) 4.2.2 kernel sources available.

JP.
[Galaxy S III Android Development] AndroidGX:
Try to be a bit more optimist ! :D;)
[Galaxy S III Android Development] Egozy:
Samsung is gonna skip 4.2.2 and head straight to 4.3, so never should be pretty accurate
[Galaxy S III Android Development] Yank555:
Exactly what I was impying, 4.1.2 -> 4.3 :D

They will only publish what the

have to

, hence whatever is official and not a leak.

JP.
[Galaxy S III Android Development] pemell:
Thanks for a great governor [MENTION=3279788]ZaneZam[/MENTION]
[Galaxy S III Android Development] N1m0Y:
Hello guys:)

Would be possible to add the freq_for_responsiveness and up_threshold_at_min_freq? You say is a good idea?

GS2 - SlimBean 4.3 - Dorimanx 9.41v1
[Galaxy S III Android Development] ZaneZam:
hi leonard, ehm nimoy :)

what do u mean exactly by "freq_for_responsiveness" ? and by "up_threshold_at_min_freq" u mean a seperate threshold for the time the cpu is idling at lowest freq? some similar function will be in version 0.8, its a kind of a up scaling break, u can adjust how fast upscaling should be ;) is that what u want to achieve, slower upscaling? beside of that are the tuneable names created by u or do they already exist in any governor? :)
[Galaxy S III Android Development] eskriminal:
they're in pegasusq, hyper, and some ondemand versions

they're exactly what you think, up at Min freq is a separate threshold, when frequency is below the freq for responsiveness set
[Galaxy S III Android Development] noobSU:
Locking CPU @ maximum frequency bug is still there. However it is pretty random. CPU hungry tasks can't even reproduce it. But still...

Happened 3 times in these 7 days. Only reboot did solve the issue not even locking & unlocking the screen solves it.

UI becomes so tasty on 1400mhz :p
[Galaxy S III Android Development] N1m0Y:
Exact:thumbup:

The goal is to obtain two different reactivity.... example:

freq_for_responsiveness 600

up_threshold 90

up_threshold_at_min_freq 65

In this way the user can decide whether to have more or less responsiveness to low or high frequencies.... maybe you could also add a freq_step_at_min_freq:rolleyes::D

Are all in the headwaters of the Dorimanx - gov Nightmare;)

I hope that my advice will be helpful to improve this fantastic governor:):beer:

THX m8;)

GS2 - SlimBean 4.3 SM - Dorimanx 9.41v1
[Galaxy S III Android Development] ZaneZam:
ok thx i understand, will think about that. for the time being in 0.8 there is now a adjustable scaling "slowdown" at a given freq/load

and a dynamic sampling rate which automatically alteres between a "high" (standard tuneable sampling_rate) and a "low" sampling rate (sampling_rate_idle) at a given threshold and with a adjustable delay. and hmm yes i like that freq_step_at_min_freq idea.. but as said have to think about all that when i have time (still not much atm! :( )
[Galaxy S III Android Development] ZaneZam:
hi

yeah good performance then with 1400mhz i guess! :p

but seriously 3 times in 7 days is pretty much i think! :(

which rom/kernel/zzmoove version? temasek+zzmoove 0.7d?

how is the load when it "locks" and is hotplugging working then?

again strange thing. i faced such a behaving ages (and many versions) ago on boeffla sammy kernel

but it

never

came back, something must provoke it on your current setting.

btw. recently [MENTION=947981]Lord Boeffla[/MENTION] worked on a similar problem in his new CM kernel! afaik

it has something todo with the latest upstream changes. maybe related? dunno if tema

is on current upstream 3.0.97 yet :o
[Galaxy S III Android Development] noobSU:
Hey!

Nope. Googy's kernel. 1.7.3.

The sweet thing is, It was locking single core on maximum frequency. As far as i remember about the last time. it just locks the cpu without even that much work_load. After changing to pegasusQ. CPU went from 1400mhz to 200mhz directly.

Btw updated Googy's kernel to 1.7.4a today. Which is 3.0.97.
[Galaxy S III Android Development] bgn9000:
Hi [MENTION=3279788]ZaneZam[/MENTION],

after ShunS3, I would like to add zzmoove to my kernel on S2.

I will give you results of my attempt.

If any help, may I post here my questions?
[Galaxy S III Android Development] Yank555:
Of course ;)

Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
[Galaxy S III Android Development] ZaneZam:
sure ! ;)
[Galaxy S III Android Development] N1m0Y:
Only ICS? :(

GS2 - NeatROM 4.8 LSW - Apolo 4.11 v0
[Galaxy S III Android Development] bgn9000:
Nop, I have my GS2 back and I can finish to update ShunS2 to JB :p
[Galaxy S III Android Development] ffolkes:
Awesome governor. :)

Do you have plans to implement something like "fast down" from this commit? Or is there similar functionality in ZZMoove already? Basically it sets a frequency limit beyond which the up threshold will be higher (as defined by another tunable).
[Galaxy S III Android Development] ffolkes:
Do you guys have any idea why I'm seeing this so often when using ZZmoove?

<6>[ 6267.919420] c3 notifier_call_chain : NOTIFY BAD tick_notify

They are being generated about every second or so in kmsg.

Thanks! :)
[Galaxy S III Android Development] ZaneZam:
Hi ffolkes,

thx glad u like it! :) and thx for the feature suggestion will have a look at it when i have time.

about the notify thing: it is caused by hotplugging events and comes from the way zzmoove switches cpu's on and off with the functions cpu_up() and cpu_down() ;)
[Galaxy S III Android Development] MIKEMON:
Gov. best I have ever used.

Super work, I use boeffla kernel and runs smoothly, the system super ..

Thanks friend for the great work
[Galaxy S III Android Development] ffolkes:
Just wanted to say, on my Note2 I've had this happen *without ZZMoove*. PegasusQ decided not to scale down last week and I went through a full charge in 4 hours. I finally wised up when my pocket was so hot for so long. Perhaps it's a problem in cpufreq or the various exynos dvfs locks. Unfortunately by the time I realized it, the kmsg buffer was long passed.
[Galaxy S III Android Development] anapospastos:
This governor is awesome. I really appreciate your work. Thanks:)
[Galaxy S III Android Development] MIKEMON:
S gov.zzmoove, I have no problem.

absolutely everything is fine and runs great.

stable system and sleep, set by the application, I am very satisfied
[Galaxy S III Android Development] ffolkes:
Update: I have found the problem in my case, but don't know what is causing it. dbs_tuners_ins.up_threshold is getting set to 0 sometimes on PegasusQ, which effectively locks it at max frequency. Manually resetting the tuneable back to default (82 in the case of PegasusQ) instantly fixes the problem. Perhaps something similar is happening to people reporting that problem on ZZMoove?