yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] MIKEMON:
Waiting for new Zzmoove in Boeffla kernel

it is for me, the absolute best governor

Thanks for the hard work
[Galaxy S III Android Development] Yank555:
Ok, that should have ruled it out then.

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6c-beta5 (Linux 3.0.82) powered Galaxy S3 i9300
[Galaxy S III Android Development] STAticKY:
Argh!! Now it won't go under 60 no matter how I set it. This is doing my head in lmao

TP.
[Galaxy S III Android Development] Yank555:
Have you checked with the time_in_state ? That should show you the numbers of cycles (or whatever it is) it spent in each state (40Hz/60Hz). As Andrei said, it's kind of flawed as in the absolute vales are not really correct, but if you compare, you see which one went up thus helping anyhow.

Haven't looked into making these time in state cleaner, but I don't really think it's worthwhile, it's good enough for me for the use we can make of it I guess.

JP.
[Galaxy S III Android Development] STAticKY:
TP.
[Galaxy S III Android Development] Yank555:
When you check several times, which one goes up ?

First line should be 60Hz, second 40Hz.

But again, don't look at the absolute values, look at the change between 2 cat's.

JP.
[Galaxy S III Android Development] Reni10:
Which version of zzmove is implemented in the Adam 2.5 kernel?
[Galaxy S III Android Development] Yank555:
[MENTION=5118425]STAticKY[/MENTION] : OK, clearly 60Hz is going up...

Really strange, I tested it back then, and it did work just fine on my kernel :confused:

JP.
[Galaxy S III Android Development] STAticKY:
I was starting to think it was bugged in temasek's kernel but [MENTION=4042238]amppen[/MENTION] just posted reckoning that he has gotten it to work....

TP.
[Galaxy S III Android Development] ZaneZam:
version 0.4 ;)
[Galaxy S III Android Development] ZaneZam:
yes thats strange JP. me too and it works well on boeffla kernel, tested this on

every

little zzmoove update (quite a lot these times *g*)

ehm after walking around (helps when thinking *g*) now like a flash i can remember something! :D

i had exactly that problem with linaro build of boeffla kernel some time ago so i did some changes in the accounting source to fix that. its a just a prototype waring but messed things up! maybe that works better in any way ;)

check this out: https://github.com/zanezam/boeffla-...mmit/6fbd31c48fac134a578ad292643da9104b666fa1

sorry i work too much i guess *g* too much things in my head...

EDIT: this version is included in the boeffla kernel
[Galaxy S III Android Development] STAticKY:
Ok . something is definitely not right here. Just flashed googy max kernel to test out lcdfreq and what do you know, max fps 40, all the time. So something isn't right in temasek's kernel... I took some v to go to sleep so I'm about to fall over Lol. In the morning I will clean my profiles from .temasek and give that another try. Last resort though. Else it must be bugged in his kernel...

TP.
[Galaxy S III Android Development] Reni10:
Any plans to update it to v0.5 anytime soon?
[Galaxy S III Android Development] Yank555:
That is Wanam's call ;)

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6c-beta5 (Linux 3.0.82) powered Galaxy S3 i9300
[Galaxy S III Android Development] habylab:
Thank you for this! Can't wait to tweak with the LCD values. Should allow some big savings!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Android Development] Yank555:
Don't get your hopes up too much, we've made that weeks ago, can't say I managed to see a huge difference unfortunately.

But do your testing and let us (me) know your findings, I'm very interested in other oppinions !

Currently I have it set up like this :

Kick_in_freq 200000

Kick_in_cores 3

Kick_in_up_delay 200

Kick_in_down_delay 200

So lcd will go to 60 only if at least 3 cores are up for 200 samples...

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6c-beta5 (Linux 3.0.82) powered Galaxy S3 i9300
[Galaxy S III Android Development] STAticKY:
OK. So uncleared my profiles for temasek's kernel and

