yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] droidphile:
Normally CONFIG_CPU_FREQ & CONFIG_CPU_FREQ_STAT will be enabled in the kernel to get Time Spend in Each Frequency State in 10Us(time_in_state) and Number of Total Frequency Transitions (total_trans). Since myself and most of the other people doesn't have this issue, there is no problem in the enabling-in-kernel part right.

I can only think of two problems.

1) Some app which has VDD capabilities is messing around with VDD values and cpufreq_stats driver is not able to read the values properly.

2) cpufreq_stats module (it's built into Siyah instead of being a preloaded module i believe, still....) is missing for some reason. Try and find a compatible cpufreq_stats module and insmod it.

Have you tried re-downloading 2.6.6 and reflashing? May be you should remove all CPU Tuning apps (setcpu, VC, No frills, etc etc and even cpuspy), reflash the kernel and install only cpu spy first. Check if time-in-state is displayed correctly. If yes, install other tuner apps one by one and find the culprit.
[Galaxy S II Original Android Development] jonamafun:
I installed CPUSpy yesterday for the first time and it was working good for a while.

Then this morning I decided to try tinkering with Voltage Control (haven't touched it for a few Siyah releases and have been running defaults). I noticed that after I started tinkering CPUSpy was no longer reporting time-in-state correctly. After a couple of hours only had 20 minutes of recorded usage.

Anyways, saved my VC settings and rebooted. Didn't touch VC after rebooting. And now CPUSpy seems to be reporting correctly.

Hope that helps.
[Galaxy S II Original Android Development] DannyDrama:
My phone is still losing power if I actually use the phone when charging. It says it's charging, but it just gets really hot and loses power. Can this be something to do with the kernel? I'm on CM7 and the latest Siyah.

It does this no matter what im doing on the phone. When not charging, there is no abnormal battery drain at all.

Anyone help? Cheers!

Sent from my GT-I9100
[Galaxy S II Original Android Development] xavihernandez:
Wanted to post something I don't wanna read more than 1600 pages but I'm pretty sure I have seen this issue and no real solution (always read something like "it's a known bug").

For those who got freezes when listening music (especially in CM7): it seems that 200MHz or less is not enough to play music smoothly especially when DSPManager is running. Then increase minimum frequency to 500MHz and there is no issue (at least I havent had a freeze for a while). Feel free to decrease minimum frequency when Music is not playing or keep minimum frequency at 500MHz.

Hope it helps people who had not the solution yet.
[Galaxy S II Original Android Development] jaher:
So far the siyah kernel isnt that good. Im moderatly to heavy using the phone i expect it should last a solid day. Is my version incompatible with some roms (2.6.6 with wicked rom) are older builds more stable with this rom (as some ppl use older builds abd say its very stable and good battery life) ??
[Galaxy S II Original Android Development] Simba501:
Maybe someone else will chime in on your rom inquiry, but there are A LOT of tweaks available. The kernel is what you make it; tune it to your liking. It took me a while to find a combination of settings that work well for me.
[Galaxy S II Original Android Development] pikachu01:
I put 0 in all of them so that ondemand scales to the highest. It's still not as smooth. Wish gokhan can revert it to its default behaviour. :/
[Galaxy S II Original Android Development] jdonk:
Holy ****, 80 posts already. Anyways, have you tried another kernel and had better results? As stated there's a lot you can do to tweak this kernel. I've stopped tweaking for quite awhile now and have great battery life/performance. Ondemandx and sio are working well right now.

I easily get a solid day, usually more, with this kernel. Have you tried better battery stats or cpu spy to see what your phones been doing?
[Galaxy S II Original Android Development] ka2uki:
hi pikachu ..how can i set this setting :

"

#smooth scaling parameters

echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target

echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_offset

echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_step

"

when i use root explorer set smooth_target to 0 ,and save it..but when i reboot my phone ..it go back to 2~

thank you~
[Galaxy S II Original Android Development] pikachu01:
You might have some other scripts that are reverting the value to 2.
[Galaxy S II Original Android Development] droidphile:
That's because 2 2 2 is the kernel default. If you want settings to stick on boot, you have to put the lines in an init.d script.

Your settings of 0 2 2 will cause governor to jump CPU to 2 levels above current frequency before jumping to a frequency above that.
[Galaxy S II Original Android Development] pikachu01:
Oops, thought he created a script for it using Root Explorer >.<
[Galaxy S II Original Android Development] jacky.toh:
Anyone having problem with connecting with bluetooth mouse with using Siyah 2.6.6?
[Galaxy S II Original Android Development] wurzelsepp3:
It's not only Siyah, bluetooth hid devices are not working on KK5 and custom kernels. CF root is as far as I know the only Kernel that works.

Has anybody testet bluetooth mice on the newset firmware jw1 yet?
[Galaxy S II Original Android Development] ka2uki:
thank you~:D
[Galaxy S II Original Android Development] mcarans:
SiyahKernel v2.6.6i changelog says:

"ondemand governor is merged with ondemandx and intellidemand governors. use this for having better battery life."

Thunderbolt! changes some ondemand parameters. Will Thunderbolt! undo the changes that Gokhan is putting into v2.6.6i's ondemand governor?
[Galaxy S II Original Android Development] DreddJudge:
This is weird. I updated to 2.6.6 and my phone would not wake up and it was overheating badly! (Could hardly touch the phone) Reverted to 2.6.5 and all is fine?
[Galaxy S II Original Android Development] PedroMRP:
gokhanmoral when you release v2.6.6i can you tell us the values of the hotplug parameters and the ondemandx?
[Galaxy S II Original Android Development] tolis626:
I redownloaded and reflashed 2.6.6 and everything is ok until now.However,everything was ok before with 2.6.6,but the "problem" suddenly reappeared.I'll see if it happens again.Thanks anyway man. :)

He doesn't have to tell you.You can find out yourself easily.Just run in a terminal window(or GScript,or Script Manager,or via adb) the following command:

cat /sys/module/pm_hotplug/parameters/loadX,where X= :

-h,threshold for enabling the second core core when screen is on

-l,threshold for disabling the second core core when screen is on

-h_scroff,threshold for enabling the second core core when screen is off

-l_scroff,threshold for disabling the second core core when screen is off
[Galaxy S II Original Android Development] PedroMRP:
I know that is just to avoid have to do that to change my script if gokhanmoral tweaks are more battery friendly :P
[Galaxy S II Original Android Development] xysonata:
I need a copy of version 2.5.1 since the newer versions starting from 2.5.2 aren't working for me (black horizontal lines showing on my screen) :( I still don't know what tweaks my phone are hating.

Can anyone please upload it for me? Thanks!
[Galaxy S II Original Android Development] armanderli:
You shall send it to repair...there is no such issue...besides your screen getting hammered....

Armanderli
[Galaxy S II Original Android Development] droidphile:
That's because of the hardware limitation of your device which can not handle min_gamma=0. This issue has been discussed in the thread already. "Advanced Search" under "Search this Thread" can do wonders. :)

Try this in your init.d script.

echo "30" > /sys/class/misc/brightness_curve/min_bl

echo "1" > /sys/class/misc/brightness_curve/min_gamma

echo "24" > /sys/class/misc/brightness_curve/max_gamma

If the problem is still there, try min_gamma=2.

It's not 'cool' to re-upload a release that the author has already removed.
[Galaxy S II Original Android Development] cmd512:
100% agreed. This is the same with stock ROM + Equalizer + PowerAMP... if you do not up the "screen off min step" for Lulzactive to at least 500MHz, you will get skips during playback.
[Galaxy S II Original Android Development] pikachu01:
If I'm not mistaken, it's due to this setting:

/sys/class/misc/brightness_curve/min_gamma

Try creating a script with this:

echo 1 > /sys/class/misc/brightness_curve/min_gamma;

See if it fixes it.
[Galaxy S II Original Android Development] xysonata:
I don't have the min_gamma setting under that folder. Should I still continue creating that script?

EDIT: Is it possible that something different is causing this? I don't have this folder on kernels like NEAK and I still have the black lines on the latest version. But when I use stock, void.echo, siyah 2.5.2b(and below), and the older NEAK kernels, those black vertical lines aren't appearing.

Could it possibly be that anything that NEAK 1.3x and Siyah 2.5.2(and above) have in common that's causing me this issue?
[Galaxy S II Original Android Development] droidphile:
Did you even read my reply in the last page properly?
[Galaxy S II Original Android Development] xysonata:
Sorry, sorry. I didn't see that post. I'll try doing that. Thank you
[Galaxy S II Original Android Development] xavihernandez:
Okay good to know that too. Then even Samsung has failed? Lmao. Anyways it is working now (I'm using ondemandx governor, I increase frequency with SetCPU anytime I want to play music).
[Galaxy S II Original Android Development] Shubbis:
This might already be covered, but i read a few pages back..

There is definitely a problem with sleep/powersaving/whatever-its-called with 2.6.6.

I always take my phone of the charger at 100% in the morning, and don't charge it again before the end of the night. With 2.6.4 i would be at about 70-80% in the middle of the day, depending on usage. When i switched to 2.6.6 i was as low as 40% by lunch. I switched back to 2.6.4 and battery was much better immediately.

I've flashed 2.6.6 and 2.6.4 a couple of times now to test, and I've flashed cleaning kernels and deleted cache/dalvik every time, but the behavior persists.

Needless to say, I'm sticking to 2.6.4 (!) :p

Besides that, awesome kernel guys.

Shub
[Galaxy S II Original Android Development] pikachu01:
What governor are you using? Try using Ondemand/OndemandX instead.
[Galaxy S II Original Android Development] Mr.Greg:
Guys, I can`t find version 2.6.4, I tried on this site http://www.gokhanmoral.com/ but said "Page not found". Any help much appreciate.
[Galaxy S II Original Android Development] veyka:
There was a nasty bug in it and all older releases so they have been removed.
[Galaxy S II Original Android Development] :
Here you go guys some battery results with latest siyah kernel and using ondemandx governor and sio scheduler. Still not the best results i had with previous versions but still good enough to last me a whole day without charging
[Galaxy S II Original Android Development] xysonata:
Okay... I've already tried making a script that changes the min_gamma to 2 and it didn't work.

I've been googling about this for days and all I've been seeing are posts about vertical lines. (I'm not entirely sure if I'm putting the right keywords) Mine are horizontal and it goes from one end to the other. It's very visible on the camera screen, grey backgrounds and other light backgrounds.

Do you think there's a different cause to this?
[Galaxy S II Original Android Development] seaweeduk:
10 hours use 36% battery, I'm using ondemand not having much luck with this kernel will try ondemandx again tomorrow maybe. Using an anker 1900mah battery display brightness on the lowest setting. Was seeing around 36hours battery life on 2.6.4.

I'm sure the problems will be resolved soon 2.6.4 was an awesome release for me.
[Galaxy S II Original Android Development] :
use ondemandx as im to scared to use lulzactive as it seemed quite aggressive even though wen scrolling through it was diamond to have..i get the same with ondemandx and well you can see results above...but i think the best time to judge the kernel on battery life is after a few charge cycles...cause my phone settles after a few hours and well you could see my results above with stock battery....
[Galaxy S II Original Android Development] cmd512:
No problem, gave you Thanks as well. I thought it was the deep sleep frequency at first, but it was actually the min under lulzactive governor (which is the one I use).
[Galaxy S II Original Android Development] Holgott:
I got second sod in two days without touching the system ...now even with ondemand govenor ..waiting for the next release to fix something on it ..
[Galaxy S II Original Android Development] cmd512:
Are you undervolting? If so, you're probably undervolting too much.

Btw gokhan, I've noticed this odd behavior on v2.6.6 that I've never experienced on any previous siyah releases: On lulz, when I come out of screen off/deep sleep, the frequency sticks to 500MHz sometimes. This is obviously noticeable in that the phone is very choppy and slow. Sometimes, it snaps out of this state and goes back to scaling properly between 200-1400. Other times, it just sticks to 500MHz, and the only way to get rid of that state is to cycle screen off and screen back on.

Now, my deep_sleep and screen_off_min_step for lulz are both set to level 5, which is 500MHz. Could some of the changes you made to lulzactive in v2.6.6 be causing it to not completely kick out of deep sleep frequency? Again, this has never happened with 2.6.5 or previous releases. Thanks!
[Galaxy S II Original Android Development] Auridran:
I don't know if it's something I'm doing incorrectly, but in 2.6.6, I've noticed Lulzactive gets stuck at 1400MHz very frequently, even while the phone is doing nothing. Conservative/Ondemand will scale between 100-200 (and rarely 500) under the very same circumstances.
[Galaxy S II Original Android Development] cmd512:
Already addressed. Gokhan tweaked the lulzactive behavior a bit for v2.6.6 to slow down the throttle down behavior given people were getting lag in their app drawers, youtube, etc. However, the side-effect was that sometimes it was slow to throttle down... and other times, it would just sit at max frequency for minutes.

This will be addressed in v2.6.6i.
[Galaxy S II Original Android Development] Holgott:
I just uvted 200mhz state by 25mv ..this wasnt a problem in all previous version. Performancewise this kernel is rly awesome, but these sods and lulz frequency issue is kind of ****ty :-(
[Galaxy S II Original Android Development] poochewer:
---------- Post added at 09:20 PM ---------- Previous post was at 09:07 PM ----------

[/COLOR]

I probably should do some more thread searching, but could you please tell me what the "nasty bug" was that was in 2.6.4 ?
[Galaxy S II Original Android Development] N6666661:
Maybe it has been asked before but what does "Siyah" means?
[Galaxy S II Original Android Development] poochewer:
I think you meant to say, "its fun to bugger around with scripts, and SPOOF !!!"

(not "stoof") LOL LOL LOL:D

---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------

As far as I know, its the strong part on the 2 ends of a bow ( as in bow & arrow)

traditionally made of animal horn or bone, where the string is attatched.
[Galaxy S II Original Android Development] thunderteaser:
Data Loss?

Hi guys! I have a weird problem: apps are disappearing.

After some searching I found out that there were a copies (backup?) of the same apks in /sdcard/download, while the /data/app ones changed their size to 0 KiB (Android Applications Manager sees them with 0 KiB, no icon, reads the name as com.name.domain, but it can't delete data). It seems it's not a MIUI specific issue; I've been searching for days and no one seems to have had the problem I'm experiencing. Do you have any clue on what's going on?

Is this some sort of data loss? This thing is really annoying, I have to redownload the same app from the market over and over again!

Thank you very much in advance! :)
[Galaxy S II Original Android Development] N6666661:
Thanks!

Maybe will we have the confirmation from gokhanmoral?:D
[Galaxy S II Original Android Development] veyka:
The interactive governor was spitting out threads even when it wasnt in use causing hung tasks and stuff.

I meant stoof, its a stupid way of saying stuff ;)
[Galaxy S II Original Android Development] :
I really hope this change isn't introducing a screen off CPU frequency limitation to the ondemand governor by default.
[Galaxy S II Original Android Development] VFO:
Gokhan, what does the changes in wifi and the addition of the white list effect? The reason I ask is even though this kernel works excellent on my phone with great battery life at home using my home wifi, this is not the case at work. For some reason the last few releases have caused me horrible battery drain when using wifi at work. It is a corporate wifi network and is the only means I have to get online while there. When connected to this network my phone never goes into deep sleep.

This has never happened before until the last few releases with the changes in wifi. I love the kernel and would love to keep using 2.6.6 but where I am at work the better part of the day I have found my self flashing 2.6.2 during the week and then flashing 2.6.6 when the weekend comes. Would you have any ideas?
[Galaxy S II Original Android Development] AndreiLux:
No, siyah means "black" in turkish, basically this is the "BlackKernel / DarkKernel" :)
[Galaxy S II Original Android Development] incubus_fr:
Even if it is the case, you can set the screen off max frequency in ondemandx. So set it to match the screen on one and voila!
[Galaxy S II Original Android Development] AndreiLux:
It does, 500MHz, why are you against it?
[Galaxy S II Original Android Development] AMDPOWERFIST:
Quick question about Siyah v2.6.6

With the default stock Siyah v2.6.6 does it come with any UV / OC settings?

Does the default stock Siyah v2.6.6 come with an enhanced charging capabilities?

Or are both of these settings manually entered via scripts / applications?

Also: Handcent SMS & BLN.... I am having issues with it not working all the time. I have already searched the forums for answers and tried the following:

* Switching LED colour to white

* Switching blink mode from "default" to "normal"

* Turning off Trackball lighting

* Purchasing the full pro version

* Resetting BLN status

no luck so far....

Thanks in advance.
[Galaxy S II Original Android Development] Codex0:
2.6.6i changelog is up :) hoping to see a dl link soon
[Galaxy S II Original Android Development] Vaedryn:
Changelog is up since 12 hours :p

Cyanogen Mod Tapatalk
[Galaxy S II Original Android Development] Codex0:
Silly me, must have been looking at a cached one this morning >_<
[Galaxy S II Original Android Development] kbnguy:
From your sig, I assumed that you're still on CheckRom.

Launch KitchenPro then -> tab "mods" choose "BLN (work also with stock mms)".

What you're missing is the right Services.jar to get BLN to work.

Good luck.
[Galaxy S II Original Android Development] olifee:
I guess he is also using his phone with screen off sometimes (as I am doing, too) ;).

Actually, I often access it via ssh, transfer files via rsync (with compression) and run rtorrent and pyload on it when on wifi. This might hog on CPU (and battery of course) a lot. But as this is not really 'normal' usage, I am totally fine with the change, it should increase battery-life in all real-world use cases.

And for us ssh'ers, the 'fix' is simple as incubus_fr pointed out above.
[Galaxy S II Original Android Development] chiggah:
whats the best settings for me ? I dont really know what frequency I should be tweaking to.

I am a light user and want the best battery life aiming for 3-4 days. Only apps I have are facebook, talkbox and whatsapp. Dont really use anything else

Trying sio scheduler with ondemandx
[Galaxy S II Original Android Development] stevehkim:
3-4 days? i dont know if thats possible.??? maybe. do you not have access to a charger? you would probably have to underclock your device to max 1 ghz.

tweaked - by me

kernel - siyah the og

rom- me you eeee.
[Galaxy S II Original Android Development] veyka:
3 days idle is doable, but facebook and whatsapp are both huge battery eaters!

Your best bet is to underclock your phone and not fiddle with it to much if you want that much battery life
[Galaxy S II Original Android Development] chiggah:
done 3.5 days without much touching on villainrom 2.5 and siyah before

I turn off notifications and sync on facebook
[Galaxy S II Original Android Development] veyka:
You should be fine without to much tweaking then, I would update to 2.6.6i when its released and use lulzactive as its supposed to be good at battery saving.
[Galaxy S II Original Android Development] chiggah:
right now on sio ondemandx 200min 1200 max - reckon i should drop it down to 800 max ? Will decreasing the min/max help with battery life ?
[Galaxy S II Original Android Development] veyka:
Try 200-1000, performance should be good and might save some battery.

But to be honest idle power consumption is great, just make sure theres no wakelocks keeping your phone awake (use better battery stats to make sure nothings keeping it awake, link in my sig)
[Galaxy S II Original Android Development] chiggah:
I also have a habit of turning on my phone to check whatsapp or facebook for like 20 seconds then turning back off, eventhough i know i did not receive any messages

Will ondemandx suit me if I do that often ?
[Galaxy S II Original Android Development] omniwolf:
BLN will suit you better. you won't have to turn the phone on at all. there is no governor that will "suit" turning the phone on all the time. all you're doing is keeping it out of deep sleep.
[Galaxy S II Original Android Development] cmd512:
I can't believe you actually answered that question, lol.
[Galaxy S II Original Android Development] bala_gamer:
is there anything wrong with siyah 2.6.6 cwm package, whenever i flash it i dont even get the recovery mode, have to flash the tar via odin.
[Galaxy S II Original Android Development] jonamafun:
I've found Facebook notifications can be a bit of a battery drainer. Even after turning off notifications I was still seeing wakelocks. For now I've frozen the official Facebook app and I'm now trying FBM as a replacement.

You can also try Easy Battery Saver from the Market. On ‘Normal’ power saving mode, it will disable your 3G data connection when the screen is off and automatically re-activate it when you turn it back on. If you are the type of person that checks apps on a regular basis instead of using push notifications, then this could be ideal and save a good deal of battery.

Also check to see what widgets you have. I found my Calendar widgets were syncing far too often for my liking, causing wakelocks under the GTALK group.
[Galaxy S II Original Android Development] cmd512:
Fix for calendar wakelocks: http://xdaforums.com/showthread.php?t=1383929

Confirmed it works. I never get wakelocks from calendar alerts anymore whereas that would drain my battery the most previously.

Facebook is ok, you just want to have it sync at something higher than 1 hour intervals.
[Galaxy S II Original Android Development] blaex:
i had noticed that the battery drain was around 5-7% in 10 minutes with sio/ondemandx (100-1200mhz) while surfing with opera web browser on wifi.

as i turned the gpu to 133mhz and 900mw it drops to 3-4% in ~ 10 minutes.

the "new" mali drivers drains a lot with stock settings on sgs2 :-(

or could it be a xxkk5 (checkrom hd 4.0) rom related problem, anyone noticed the same on other rom-builds? i think its the rom whos having some battery issues on custom kernels.
[Galaxy S II Original Android Development] cmd512:
Not sure, I'm on 30 secs myself lol. I wait for the phone to finish booting up and loading everything before messing with it anyway, I got a few seconds to spare. :p