yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Thank you for your time and information, pikachu01. :) I really appreciate your help and I do not mean to doubt you even though you have stated a few times now that these idle states cannot be entered while the screen is on but it is posts like this (poetialy not a valid source) that makes me think that these idle states were designed to be used while the screen was on! http://xdaforums.com/showpost.php?p=23252902&postcount=17

Important points from post:

- "AFTR - clock is gated, CPU core power removed, cache power remains - this eliminates a great deal of static power consumption - cannot be entered if second core is active"

- "These are not deep sleep states. Deep sleep is also known as "suspend" - where almost the entire system is shut down."

- "These are CPU idle states, which allow the core to save power even when the system is "running". They take significantly less time and energy to enter, but save less power. Also, there are only three of them - IDLE, LPA, AFTR."

- "if the voltages for two frequencies are the same, it's better to run at the higher frequency and drop into AFTR/LPA to shut off core power more often."

- Other info http://lwn.net/Articles/495469/

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

I think siyah 3.3.1 (which I use) does not include the v3.2.8.x bugs which have been mostly reverted. It (3.3.1) has so far been very stable and smooth for me but I'm sure the next stable version will be good too :)
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
I tried v3.3.1 but I dont know :rolleyes: I think I better wait, I saw the changelog I know it has been fixed but still :rolleyes: I will wait for the next version and see the comments also :).
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Lol, you will be waiting forever.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
The amount of battery drain can only be logically accounted for if you wait until whole battery is drained. The fuel gauge doesn't scale linearly for an amount of energy used. Try using the kernel for at least 1 battery cycle before commenting. :)

Also some apps you newly installed might cause higher battery drain. Check that too.

After doing some more reading, I can see that there are two states, IDLE and LPA with usage stats in cpuidle:

/sys/devices/system/cpu/cpu0/cpuidle/

The clock gating is just gating the clocks of some parts of the core (not all).

So you're right, the screen can be on while the core waits and clock gates, turns off power on some parts of the core. All those are Core C-states, not package C-states.
[Galaxy S II Q&A, Help & Troubleshooting] vizdak:
Use it now. No one knows when will be gokhan will update the siyah version for S2.
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
Hi, I would like to try these settings with pegasus but I don't know where are those setting in Extweaks. Can some one help me ? I'm running 3.2.7.1
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
You'll need to use scripts to set these :)

If you install ThunderBolt!, you'll be setting these as well (but with different values, my own values). You can edit the script from that point there to cater to whatever settings you choose.
[Galaxy S II Q&A, Help & Troubleshooting] willybarca:
use setcpu
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
I wouldnt have commented if I didnt have a full battery cycle :rolleyes:, come on man am not a nOOb :p
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Then dump the better battery stats log. I've mentioned it twice now .
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
For people who want a little extra from their extweaks app:

(this is presented, as is, and only meant for people who know how to use it)

I've modified the Extweaks config-files to include the

