yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Every governor keeps cpu on maximum when playing games. Normal...

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] brujo55:
my mistake jajala,

but pegasus governor is more friendly,never stuck at max freq all time.
[Galaxy S III Android Development] ZaneZam:
well that depends really on the game and the load it produces. zzmoove is known for its fast scaling but this can be adjusted! ;) (especially in upcoming 0.8 version! )

attached pic shows online cores and load during playing a not so hardware intensive game - the freq is up to 1100mhz because of the Screenshot I made, 2 seconds before it was running on 500mhz and one core ;)

just an example that it doesn't always "stick" (why always that term?) and not on every game. actually it never "sticks" it's just that simple: thresholds are reached scaling/hotplugging triggers. this is a normal behaving. had plenty of discussion with people which did a wrong interpretation of what they saw in monitoring Tools. just want to underline what lord boeffla said that this is normal and can also be tuned if wished but of course at the cost of performance then ;)
[Galaxy S III Android Development] zeli9:
What is that floating CPU monitoring app?
[Galaxy S III Android Development] ZaneZam:
perfmon from chainfire very nice tool from one of the best :good:;)
[Galaxy S III Android Development] zeli9:
Great! Getting it right away! :)
[Galaxy S III Android Development] brujo55:
sound great,cant wait.
[Galaxy S III Android Development] nicesoni_ash:
Bumping my post after more than 24 hours. Can someone reply about this please? Thanks.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Just to let you know, it is not ignorance by me. Just I never used wifi direct at all, so I cannot comment. Still hope someone else can give opinion here.

Andi
[Galaxy S III Android Development] nicesoni_ash:
I understood that already when you replied half my post, that's why I am hoping someone else will reply about this.

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] enigma1981:
Sorry for OT but what battery life do you get with that zerolemon monster?

Swyped from my Galaxy SIII using XDA Premium 4
[Galaxy S III Android Development] mad_ady:
Is it a feature or a bug? I was using my phone while charged, but still plugged in (@1225mA), doing some tapatalk reading and after about 5 minutes I felt it got hot. I checked the temperature and frequency and the cpu was doing 74 degrees at 1400MHz. After I disconnected power it began to cool. I'm using pegasusq with battery saving.

So, is it normal to get full cpu while charging?
[Galaxy S III Android Development] andip71:
At least on kernel side there is no function to completely disable touch light. This is a rom function, I think almost all roms allow you to switch that off completely.

Never had that.

And hotspot only works with mobile connections, i.e. when you enable the hotspot it relies on your mobile network for the internet connection and WIFI is used to provide the hot spot. So this is normal.

After switching off the hotspot it should connect to your WIFI network again however.

Was just about to write that:

CM and Omnirom have their own setting which can reset the governor. And as the rom loads after the kernel, it overwrites it in the end.

But, as you found already, this can be switched off.

Now should work fine for you.

It is neither a feature nor a bug.

Would have been very interesting to see which process was taking all the CPU at that time. Maybe, if you ever have this again, you can check processes in tools like "OS monitor" and see which one is putting your CPU up.

Andi
[Galaxy S III Android Development] querotequila:
Thank you for your reply. But the odd thing is that with googy and same ROM configuration the lights don't turn on.

Enviado de meu GT-I9300 usando Tapatalk
[Galaxy S III Android Development] Nic2215:
Did u set back light to off in kernel under lcd display, for me using temasek, after I off it in kernel setting, when I touch the menu and back key only it lights up to completely off it I need to go to the ROM setting , what rom are u using?
[Galaxy S III Android Development] querotequila:
AOSB 1.3.2, and I do exactly these steps, but the lights does not turn completely off. They have an odd behavior, they still on and with 5 secs timeout, and only if you touch the keys, not the screen.

Enviado de meu GT-I9300 usando Tapatalk
[Galaxy S III Android Development] andip71:
Again: Touch key led in CM world unfortunately changed to become difficult during CM10.2.

Some roms have the controls in the rom itself, some delegate it to the kernel.

The option to switch them completely off is not integrated in the kernel, this is a rom function.

So search for this in your rom first, disable the stuff there.

