yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] m1trand1r:
+1 on this....I have galaxy3 and the differences between lagfree & ondemand governors on bench scores are huge....i mean...with ondemand bench score is higher and actuall performance is lower(lags etc.) while on lagfree bench scores are lower & actuall overall performance is much better....so...yes...benchamark is not realistic....and i'm sorry for darn offtopic....i just had to say it:p

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] bleuxeon:
This commonplace is well located in the noob lurning curve.

When the noob leaves his dust status, he is so happy that he starts repeating in every posts of any thread for any reason, what was the most understable for him :cyclops: : "benchmark is crap..."

1) You didn't read any line of my post except "benchmark".

2) Even Gokhanmoral use this very same benchmark from time to time to check....

...things that you would probably never catch.
[Galaxy S II Original Android Development] robertobsc:
Hi guys.

Here is the concept of screen_off_min_step (from droidphile's post)

============

iv) screen_off_min_step - Steps in frequency table to be used when screen-off. Example: If available freqs are 1600 1400 1200 1000 800 500 200 100 (L0 to L7) and screen_off_min_step=5 then 100,200 and 500 (L5 to L7) will be used during screen-off depending on the demand.

============

Here is our wounderful freq_table:

static struct cpufreq_frequency_table exynos4210_freq_table[] = {

{L0, 1600*1000},

{L1, 1500*1000},

{L2, 1400*1000},

{L3, 1300*1000},

{L4, 1200*1000},

{L5, 1100*1000},

{L6, 1000*1000},

{L7, 900*1000},

{L8, 800*1000},

{L9, 700*1000},

{L10, 600*1000},

{L11, 500*1000},

{L12, 400*1000},

{L13, 300*1000},

{L14, 200*1000},

{L15, 100*1000},

{L16, 50*1000},

{L17, 25*1000},

{0, CPUFREQ_TABLE_END},

};

So, thats the frequencies and its levels. The greater the level, the lower is the frequency.

It means that no frequency which has the table level lower than the screen_off_min_level can be applied in screen off.

I'll also take a look at this to certify that is been respected.

[EDIT]: Here we have the evidence that the frequency doesnt pass of 200 Mhz if we set the screen_off_min_level to 14.

<3>[ 5377.630595] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.650600] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.670602] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.690617] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.710593] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.730633] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.750590] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.770594] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.790614] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.810598] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.830588] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.850597] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.870589] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.890625] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.910597] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

<3>[ 5377.930613] [PUMP UP] cpufreq_lulzactive_timer 100>=60, from 200000 to 300000

This mean the timer function always try to pass of 200 to 300, but after that the adjust screen off function turn the frequency back to 200.
[Galaxy S II Original Android Development] red.hat:
L)

So Roberto, what is the best screen_off_min_step value to use. It seems setting it at a higher value is causing the sod's. In terms of battery am 14 hours after my first sod

I spoke to soon. I just had a sod.
[Galaxy S II Original Android Development] :
I'm sure I catch even more things than you, since you believe in benchmarks, and I'm pretty sure that gokhan doesn't believe very much as well, did you see some options on ExTweaks? Like "may increase ui responsiveness but lower benchmark scores"? Did you also know that there are bad devs (not gokhan) that make a mess with the kernel to increase benchmark scores to noobs like you believe and use their kernel? Did you know that this mess can make the kernel all fuct up?

Go learn something before going here with authority.
[Galaxy S II Original Android Development] bleuxeon:
Could you please tell me where to download Siyah kernel?

And what exactly is ExTweaks?

:silly::silly::silly::silly::silly::silly::silly::silly::silly::silly::silly::silly::silly:
[Galaxy S II Original Android Development] :
Here
[Galaxy S II Original Android Development] m1trand1r:
Obviously...ExTweaks is an app for Siyah kernel configuring & tweaking....search for it at PlayStore:p

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] ROX77:
Hi Roberto, understood screen-off settings, but there is a problem when screen is on. Cpu stays always at the maximum frequency (in my test 1200) and can't go down (even with screen off).

And other people on italian forum had same results with various ROMs.

Maybe that freezes and reboot that people are encountering are caused by the high temperature of cpu?

*Inviato col mio Aifogn rettangolare brevettato :cool:
[Galaxy S II Original Android Development] robertobsc:
Man, do me a favor.