-classic-hotplug parameters (those removed, because people didn't use them right)

-GENTLE_FAIR_SLEEPERS setting

-ARCH_POWER setting

-Ondemand suspend freq.

-PegasusQ settings (last tab)

I've been testing this with 3.2.7.1

(so use on your own discretion on other versions) (although I think it can do no harm)

included in the .zip are the 4 config-files

battery.profile

default.profile

performance.profile

customconfig.xml

and these have to be put in:

/res/customconfig

(make a backup copy of the original files, just to be sure ; else you'll have reflash the kernel, and your back to normal)

To put them there, you'll have to use an explorer app with root permission, to write in that folder (like root-explorer, and mount R/W)

Again, this an 'as is' sharing (but I think those of you who are a bit creative and know a bit of XML files can extend it to unseen limits....

Used well, you can get still that extra mile out of your device...enjoy!

EDIT: sadly these settings won't survive a reboot, and will be overwritten by siyah defaults (baked into the kernel) :(....
[Galaxy S II Q&A, Help & Troubleshooting] ndnesh:
Hi Guys i have a problem, i had Siyah 3.2.7.2 and everything was perfect.

I flased 3.3.1 and now my Wifi is not turning on at all. Whats worse is that the Settings screen does not show the wifi Mac Address at all. it simply says "Unavailable".

I am on the XWLPG ROM, and since i have had this issue, i have done a factory reset(with a data wipe/USB Wipe), Reverted to Gingerbread 2.3.6, tried Siyah Kernel on the Gingerbread(the gingerbread version of course), Came back to ICS, Flased the Stock ICS for India(XWLP7), and finally came back to XWLPG.

In each of these scenarios, i was not able to see the Mac address in the Wifi Advanced settings and also in the Normal Settings.

Have i bricked my wifi adaptor?

I usually wouldnt worry about this, but its just that my warranty just expired(June 3rd).

So i dont know what to do. Some said that its an issue with wifi Modules, i have done everything i can to try and fix this. but im stuck.

Can anyone please help!?
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
..just answered in the dev thread. not that it can be much help I think...
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
Calm down man :p, no thanks :) I will wait for some more cycles... :)

Thanks :)
[Galaxy S II Q&A, Help & Troubleshooting] greenemperor:
Just download the chainfire's brick bug test and shows that have bad chip,00x19.I use Omega aokp v4 with siyah 3.3.1 so is the omega the problem?

Needed to flash another rom?
[Galaxy S II Q&A, Help & Troubleshooting] Tye:P:
Does anyone know how to manually change the voltage values for the screen itself?

Can it be done via script/config file or does it require re-compiling the kernel?

The reason I ask is that awhile back, I forget which version of the kernel Gokhanmoral mentioned he had reverted a change that applied an UV to the screen but some users were reporting a grey tint on the screen edges so it was removed. I was using that kernel at that time and didn't have any issues and as the screen is the largest contributor to battery drain I'd like to play around with these values. (I wish I could supply the post but I can't find it).
[Galaxy S II Q&A, Help & Troubleshooting] naveediftikhar:
No mate its not the rom..its ur hardware..its ur chipset and no rom can change the faulty or brick prone chipset u have inside ur phones hardware so no point in chaning ur rom..keep on using it or flash anythin else u want hoping that ur phone doeant get bricked?
[Galaxy S II Q&A, Help & Troubleshooting] ndnesh:
Hi John.... your reply and my question seems to have been deleted from the DEV thread... so can you please let me know what it was that you said ?:)
[Galaxy S II Q&A, Help & Troubleshooting] baza14:
No, it's not hardware. That's bad firmware for that chip.
[Galaxy S II Q&A, Help & Troubleshooting] Ba7rani123:
If I flashed v2.3.8, does my app data get corrupt or what gets corrupt exactly ? :/
[Galaxy S II Q&A, Help & Troubleshooting] greenemperor:
I got 2 different answers so please advise if needed to change the rom(omega v4)..
[Galaxy S II Q&A, Help & Troubleshooting] baza14:
No, there is no need to change it. Read here http://xdaforums.com/showpost.php?p=27182818&postcount=148
[Galaxy S II Q&A, Help & Troubleshooting] naveediftikhar:
either ways mate the point i was trying to make is that greenemperor doesnt have to change his rom as its no good..onw can switch from anythin to anythin and it wudnt help..itll stay what it is...!
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
Hi,

I've undervolted my S2 to 850mv at 200Mhz with Voltage Control and I wanted to enable the 100Mhz step. I wanted to undervolt at 100Mhz too but the minimum is 850mv.

Would I gain any battery life if I enable the 100Mhz that has the same volt as the 200Mhz step ?

thx
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
No.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] virusZz:
Where can i find SiyahKernel-3.2.7.1 download link?
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
http://www.sendspace.com/file/6lher4
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Actually yes. Power consumption is the product of frequency and voltage, hence 200MHz will be twice as power consuming as 100MHz, even at the same voltage, but this is not an exact formula as a lot will depend on how the combinational logics are setup.