This time all i did was switch to zzmoove and enable lcdfreq with kick in cores set to 4 and kick in freq to 1300(my max CPU freq is 1400). Still not working as it should. Also I DO think he is still using andreilux's original implementation of lcdfreq touch boost...

Edit: one last thing to try, backup, complete wipe, flash ROM without gapps, flash kernel, install stweaks, install fpsmeter, install nenamark, set gov to zzmoove, set lcdfreq settings, test... If that fails I'm adamant that there is a problem..

TP.
[Galaxy S III Android Development] STAticKY:
OK so I did all this and still the same result.

TP.
[Galaxy S III Android Development] amppen:
zzmoove along, people, there's nothing to see here

Nah, close but no cigar. It turned out to be bo****ks after all. I cat my .../lcdfreq_* and they were all as they should - turned on, all 4 cores, maxfreq, but still when I

cat /sys/class/graphics/fb0/lcdfreq/level

I get 60Hz.

So, I don't know what exactly fixed

one part of my problem

, that would be tuneables not working at all, but I wiped everything and installed latest temasek's rom and latest abb-wolfson kernel. Then I installed stweaks from playstore (not titanium backup) and put all the tuneables in through stweaks (and not manually via editing profile). Some of my hotplugs wouldn't stick so I had to force those editing manually, but luckily all lcdfreq related sticked.

I try to figure out something else, maybe there's new info I haven't seen yet. I was away for a while, I answered this one first thing.

Offtopic: Nice avatar. But what does it mean, that you got no love for the colour blind, eh? ;)
[Galaxy S III Android Development] Yank555:
I suppose Temasek might still have one commit in his sources that ups lcdfreq to 60Hz whenever you touch the screen.

STAticKY pointed it out here.

Temasek replied here.

Seems still in there, Temasek's experimental github still shows it in there... Maybe he didn't push to github yet ?

JP.
[Galaxy S III Android Development] JustArchi:
Let me guess the solution... :D
[Galaxy S III Android Development] ZaneZam:
hehe archi, yeah but instead of killall "bugs" currently the command for me should be something like killall "development" or these tasks will run forever! :D well coincidentally i just killed one of these which was called "RC2" :)

i will throw out this version a bit later today (i guess today *g*) to someone who will include it in his kernel soon *gg*. and guys this version, i promise, will be the last pre-version ever!!! next is definitely final 0.8 and available for everyone, i really can't stand it any more :) ...but these damn bugs, grrr!! :o
[Galaxy S III Android Development] andip71:
Ooooooooooooooooooh? ;)
[Galaxy S III Android Development] MIKEMON:
@ Zanezam

I eagerly await a thank you

Boeffla Lord, I hope placed in a new version soon

thank you all
[Galaxy S III Android Development] SaschaKH:
Oh sh.. I see a beta 6 comming, but I want to test the beta 5 linaro for at least 2 days more.
[Galaxy S III Android Development] andip71:
Yeah, sorry Sascha.

[MENTION=535343]all[/MENTION]: All my 5 kernels are out in new beta versions now, all of them including zzmoove 0.8 RC2 with a new profile (all credits to ZaneZam).

Andi
[Galaxy S III Android Development] nelsonw:
Wow, the insane preset of zzmoove it's... Well.. Insane... Great work [MENTION=3279788]ZaneZam[/MENTION] and Andi.
[Galaxy S III Android Development] Choristav:
I'm afraid I must post here

Thank you [MENTION=3279788]ZaneZam[/MENTION] & [MENTION=947981]Lord Boeffla[/MENTION]
[Galaxy S III Android Development] Hbohd:
Hi Zane :)

Couldn't help myself to ask: how is zzmoove development going on?

Were there any changes, improvements since last RC2 version? Or is it ready for public publishing? :)

I know it might be considered as asking for ETA, however it's hard to wait and wait patiently :p
[Galaxy S III Android Development] ZaneZam:
Hey no problem Hbohd,

if I would give u more information here then there would be no "ETA request". :) Sry for that...

