yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] cyberlord86:
There is something I need to ask, again. :)

There is one glitch that I did not want to report eariler, because I waited to happen on at least 2 times on 2 different kernels. For no particular reason, when my phone is awakened from deep sleep, it is starting to lag like hell. Animation and scrolling. When I open CPU meter thingy it makes it even more strange: cpu freq is stuck to max but only on 1 core. When I reboot everything is back to normal until another random occasion.

ROM is ArchiDroid, and it is happening on both versions .12 and .13.
[Galaxy S III Android Development] ZaneZam:
thank u very much archi good to hear that from you as you surely did a precise jop with testing.. as always :good::)

and yeah it's really surprising that moderate runs so good...:victory:

ehm two questions: did u use the kernel setting "multi core powersave" in any way? beside of that did you check if any service is stressing the system for example with system monitor app?
[Galaxy S III Android Development] JustArchi:
You can use Cool Tool bundled with ArchiDroid to get app/binary which is causing the cpu lock. This may not be connected with the governor/kernel at all, but zzmoove would still run on all cores in case of such excessive load, to balance it, so I think it's possible.

Also, running "top | head" from the terminal should give your top 10 cpu processes, which is also enough for determining what is the problem.
[Galaxy S III Android Development] cyberlord86:
I forgot to mention: i am not using any kind of multicore powersave. And about service that goes into rage... tbh I did not check that with particular app. But, there is few reasons why not: it is fresh system with 10 basic apps: youtube, shazam, google translate, etc... not a single heavy app there. And second, when i switch to different governor, those stucking thing is gone.

---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------

But yeah, I can go into deeper analysis of the problem... :)
[Galaxy S III Android Development] MBurns2:
Thanks zanezam for the new profiles..

I believe that zzmove battery plus is awesome, imo the best zzmove for battery saving.

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] Yeti47:
I'd agree, I had issues with battery yank, but with battery plus works a dream. It's great that the different options are supplied as everyone's usage is different, so great we can play around with them to get the best one. Thanks!!
[Galaxy S III Android Development] MethMargera:
hahaha..i love both moderate n battery plus..<3 <3 <3

awesome job [MENTION=3279788]ZaneZam[/MENTION]

*wink*
[Galaxy S III Android Development] ~DemonLord~:
I have a question for the gaming profile, you say it will keep the phone cooler, does it do that by staying at a lower frequecy? Meaning does it improve battery during gaming than usual or just keeps phone cooler while giving the regular killer performance on regular profiles.
[Galaxy S III Android Development] ZaneZam:
yes exactly daemonlord, but i can't say for sure if it saves battery. i would need some long play tests with and without scaling blocks enabled for comparison - never did something like that, i'm not that big player *g*. the main aim was to keep the phone cooler because the cpu overheating was one big problem in previous versions. but well as i wrote in the changelog: theoretically it could save same energy but on the other hand as allways by reducing performance there can also be some lags. ;)
[Galaxy S III Android Development] JustArchi:
Games usually need a "fixed" amount of juice, previously zzmoove was preparing for more (based on cpu load), and this caused game to run at full power, even if it required only a half.

Now it's much better because zzmoove can detect such "constant load" and adapt frequencies to required ones instead of preparing for more, which finally results in saving on battery life and heat.
[Galaxy S III Android Development] ~DemonLord~:
Well a i noticed a few things after testing it, my device was actually a little cooler than usual :D , using powersaver so nothing goes less than 1000mhz, no lag what so ever actually it was smoother than before ( i used heavy battery saving profiles before) , i observed the frequencies using CPU Z but i was a bit shocked tbh, with no background process even after clearing ram, all 4 cores ran at the max speed (1000) slipping to 900 or 800 for a second, then occasionally turning 2 off just to turn them back to max. So basically good performance, less than average battery, seems very trigger happy, yet still notably cooler device which is tho not obvious from what is observed but it does what it says so great job! :)
[Galaxy S III Android Development] darkchazz:
What's the best profile for saving battery without lag in the UI ?
[Galaxy S III Android Development] Buckycasuals:
Looks great. What is your config for such a batt life?

---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------