Some somewhat related info:

http://forums.anandtech.com/showthread.php?t=119229
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
So you don't support entropy's theory of processes being completed faster on 200Mhz?

In turn you will use less battery, because the process won't have to run as long.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Process will get completed depending on how the frequency scales through load. If the process has a load > 100 on 200MHz, it'll be scaled by the governor to a higher frequency. Hence, "processes completed faster" on 200MHz isn't even in the equation.
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
But when I read an article I don't need the CPU to be high so in this situation the 100Mhz might be useful, isn't it ?
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
If that will be enough for reading the article then yes. If not then your CPU will scale up anyways.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
hi..you had a problem cMiui backup

i think it's clearly related to cMiui and I suspect one of three things:

1. there was an issue with some roms putting /.secure_android folder on the external sdcard instead of on the internal sdcard (or vice versa, can't remember right now), so if you have apps stored/moved to sd , this might be the issue

2. it could be that cMiui has issues with swap the mounting point of the internal and external sdcard, and maybe there's a setting somewhere you can toggle to switch them

3. or in the farmost far sought possability, it could be a another side effect if you're coming from 3.2.8.2 to 3.3.x without wiping data partition (since the problem affects the data partition, but this I'm not so sure about, because one of your roms does backup ok....

hope this leads you in the right direction...
[Galaxy S II Q&A, Help & Troubleshooting] pilgrim011:
100 MHz is bad for some of us that rely on alarm to sound in the morning. There were many complaints from people that alarm didn't go off when 100 MHz was default for Siyah. That is why GM decided to use 200 as the default freq.
[Galaxy S II Q&A, Help & Troubleshooting] KennyLegend:
I would disagree after reading Entropy512's and Andreilux 's opinions on this back along.
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Alarms are working well for me even after putting 25MHz as the lowest frequency. That's because I set the governor tunables to scale correctly according to load.

Can you tell me why though? Just putting the fact that you disagree amounts to nothing.
[Galaxy S II Q&A, Help & Troubleshooting] berq219:
Ermm I have an issue. Sorry if it's been answered a couple of times, searched it but could find no answer.

I'm on Siyah 3.2.7.2 on latest Paranoid. (Flashed the kernel on older Siyah yesterday) I installed ExTweaks to turn the BLN on, when I use the test it button it works fine but it does not work when I use the phone. What am I doing wrong?
[Galaxy S II Q&A, Help & Troubleshooting] #illidan:
Anybody having issues trying to switch on the phone when its charging?

Pressing down the power button only gets you to the suspended power animation again & again which will no longer animate as asop charging has been implemented on cm9 but only works on stock kernel.

Phone will only boot by either removing the charger or by going into CWM.
[Galaxy S II Q&A, Help & Troubleshooting] rakeshishere:
All the custom kernels have this problem on recent CM9 nightly build so its not specific to SIYAH ;)

Sent from my Galaxy S2 powered by CM9
[Galaxy S II Q&A, Help & Troubleshooting] #illidan:
I know that & so I mentioned asop charging commit but I was still just confirming.
[Galaxy S II Q&A, Help & Troubleshooting] gwiqu:
the Latest Siyah kernel 3.3.1 dun have the brick bug in it right? O.o
[Galaxy S II Q&A, Help & Troubleshooting] readz_one:
after i flashed the siyah kerenel 3.3.1 , my phone become really hot after a few hours. is this a problem with the kernel or it's thr rom's problem ?
[Galaxy S II Q&A, Help & Troubleshooting] runedrune:
No.

10chars.
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Re 100 vs 200 mhz battery

Hi I know this question was not directed at me but I have recently been testing with 500mhz (950mv) as minimum frequency and I have experienced no decrease in battery life so far vs 200mhz (850/900mv). Actually batter life sems to be 5+% better despite over an hour of gaming.

This may be due to:

1. Less need to scale up the governor as high loads are reached less often (despite low freq_step).

2. Cpu can spend more time sitting in idle states (aftr/lpa) as 500mhz is 2.5x faster than 200mhz despite similar voltage (+50mv for me and same on stock)

More importantly:

1. Waking up phone from deep sleep seems to be significantly faster! (1 vs 2-3 seconds)

2. Overall performance seems to be smoother!

3. Phone spends more time in deep sleep but with 200 or 500mhz battery drain overnight is 0-1% at wost :)

4. Cpu spends much more time at 500mhz than at 800-1000.

I will definitely keep testing this is the only potential downside seems to be battery life and so far that seems to be slightly improved and I will interpret that as 'no significant loss'.

I would defiantly recommend trying it! It may not work like this for others but it's worth trying :)
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
I'm not sure how to interpret that. You mean there's actually a difference between how fast a task can be accomplished as dictated by its minimum frequency?

If your governor is set correctly to scale to the correct frequency for certain tasks, I fail to see how setting a higher minimum frequency can result in the processor idling faster. The maximum frequency being 1.2GHz and all the frequencies in between would work as well to accomplish tasks. Your frequency is not locked to the minimum frequency when you're processing tasks (unless you set your governor to do that).
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
I think what I meant by task was 'background processes' in that sense. Btw I use an app called 'cooltool' to monitor no of cores, freq and usage. Anyway I completely agree with the scaling point; if I run an app I can see that the freq will scale up and then down with the load. In this sense minimum frequency will only be able to dictate how quickly maximum freq is met (assuming a low freq_step such as 30 on siyah default but not with 100 as in stock sammy)

What I was referring to in my post was the cpu activity running background 'tasks' when you are reading a text or reading a webpage without scrolling etc. Using cooltool I see that in both these situation the cpu stays at the min freq (200 or 500) but that with 200mhz the cpu usage graph shown with cooltool is always much higher than with 500mhz.

I could be wrong but to me this suggests that my personally observed no loss of battery power when using 500 as min freq is due to the fact that these small background processes (that do not need to scale the cpu so <90% of 200mhz) will be completed faster at 500mhz (up to max of 2.5x faster) and then the cpu can spend up to 2.5x more time sitting in a throttle/idle state while the text/webpage or simple/static page is viewed.

But like you said, when running an intensive app the cpu will scale beyond min freq and would not be relevant as I completely agree.

I may be completely wrong about my guess but I hope you can better understand why I was thinking that :) Thanks again for your input and help! It may be the case that 100>200>500 or vice versa but since I seem to be observing 100=200=500 for battery but see some performance benefits with 500 over the others it made me think about why this could be. You seem to be using 25mhz though so must personally find this better than all the above?

Ps if using chrome google will translate this page but it is a good (allthough outdated) read about power consumption for the GS2 :) - http://www.android-hilfe.de/samsung-galaxy-s2-i9100-forum/180670-info-akkuverbraucher-des-galaxy-s2.html
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Whether it's background process or not, the same rule applies for whatever frequency scaling it is. That is, the process's load will determine the frequency scaling. (Unless it has a nice value that is different, though the load calculation would still apply, though it will get a different priority compared to nice 0 processes).

Take note that CPU frequency power consumption at low levels (100,200,500) doesn't really make much of a difference compared to the display. Hence, if you have a high display time, it makes little to no difference on what your minimum frequency is.

This however is different if your display time is low where power consumption would skew towards your frequency scaling. Or when you have syncing going on where your device would spend more time being awake (with the screen off).

And for your 3rd paragraph, still doesn't make sense. If the background task doesn't represent a high load, that means the scheduler will still optimize it to be completed within a certain time. The delta between having it running at 500MHz as opposed to 200MHz wouldn't make a difference at all.

Reading the forum post, I see this:

Not sure what to make of this. But if the reason why 100MHz consumes more battery than 200MHz is this reason (that the kernel calculates battery consumption for 100MHz wrongly, or the hardware is whacked for 100MHz), then what's with bringing "calculating faster, that's why go to idle faster" theory is brought in. Though this is a translation, and I'm guessing this is what the author means.
[Galaxy S II Q&A, Help & Troubleshooting] berq219:
Seems like I found out the problem so if anyone's encountering the same issue here we go:

I was using GoSMS so it's default settings wakes the phone. That's why the BLN seems like not working. Just turn off the wake up option from the notification settings and there you go! =D

Btw I read the BFN is gonna be added to siyah :O I guess its much better than BLN! Cant wait :O
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Again I may be wrong but it may help to work off an example scenario: reading an open text while some background tasks are run. Min freq = 200 or 500mhz.

Assumptions:

1. CPU freq will be at scaling min (200 or 500) - no need for higher freq

2. There is a steady approximate 50% load at 200mhz = 20% load at 500mhz (Not enough to scale up)

3. 100% load power usage of 500 mhz is about 2.5x higher than 200mhz but so is performance

4. At 200mhz cpu sits in low power idle for 50% of the time (100-50%)

5. At 500mhz cpu sits in low power idle for 80% of the time (100-20%)

6. Whilst at idle (aftr/lpa) both 200mhz and 500mhz use an approximately equal and very low amount of power and amusedly the 500mhz freq spends more time in this low power state whilst performing the same tasks.

My possible conclusion: the fact that the cpu is in an idle state for 80% vs 50% of the time at 500mhz outweighs (or at least balances) the fact 500mhz may use a little bit more power. It uses more power when running but is running for less time.

This is what I think may explain the lack of extra battery drain when my phone spends most of it's time at 500 vs 200 mhz when you would expect some more drain. This of course is assuming the aftr/lpa can be entered for 50% of the time at a 50% workload.

But regardless of weather this is true or not. It seems that my phone is using less power with 500mhz as min freq but also with fast resume from sleep times and a little bit of an increase in smoothness!

I may be mistaken but I had understood that he meant that he did not use 100mhz because it was less energy effecient and that because "one and the same operation is energetically carried out most effectively at 200 MHz!" - I think that the error he refereed to was the fact that 100mhz was shown to be less energy effective and by error he meant "not in accordance with what expected to find".

While I have been studying I have left my phone on with Badass Battery Monitor Open and a high display timeout to prevent deepsleep. Here the phone just sits almost idle at the lowest frequency and I have used this method as a crude an approx measure of "how many percentage points were lost for 30 minutes at 200mhz vs 500mhz" whilst almost idle (only small background tasks like the os etc. The app indicates battery usage with time in brackets as follows - Batter Usage - 4% (00:15:18)

Maybe this small difference only happens with my phone but if you were interested try the above (or similar method) using 25mhz vs 500mhz min freq as an extreme example?

Thank you, as always, for sharing your knowledge with me. I really do appreciate it :)

---------- Post added at 07:49 PM ---------- Previous post was at 07:48 PM ----------

What is that btw? Does the 'F' stand for 'Flash'? Thank you :)
[Galaxy S II Q&A, Help & Troubleshooting] berq219:
Yeap! =) Have a nice Sunday!
[Galaxy S II Q&A, Help & Troubleshooting] confusedmuse:
Dynamic frequency scaling allows the CPU to reduce the frequency and voltage in idle state to conserve power or to reduce the amount of heat generated by the chip.

Lower steps doesn't increase the processing time, as the necessary frequency to treat any process as fast as possible is dynamically adjusted by the governor.

Only underclocking would have an impact on the processing time.

A high minimum clock is just energy waste.
[Galaxy S II Q&A, Help & Troubleshooting] ndnesh:
Hi John,

Thank you for your reply. I don't understand however how this is connected to the wifi not turning on.? I also, I I have never flashed Miui ROM on my phone....

If it helps, I have the same issue that's being described in issue 28036 in the Google bug report.

I'll post a link here soon.

Any help is appreciated :-)