... but my silence again has a good reason. I'm just finishing it for final release and yes it's pretty much RC2 so no big improvement just a last cleaning ;). but what makes me "slow" a bit atm is the creation of the new settings I should really give them at least a view hours of testing ;)

anyway my personal eta would be at any time tomorrow. at least I hope I get it finished as you are not the only one which is waiting... :o

Btw thx for your patience guys!!

stay tuned...

ZZ
[Galaxy S III Android Development] ZaneZam:
ZZMoove Version 0.8 Final released!

Hi Guys,

i can't believe it myself but after months of fiddling around with that near never ending version 0.8 it's finally done!

(at least from my point of view :) ) so as recently announced: sources updated on github and info added to second post

(it obviously would "blow" the first post *g*) also check out the new settings in profile file!

have fun with it and i hope u enjoy it!

PS: sorry for the format mess in the second post, will try to sort it out these days....but for the moment i need a break :eek:
[Galaxy S III Android Development] habylab:
Have passed the news onto Anas! Great work, huge change log.
[Galaxy S III Android Development] psndna88:
good... will try it

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v53 + AGNi pureCM ANYROM v2.7.4 3.0.101 with ART
[Galaxy S III Android Development] OldBoy.Gr:
Cant wait to try it. Im already out looking forward for note2 kernels that will support it. Hopefully devil will too when its dev finds some time to do so, inbetween family and work.

And while the above said imply my gratitude to you ZaneZam indeed including all those who have helped one way or the other, I'd like to explicitly THANK YOU for your hard work and determination.

That said let me see if my java skills are getting any better...

static class ZaneZam {

ZaneZam (thankYou(Dev aDev1,Dev aDev2, String rest)){

System.out.println("Thank You ZaneZam"+aDev1+" "+aDev2+" "+rest);

System.out.println("Gone happily insane, be back shortly");

System.out.println("after the break");

}

public void rocks(String aString){

System.out.println("once again");

}

}

class NewZZmooveInTheHood {

public static void main(String[] args) {

ZaneZam Zzmoove08=new ZaneZam(Yank555, LordBoeffla,"rest I forget");

Zzmoove08.rocks("the World");

}

}
[Galaxy S III Android Development] andip71:
Boeffla-Kernel will come out today with updates for all devices and platforms as release candidate versions, of course with the hot-off-the-press zzmoove final.

Stay tuned... :)

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] AndroidGX:
Nice job ZaneZam, Andi and Yank ! :cowboy:

You finally did it hehe :cool:

Just released SimpleGX kernel v1.2.0 with latest 0.8 ! :angel:

Cheers' :good:
[Galaxy S III Android Development] psndna88:
TRYING ON OMAP4,

from drivers/cpufreq/cpufreq_zzmoove.c:429:
drivers/cpufreq/cpufreq_zzmoove.c: In function ‘cpufreq_governor_dbs’:
drivers/cpufreq/cpufreq_zzmoove.c:4858:38: error: ‘struct dbs_tuners’ has no member named ‘up_threshold_hotplug_freq2’
|| policy->max < dbs_tuners_ins.up_threshold_hotplug_freq2
^
include/linux/compiler.h:147:42: note: in definition of macro ‘unlikely’
# define unlikely(x) __builtin_expect(!!(x), 0)
^
drivers/cpufreq/cpufreq_zzmoove.c:4859:38: error: ‘struct dbs_tuners’ has no member named ‘up_threshold_hotplug_freq3’
|| policy->max < dbs_tuners_ins.up_threshold_hotplug_freq3
^
include/linux/compiler.h:147:42: note: in definition of macro ‘unlikely’
# define unlikely(x) __builtin_expect(!!(x), 0)
^
drivers/cpufreq/cpufreq_zzmoove.c:4861:38: error: ‘struct dbs_tuners’ has no member named ‘down_threshold_hotplug_freq2’
|| policy->max < dbs_tuners_ins.down_threshold_hotplug_freq2
^
include/linux/compiler.h:147:42: note: in definition of macro ‘unlikely’
# define unlikely(x) __builtin_expect(!!(x), 0)
^
drivers/cpufreq/cpufreq_zzmoove.c:4862:38: error: ‘struct dbs_tuners’ has no member named ‘down_threshold_hotplug_freq3’
|| policy->max < dbs_tuners_ins.down_threshold_hotplug_freq3))
^
include/linux/compiler.h:147:42: note: in definition of macro ‘unlikely’
# define unlikely(x) __builtin_expect(!!(x), 0)
^
make[2]: *** [drivers/cpufreq/cpufreq_zzmoove.o] Error 1
[Galaxy S III Android Development] ZaneZam:
yeah indeed changelog is so huge that i sometimes forgot about if i have already included a change :)