Turn the debug_mode parameter on.

echo "1" > /sys/devices/system/cpu/cpufreq/lulzactiveq/debug_mode

and when you notice that the frequency is stuck, execute this command in a terminal emulator or adb:

dmesg > /sdcard/dmesg.txt

And send me this file so i can understand that.

Also send me your LulzactiveQ settings.

---------- Post added at 11:34 PM ---------- Previous post was at 11:05 PM ----------

Guys, just to report that i have dome sone alterations in LulzactiveQ governor.

- Found and fixed some bugs.

- Included a little fix/improve of sampling up / down frequency logic from Neak Lulzactive.

- Improved the default tweaks.

I compiled with the newest version of Gokhan sources and im testing a lot here.

I'll pass today and tomorrow testing it, if everything goes well i'll send to gokhan so he can include in the weekend new version (if he can).

Just to make sure that we are in the same sintony:

There's always someone that complains. I saw one comment that made a impression on me that this is MY governor, a experimental thing of MINE that's apart from Gokhan's, like he just putted it there.

That's obiously nonsense. Yes, i have developed it, but first, others people could do this and second this is for everyone and of everyone, and i would say Gokhan is the highest symbol of the Kernel improvements and newests algorithms and ideas to make things better.

So this is our new governor, so we can get a new try to get a even more battery life, better performance, always trying to find and make things better, a new tweak, something hidden, and always evolve.

And i just can thanks Gokhan to make this possible to us.

I'm sure almost everyone here have this exactly thought. This is for who doesn't.

I'll post my evolution here tomorrow night.

Cya!
[Galaxy S II Original Android Development] FadeFx:
Sorry, didn't see that...

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

tapatalked from Galaxy S
[Galaxy S II Original Android Development] apk_xiz:
hi OP /or anyone who know aabout this.

in your play store extweaks picture (and also 1 day ago ) their iss a option in cpu>ARCH_POWER

but in my extweaks it is missing ,any fix (i have latest extweaks+pro + kernel 4.1.2)
[Galaxy S II Original Android Development] Tungstwenty:
It's normal. ExTweaks will display whatever settings each particular kernel version allows to be tuned, and these latest versions happen to not have that any more. On the other hand, perhaps it's not visible from the Play screenshots but there are several new params that didn't exist at the time the app was published - and it doesn't need to be updated to display more params or less since it gets that info from a file within the kernel
[Galaxy S II Original Android Development] noscentsbrad:
What are CFS tweaks? N what r the best ones?
[Galaxy S II Original Android Development] CamoGeko:
Something thats best for one device might not be good for another.

Try different stuff out yourself and see. ;)
[Galaxy S II Original Android Development] bleuxeon:
I never thought I would see answers to my questions :cyclops: I was simply kidding you.:D
[Galaxy S II Original Android Development] Many40:
Sorry for OT. They've been aware of that (to continue kidding) :)
[Galaxy S II Original Android Development] mesaj:
Dual boot with Sense4all don't work for me. No option to choose secondrom, just goes with primary. CM9.1 works good. I tried recreating dualboot but same as before
[Galaxy S II Original Android Development] gokhanmoral:
Sense4all is not supported with this kernel either with primary or secondary rom.
[Galaxy S II Original Android Development] ZVM75:
i get SOD

can any explain why?
[Galaxy S II Original Android Development] m1trand1r:
Hey guys:)...well let's see if my config'll help to anyone of you....

ExTweaks settings:

cpu tab:

UV: -50mV

Governor: pegasusq

cpu hotplug(default)

cfs tweaks/linux kernel(default)

cpu idle and power mode: AFTR+LPA(default)

max cpu clock: dual core mode

scaling max freq: 1000mhz...min 300mhz.....

Zram size: 100mb

and some new status here:

and just to let you know guys....i've flashed KH3modem.bin on my s2 2 days ago.,i've found it in general section....and results are impressive:

My phone does not heat up above 35°C anymore(even when playing GtRacing game:D...before it heated up to 51°C:p:eek:)when on charger temp goes up to 44-48°C....before it was constanly at 51°C(bad for battery life) even if i didn't do much stuff it was hot......3g connectivity is alot better and overall my baterry lasts longer since i did this....