Try Yank Batt or ZaneZam Batt plus with zen. No UV
[Galaxy S III Android Development] JustArchi:
zzmoove moderate.
[Galaxy S III Android Development] aliw32619:
I don't mind if my phone lags so which is the best battery life governor?
[Galaxy S III Android Development] cheese458:
Battery plus
[Galaxy S III Android Development] pdario:
Hello, I'm trying to set profile 5 with Android Tuner at boot, but it seems it can't... it just sets zzmoove governor without setting profile.

Could you please walk me through?
[Galaxy S III Android Development] Emre9110:
I wanna use profile 5. Is this ok?

Sent from my GT-I9100 using Xparent Skyblue Tapatalk 2
[Galaxy S III Android Development] DrEVILone81:
Your governor and the profiles with it makes a beast with our S3 out of it.....hope this explanation was not to german in the way of expression..:laugh:

"Mega geil der Zzmove" "Zzmove fegt alles weg" :good::laugh:

Hope this governor can be established in more kernel....please go on with your incredible development.....Android needs you
[Galaxy S III Android Development] maxfu:
Does this governor support big.LITTLE CPUs such as Samsung Exynos 5410?
[Galaxy S III Android Development] Yank555:
It would need to be ported... don't know if thise architectures use hotplugging governors (as zzmoove is) or rather like Qualcomms use a separated (in-kernel or not) hotplug driver and only scaling governors...

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v83 on Yank555.lu htle v1.0a (3.4.90) kernel.
[Galaxy S III Android Development] maxfu:
I got an big.little optimized ondemand governor, will this help?

https://github.com/maxfu/android_kernel_exynos5410/blob/master/drivers/cpufreq/cpufreq_ondemand.c

and more:

https://github.com/maxfu/android_kernel_exynos5410/blob/master/drivers/cpufreq/exynos-ikcs-cpufreq.c
[Galaxy S III Android Development] Yank555:
Quick look in the first link tells me, hotplugging looks to be added into the governor...

That would mean this logic would have to be 'implemented' in zzmoove, as from what I gather, though I stopped looking at Exynos after i9300 because of Samsung secrecy politics, you can't run both big and little at the same time, at least for the older generation of octa cores.

So that would have to be taken into consideration if you want to port zzmoove to your device.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v83 on Yank555.lu htle v1.0a (3.4.90) kernel.
[Galaxy S III Android Development] habylab:
Could I ask for the 0.9alpha 2 to be pushed to final? It works perfectly. I know the changelog is small, but sometimes that is a good thing. It is very tuned as it is! I am using your test boeffla and it is excellent with the moderate profile.
[Galaxy S III Android Development] ZaneZam:
hi habylab,,

sry for the late reply i saw your posts around but was too busy to answer immediately

eh 0.9 final would be a little bit too fast for me *g*, i didn't even nearly reach my scope for it and the changelist is still so small because i unfortunately had no time to further work on it yet. BUT i will bump the alpha 2 version to beta1 and throw it out soon because yes as u said its really working well so far and we do not want unnecessary long release delays again, don't we? :D

will keep u informed! :good:

cheers

ZZ
[Galaxy S III Android Development] habylab:
Excellent news, thank you! I wonder if [MENTION=4898097]arter97[/MENTION] would be interested in the beta...?
[Galaxy S III Android Development] Olioaglio:
Don't forget to count in [MENTION=4365701]psndna88[/MENTION] and [MENTION=4196889]DerTeufel1980[/MENTION] ;)

Olioaglio
[Galaxy S III Android Development] ZaneZam:
ZZMoove Version 0.9 beta1 released!

Hi Guys,

i promised that i don't let people wait so long for stable stuff so i've just released

a late (yeah not early, still some delay *gg*) beta1 of the coming "slimline" version of ZZMoove

nothing major (beside of some weight loss because of the poll result, thx for voting btw!) has been changed

and this is actually just the bumped alpha2 version (for details check second post)

It's not a final as it has not reached my aimed feature level for 0.9 yet but it's stable and was tested for

some weeks with absolutely no problems and (as usual *g*) the alpha versions already even found their

way into yanks kernel(s) sooo it's already "in the wild"! ;)

enjoy this "new" slimline beta!

cheers

ZZ
[Galaxy S III Android Development] habylab:
Thank you for all the hard work!

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] trein91:
Is it possible to somehow toggle between the different zzmooove profiles via a Tasker script or something? I'm on arter97 kernel. Thought I'd ask here since someone mentioned that.