and one line is even too much as it was from a beta->beta change (the one with the "oops" *g*)

but anyways now its released and stays there forever :)

lol that's very nice, thx OldBoy. kudos for that code part!! even if i "hate" java :)

superb my friend !! :cowboy:
[Galaxy S III Android Development] you_man:
Hi, [MENTION=3279788]ZaneZam[/MENTION].

Great job, thank you!

You have implemented a new profile, if so, what? :o
[Galaxy S III Android Development] ZaneZam:
yes i included a modarate setting as u wished :)

and it surprisingly runs very well with most of the time just 2 cores online.

soon you_man can try it for example with boeffla kernel ;)
[Galaxy S III Android Development] you_man:
Great, waiting kernel Boeffla.

And what do you recommend for best battery ZaneZam Battery Plus or ZaneZam Moderate?
[Galaxy S III Android Development] ZaneZam:
oops again a macro issue!! sry :o

but u can still try to compile it with 4 cores enabled, only difference would be that more tuneables are available then.

scaling/hotplugging should recognise that there are only 2 cores in the system ;)

damn so i have to make a little update for that case...
[Galaxy S III Android Development] ZaneZam:
can't say it in particular yet still testing these settings. i just gave them a few hours of function testing, but no long term tests.

logically it would be bat plus as it has a more "rise to idle" behaving and a higher sampling rate etc. but i would suggest

just try it an report back how it works for you_man :) (did i mention how much i love wordplays? *gg*)
[Galaxy S III Android Development] psndna88:
ok it did compile with 4 max cores
[Galaxy S III Android Development] you_man:
Yes :cowboy:
[Galaxy S III Android Development] andip71:
All 5 Boeffla-kernels are out now with this new zzmoove 0.8 gov.

S3 Samsung 4.3

S3 CM11

S3 Omnirom

n8000 Samsung 4.1

n801x Samsung 4.1

Have fun

Andi
[Galaxy S III Android Development] ZaneZam:
fine, and i just made a quick fix for it. will amend the final commit soon und let u know :highfive:
[Galaxy S III Android Development] AndroidGX:
A quick idea for you [MENTION=3279788]ZaneZam[/MENTION] : would it be possible to remove the profile file "cpufreq_zzmoove_profiles.h" to be required to compile zzmoove gov only in the next 8.x version ? as it seems useless in pure stock kernels (no profiles shown but just zzmoove gov only) :good:
[Galaxy S III Android Development] ZaneZam:
Updated Sources!

yeah i had that in mind (and even had it implemented *g*) but that clashed with other precompiler automated stuff (hotplug tuneables)

but i will try to find a way in 0.9! ;)

-----------------------------------------------------------------------

guys (especially [MENTION=4365701]psndna88[/MENTION])

I use this post in addition to inform u that i just amended the final commit with the fixed compile error when compiling for non-4-core systems.

so please re-pull, that's hopefully the last time u have to do that :)

cheers.

ZZ
[Galaxy S III Android Development] psndna88:
ok ill do it
[Galaxy S III Android Development] ZaneZam:
Information Updated!

Hi guys, me again :)

just quickly two infos :

