yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ZaneZam:
hi fflokes,

you are messing with the beast eh? i know where u were going through :D

thx for the efforts and the info , nice debugging!

well the scaling logic has grown to a quite complex thingy in recent versions but it's still a logic and has to follow rules

but sometimes the "beast" plays games with u, we just have to reveal which one exactly (sometimes it's complex like chess,

sometimes simple like "uno" *g*) but so far i always won the games its trying to play, fortunately *g*

ok enough personification now :)

i will try to reproduce this with your code when i have time - my permanent issue atm beeing low on time for the funny things :(

but i will check that out, even though i never had that stucking problem again since many versions and v0.8b1 runs since weeks

without issues, but well i know it's the beast and everything is possible! :D

and in short: no i have no clue atm. :)

cheers

ZZ
[Galaxy S III Android Development] ZaneZam:
interessting ey, veeery nice jop man!! many thx for sharing this!! :good: i even have a few of that features on my todo list (about over a month old list though *g*) :) will check out your repo asap! btw. i like that picard tuneable *gg* now i think about to add a "make_it_so" confirmation tuneable :D
[Galaxy S III Android Development] erwinhayamz:
Awesome!

I've been using this governor in boeffla kernel, battery life's great, so snappy, thanks :good::good::good:

Just a bit bug here, when i'm playing Samurai Siege (game), i notice there's an extremely hot temperature behind my i9300, just around battery (Trying all zzmoove profile, it's come with the same issue). When i switch to pegasusq governor, the hot thing dissapeared. Any thought with this?
[Galaxy S III Android Development] ZaneZam:
hi erwinhayamz,

thx, yeah tested and confirmed even with all new settings and current v0.8b1 but i have to make that statement: it's not a bug, its a behaving :)

u will get higher temperatures with zzmoove because the cpu stays more often on higher freqencies as it does with pegasusq. zzmoove still has an "itchy trigger finger"! that will give u smoothness but on the other hand generates more temperature.(especially when u overclock to 1,6ghz!) not a problem when u use the phone "normally" but seems to be one if u play games like Samurai Siege which keep the system load

constantly

higher than "normal".actually i am not playing much so that never bothered me but i don't like that behaving and will look into this in upcoming versions :good: will try to calm the "beast" during gameplay, maybe with a new setting or in code, will see. meanwhile i suggest to use pegasusq if u want a cooler phone when playing games. ;)
[Galaxy S III Android Development] erwinhayamz:
Thankss, i'll wait for the next update then, couse i love the zzmooves 'snappiness' cheerss!
[Galaxy S III Android Development] JustArchi:
ZZ, I think that it would be perfect to implement something like "stay counter" or similar. It would track load and if it will be more or less stable during last ~30 seconds, zzmoove would slowly lower frequency to "required" one instead of preparing for more. Because if load is stable f.e. 80% at 800 MHz then we can guess that it won't get higher soon.

This way zzmoove would be able to adapt to the game and use only required frequency, while after game finishes it would jump to old good fast scaling mode.

Obviously there should be also a tweakable value for frequency, which we're looking for. Let's say that anything which requires 800+ needs to be adapted to this "perfect scaling" feature :laugh:.

Just my 3 cents.
[Galaxy S III Android Development] ZaneZam:
thx nice 3 cents archi! i consider to try out your idea... but first i have to finish 0.8 before it's getting older and older and older... :D
[Galaxy S III Android Development] tommi.a:
Hi Zanezam,

long time no see!

How is it going with ZZMoove 0.8?
[Galaxy S III Android Development] ZaneZam:
hi tommi and all,

sorry for the long silence, had to "scale down" activity a bit ;)

currently version 0.8 is in beta 3 stage, still have to sort out some

little bugs (mainly in tuneable stuff for profile support)

then we are good to go i think. but should not take that

long.

will keep u informed! :highfive:

Cheers

ZZ
[Galaxy S III Android Development] OldBoy.Gr:
First timer here, in my quest on zzmoove settings and in advance I feel the need to congratulate and thank you for your great work. Your 'beast' soon became my most favorite governor and weapon of choice when it comes to phone efficient tuning.

What I would like to ask is this.

Would it be meaningful to have different freq steps for upscaling and downscaling so we can bias towards either downscaling (battery friendlier) or upscaling (lag killer, performance oriented)?