Then lock your screen (the settings only get properly applied after locking the screen with power key once, sometimes even a reboot is required), unlock again and try.

If it is still not off, go into boeffla config and change the control from kernel to rom or from rom to kernel, just toggle the control switch.

Lock the screen again with power key, unlock, try.

If all combinations do not help, let me know exact kernel version, rom version etc.

I do not try all roms, this is impossible. And maybe there are roms where this is really not possible. Who knows.

Andi
[Galaxy S III Android Development] ascariz:
suggestion

please add widget to change profile with 1 click on homescreen. tq

(FYI i bought your app to support your kernel).
[Galaxy S III Android Development] andip71:
Read app help please, this is already in since the very first version.

Just not a widget but homescreeb shortcuts.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] akz1x1:
Can you please add touch led duration settings for cm Boeffla config app...

Because I'm not able to set touch led duration value less than 1 sec using cm settings...

.6 sec was possible with stock
[Galaxy S III Android Development] querotequila:
Thank you for your patience, explanation and your amazing work. I'm sorry if I bothered you because I was not capable to found the solution by myself. I miss the point that I must lock and unlock to led turn off, and change the control to ROM.

Now everything works fine.

Thank you again and sorry about my bad english.

Enviado de meu GT-I9300 usando Tapatalk
[Galaxy S III Android Development] RuralGalaxy:
I have problems to activate boeffla sound with Omni rom? Anybody know how? I active, but when close the app and reboot the toggle turns off...:(

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] kouros17:
Install the Boeffla-Config V2 and set the volume firstly from there. ;)
[Galaxy S III Android Development] RuralGalaxy:
I tried too.. I activate inside config v2 and boeffla sound app from store...

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] Nic2215:
You should not be using two, chose either one, in this case go with v2,unless you are not tweaking your cpu, governor and etc.
[Galaxy S III Android Development] RuralGalaxy:
Yes, I tweaked, and using uV, for that reason.... But now I will try using only one, I hope will works jeje Thanks ;)

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] andip71:
No no, I was not bothered. I just needed to make the point clear it is not a kernel function.

And of course guide you to the solution.

Glad it works now, enjoy :)

Known issue meanwhile with Omnirom. They included Boeffla-Sound control in the DSP Manager app as well.

So Boeffla-Config and this app are conflicting.

Two things you can do:

- Freeze or remove DSP Manager, then you have full control back in Boeffla-Sound (recommended way)

- Set same settings in both Boeffla-Config and DSP manager all the time (cumbersome, but also an option)

Andi
[Galaxy S III Android Development] _Negan_:
Lord sorry for the noob question but is much time that I would like to ask this to a competent person and I think you re the right one...what makes so different the speaker sound of custom ROMs (worst) and Samsung ROMs(Better)? Depends of Samsung ROMs has proprietary drivers like for camera? Thanks for the answer
[Galaxy S III Android Development] Scarface1991:
[MENTION=947981]Lord Boeffla[/MENTION]

What do you think about the upcoming Oppo Find 7? It sounds like a extremely interesting device. It even has a removable battery and a micro sd slot, which is always a deal-breaker to me. Specs are also top of the line. I think this will be my next Smartphone and I wonder if you consider getting it too, so your fantastic Kernel makes it on the device.

These are all confirmed "leaks" that sound very interesting to say the least:

http://www.oppoforums.com/threads/find-7-confirmed-features.9719/

And also Oppo has a great relationship with developers unlike Samsung

Sorry for offtopic.
[Galaxy S III Android Development] andip71:
Hm, this is a good question. From kernel side, the sound drivers are the same between Samsung and CM/Omni. So the reason must be on the rom side.

But I am no rom developer, so I cannot say too much about it.

Only thing is... CM/Omnirom have the DSP manager included, maybe this is making sound worse for some instead of better? Just a wild guess however.

I am always interested in looking into new devices with good specs and hopefully decent pricing. Too early to say anything now, but when it is time to consider a new phone, also the Oppo would be on the investigation list.

For me the important points are:

- sd card slot

- replacable battery

- wolfson micro audio hub (not sure on that device?)

- realistic price

- no lock downs that prevent development

So maybe the Oppo could be a good match, yes.