updated third post with some useful information about build in profiles and switching to them! :good:

and i've made the zzmoove beta repository puplic now to avoid "teaser and waiting disasters" in the future :)

cheers!

ZZ
[Galaxy S III Android Development] habylab:
Would this be applicable to something like the Nexus 7?
[Galaxy S III Android Development] MIKEMON:
@ ZaneZam, hello friend

What is the ideal setting zzmoove optimal

Thank you for the great job, it's my favorite governor
[Galaxy S III Android Development] ZaneZam:
just had a quick look into a nexus 7 kernel, yeah might be possible but to know how much work it really is

needs a deeper investigation, though ;)
[Galaxy S III Android Development] MIKEMON:
The best description I found the Governor in OP

Thanks buddy, great job
[Galaxy S III Android Development] ZaneZam:
fine, thank u very much bro and also for "using" the OP because my fingers are starting to hurt :)
[Galaxy S III Android Development] N1m0Y:
A very small error in the comments....

the profile is zzopt 6 and 7 is the profile zzmod:p

Congratulations for the fantastic result that you got... Thank you very much:thumbup::beer::beer::beer:;)
[Galaxy S III Android Development] ZaneZam:
Thx for the heads up nimoy yes I know I even mentioned it in the third post. ;)
[Galaxy S III Android Development] ahac85:
Hi I dnt understand how I can use new profiles, can somebody give a step by step guide using terminal emulator. Im on boeffla 5.2 rc1 kernel

Sent from my GT-I9300
[Galaxy S III Android Development] MIKEMON:
tunable or endure than Lord Boeffla Add to

Absolutely, super job
[Galaxy S III Android Development] ZaneZam:
use the info in third post and do for example:

echo 5 >/sys/devices/system/cpu/cpufreq/zzmoove/profile_number

"5" would be the profile number

or just use the easier way with Android tuner or setCPU ;)
[Galaxy S III Android Development] ahac85:
Would I need to install the profiles?? OR r they already included, sorry ive read op but I'm still somewhat confused:confused:

Sent from my GT-I9300
[Galaxy S III Android Development] ZaneZam:
Yes one of the main features of version 0.8 are the now build in profiles so no need to add anything just config like described ;)
[Galaxy S III Android Development] ahac85:
Setcpu did the trick, thank u

Sent from my GT-I9300
[Galaxy S III Android Development] Buckycasuals:
Great work [MENTION=3279788]ZaneZam[/MENTION] . I will like to know Yank battery and ZaneZam battery plus, which one gives good battery life and performance.
[Galaxy S III Android Development] ZaneZam:
thx! well it's not known yet i'm still at long term testing ;), conceptional it would be yank bat. zanezam bat plus goes more in bat direction and should be a bit faster then the old zanezam bat setting but is not as smooth as yank bat (on my system!) atm i only can suggest you to check it out, see and report, thx :highfive:
[Galaxy S III Android Development] gsw5700:
V0.8 is a definite improvement, zzmove optimal is lightning, I've yet to determine battery life...

PS. ZZ, got your eyes on any of the new phones being released?
[Galaxy S III Android Development] ZaneZam:
thx gsw, happy to read about such a opinion from you! :)

well yes my eyes are almost "everywhere" :eek: *gg* but i think i will stay with my S3 for a further while

as no device is teasing me a lot atm and beside of that i had to spend my "phone savings" for this

second

device as i've lost my first one in a spectacular manner :D now i can laugh about that but it wasn't really funny

back then.
[Galaxy S III Android Development] ZaneZam:
Version 0.8 is out, long live Version 0.9! :)

Hi guys,

i wrote

after latest changelog of 0.8

indeed but well that obviously doesn't apply to my friend and co-dev [MENTION=2033478]Yank555[/MENTION] :)

during a chat session yesterday where we discussed the latest changes oin 0.8 he decided to do some more fine tuneing and so we have now an early version of 0.9 (alpha not puplic, aaah teasing starts again *gg*) since a few hours which has following included:

- fast_scaling tuneable splitted into fast scaling up / fast scaling down ones with possible values from 1 to 4 and 5 for auto fast sclaing

- removed Legacy Mode

- removed DFS

yes for this change we have to remove legacy mode as it is too inflexible!!

so before making such a step final i would like to know if u dev-guys out there are using the features "Legacy Mode" and "Dynamic LCDFreq Scaling" in your kernels. i'm considering to remove LCDFreq Scaling in addition as for me it's just a very nice proof of concept not more not less, i know of nobody who has reported/can confirm an improvement by using it.Yank555 and me inclusive! ;)

....but correct us if we are wrong and if you still want to use it by clicking the just created 14 days poll! ;)

if the result of the poll underlines my purpose then v0.8 will be the last version which has included these features. if not then we will create a "spin off version" called "legacy" and try to merge in new features there but that would makes things more complicated/costlier of course

thx for helping me with this decision! :highfive:

beside of the changes Yank555 recently made in addition some points of my scope for version 0.9:

- add threshold tuneables to auto fast scaling

- exynos thermal interface to control scaling blocks depending on cpu temperature

- possible change of default profile at governor start (atm it does nothing when changing the value in the default macro)

- try to make profiles support optional at compile time

- and so on and so on we will see... i'm a little bit tired atm but definitely not finished! :)

cheers!

ZZ
[Galaxy S III Android Development] cyberlord86:
Hmm, I was reading abiut and have 1 question. If Moderate is favoring 2 cores, but not as a rule, so it allowes the system to use all 4 of them; which setting is more performance wise... Moderate or Optimized? :)

The same question goes for Inzane vs Performance?
[Galaxy S III Android Development] ZaneZam:
well moderate uses most of the time 2 cores and only if the system needs more power (hence the threshold values 100 in hotplug up thresholds) it enables the others in addition. optimized enables them much faster (almost instantly if u whach the core activity) therefore i would say optimized is more performance wise. but i was surprised how well the system still runs with just 2 cores online. how much it differs for u personally depends on much things. how u use your phone, how well optimised it is and what u are mainly doing with it. ;)

"inzane" is an experimental complete new scaling method, i can't say much about it yet i'm still testing it (and the rest of the profiles, yeah still! *g*) but i've the personal impresson that it is more snappier/faster but maybe not as smooth as performance (applies for version 0.8 *g* thanks to yanks pre-work :good: and some hours of my work im currently testing 0.9alpha-2 and it looks better! yeah stop teasing idiot! *ggg*). i would say inzane is the winner here. that scaling method has definitely future in zzmoove, glad i did that experiment! :victory:

beside of all that i honestly have to say that there is not that huge difference between all the settings, zzmoove per se has a very hasty behaving and so the "magic" behind setting it "right" is just to make it "slower" without getting lags. :) you might ask yourself why so much settings then, well because i like to give people the option to choose and see which one fits the best for their personal usage. i really cannot give a universal setting for all of us there are too many factors around ;)

short question and (again) a too long answer...sry *g* but somehow it mutated into a statement for all of u :D
[Galaxy S III Android Development] cyberlord86:
Dat answer. :) Thank you for such a deep observation. :) And yes, for some reason Moderate gives me smoother UI experience then Optimized. And less wake up lagg on received phonecall. :P

Maybe placebo, but Moderate my fav setting. :)
[Galaxy S III Android Development] ZaneZam:
Fine very good then you maybe found yours ;)
[Galaxy S III Android Development] JustArchi:
ZaneZam - for me new moderate preset is BEST, I'm serious, I've tested everyone of them, and in my honest opinion zzmoove - moderate is the best option for having very smooth system without going insane, if you know what I mean :D. My ArchiDroid never was that smooth, hats off man, you totally deserve it :cowboy:.
[Galaxy S III Android Development] cheese458:
Me too. So smooth and not a battery killer.battery plus is a bit too battery friendly for me