Mind you I am not a dev so what I'm asking might not even make sense let alone be even possible so excuse me in advance if that's the case.

Eitherway thank you all who created and contributed in such a wonderful project in any way.

Best regards

Life is what happens while we... make plans!
[Galaxy S III Android Development] ZaneZam:
Hi OldBoy.Gr

thx for your kind words, happy to hear that u were not bitten by "the beast" and u like it! :)

funny that u mention that now, i just thought about faster down scaling some days ago during test of current version. ;)

well that sounds like a new mode for the fast scaling feature. as u surely know atm u can

give it a value from 1-4 for fast up scaling and 5-8 for fast up and down scaling,

normal up / fast down is missing indeed *g*. i think it would be no big deal to add a mode with range

9-12 for that purpose. will check that out and will see if it has a relevant effect.

regards

ZZ
[Galaxy S III Android Development] OldBoy.Gr:
I'm the one to thank you for such a beautiful 'beast'. Yes I use value 5 for that feature and durely seems to keep the 'beast' on a leech for now but still not 'tamed'. After all I m pretty sure tthat 'beast' nick did not come out of nowhere. Certainly there's a valid reason. ;)

Looking forward with excitement for the next release in line, whatever the changes/additions (or not) might be

Best regards

Life is what happens while we... make plans!
[Galaxy S III Android Development] maazy:
Hey, ZZ

Just out of curiosity, after developing a new version, how do you test it against the old version? :cool:
[Galaxy S III Android Development] ZaneZam:
hi maazy,

ehm by just using it :D

well u surely want a more precise answer don't u? *g* here u get one:

i usually make no comparison against older versions except when there is a problem with the new version to see if a new feature might be the culprit ;) honestly i do not need that comparison as i have a very good "feeling" how it should be after many weeks of watching monitoring apps and testing features (net view and testing time *gg*) i almost have the same base installation (always stock rom's with boeffla kernel) and same apps installed/running as i barely change my system and therefore i know very well how the beast should do its jop at least on my system.

For new features i go a "extrem-first-to-normal-stepping" way. first i check the max values to see if all works how it should as u mostly only "see" a feature by driving extreme values, then i lower them stepwise to a "normal" level (should be at previous bat saving/temp level or ideally better) and by that i start optimizing it. if at the end the values are working good from my point of view and my taste (tendential in bat-saving direction at cost of performance *g*) a long term test follows with maybe further optimizations! thats my way of doing it but there are also many talented and maybe even more meticulous tuners around such as my co-dev-bro Yank555 which did an amazing jop with his balanced yank settings! :good:

that's it, more or less :)

PS: these days i'm again more wrestling with the beast insted of otimizing it as it was again a little bit freakish :D

but all is well now (i think *g*) i'm carefully watching it just right now :eek:
[MENTION=5071121]OldBoy.Gr[/MENTION] that's one reason why i started calling it "beast" it's like a nasty gremlin sometimes ;)
[Galaxy S III Android Development] OldBoy.Gr:
Indeed I understand. Nevertheless my comment would be something like...

"And what a beautiful beast it really is! "

And along this line i can just imagine how wondetful it is to have control over such a beast in the palm of your hand!!!

Life is what happens while we... make plans!
[Galaxy S III Android Development] MojoManagement:
I hope you will trigger thread when 0.8 is released :)
[Galaxy S III Android Development] ZaneZam:
Beta 10

aye aye sure mojo ;) i just finished beta 10 and therefore reached the end of my self set beta-versions-limit. :)

next will be some code cleaning, profile tuning and documentation (uff *g*) then we are good to go... finally :o sry for the long delay!

meanwhile if u want a preview u can use one of recent boeffla kernel betas or yank kernels as they have latest zzmoove betas

included for testing.
[Galaxy S III Android Development] MIKEMON:
Good work, my friend
[Galaxy S III Android Development] Scarface1991:
I read somewhere (I believe in the boeffla thread) that you included something in the new beta to remove the stuttering when listening to music with screen off. Is it already in the newest zzmoove beta?

Until now I didn't experienced any music stuttering with the newest boeffla beta using zzmoove yank battery profile.
[Galaxy S III Android Development] andip71:
Yes, this was addressed by ZaneZam in beta10 of zzmoove 0.8, which is contained in latest Boeffla-Kernel beta.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] AndroidGX:
It looks to be currently exclusive to your Boeffla kernel anyway :p (since usually you were updating your github about betas but no more (17 days now) since you added ZZMoove beta v0.8 on it... :eek:)