Andi
[Galaxy S III Android Development] _Negan_:
Thanks for the answer Andy.

I use ATM fusion ROM with your kernel but I've tried also slim and cm but the sound is the same. With boeffla sound active for example I can't put speaker to values > 59 to avoid scratch sound...with boeffla sound disabled sound volume is much lower than Samsung stock ROMs. I keep DSP disabled. If you told me that the drivers are the same I really can't understand why so much difference. And I m not the only one that has noticed that. Thanks again m8
[Galaxy S III Android Development] dan55:
yes is a pain with the poor non sammy sound - ive been using Neat just recently and sound on v2.8 was horrid! ..... But, Boeffla made it MUCH better for in call sound - the best ive had i think :)

cheers

dan
[Galaxy S III Android Development] _Negan_:
Yes anyway I was talking mostly about speaker sound for example to watch a vevo video on YouTube etc...sound on stock is more sharp and loud...as I told with custom I reach the better compromise of loudness and sharpness with boff sound enabled at value 59 max. Anyway is still a step or two below stock Sammy ROMs.
[Galaxy S III Android Development] Buckycasuals:
Which scheduler works best with zzmoove governor?
[Galaxy S III Android Development] Scarface1991:
Hmm the CPU was stuck at 1.4 Ghz at all 4 cores again and it happened completely randomly. I turned on the CPU Monitor and it showed that a process called "daemonsu: 10206" was responsible for the most CPU Load. I have no idea what it means though or how it was triggered.

Have you guys saw something like that before?

Using the latest SlimKat with latest Boeffla Beta with Pegasusq Boeffla Moderate Governor
[Galaxy S III Android Development] lchiocca:
Daemonsu is the background process from your superuser application (daemon thread). Might be worth a couple of minutes to write a mail to the developer of your su app.
[Galaxy S III Android Development] andip71:
Exactly. This is the superuser daemon, which seems to be somehow blocked.

Very good finding, if more people having the CPU stuck issue can check if the same process goes wild for them, it might be worth letting Chainfire know.

Apart from that: If your rom is using supersu as root mechanism, I would recommend you flash in CWM the 1.93 version which can be downloaded as a zip from Chainfires supersu thread. I always do it after every rom install, never had that issue.

Maybe coincidence, maybe a pattern.

Andi
[Galaxy S III Android Development] Scarface1991:
I already installed the newest SuoerSU as a system app with the script so that it survives ROM installs.

I had a different problem about 4 times now in the last couple of days. When I listen to music with Google Music or Ulisten sometimes my screen cannot be turned on anymore. It's like the sleep of death, only while the music is playing. Yesterday I had the issue again.

Was listening to Music with Google Music and the music began to stutter pretty bad and I wanted to turn on the screen but the screen would not go on. When I plugged the headset the music switched to the speaker, which shouldn't happen because Google Music has the feature of automatically pause the music if you pull the headset out suddenly.

So I had to force reboot to solve the problem.

Anybody else had the same issue?

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] k-semler:
Are there any plans to integrate support for rapid charge into the kernel?
[Galaxy S III Android Development] Scarface1991:
I'm using the latest SlimKat. I switched from the AOSP Neat ROM to SlimKat without a full wipe since they are using the same base and didn't have issues so I thought it's fine. However maybe I really should do a full wipe then.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] andip71:
I also had that rarely during testing.

Intelliactive is a new governor, it is basically the very first version, so expect bugs.

If it buggers you too much, fallback to pegasusq.

Andi
[Galaxy S III Android Development] granadier:
I'm in the same situation as scarface1991 but since January.. In December I install boeffla.. All good.. But in January on cm11 m3 I guess I did a full wipe and install the kernel.. Since then I have to force reboot cuz of cpu 1.4 ghz all cores and did the same as scarface1991. 3 weeks ago I did a full wipe and install a nightly and every 4 days I update the system with the latest one but still the same.. What can I do then??
[Galaxy S III Android Development] andip71:
Scarface's problem is his display not activating again when my memories are right.

CPU stuck on 1400 is something else.

What governor are you using?

Did you check if a process was requesting CPU power which made the CPUs stick to 1400?

