yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Yank555:
You need to have usb debugging enabled in dev options, connect S3 to your PC via USB. On the PC you need Drivers and adb executable (it's part of Android SDK).

You run "adb shell" from PC and have a shell allowing to use dmesg, logcat etc...

That way you can monitor the device from PC while you're using it...

JP.

Sent from my SlimBean 7 / Yank555.lu CM10.1 kernel v1.6e-beta1 (Linux 3.0.86) powered Galaxy S3 i9300
[Galaxy S III Android Development] kofe:
i will try that also when i will have more time to play with my phone :)

Noticed the edit for the post above?

Now even reflashing temasek;s rom and kernel doesn;t help. Still bootloops...

Good thing i have a nandroid :)
[Galaxy S III Android Development] Yank555:
Very strange !? Booting (well trying) a CM ROM with a Sammy kernel should not corrupt any filesystem... not that I tested that, though ;)

Good you had a nandroid ;)

One should

always

have a backup.

And if one hasn't, and would have needed one, that'd be bad, but a good lesson learned for life and it sure won't happen again :D

JP.

Sent from my SlimBean 7 / Yank555.lu CM10.1 kernel v1.6e-beta1 (Linux 3.0.86) powered Galaxy S3 i9300
[Galaxy S III Android Development] alberber:
Hey mates, I'm playing around with the lcdfreq settings. My aim is the screen to use the 40 Hz freq while not touched or very light use and these are my settings:

- kick in down delay: 5

- kick in up delay: 10

- kick in freq: 500000

- kick in cores: 1

I also set the touch boost frequency to 600MHz so when I touch the screen it should (theorycally) mainly use the 60 Hz freq.

What do you think? Any help is much appreciated :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] oae08:
Do you notice any significant battery gain when using these settings?
[Galaxy S III Android Development] alberber:
I'm still testing mate! I'll report back as soon as I can.
[Galaxy S III Android Development] oae08:
Great. Would like to know if you felt noticeable battery gain :)
[Galaxy S III Android Development] alberber:
Some statistics... From 98 to 83%, 1 hour and 20 minutes with screen on, high brightness (around 50-70%), using 3G.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] oae08:
Good results. But how much were you achieving without lcdfreq and the same useage? Test so we can compare :p

Btw what rom are you using?
[Galaxy S III Android Development] alberber:
With a 15% of battery life... I used to achieve around 1 hour of screen with low brightness (0-30%). So I've gotten such great results, but I think that must be a lucky strike (currently I'm not achieving the same :cry: ).

Anyway, I guess my battery is kinda broken, I should buy a new one.

I'm using Omega rom :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] Yank555:
In case anyone is interested, these are my "new" battery settings, scales a little easier, hotplugs a little less (reworked screen off settings as well), aim is to keep it snappy, and potentially reduce battery usage a little both on screen on and off :

CPU governor set to zzmoove.

Touchboost enabled at 500MHz.

CPU max. frequency set to 1.6GHz.

zzmoove - yank-battery profile :

zzmoove - sampling rate set to 180000.

zzmoove - sampling down factor set to 1.

zzmoove - up threshold set to 80.

zzmoove - down threshold set to 40.

zzmoove - ignore nice load set to 0.

zzmoove - frequency step set to 10.

zzmoove - smooth up set to 65.

zzmoove - up threshold hotplug1 set to 85.

zzmoove - up threshold hotplug2 set to 90.

zzmoove - up threshold hotplug3 set to 98.

zzmoove - down threshold hotplug1 set to 65.

zzmoove - down threshold hotplug2 set to 75.

zzmoove - down threshold hotplug3 set to 85.

zzmoove - sampling rate sleep multiplier set to 4.

zzmoove - up threshold sleep set to 85.

zzmoove - down threshold sleep set to 75.

zzmoove - CPU step for standby set to 1.

zzmoove - smooth up sleep set to 90.

zzmoove - hotplug sleep set to 1.

zzmoove - yank-battery profile applied.

zzmoove - CPU freq. max for standby set to 600MHz.

zzmoove - 1 step up/down fast scaling enabled.

zzmoove - fast scaling for standby disabled.

zzmoove - early demand enabled.

zzmoove - early demand threshold set to 50.

JP.
[Galaxy S III Android Development] gsw5700:
Many Thanks, are you using an init.d script? If so, would you mind sharing it.