and I'm on Siyah v 4.1.2 which is latest...and did not face any SoD's or whatsoever....I hope u will find this info useful:)

and last screenie while i'm writing this post:

allmost 6hrs of screen up time:D

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] m1trand1r:
geez...last screenie again:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] nitinvaid:
Stock battery???
[Galaxy S II Original Android Development] m1trand1r:
yup:D...i bought phone a month ago:)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] raptor22:
Small request here.

Can someone, hopefully gokhanmoral, create/compile a custom Siyah v4.1.2 with fb suspend enabled to get CRT TV animation working on JB ROMs? Anyway big thanks for the great kernel have been using it ever since I got my S2.
[Galaxy S II Original Android Development] m1trand1r:
@Gokhanmoral and @all

I'm sorry for posting batt stats here...i saved previous post and after i continued writing it i missed general thread...and it ended here:angel::silly::cowboy:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] olrait:
Got many SOD's with Siyah since some relases ago, same with Dorimanx's (even freezes).

But everything runs well now on siyah 4.1.2. Haven't got a single sod/freeze since installed it (day of release).

Installed after wiping cache/dalvik, and wiped them again after installation, fixed permissions before rebooting into android. Kept default profile on CWM.

So..:

1- Wipe cache

2- Wipe Dalvik

3- Reset ExTweeks profile

4- Flash kernel

5- Wipe cache

6- Wipe Dalvik

7- Reset ExTweeks profile

8- Fix permissions

9- Reboot

Changed only BLN settings on exTweaks. So pegasusq, cfq, etc. No UV, no gpu tweaking... So far so good for me. Thanks GM, again.

RR ICS 2.6.1.

Didn't test on JB yet.
[Galaxy S II Original Android Development] red.hat:
Robertobsc, I can't wait to see the tweaks for the new lulzactiveq. It seems it is really battery friendly with great performance if tweaked appropriately. Will you be creating a script with all the changes?
[Galaxy S II Original Android Development] ROX77:
Had 3 SODs even with smartass2, so it's not only a lulzactiveq issue.

Could anyone explain me how to solve this error on the script, to enable debug on lulzactiveq?

I can't create a folder in this path, even manually with rootexplorer (mounting as r/w). Why?!?

Thx

*Inviato col mio Aifogn rettangolare brevettato :cool:
[Galaxy S II Original Android Development] Simba501:
Gok,

Would you consider looking into implementing "Slide to Wake?" Showp-1984 has it in several of his HTC kernels. He pointed me in the direction of its specific branch in his Git to show what all is needed.

For those unfamiliar, you can observe the behavior here.

EDIT: It appears that it is implemented in Fluxi as well.
[Galaxy S II Original Android Development] :
Question.

Setting Hotplug mode to Second core always off won't make any effect using pegasusq, right?
[Galaxy S II Original Android Development] AlkaDragos:
PegasusQ has its own parameter for number of cores used. MAX CPU LOCK parameter on CPU tab in ExTweaks (Dual core mode / Single core mode) ;) also this is not the right thread to ask this kind of questions.
[Galaxy S II Original Android Development] arsalanaly:
lemme try your settings widh siyah 4.1.1
[Galaxy S II Original Android Development] tigerphil:
I'm using Siyah 4.0.1 with CPU SPY and BBS but i dont seem to be getting any CPU states shown when i check if my phone is sleeping etc.

I have checked the file "/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state" which exists but the folder is empty :confused:

Is there a fix to this or would it be better to re flash the kernel?
[Galaxy S II Original Android Development] :
Go 4.1.2
[Galaxy S II Original Android Development] tigerphil:
Will start downloading now and flash this eve. Hoping it sorts the problem as have had deep sleep problems with the rom in the past.

Update. flashed 4.1.2 but still the same problem. File "/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state" is still empty
[Galaxy S II Original Android Development] intronauta:
This is the last_kmsg of my last SOD with v4.1.2 (the third today)

My custom settings in extweaks for my LWLPD Stock (4.0.3) are:

CFS tweaks->Linux defaults

smooth scaling->1000Mhz

Governor-> conservative 1000-200Mhz

zram->100MB

Force Mass Storage Mode

No externar apps or scripts for undervolt or related cpu tweaks, /init.d is empty.

I've downgraded to v4.1.1 and testing if get SODs and is related to something new in the rom, because never suffered this problems with this version