Apart from that, I never saw that at my end. Neither with CM11 nightlies, Tema CM11, Omnirom and Slimkat.

Andi
[Galaxy S III Android Development] granadier:
Zzmoze standard I guess... 1.4 ghz and no I don't know what process was doing that. I'll report when it happens.. And scarface1991 also has the cpu limit at 1.4 look his screenshoot. And also have the display not activating again issue. the cpu at 1.4 limit was causing me the display not activating issue. When I check the cpu usage saw all cores were at 1.4 and when I looked the screen don't response until almost 30 seconds later
[Galaxy S III Android Development] andip71:
Quick question, after having some conversation with ZaneZam.

Which tools are you using to monitor CPU core frequencies?

We have a suspicion...

Andi
[Galaxy S III Android Development] makimo2989:
Hi Andi,

I have the same problem as granadier, if I were to use ZZmove Battery or Battery Yank, all the core will be engaged indefinitely (and temperature will reach around 65-70C). Only when I switched to ZZmove Battery Extreme Yank that eventually only 1 core will be used. I can't pinpoint what exactly are using the cores, in OS Monitor, only System is the highest at around 11-13%, and followed by Google+ at around 8-9%, but total usage is around 20-23% only... and it will hang for around 30 secs before my phone will respond again...

BTW, I'm using CPU-Z as monitor... I hope this helps... :)
[Galaxy S III Android Development] andip71:
Well, it does not really help, but this is not your fault.

I am always using zzmoove battery yank, and never faced this issue.

What about trying pegasusq for 1-2 days, so we can see if it is a general issue or due to the fact zzmoove is still in beta?

Andi
[Galaxy S III Android Development] makimo2989:
Thank you, will do! I'll see if that helps and get back to you guys, cheers!
[Galaxy S III Android Development] Yeti47:
Same happened to me, which was why I went to pegasusq last week. Been running fine ever since on one core at 200 when idle. Happy to go back to battery yank and test...
[Galaxy S III Android Development] andip71:
Thanks Yeti.

[MENTION=3279788]ZaneZam[/MENTION] will not be happy to read this ;)

Andi
[Galaxy S III Android Development] Yeti47:
Dev work always has teething troubles no matter how hard you test, and every phone runs different app combinations so is expected... :)

I rebuilt my phone at the weekend, so not the same findings as last week.

With pegasusq / boeffla battery saving / multicore aggressive the cores remain stable. Doing nothing cpu remains under 10% normally and uses 1 core at 200 with a few quick blips up to 1000.

With zzmoove / battery yank / multicore off the cores act more like a highly stung race horse. They jump around all the time using 1 to 4 with occasional jumps to all at 1400. The cpu remains the same, normally under 10%.

Temp has remained stable so far, 43 as I type. Last week the phone often got warm.

Sorry that I cannot report anything definite...

Will watch during the day and report back.
[Galaxy S III Android Development] ZaneZam:
no not really andy but NOTHING can stop the release now which definitely will happen in a few hours :D

indeed indeed true words about testing and infinite

different

setups.. :eek:

yeah and the scaling behaving u described sounds like the beast :D

but something must 'tickle' it :) and the latest experience showed me for example if u are watching the

core/scaling activity with perfmon then u might run into a measurement error, somehow

it stresses the system more than other monitoring tools and then freq jumps also around like

u described - just saw that yesturday (and other not so nice things in addition *g*) during setup of

new governor profiles. try to get some 'second opinion' with other tools in addition... ;)
[Galaxy S III Android Development] Yeti47:
I was using omni performance tab for core frequencies, and osmonitor for cpu usage. Any other suggestions for better tools?

Rebooted a few hours ago to ensure nothing is hanging around. Time in states image is below, which gives a fair idea of what is going on. Doesn't look too bad, apart from 200 and 14000 always being equal.
[Galaxy S III Android Development] ZaneZam:
thats strange, never saw such stats :confused:

no idea what that can be, did u try switching settings?
[Galaxy S III Android Development] Yeti47:
That's why I switched to pegasusq which appears to be much more stable. Note though have been on zzmove for ages and has always been good, just changed recently.