Sent via TCP/IP
[Galaxy S III Android Development] ZaneZam:
Thx JP! :)

I will provide the init script beside of all others when I have a minute or two but still very busy times here :(
[Galaxy S III Android Development] Yank555:
No unfortunately not at hand, I have this generated when installing my kernel...

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta3 (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Android Development] alberber:
Yank, what do you think about reducing sampling rate to 100000? Maybe it helps the CPU scale faster so it doesn't stay much time on high frequencies? Or am I wrong?

Thanks for sharing your settings with us!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] ZaneZam:
might be that the scaling will be a little bit faster but 100000 produces also more overhead by the governor itself.

i think most relevant settings for a faster scaling are still the theshold values.
[Galaxy S III Android Development] Yank555:
Totally agree with Zane ;)

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta3 (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Android Development] mattiadj:
I'm using yank kernel (latest) with zzmove with optimized profile but.... Only core 0 is always used at 100%! Others are offline I can say... Always! It's normal??

From universe with my gs3
[Galaxy S III Android Development] davtse:
I'm using a more extreme version of your battery profile(CPU thresholds 90,97,99) and it's smooth and lag free for most of my usage. Heck, I'm on 2+ days and almost 3 hours of screen on and I'm still at 60% with my extended battery. With a good signal I have no doubt I'd hit 10 hours screen on and maybe 4-5 days standby.

Have I mentioned how awesome zzmoove is?:D

P.s I'd ask it to marry me and have my babies but its probably too fast for me :p
[Galaxy S III Android Development] Yank555:
If it's not lagging why have cores online, they would just waste battery...

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta3 (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Android Development] ZaneZam:
[MENTION=1412615]100%[/MENTION] it's normal if u set core limit to 1 core and that would mean u have the hotplug threshold tuneables 1-3 all set to 0 can you check this with the usual suspects aka setCPU or android tuner?
[Galaxy S III Android Development] Pantherx12:
I've been thinking recently that a single core juggling tasks can take longer so whilst its energy output over x time is less it may take more time to complete the tasks assigned so total energy expenditure will be the same.

It is something I'll have to so some testing on this device but on my Novo spark having the CPU1 hot plug threshold set fairly low ( meaning it comes on fairly often,not sure if im using right terminology) was actually more efficient!