Weird advertising ! :angel: ;)

Anyway I'm sure that final revision will be a bomb, like it is currently with v0.7 :good:

Cheers'
[Galaxy S III Android Development] Yank555:
The problem is, as soon as a beta of zzmoove is in the a kernel, we can't push our repos, as it would push zzmoove beta publicly and that would not be good, I think Zane's way to do proper beta testing to be the correct way, but you need a tester base.

0.8 beta has been taking unusually long (real life takes precedence), older 0.8 betas have been in my AOSP kernel for months now (first was 2013-09-23), and yes, I haven't pushed my AOSP repo ever since either (last public change was 2013-09-23), as I respect that way of doing things...

As soon as 0.8 is out of beta, all will be back to normal.

JP.
[Galaxy S III Android Development] andip71:
I think Yank explained it already... we are only allowed to push once ZaneZam give us final ok for it. Then of course it will be done straight away.

And no, the new zzmoove versions are not exclusive to Boeffla, also Yank kernel has them in already.

And yes, Yank and my kernel are somehow a bit exclusive on that, true :)

Andi
[Galaxy S III Android Development] AndroidGX:
Thanks for the clarifications guys, anyway if Zane is looking to another beta tester with a stable kernel, just tell me I will be pleased to do some reports and help as much as I can :good:

Otherwise no worries, I will wait for stable version and will understand :)

It's normal that your guys desserve betas since you both are working close with Zane about the governor ;)

Cheers'
[Galaxy S III Android Development] ZaneZam:
yes indeed as andi already said i included an idea in latest beta which seems to fix this, BUT as u know not all of those stutter problems are related to zzmoove so it's really just for those people who were directly concerned to this particular "bug" (in fact it "just" was a too harsh sleep setting). great to hear that it works for u, wasn't 100% sure if the changes i made are enough (i even was about to add something in addition but skipped that for now) it's a very important information for me, thx! :good:

oooh AndroidGX i really hope it will be a bomb (not literally! *gg*) and hehe no it was not really an intended advertisement but somehow it transformed to one recently :D

but well, as my great fellows Lord Boeffla and Yank555 (thx for diving in here guys! *g*) already stated, usually i have a very bad feeling about releasing betas as i have to be as sure as possible that it works good for the most of u ("all" would be an illusion *g*) and is stable at least in function and quality check takes a "little" bit of time. so at one point and after an unwanted long term test of an early beta from my side (as Yank555 stated i unfortunatelly had to priorize "real"-life stuff) i had a good feeling and gave my friends here access to the private beta repo and a "go" for releasing it in their kernels to see how the new beast works in the wild (not really having in mind how much users these two great devs are serving - [MENTION=2033478]Yank555[/MENTION], actually i was "shocked" about the downloads *ggg* ) The "more patient" one of these two guys Lord Boeffla hooked in with a later beta then, but if u know andi u know that this is usually a "near-final-sign"! :)

long story made short it will be soon available for everyone but i still have to finish some stuff (mostly the beloved documentation! *g*)

and even if i'm repetitive: that will not take that long any more :)

cheers

ZZ
[Galaxy S III Android Development] ZaneZam:
thank u AndroidGX much appreciated! good testers are allways needed and i will take the offer if i come to that point! ;)

and yes admitted :angel: Lord Boeffla and Yank555 will always have the "be-close-friends-bonus"

i'm very plased and happy to be able to work together with these two great guys.

ok stopping now i'm getting sentimental.. :crying: but its a fact! ;)
[Galaxy S III Android Development] andip71:
Thanks ZaneZam, very nice words. Same goes for you as well.

It is always a pleasure!

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] Yank555:
Let me join the party, a real pleasure it is indeed to be able to work with the both of you ;)

zzmoove is making its way to my Notes 3, still WIP, but it's compiling fine already, hope to get to work on it tomorrow evening again.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta3 kernel.
[Galaxy S III Android Development] ZaneZam:
And this was an example of intentional advertisement! :) and a nice one!

good to see the beast in this "zoo" too JP aka beast master :D looking forward to your full working version