** One cuestion, Is there anything interesting in the last_kmsg? Seems very generic info and I can't find anything interesenting or related with the problem.

my2cents.
[Galaxy S II Original Android Development] jgcaap:
Seems fun :) i prefere the way it is now. In case is implemented i hope there is a option to de/activate.
[Galaxy S II Original Android Development] bluefa1con:
Fluxi did this in the last version of his kernel before he disappeared
[Galaxy S II Original Android Development] Mohamedselim:
Suggestion for Gokhan why not implement option in Sayih kernel recovery to boot to second rom directly (check box) or so

So we do not have to swap roms to make one of them default

If we like the second rom more so we could (if we want) make it default with every boot

If this option is unchecked so we return to normal 3 second wait then first rom default boot
[Galaxy S II Original Android Development] grzesdroid:
governor who will be better? lulzactiveq? maybe pegasusq? Can anyone provide a good setting for the gov?

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] rav4kar:
NM.
[Galaxy S II Original Android Development] Josuhu:
4.1.2 SOD

Since installing 4.1.2 I have had two SODs. Extweaks is default. Running CM10 rom.

Every SOD seems to eat about 10% of battery.
[Galaxy S II Original Android Development] :
I'm getting SODs too, 2 3 per day, on ics from as in signature. Sorry for this post, which is quite useless since I don't attach logs. I had android logger disabled, therefore I couldn't catch them after the fact :) just wanted to share my experience!

Sent from my SGS2 - SlimICS Rom & Siyah Kernel
[Galaxy S II Original Android Development] Josuhu:
What governor did you use while getting SODs ? I used Lulzactive and now testing Peqasus if it makes a difference.
[Galaxy S II Original Android Development] Zytrel:
zram still likes to crash. Without it, everything is smooth and stable:
[Galaxy S II Original Android Development] marcwkh:
Rild still restarts in mid night in latest version + stock 4.0.4 (ZSLPP), tried matching RIL with baseband but no improvement, this problem does not occur in 3.2.7.2 (issue started since v3.3.1, but not taken seriously before I can stick with 3.2.7.2 with 4.0.3 ROM. Now I can't use 3.2.7.2 with 4.0.4 rom)
[Galaxy S II Original Android Development] khal_nayak:
yesterday i installed 4.1.2 and since then i only changed a few things in the default config, changed to smartassv2 and sio, min and max frequency to 200 and 1000 and thats about it but later noticed, when the phone is in deep sleep, it newer awakes, it crashes in deep sleep, need to reboot only to make it work so i returned to 4.1.1 and problem was solved so this is something to look out in 4.1.2
[Galaxy S II Original Android Development] slipmeknot:
Also had SOD every time my phone gets into deep sleep. Thought it was just me now back to 4.1.1 :(
[Galaxy S II Original Android Development] qqqqqq0:
+1

GT-I9100 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy S II Original Android Development] hawkerpaul:
Hi Gokhan.

Just a small point about CWM 6 backups.

You put a confirm prompt in v5 when the backup option was selected.

This has gone from v6. If you select backup, it performs it immediately without confirmation (I tried the external sd card backup option)

Without the confirm prompt its easy to do a backup by accident if you've pressed the screen too many times when going into the backup/restore option.

Also, I've noticed that backup is extremely quick in this version. (tar format I THINK, as I have no blobs folder) I hope its backing it up properly! :)

If I select the dup (dedupe) format from the menus and go back into select format, it still has (default) next to tar. Is this a bug?
[Galaxy S II Original Android Development] apollopayne:
Maybe I'm just lucky but running 4.1.2 fine without any sod or any other issues. Current rom RR 2.6.1 all settings default.
[Galaxy S II Original Android Development] 000zui:
+1 never had any problem with 4.1.2, not default settings. Pegasusq + cfq

GSII @ Siyah 4.1.2 # NeatRom Lite XWLPI / PFittech Rom 1.1.1 JB # Jkay&Mod personali
[Galaxy S II Original Android Development] pcristi:
I have a some problems with last CM10 builds 10-20120821 / 20, I go back to 10-20120812-EXPERIMENTAL-i9100-CODEWORKX, and not SOD, not problems with auto brightness. :)
[Galaxy S II Original Android Development] Didgesteve:
SOD fix