I know you guys have done lots of testing but have you tested the effects of such a set up yet? ( CPU 2 and 3 don't matter so much)

I'm going to be testing over the weekend at any rate.

At the moment I've forced all 4 cores online* and all four cores do get used ( much lower utilisation on each core) and so the frequency remains a lower more consistently so voltage through the individual cores is lower so could be some savings to be had allowing the cores to come online easier.

* just for testing purposes.

Anyone care to join me in my testing?
[Galaxy S III Android Development] oae08:
Its interesting but i think someone before tested and said cpu2 and 3 will consume more energy. Maybe in some cases though cpu1 will be better.
[Galaxy S III Android Development] Pantherx12:
Yeah I only forced 2 and 3 on just to see if they did all get used when I'm not really doing much. Android seems a lot happier to use all resources it has access to than windows for example :)

Definitely going to play with cpu1 settings though more thoroughly though.

Also has to be said with all 4 cores forced online this phone is smooooth.
[Galaxy S III Android Development] Yank555:
Well you have to look at it like this :

A core will use juice just for being online, then will use more as freq. increases.

1 core at 400MHz will use less than 2 cores at 200MHz. Thus it's best to have as little cores online as possible.

CPU load is an absolute value at one given moment considering only the cores that are online at that moment, so the exact same 'reallife' load would for example be 50% in single core and 12.5% on 4 cores, but 12.5% on 4 cores will most likely use quite more juice.

Also, time in state is measured globally as well, so if for example you have cores 2,3 almost always off, there is no way to know it using time in state as it's global not per core (as it is on Qualcom devices, some at least).

JP.

Sent from my SlimBean 7.5 / Yank555.lu CM10.1 kernel v1.6e-beta3 (Linux 3.0.87) powered Galaxy S3 i9300
[Galaxy S III Android Development] davtse:
And this is why you're a dev and i'm an end user. Didnt know this. Always good to learn something new :good: I've run out of thanks for the day so I'll thank you manually here!:good:
[Galaxy S III Android Development] gsw5700:
Attached an interesting paper on the use of DVFS and hotplugging. basically, it is really too complex for me but not for you guys! Its a 2 core phone 1Ghz 1GB phone but should still be relevent. The guy is saying normally, performance is measured as throughput and not responsiveness. Hotplugging a core can take up to 100ms (1/10th second) reducing responsiveness. Response times for hot-plug was close to that of a single core!

Would love to hear your interpretation on the contents of this (or other papers).

Other questions

Does this mean its better to idle on 1 core and always keep, say 2 cores on when active?

Does 2 cores running at 700Mhz consume less power than 1 core running flat out at 1.4Ghz?
[Galaxy S III Android Development] STAticKY:
Your last question was answered by yank a few posts up...

TP.
[Galaxy S III Android Development] gsw5700:
But at what point does it make sense to use another core as the power curve isn't linear? How does response time get affected by hot plugging another core and how does this affect power consumption? Probably getting too deep lol

Sent via TCP/IP
[Galaxy S III Android Development] STAticKY:
I think this is the point of zzmoove. It has extremely aggressive hot plugging to achieve its smoothness. But at the same time being able to save battery by race to idle and aggressive down too..

TP.
[Galaxy S III Android Development] davtse:
I agree. I think that's the beauty of zzmoove. Under sudden and extreme load it hot plugs up to cope with demand and then aggressively hot plugs out to save battery.

Pegasusq does it differently by increasing thresholds to hot plug up the other CPUs. More battery savings but not as smooth as zzmoove 0.6.
[Galaxy S III Android Development] mattiadj:
No mate i don't use any type of app to limit cores usage. I have only used optimized profile in yank kernel. But with perfmon I have noticed that also during games my phone uses only one core!

My phone became a lot hot and games are laggy. I think that the reason of this behavior is due to the use of only one core that is not enough.

What can I do?

From universe with my gs3
[Galaxy S III Android Development] Yank555:
Well the heat, if on one core, can only come from the GPU. Also know that many "heavy" games are way heavier on GPU than CPU, thus if the load is low, the CPU will throttle down.

Plus ... if the phone heats up too much, you'll hit thermal throttling, for safety reasons, and that will most definately give you lag as everything is turned down to let the device cool off.

Use the tunables to set zzmoove up as you want it to be, or if you have better results on a different governor, they are there to be used as well :D

JP.
[Galaxy S III Android Development] ZaneZam:
yes exactly that was the aim! power on demand and as low as possible on idle times ;)

but it seems versions >0.4 are a bit too aggressive, so we have to throttle the beast again.

let's see if we can accomplish this.
[Galaxy S III Android Development] mattiadj:
No mate now (in the days) I'm not playing nothing since I can reach 55 c easily doing nothing! I'm under 3g connection (is good and stable connection...) and under wifi the thermal situation is small better. Only small... If you want check my threads in q&a and help me to discover the culprit of my heating problem!

About zzmove I'm not an expert and I don't know how can I play with settings... In your kernel I have only changed in aroma your last settings from 50% to 35% and setted max CPU screen off freq to 400

From universe with my gs3
[Galaxy S III Android Development] davtse:
Throttle meaning increase the up thresholds of the various CPUs? Sounds good to me :D
[Galaxy S III Android Development] ZaneZam:
again just to be sure that we talking about the same thing your cores 1-3 coming up never?

what happens if u use stability test are the cores coming up if u do a "classic" or "Raw Mflops" test? if they stay offline when you use the stability test then either my first reply to you applies (somehow accidentally hotplug thresholds set to 0) or something other wired happens. normally they should come up at given hotplug thresholds nearly in a row!
[Galaxy S III Android Development] ZaneZam:
yes and in addition a little "idea" (or better said a recollection of something *g*) i had yesterday in sourcecode of zzmoove.

curious if that brings us back to more bat saving. still all in "theory mode", had no time to implement/test yet, unfortunately.
[Galaxy S III Android Development] davtse:
take your time man, we leave it in yours and [MENTION=2033478]Yank555[/MENTION] 's capable hands. :good:
[Galaxy S III Android Development] mattiadj:
Not problem with stability test. All 4 cores up at max speed or at 800 mhz.

But during games like real boxing why only one core is used?

From universe with my gs3
[Galaxy S III Android Development] gsw5700:
Using zzopt, all 4 cores run evenly at the approx same frequency whilst running intensive tasks, looks good