My main use for it would be to switch between inzane, moderate, and battery + depending on the cpu temperature. Currently I use setcpu to underclock on high temperatures. But sometimes the setcpu bugs and locks on the high temperature profiles, even though the temperature has dropped again afterwards. (ie think it's still 45C or something, and underclocks, leading to more lag when in actual fact its only 30C)
[Galaxy S III Android Development] ZaneZam:
what u are trying here is a nice approach and even something I have on my feature list for 0.9 - a thermal interface directly from the thermal sensor to the governor, but with real cpu temperature! I assume your mentioned 45° are the as usual taken temperature from the battery sensor ;) well enough dreaming back to your question: I already answered in arter97 kernel thread. u can archive this by changing only one tuneable "profile_number". I was going to make same scripts to switch profiles so if you can wait a bit u can download them from here and use them for your propose. don't know if Tasker can directly write to sysfs, if it can just give that tuneable the wished profile number and the governor will switch to the profile instantly.
[Galaxy S III Android Development] MIKEMON:
My friend the good work as always
[Galaxy S III Android Development] trein91:
Thanks. I'm presuming there's a way to do that in tasker but since I've no clue with coding I'll ask on the tasker google groups section. Btw will any of this work?
[Galaxy S III Android Development] SaschaKH:
I haven't tried it on S3 but if it would work, couldn't it do what your looking for?

https://play.google.com/store/apps/details?id=org.jop.android.cpuprofiler

Gesendet von meinem TPC-9000 mit Tapatalk
[Galaxy S III Android Development] trein91:
Nope. Like setcpu, that only sets the kernel governor. Not the governor's internal preset profiles
[Galaxy S III Android Development] andip71:
As ZaneZam said, you need to set only one tunable in the sysfs to achieve what you want.

Or you use another kernel that has tasker integration capabilities built-in.

Andi
[Galaxy S III Android Development] ZaneZam:
yeah maybe with "run shell" and with a shell script or directly with a commant like this:

echo "5" > /sys/devices/system/cpu/cpufreq/zzmoove/profile_number for profile 5 (battery plus)
[Galaxy S III Android Development] trein91:
Awesome. It works. Via "run shell" and ticking the "use root" feature.

Changes doesn't show up in atweaks though but it's fine. (since I can see the difference via perfmon and solid Explorer)
[Galaxy S III Android Development] JustArchi:
Hey [MENTION=3279788]ZaneZam[/MENTION].

Could you tell me what's the most proper way for hardcoding default preset? Like number 7 instead of default 0 (with all values). I mean in your code of course :).

Thank you in advance.
[Galaxy S III Android Development] ZaneZam:
hey archi,

that would be with the provided macros in the source code but not all tuneables has default macros I would have to put in "some" more :) I anyway will make an improvement to the profile function as soon as I have time to, so i will have a look then for you. ;)
[Galaxy S III Android Development] JustArchi:
Everything I want is to set ZZmoove to use custom profile in the code itself, so it can load hardcoded preset "without" setting it via echoing value in sysfs. If you could add such option, like #define DEFAULT_PRESET 7 it would be great. This way I can tune zzmoove to my own preference using your awesome built-in presets while still giving users a freedom in terms of modifying it later. And mostly important - I don't need to do that in init.d :).
[Galaxy S III Android Development] fusionjack:
not sure if i correctly understand what you want...

there is macro DEF_PROFILE_NUMBER in cpufreq_zzmoove.c and i think if you set this macro to a specific profile number, it'll be used as standard. for a custom profile, adding a new profile in cpufreq_zzmoove_profiles.h should do the trick.