and if it doesn't well behave just call in! :)
[Galaxy S III Android Development] OldBoy.Gr:
Me being NOT a programmer, let alone a dev, used to toy and tinker a little bit with C in my teens but of course nothing as deep as what you guys do. I was doing it for just the pure fun of it and the personal feeling I got when I could create something out of nothing.

Nowadays I fancy spending my spare time reading about Java a little (still got the itch), nothing serious again but I do like to get the taste and feeling of a more modern language from oo model and the likes. It is a different world ... yet again. It's another proof to my eyes of how vast programming world can be. Or should I say world within worlds? Needless to say it still feels as good, if not even more, when I accomplish anything, even the simplest of things like the notorious "Hello world" paradigm.

The seer feeling that I can communicate with the machine on my terms is itself alone more than enough to keep me going. So I certainly can't (and won't) classify me as a programmer, not even remotely but there is one thing I certainly learned as a hobbyist back then and now again as student. And mind you, I learned it well..

One of the most precious things in a project(among other things, be it for the fun of it or for your everyday job, if not THE most precious of all things, is TIME. And in so many ways too.

So all you fine people who are working so hard and are always committed to bring the best out of whatever you create, take your time for you not only deserve our patience at least, but you have earned it already as well. After so many efforts and personal time you have spent and while you keep doing it in a way that it looks as if it's easy while it's not, I for one believe that the right to expect patience from me as a user, is a right that you've earned again and again and again.

That said, I don't know if the above even makes any sense, but I firmly believe that those to whom it does make sense, are some of those I can't thank enough ever.

Best regards
[Galaxy S III Android Development] ZaneZam:
no question what u wrote makes absolutely sense to me and touched my heart OldBoy.Gr :)

very well said man, thx!
[Galaxy S III Android Development] Abo3mood:
I reverted back to Googy-Max2 2.1.5 which is awesome.

Could u please tell me how to tweak ZZmove to work with 2 cores most of the times in a similar way like boeffla-moderate if possible.

I guess I select ZZmove-custom under governor tab & change settings under ZZmove tab ?

Thanks in Advance :)
[Galaxy S III Android Development] ZaneZam:
hi,

i can't tell u exactly how u can set this in googy kernel, but i can tell u which tuneables has to be set to have permanently only 2 cores online:

up_threshold_hotplug3 = 0

up_threshold_hotplug2 = 0

up_threshold_hotplug_freq3 = 0

up_threshold_hotplug_freq2 = 0

or

for a pegasusq moderate like behaving (u have to try yoursef if this really suits your needs - i just did a fast test)

up_threshold_hotplug3 = 100

up_threshold_hotplug2 = 100

up_threshold_hotplug_freq3 = set to your freq max value (mine is currently 1600000)

up_threshold_hotplug_freq2 = set to your freq max value (mine is currently 1600000)

an "advantage" with zzmoove would be that it turns off the second core in addition (and fast) on "idle"

and in general switches cores faster then with pegasusq. that isn't 100% the same behaving, but similar ;)

good luck

ZZ

EDIT: Thx for giving me the initial idea for an moderate zzmoove profile!:good::D
[Galaxy S III Android Development] MojoManagement:
Beta 10 already, very excited....
[Galaxy S III Android Development] Abo3mood:
Looks like 0.8 Is coming soon, hopefully ;)

​
[Galaxy S III Android Development] ZaneZam:
polishing the beast :)

well indeed guys my absolute silence indicates that it will not take too

long till the new beast will jump around on your devices,

i'm just polishing it for the "appearance" but i still must brush its teeth :D

now serioulsy beta 10 was good, the yet final might be even better in terms of stability.

i changed "some" things and fixed little bugs in addition in the final version. and since yesterday

it runs very good for me here! but however the experience in the past has shown that this doesn't

mean that it also have to for all of you, but at least i strongly hope so! we will see... ;)

stay tuned...

ZZ
[Galaxy S III Android Development] OldBoy.Gr:
You mean while the beast behaves in your presence, it might as well NOT do the same with us? Maybe after you let it go out in the open, it will turn wild and show to some of us it's 'beasty' side?

Cause if that's what you meant, then I think to myself...what an excitement and a joy will that be! Finally if I can't help by being a dev at least now I can help by being a good user that will report back possible 'beasty' ... moments ;)

So my thoughts drift and fade into that one 3 words line...

"Bring it on!"