Sent via TCP/IP
[Galaxy S III Android Development] ZaneZam:
Ok i see then it's like [MENTION=2033478]Yank555[/MENTION] said it's not a MUST that all or more cores than one comes up during gaming. i mean it depends on the game

u play for example if u play any chess game there will be more load on CPU than on GPU due to it's internal combination calculations

but on most grafical oriented games the main load lies on GPU and lesser on CPU. I do not much gaming any more since i have my S3 (stange actually, on S1 i played a lot *g*) but i can share my observations with some benchmark apps like antutu or "quarkdrand" *g*. if u look at the cores during a benchmark u see that on grafical calculations the amount of cores stays under 4 or even under 3 most of the time. of course that depends a little bit on the actual setting but if there is low CPU load the cores will not switch! ;)

anyways maybe u can try the performance or optimized setting for gaming there are all (respectively some in case of optimized) performance otions active and that should bring u some boost. but do not expect that there will be more cores online then, it really depends on actual CPU load. well and regarding the heating problem can you try to set the tuneable disable_hotplugging to 1, plz? i'm just curious if that changes anything, thx!
[Galaxy S III Android Development] mattiadj:
Okok it's clear now. But perfmon doesn't allow me to monitor gpu....

Well I have made this change in rom toolbox pro but I need to reboot to apply?

From universe with my gs3
[Galaxy S III Android Development] Yank555:
Well all cores will run at the exact same freq. all the time, Exynos has no ability to work otherwise.

In Qualcom CPUs eacht core can have its own freq, but not on Exynos.

When you see different freq. for each core, that is just a glitch in the app, where between reading the 1st core and last core freq. has been changed.

Those tools cannot display freq. in realtime, freq. just moves to quickly, they just grab a snapshot once every second or so. Doing more would require so much CPU power that the display would be biased by the aggressive readings of the app since that would put too much load on the CPUs and make them throttle up.

JP.
[Galaxy S III Android Development] maazy:
Hi, ZaneZem. I used to be an Lulzactiveq fan, but since I tried the last version of ZZMoove, I can't live without it! Thank you for providing us this wonderful gov.

I'm using the last Boeffla. There, we have ZZMoove Battery and ZZMoove Performance. Is ZZMoove Battery much more battery friendly? Because I feel almost no difference in performance when I switch between them.

Thank you in advance!
[Galaxy S III Android Development] ZaneZam:
hi maazy,

thx, yeah it should be more battery friendly all performance settings are off, thresholds and sampling rate are also set accordingly on that setting but regarding performance it seems that doesn't really bother the new "beast" versions *g*! but the characteristic behaving of zzmoove

is still the same on all settings - full power on demand and quied as soon as the power isn't needed anymore.

i'm currently working on a new version to be able slow down that behaving (for now the hotplugging) because it produces a bit overhead by the governor itself and therefore it consumes a little bit more power by just being active. will see if i can calm down the beast ;)

so in short u can use battery setting with almost no performance lost ;)

but u can also try to use some sharper values by using yanks battery setting, he did some optimizations in battery direction, look at

this post: http://xdaforums.com/showpost.php?p=43941119&postcount=119

maybe u can try this setting in addition by using apps to change the values (unfortunately no init script available yet, but it will come!)

and report back how it works for u?

regards

ZZ
[Galaxy S III Android Development] maazy:
Sure :) I'll try Yank settings as soon as I can and report back. Thank you again!
[Galaxy S III Android Development] psndna88:
successful implementation of 0.6a for my p3100 kernel omap4430 !

silly inverted freq table !

sent from I9300 CM 10.1 4.2.2 official + AGNi pureCM v2.3.2
[Galaxy S III Android Development] ZaneZam:
kewl! nice to hear that! :) yeah that freq tables gave me also some headaches during development

of the scaling optimizations, but the other way around in the table hehe... yank did again a very good jop with

making this compatible to omap! :good:
[Galaxy S III Android Development] Pantherx12:
So like I said I would tested out battery life with hot plugging disabled managed to pull this today.

Which is actually the best screen on time I've ever had.

Aside from going quad core I disabled touch boost ( since no need for it when all 4 cores are active)

Going to play more,I was deliberately keeping my screen on today ,tomorrow I'll see how the phone lasts in my pocket most of the time :).
[Galaxy S III Android Development] STAticKY:
[MENTION=3279788]ZaneZam[/MENTION] is it possible to have hotplugging enabled on screen off and disabled on screen on?