I'm new to Siyah kernel and this thread, but even after a short while I can see the time and effort gokhanmoral and you guys put into it.

I've suffered from SODs in the past, almost every time I've tried this kernel, but I've persisted as so many people say how good it is (which it is).

I'm on SLIM ICS, and I recently found a fix.

In Extweeks under GPU I disabled Mali boost, and set the minimum frequency to 100.

No more SODs.

Hope this helps
[Galaxy S II Original Android Development] pilgrim011:
Could you please elaborate how the problem manifests? I am wondering if it's the same problem as many of us faced recently - complete signal loss, recoverable only by rebooting the device, with massive battery drain, when going to network settings message "insert SIM card blah blah" pop ups? I don't know when it started, but I started to notice it on 3.5.2. After that I have tried everything - changing ROMs (XWLP7, XWLPD, XWLPG), changing RILs (either manually or via GetRIL app), changing modems (XXLPS, XXLPX, XWLPW...) ,changing Siyah versions, mixing different modems/ROMs/RILs... Now I can say that the problem is almost certainly some recent change in kernel, because I'm on the 3.2.7.1 last four days and finally I'm not experiencing unrecoverable signal losses. But I really really miss eargasm... I'm wondering when GM will release eargasm app like he announced. Or maybe take a look at this issue because it's really serious for me - I could leave it overnight with 50% juice left, and be late for job (my phone is my only alarm clock) because it powered off somewhere in the middle of the night because of heavy battery drain after the signal loss...

GM, if it's difficult to find the cause of this problem (not everyone is experiencing it), would you be so kind and just add eargasm to the best Siyah release - 3.2.7.1? If it's not that easy, nevermind, but just in case I'm attaching here 3.2.7.1 because it's not on your website. Thanks :)
[Galaxy S II Original Android Development] gokhanmoral:
can those who have SOD issues with the latest version report their sdcard brand and class and also ROMs in the user thread please?

not to this one, but to the other thread that is in general section
[Galaxy S II Original Android Development] marcwkh:
I have tried stock (SZLPN), XXLPS, XXLPX XXLPW, XXLQ5, XXLQ6 modem with RIL matching with getRIL problem didn't improve.

the rild restarts when it is idle (mid-night), but it will become more frequent when I travel around and not using the phone ( getting 5 dump state files in /data/log after traveling in busy urban area), usually recoverable by itself, but got to reboot in one occasion to make cellular signal work again (the phone was warm to touch, I guess it is due to battery drain)

I am also certain it is due to kernel not due to ROM (tried stock 4.0.3 and 4.0.4),

The rild restart occured since 3.3.x and it become worse since 3.4 (or 3.5? not very sure) therefore I suspect the problem is related to the modem driver in the kernel (don't know if the term proper)

I agree with you that adding new features on top of 3.2.7.1 is great, but if it is impossible, making bluetooth workable in 4.0.4 rom would be great enough for me.
[Galaxy S II Original Android Development] abdussamad:
im using XWLPU neatRom lite v3.2.1 and siyah v4.1.2.i didn't have this problem before after charging today my phone kinda wakes from standby for charging automatically,like It gives the beep of charging(when charger is connected ) and shows the icon of charging and then its normal again.it does this for like 2 times and then it doesn't.i plugged in the charger again and again it did the same thing after removing from charging,is this a known issue???

---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------

first this was happening over and over again then from extweaks i resetes the fuel gauge chip,then it was happening only twice
[Galaxy S II Original Android Development] markjh:
Try to clean the USB socket.
[Galaxy S II Original Android Development] jaswinky:
I also have SOD with SmartassV2-cfq (freqs 100MHz-1200MHz) just after changing default hotplug setting to "both cores on" mode and then switching screen off. Returning to 4.0.1 better than 4.1.1 because 25MHz-50MHz freqs gave me better battery results...

Thanks anyway for the job.
[Galaxy S II Original Android Development] pikachu01:
Got the RIL problem again on stock Samsung. Using 100MHz as minimum frequency. :/

Looks like this problem isn't resolved yet :(
[Galaxy S II Original Android Development] pilgrim011:
At least we now know that problem isn't present on 3.2.x kernels - as marcwkh pointed out, it started with 3.3.x versions, so now it's probably easier to solve it.