PS. Just wish for a good note2 7100 kernel that will support it. The rest will be between it (the beast) and me! The result? Oh well... that will be right here, published and documented as it should ;)

Best regards

Life is what happens while we... make plans!
[Galaxy S III Android Development] tony45x220:
I'm on the Galaxy Note 2 v2.04b2 version of Plasma kernel (which may or may not apply to this governor it's from November 2013) but my question is which setting in the tunable parts of the governor allow you to turn off the instant "touch boost" everytime I touch the screen it automatically turns on two cores to 1.4Ghz and I think it's quite a waste... And can anyone share their settings for this governor, I'd like to have my CPU time in state clocks a lot higher in the 100mhz range in sleep... This governor never seems to settle down and sit at min frequency like the 70-90% min frequency time I get with ondemand.

PS ignore my signature just haven't had time to change it yes I'm on the sprint Galaxy Note 2 lol
[Galaxy S III Android Development] Yank555:
That's not part of the governor, neither zzmoove, nor PegasusQ btw. This is hardcoded in the kernel, but I made a mod quite a bit ago where this could userconfigurable, so you could adjust the touch freq. yourself.

Your kernel dev would need to include that (I can't point you to the exact commit right now, but if he knows his way around in github, he sould be able to find it in my repo.

JP.
[Galaxy S III Android Development] tony45x220:
OK thanks for clearing that up! I'm running an older 4.3.1 build since I don't think the source for KK is out yet, so not much customization, it'll probably be included in a more recent build once my dear get around to it.
[Galaxy S III Android Development] MIKEMON:
@ ZaneZam

I do not know why it seems to me gov.intelliactive in Boeffla kernel to something faster?

Zzmoove optimum is super, it seems stable, but I feel intelliactive greater smoothness system.

For me, the absolute best zzmoove optimal ....

thank you for the information
[Galaxy S III Android Development] ZaneZam:
hi misacek,

well that might be because with intelliactive the system doesn't have to wait for cores to go online

as it rarely plugs and in addition the scaling frequency is mostly in mid to higher range with intelliactive

something which might also be possible with zzmoove depending on settings, but the question

is how much is the impact on batterly life with such a setting. maybe something to test but first i have

to take care about other things ;)

btw: ever tried the performance setting? that might be something for u if want it "faster" :)
[Galaxy S III Android Development] Hidden-Hunter:
Hi [MENTION=3279788]ZaneZam[/MENTION]

Gov Zzmoove is stable and faster and best profile for battery saving, But Gov zzmoove using all cores, The governor ZZmoove changed using only 1 core or 2 Cores ??:laugh:

Thanks:good:
[Galaxy S III Android Development] ZaneZam:
depending on the used setting yes it's using all cores, you want to know how to set it to have only 2 or one core active?

you can turn off cores manually by setting the tuneables like so:

only 1 core :

up_threshold_hotplug1 = 0

up_threshold_hotplug2 = 0

up_threshold_hotplug3 = 0

only 2 cores:

up_threshold_hotplug2 = 0

up_threshold_hotplug3 = 0

im working on a moderate setting which uses almost everytime only 2 cores automatically....

....but first i have to fix some bugs in current version 0.8 which isn't release yet because of that! :(

but this time i can't blame the beast, i contaminated the source with some ugly stinking selfmade bugs :D
[Galaxy S III Android Development] andip71:
But tell me... why are you doing that?? :D

*running*

Andi
[Galaxy S III Android Development] ZaneZam:
obviously i love the chellange, self made mistakes are the best as u surely know andi! :)
[Galaxy S III Android Development] AndroidGX:
I can see that some insecticides are needed then :D:laugh:
[Galaxy S III Android Development] ZaneZam:
Yeah indeed AndroidGX I sprayed some good beetle poison on my phone and let it rest for one week. now everything seems fine the bugs are death (at least the ones I was aware of) :D
[Galaxy S III Android Development] AndroidGX:
:D:D
[Galaxy S III Android Development] MIKEMON:
@ ZaneZam

thanks for your work, for me, the best governor

I use Boeffla kernel and optimal Zzmoove / but sometimes angry /

I'm waiting for the update and will, I hope perfect

many thanks
[Galaxy S III Android Development] you_man:
Hi [MENTION=3279788]ZaneZam[/MENTION].

As advances with new profiles?:laugh:

Looking forward to your labors.