TP.
[Galaxy S III Android Development] habylab:
I assume so if you set the hotplug screen off variable on and the other off?
[Galaxy S III Android Development] STAticKY:
And how do I set that. I can't find the tunables for it

TP.
[Galaxy S III Android Development] ZaneZam:
Hehe had to read twice. "on screen off on screen on" wtf?. Ehm not yet but good idea! Will include this in upcoming version!
[Galaxy S III Android Development] STAticKY:
Awesome. Iv edited my post to make it more understandable.

TP.
[Galaxy S III Android Development] Pantherx12:
Hey guys my normal use testing results were massively skewed to to huge google services wake locks *( taking about 44% of my battery after 12 hours of usage) and I've gone back to a Sammy based rom so I'll have to do all my testing again heh. ( I missed MHL)

I'll report back as soon as I can.

* if anyone else is experiencing this updating the playstore manually seems to do the job.
[Galaxy S III Android Development] ZaneZam:
hotplug_switch only for suspend done! now testing :good:;)
[Galaxy S III Android Development] tincmulc:
Because I'm still a little confused about the on screen off disable thing, I would like to confirm it.

Screen on: all cores forced online

Screen off: 1 core online, the rest hotplugged out.

Correct?
[Galaxy S III Android Development] ZaneZam:
hehe u are not the only one who was confused :)

it's just the "disable_hotplug" switch only for sleep. so if u enable (=hotplugging off) this switch hotplugging will be completely disabled only at screen off when screen is on again hotplugging will also be reactivated. ;)
[Galaxy S III Android Development] tincmulc:
When hotplugging is disabled, how many cores are online? All? One?
[Galaxy S III Android Development] ZaneZam:
Yes all :)
[Galaxy S III Android Development] tommi.a:
ZZMoove Battery - Stick to 1 core and Sleep Mode

Hi there,

new here on xda as a member but reading both boeffla kernel and zzmoove thread for some weeks already.

I really like boeffla kernel with zzmoove battery and zram as they give me a long enduring battery and the phone is still very smooth.

To achieve even better battery I reduced cpu max clock to 800Mhz while using zzmoove battery with default settings as this setting is still sufficient for my daily needs (reading emails, surfing some web sites, calendar, listen music, etc.)

I made two observations:

1) From time to time and under unclear conditions the CPU sticks on only one core. No matter what I do, it sticks only on core 0 and does not utilize other cores anymore. To get rid of this I temporarily switch the governor to lulzactive and back to zzmoove battery after few seconds. Now again up to 4 cores get used. Observed this ca. 10 times in the last three weeks on I9300XXEMC2, on yesterday's upgrade to recently released I9300XXEMG4 I did not yet see it.

2) Every time the phone goes to sleep mode (or wakes up from sleep mode?) it uses for a short time more than the configured 800MHz, i.e. 1000MHz. This is only about 10 seconds per hour but nevertheless I don't understand why this happens.

Found this out by using CPU Spy:

- CPU Spy Reset timers

- Switch off screen

- Use the power button to switch on screen again

- CPU Spy Refresh timers

Accessing the 1GHz only happens in conjunction with transitions to/from deep sleep. If e.g. the MP3 player runs while screen off, the 1000MHz don't get touched at all (CPU Spy: Unused CPU states: (all > 800MHz))

Is anybody else able to reproduce such behaviour?

Thanks
[Galaxy S III Android Development] ZaneZam:
1.) might be a bug that comes up from time to time. Had that too long time ago but it never came back on my device. I know some people still have it but dunno what's the cause yet. Little bit difficult to fix as it comes up completely coincidentally so I can't give any advice atm sorry. :(

2.)

Yes that are hardware wakeup frequencies. when u use the implemented soft limit of zzmoove governor (and as it also is active in all zzmoove settings at screen off in boeffla kernel) it is normal that these peaks exists as that soft limit unfortunately can't avoid these freq jumps. This applies also to touchwake frequencies jumps if u have set the soft limit under touch boost frequency. That is usually 800mhz in stock setting. So when u set for example soft limit to 500mhz u will still see jumps to 800hz when u touch the screen ;)
[Galaxy S III Android Development] ZaneZam:
ZZMoove Governor v0.7 released!

Yo Guys,

check out the first post and enjoy !! :)

ZZ
[Galaxy S III Android Development] oae08:
Thats awesome. Cant wait to be implemented in temaseks kernel.