i didn't try it yet and i could be wrong...so ask the master [MENTION=3279788]ZaneZam[/MENTION] ;)
[Galaxy S III Android Development] JustArchi:
I found this macro but based on other variables and definitions I'm not sure if this will work. Changing this number probably won't apply values, for me it looks like just a default value for sysfs interface, zzmoove doesn't apply values based on that, it only sets this value in sysfs if you know what I mean. But yeah, ZZ is the master here, I'm waiting for his implementation :).
[Galaxy S III Android Development] ZaneZam:
yes exactly guys that's the point currently the Def profile macro is just a number for the tuneable to show in sysfs. the profile change is only triggered when the profile tuneable gets a new value. I would have to start the profile apply loop at governor start, will try that if it works without problems (start/stop is a sensitive thing that's what I learned very much from zzmoove *g*) then the default profile macro is the thing to set to hardcore a default profile. [emoji6]
[Galaxy S III Android Development] fusionjack:
[MENTION=3279788]ZaneZam[/MENTION]: as we on this topic, if the user change profile_number and sampling_rate, will the sampling_rate be replaced from the profile template? should the profile_number 0 be used, if the user want to set other gov settings like sampling_rate to his own desired value?
[Galaxy S III Android Development] ZaneZam:
that depends on what happens first. if the sampling rate is set after profile then it will be set to desired value and the profile will switch to 0 (custom mode) for information that a profile value has changed. if the sampling rate was set before setting a profile then it will be overwritten by it. but I will try to improve that functionality by locking unlocking the profile mode because the actual behaving could lead to problems when applying tuneables at boot for example with setCPU. it's not clear when and which values will applied first. it even could clash if setting a tuneable comes at the same time the profile tuneable is set. ;)
[Galaxy S III Android Development] fusionjack:
thanks for clarifying...i think i have done the right thing last night by persisting only the profile_number through the built-in app and only applying profile_number during booting. :p

another question, assume the profile number 2 has been used before and then the user has set only one of the gov setting 'samping_rate' manually without changing other settings. does it mean that the other gov settings will remain from the profile number 2 although the profile number is changed to 0?
[Galaxy S III Android Development] JustArchi:
Waiting for your implementation then :). Should be fairly easy I think.
[Galaxy S III Android Development] ZaneZam:
that's the easiest way and actually like lord boeffla does it with his app ;) and Yes values are staying the profile number change to 0 is just informational ;)

yeah IF my plan works as expected, we will see :)
[Galaxy S III Android Development] MIKEMON:
yep, thanks friend
[Galaxy S III Android Development] ZaneZam:
ZZMoove Version 0.9 beta2 released!

Hi Guys,

I've just updated the second post with information about a new beta for v0.9 of ZZMoove.

This time it's mainly a "requested features" release ;) so u can thank [MENTION=5161352]JustArchi[/MENTION] and [MENTION=1228651]fusionjack[/MENTION]

in addition for following ideas:

- support for setting a default settings profile at governor start without the need of using the tuneable 'profile_number' (JustArchi's request)

- added 'blocking' of sysfs in all tuneables during apply of a settings profile to avoid a possible and unwanted overwriting/double setting of

tuneables (try to react fusionjack's problems when setting tuneables with apps like setcpu, even though i still can't get it setting of tuneables at boot BUT also not with other governors (!!) so i highly suspect setcpu itself - but let's see how it goes for fusion)

- added tuneable 'profile_list' for printing out a list of all profiles which are available in the profile header file (fusionjack's request)

- fixed non setting of 'scaling_block_force_down' tuneable when applying profiles (ha! ok one by me as i found that during making the above ones *gg*)

special thx to JustArchi for testing a pre-version :good:

enjoy and cheers!

ZZ
[Galaxy S III Android Development] habylab:
Excellent! Is there a test version?
[Galaxy S III Android Development] ZaneZam:
not yet but I guess soon there will be one [emoji6]
[Galaxy S III Android Development] andip71:
Yes, very soon... ?

Sent from mobile
[Galaxy S III Android Development] ImShadix:
Where's the downlod link omg ?
[Galaxy S III Android Development] MIKEMON:
great to hear this

I expected
[Galaxy S III Android Development] SaschaKH:
Links to github are in second post: http://xdaforums.com/showthread.php?p=42637763 or maybe wait for a kernel with the governor.
[Galaxy S III Android Development] andip71:
Maybe tomorrow I find some time. Need a last beta before a stable :)

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] shabtab:
Still no Boeffla Update :(
[Galaxy S III Android Development] ZaneZam:
still no world peace? patience please! :) lord boeffla is facing very busy times these days so we have to be sympathetic about that. and btw latest update is nothing u literally will miss if u don't use it ;)
[Galaxy S III Android Development] andip71:
But 2 hours ago there was one ?

Sent from mobile
[Galaxy S III Android Development] MIKEMON:
But also, great team work together

Andi § ZaneZam

thanks to you
[Galaxy S III Android Development] StuttgartKiwi:
Table of profiles

Hi [MENTION=3279788]ZaneZam[/MENTION]

I found the following helpful table of the zzmoove profiles in your Github, in the "cpufreq_zzmoove_profiles.h" file. I had been searching everywhere for a good, clear explanation of each profile, and finally I found it.

Would you consider adding this table to your original post, so that all users can easily find it there? I think that would be very helpful!
[Galaxy S III Android Development] ZaneZam:
sure, will merge it with the info in the third post ;)
[Galaxy S III Android Development] trein91:
Is there a similar governor to this for the s4 i9505?