Am going through the different profiles and boeffla settings to see if anything will change it. Haven't found anything so far (and am at work so can you do so much :(). Will try some more, then also go back to pegasusq for a few hours and post the picture for comparison.
[Galaxy S III Android Development] Yeti47:
A bad workman always blames his tools... Looks like it's more a fault of the monitoring tools, than the governor. Under pegasusq looks like 14000 is used more than zzmoove....

As a side note had an issue last week were my phone would always ignore my boeffla kernel settings and startup in zzmoove/std. Fixed it by turning all omni performance settings on and off. Has happened again today and this does not fix it, so going to format system and reflash. So, could be my rom is screwed and anything it does out the ordinary should be ignored. :(
[Galaxy S III Android Development] MrWWolf:
Sorry if I repeat the problem, but search don't go.

Flashing Boeffla 2.2 beta 6 on CM11 nightly 19/03 camera stop to work, I found the solution here http://xdaforums.com/showpost.php?p=50314036&postcount=233 . Tanks to [MENTION=5566418]limitedMUSCL[/MENTION], all works fine now. :good:
[Galaxy S III Android Development] limitedMUSCL:
It looks like the kernel is providing an outdated /system/lib/hw/camera.smdk4x12.so
[Galaxy S III Android Development] Nic2215:
I smell new kernel version is coming out soon :thumbup:;)
[Galaxy S III Android Development] andip71:
Yes you have a good nose :)

I plan a rc1 version for today. Already done and testing on my phone...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
...but you know this lib does not come with the kernel but with the rom itself???

Tststs...

Andi
[Galaxy S III Android Development] habylab:
Oooft. Going out to London today, a new kernel would suit me fine in the next half hour...

Kidding, but good work having it done already. Test away!

Sent from my Omni 4.4 Galaxy S3. Proud Googy Beta tester.
[Galaxy S III Android Development] limitedMUSCL:
I do not know what the kernel provides, cause I don't have it installed. I thought this being overwritten could be a reason, just that. If it's not, good to know. U don't need to be angry at me... :P Lol

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] andip71:
Could be almost possible. Will start upload in around half an hour :)

I am not angry, but had to correct this message as the kernel does not come with an outdated camera lib. It just comes without any, as the lib is provided by the rom.

All good :)

Andi
[Galaxy S III Android Development] andip71:
RC1

Hi all,

just started uploading all kernels for all devices and platforms.

All these kernel are release candidates (RC), so they will be likely the next stable versions in a few days.

Version 2.2-rc1

21.03.2014

Updated zzmoove governor to version 0.8 Final (credits to ZaneZam)

Reverted some scheduler changes to be closer to stock kernel again

Initramfs updated to version of 21.03.14

Enjoy

Andi
[Galaxy S III Android Development] makimo2989:
Already using RC1, initial impression is (as always) - rock solid! Plus even zzmove is not so BEASTLY anymore! I am now on zzmove-battery yank, and CPU-Z has indicated that mostly only 1 core is being used when idle (load around 4%). Previously on battery-yank, the CPU will swing from 4 to 3 to 1 core erratically, even when idling. Great work Andi and ZaneZam... :)

BTW I'm using the Omnirom kernel for CM11, because I remember that you said that in its core, it is more advance than the CM11's kernel. Is that okay? I'm still a newb on this...
[Galaxy S III Android Development] andip71:
The Omnirom kernel is generally a bit more advanced, as it implements newer Samsung code. And luckly it runs on CM11 as well these days (which can change daily however with a new nightly).

That is why I still provide also a genuine CM11 kernel on top.

Andi
[Galaxy S III Android Development] XDAMaxe:
Hi Andi, [MENTION=3279788]ZaneZam[/MENTION] explained the new settings of zzmoove v0.8

* 'zzbatp' (a new battery friendly but still fast setting)

* 'zzmod' (optimized based 2 core moderate setting)

* 'zzinz' (based on performance with insane scaling enabled)

* 'zzgame' (based on performance with scaling block enabled)

here

idk how things work but do you plan to provide them as new/additional governor profiles in boeffla-config v2 (pro) ?

(as far as I recognize they are not included yet... aren't they ?)

Thanks for your (and of course zanezam's) fine support