Sent from my Galaxy S3
[Galaxy S III Android Development] andip71:
Most simple is: You ask the developer of your current custom kernel to just include zzmoove into his kernel.

The governor is not device-specific as such, it can work fine on a S4 as well.

Andi
[Galaxy S III Android Development] ZaneZam:
that's right but i have to add IF the kernel source is 3.4+ then it would not be possible at the moment!

afaik recent S4 kernel sources are based on 3.4 ;)

the 0.9 version isn't called 'stable' yet because it's missing at least one point on my feature list and that is the preparation for

3.4+ source compatibility. but after that change there is still a lot of work to do to make it really run on 3.4+

sources. But at the end to let zzmoove 'survive' i will have to find a way sooner or later :o

btw. currently i'm preparing version v0.9 beta3 for the release, so stay tuned! ;)
[Galaxy S III Android Development] andip71:
So the dev would need to adjust it to the 3.4 kernel sources on top. Well, still doable :)
[Galaxy S III Android Development] razen_kain:
Would zzmoove have problems if I'm using a kernel that skips frequencies? For instance; my kernel only uses 2;5;8;10;12 ghz it will skip over 3;4;6;7;9;11.

with JB this was not the case. All frequencies were available and zzmoove was amazing but since flashing kk been getting random sods/freezes.
[Galaxy S III Android Development] ZaneZam:
yeah andi doable and even partially done for 3.7 sources (about a year ago) and recently for 3.4 sources also but nothing stable/100% functional so far. after Yank and i had some fun with the sources some while ago for his Note project it has revealed that it's unfortunately not that easy, otherwise JP would have done it already, as u know andi he can be a "speedy guy" if it's running well :D

i would say it should not have problems with that. But then i would suggest to disable fast scaling as this function skips steps in addition in the governor. how to u skip the freq? you made a own system freq table for that purpose?
[Galaxy S III Android Development] ZaneZam:
ZZMoove Version 0.9 beta3 released!

Hi Guys,

Added Information about the just released 0.9 beta3 version to the second post!

Special thx to [MENTION=349360]ffolkes[/MENTION]! it's been a while since i said that i will check out your sources and almost one child production time later i finally did! really proud of my brain that i didn't forget that even without a note! Yeah! :D well with such a little note it maybe would have happen earlier! :) not all of your improvements found their way into the latest version but at least the ones i was considering as useful. let's see how they work, at least for me they do very well a couple of days now.

[MENTION=535343]all[/MENTION]

btw. all new features are disabled by default, i need some more time for playing around with the new wheels so maybe next version will have some of them enabled by default. if anyone is willing to test and can provide some good values feel free to post them here.

enjoy!

ZZ
[Galaxy S III Android Development] habylab:
So if all new features are disabled by default, are there any differences between the two aside from that?

Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
[Galaxy S III Android Development] ZaneZam:
Yes some bug fixes (e.g hotplug sleep was not set with profiles) and sampling rate sleep is higher now on all profiles, means hopefully a bit more bat saving at suspend. Yeah [MENTION=5161352]JustArchi[/MENTION] that's a result of our little discussion recently ;)
[Galaxy S III Android Development] razen_kain:
I have no idea. I'm using the gs2 (i777) and since i first flash kitkat last December. The frequency ranges changed. It's the same on every kk ROM/kernel. On JB ROM and kernel all freq steps are available.
[Galaxy S III Android Development] xKarlo:
Which one is the Best for the Battery Life?

ZZ-yank Batt, Zz- yank batt extreme or Zz- batt plus? [MENTION=3279788]ZaneZam[/MENTION]

Thanks!

Karlo.