yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] droidphile:
@All who are experiencing any weird wild battery drain without any warning. Examples include:

1) After a reboot battery dropped to 20% from 40%.

2) After performing a nandroid backup and reboot, battery 'drained' so much.

3) Percentage was 72, then it shows 73 then again 72, all funny values.

Fuel gauge misinterpreting actual reading and displaying funny values can mostly be solved by resetting the gauge chip.(The drain i'm talking about is only bad reading by gauge because of sudden heavy load. Drain caused by userland wakelocks, forgetting to turn off GPS, etc can not be solved by the following).

Fuel gauge reset signal, only i9100: [Thanks to Entropy512]

echo "1" > /sys/devices/platform/i2c-gpio.9/i2c-9/9-0036/power_supply/fuelgauge/fg_reset_soc

After the reset, you may have to give it a few more hours for gauge to report proper values. All should be well after that.

PS: If anyone can find a shorter symbolic link to fg_reset_soc in sysfs, please tell me!!
[Galaxy S II Original Android Development] liamR:
You were right it's only happening with ondemand governor. I switched to conservative for now... Thanks!

Sent from outta space.
[Galaxy S II Original Android Development] hausmanis:
thx alot and it should be easy doing that, dunno wtf im doing wrong, but thx alot for that, such a complete script!
[Galaxy S II Original Android Development] islander999:
i have just installed the Siyah v2.6.11 on the yakkas ROM v5. From the reboot i had 99% battery life...now wich is 4hours later or a little bit more, i still have 96% of the battery (of course i didn't have to use the phone too much). Just to give another point of view...does'it help maybe?
[Galaxy S II Original Android Development] CamoGeko:
I think you're going to have to make yourself a bit clearer mate...."does it help your battery if you use your phone"? (that really doesn't make much sense in english lol)
[Galaxy S II Original Android Development] stevehkim:
question guys, im doing my own little test and im back on siyah 2.6.1. was wondering if 2.6.1 will allow gpu settings of 40, 166, 267 as well as hot plug parameters. TIA.

My remix:

EM EYE YOU EYE

SIYAH nara to the rest, I'm rollin with the best.

SGS2 I777
[Galaxy S II Original Android Development] lpsi2000:
Last time I checked there is no custom kernel for ICS yet. Everyone is waiting for source code

I think you might have missed the part of this kernel and ICS ROM, unless you are using it with an ICS ROM.
[Galaxy S II Original Android Development] mundixx:
Sorry for the noobish question. But how do i apply that fg_reset_soc code?

Sent from my GT-I9100
[Galaxy S II Original Android Development] stevehkim:
Sorry guys quick question. I want to run my device at 1504 mhz. What would be valid frequency steps starting from min to max 1504?
[Galaxy S II Original Android Development] veyka:
Download a terminal editor, copy paste or type that in, if it says permission denied type su then that command.
[Galaxy S II Original Android Development] :
Check few posts back and you will see that i have advised someone that the kernel does not work on ICS roms as no sources out yet. Plus how did you get ICS rom when i said i am using Go Launcher:confused:

But anyway i am more than happy with the kernel and for me every new release outdoes the old one:)
[Galaxy S II Original Android Development] stevehkim:
got it. 1.5 ghz's in it. running smooth.

Siyah OC'd to 1.5 ghz.

SGS2 I777
[Galaxy S II Original Android Development] poochewer:
Well beleive it or not I have gone back to 2.4.2 and I must say say it is absolutely marvelous for me on my phone. Very nippy on speed and sleeps very well and seems to have the best battery life of all!

I really appreciate the effort that gokh has put into all these new innovative kernel releases, but I have to use what works best for me on my phone and at the moment on 2.4.2 I'm over the moon.;)
[Galaxy S II Original Android Development] stevehkim:
i feel ya brothas. i myself am using 2.6.1 as that release is my bread and butter. but all the new releases have been fantastic. smooth stable and fast. just my phone seems to hold its heart to 2.6.1.

Siyah OC'd to 1.5 ghz.

SGS2 I777
[Galaxy S II Original Android Development] Simba501:
Ha, yeah. I'm on 2.6.9, which is the best for me. I'll probably sit on that version for the duration.

On another note, I see you're OC'd to 1.5; what voltage are you running it at.
[Galaxy S II Original Android Development] :
@gokhan

Ever thought about adding a commenting funktion on your page? People could tell directly, how they feel about every build and inform you about bugs, stuff that was better in former kernels and what they think about the new functions you added.

Think about it, it would be way clearer than in here, where everything gets mixed up, because this thread is for all versions ;)
[Galaxy S II Original Android Development] poochewer:
That is a TOP idea! I supose every bit of feedback can only help.
[Galaxy S II Original Android Development] veyka:
But then he would have two places to look, and generally feedback should list the kernel version anyway.
[Galaxy S II Original Android Development] gokhanmoral:
I thought about it but I did not enable comments for two reasons:

- there are a lot of spammers and spam prevention is not easy

- it is hard to follow more than one place for me. that is why I had to say "thank you but I don't have time for that. please help me translating to turkish and re-publish them" to some of my turkish friends.

by the way, those "x.y.z version was better because..." comments are useful for me. I always compare the current version with those versions and try to see if there is really a big change which can cause it.
[Galaxy S II Original Android Development] stevehkim:
I have it set to 1400 mv at the moment. and 1304 mhz at 1300 mv's. It's been a few hours running it like this with a few quadrants and antutu's to see if it's stable. Gonna lower another -25 mv's in a few.
[Galaxy S II Original Android Development] Mutalisk:
Ok, thanks to Entropy I know now that my idea of collecting governor modules most probably wouldn't work. Thanks ;)

I hate to do that, but then I have a feature request. I stayed some days on Redpill-kernel (to lazy to reflash Siyah) and I noticed that Sleepy governor fits my needs almost perfectly.

Sleepy is an Ondemand based governor called the way it is "because it loves to idle" and really, it's hardly upscaling randomly and deepsleep also seemed a tad bit better than our already very good ondemand (not sure if that was governor related though) while I didn't notice performance penalties in my use, any opinion about implementing it?

Of course your other projects (work, app etc.) are more important, and I'm still very curious about your Darthvader though, gokhan ;)

Thanks!
[Galaxy S II Original Android Development] Phelicks:
How could I undervolt screen from 3,0 down to 2,5V?
[Galaxy S II Original Android Development] tolis626:
Well,you can try upping your powersave bias in ondemand's settings in SetCPU,or do it with an init.d script command.I suppose that you'll achieve the same effect more or less.
[Galaxy S II Original Android Development] Mutalisk:
Thanks a lot Tolis!

Tried that, result is better but not the same unfortunately.

In the end I'd prefer Sleepy, but I can't really compare the difference battery wise as they're not in the same kernel of course, and even though the Androidmeda guys did it, I'm not sure if the difference would be enough for gokhan to implement it in siyah as an extra governor.

(placebo?! :D))

Just an idea ;)
[Galaxy S II Original Android Development] tolis626:
How can you actually say it's not the same?It might be ondemand with any value between 1 and 1000 in powersave bias and the four other settings.Come on dude,it's more like placebo did its job here,admit it. :p
[Galaxy S II Original Android Development] OisteinR:
I've been using this kernel for a looong time, and it's fantastic. Something strange started to happen some time ago, but I don't remember exactly when...

I'm using Ondemand governor, moderate UV no OC. 100-1200

One or two times a day my governor changes to Lulzactive..

I'm using VC and I have no scripts in init.d

What else can make this sudden change?
[Galaxy S II Original Android Development] Mutalisk:
I can actually say it's not the same because I compared them ;P :D sleepy and our ondemand have some different files in system/cpu/cpufreq/governor_name ;)

Your turn :D
[Galaxy S II Original Android Development] xuxuzao:
hey man,

i am having some sod's with your settings

iam running miui + siyah + thunderbolt without screenstate

i've changed the maxfreq to 1000 and min to 200

also checked the voltages cuz yours were to low for my phone and even with stock voltages i get sod

any tips?

tks!!
[Galaxy S II Original Android Development] lpsi2000:
Only because you quoted / responded to the post asking for kernel battery performance against an ICS ROM, take a look at your response.
[Galaxy S II Original Android Development] Entropy512:
Hmm, have more details on this? It sounds almost like it is similar in concept to Wheatley, taking time in idle states into account.
[Galaxy S II Original Android Development] Mutalisk:
I'll reflash asap.

I guess you could read the sources for hyperdroid kernel in github, there sleepy was implemented as well (called solo if I remember right), i'm not at my computer, so I can't give you the link that quick.

I'll reflash and see what I can see there :)

I do not know a lot more, provide more info as soon as I can.

Thanks :)

---------- Post added at 11:57 PM ---------- Previous post was at 11:36 PM ----------

Ok, I can't find out how it exactly works, it doesn't have a down_threshold in CPU/CPUfreq/sleepy but a deep_sleep and a fast_start.

i'm a noob, can't tell you more than pongster created it.

i'm sorry if placebo was too strong :D

I can't prove my feeling but I think sleepy is a good governor :)

Good night everybody.
[Galaxy S II Original Android Development] Entropy512:
I'll look into that. I know that a governor that accounts for deep sleep states will likely avoid 100 MHz operation in most cases - that's why I don't even have 100 MHz support in my own kernel.

I disagree with Ezekeel's approach for Wheatley, but another governor that takes into account idle states could be interesting.

Edit: I'm not finding any "sleepy" governor in the HyperDroid repo or Pongster's personal repo. (Oh, it's called solo there - will look...)
[Galaxy S II Original Android Development] :
Entropy question for you please mate..What do you think of SavagedZen governor?
[Galaxy S II Original Android Development] PedroMRP:
If that governor can really save battery (without compromising smoothness) in a way that we can't reproduce by tweaking the Siyah's ondemand governor I think that it would be a nice addition to the kernel.
[Galaxy S II Original Android Development] PedroMRP:
I found the sleepy governor by looking into the commit changelog.
[Galaxy S II Original Android Development] Entropy512:
If you read my kernel thread over in I777-land, you'll see that in general, I am not a fan of alternative governors in most cases, especially ones that have wacky names not even remotely descriptive of what they do. It's been shown that small optimizations to existing governors usually gets you better results with fewer buggy corner cases.

Look at "lionheart" for example - the only good thing to come out of that hype was definitive proof for users that small tweaks to conservative can make it an excellent and flexible governor. (Unfortunately, many are still drinking the kool-aid, even though it has been proven that lionheart is nothing more than conservative with its minimum polling rate reduced. FYI, nearly every available I9100 kernel has this simple change and has had it for a while now.)

The one exception where I am very interested in alternative governors are ones where deep idle states are taken into account for governor decisions. This is a novel concept not implemented in current governors (except arighi's modifications to ondemand and Wheatley - it looks like sleepy is heavily based on arighi's ondemand patches), and if done properly, can provide benefits in power consumption. The problem is that, unfortunately, determining the optimal tuning for such a governor is HIGHLY dependent on the CPU architecture - Wheatley will without any doubt not work as designed on most I9100 kernels, for example, due to AFTR and LPA getting lumped into a single deep idle state.

Edit: I did find sleepy eventually, it was in a less obvious branch. It's kind of vague at this point which repo is even the HDK repo, there's one on bitbucket and one on github... It looks like it is only tracking general idle time, not deep idle time. See my above comment about Wheatley.
[Galaxy S II Original Android Development] remorema:
hey gokhan. any news on bt mice and keyboard fix?

Tapatalked from "The ICS Killer"
[Galaxy S II Original Android Development] :
Cheers thanks for your reply. Much appreciated. Looks like more reading to do then.
[Galaxy S II Original Android Development] Entropy512:
I think I found a candidate fix for BTHID, we got lucky that Samsung keeps ****ing up the Epic 4G Touch and re-releasing source code drops as they keep fixing all the stuff they broke. :)

I am now 100% positive that Samsung is not GPL compliant with I9100 kernels, if any of them are working with newer bases.

I probably would've found this earlier if they hadn't really screwed up with AT&T UCKK6 - that build needs the fix but doesn't have it in the stock kernel!

I'm giving it more testing now, if it continues to work and doesn't blow up I'll link GM to the patch (haven't released it or pushed it to github quite yet - just testing it on my own device until tomorrow.)
[Galaxy S II Original Android Development] omniwolf:
i'm using neither - i'm not UV'ing or OC'ing. I have no boot settings (except the GPU stuff, but as already mentioned i was getting SODs before adding this)
[Galaxy S II Original Android Development] UpInTheAir:
Maybe the simplest thing;

Clear scripts and reflash the kernel?
[Galaxy S II Original Android Development] sansunggalaxys2:
Would be cool even though i wouldn't use it
[Galaxy S II Original Android Development] chiggah:
do you guys use bfq (default) or sio ?
[Galaxy S II Original Android Development] zaphod777:
yes it will change the boot animation
[Galaxy S II Original Android Development] theory_87:
Gokhanmoral, can look into why I can't set the sampling rate in setcpu? I can't set with both 1.7.7 and 1.7.8 beta4. I can set and apply but it will revert to default value after awhile. Didn't try other version kernels before so I'm not sure if it working on those.

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] lupos89:
No it will not!!! ;)

Sent from my GT-I9100
[Galaxy S II Original Android Development] incubus_fr:
Same for me using beta2 and ondemand governor.
[Galaxy S II Original Android Development] Rayids:
I am trying to flash the kernel via Odin... But it keeps getting stuck at zImage and now my phone won't even boot or enter Recovery, When I am trying to enter recovery it just flashes back to the Boot screen with the triangle and gets stuck, any help?
[Galaxy S II Original Android Development] tripc1:
try get your phone into Download mode (HOME+POWER+VOL-DOWN)

if that doesn't work try to use JIG

then try to use other kernel
[Galaxy S II Original Android Development] zaphod777:
opps I got my threads mixed up ;)
[Galaxy S II Original Android Development] ebliss:
I just got the screen being unresponsive. had just installed an app via Amazon appstore. after restart, it's back to normal.
[Galaxy S II Original Android Development] beppez82:
Got reboot on b4 too after market update and also random while in sleep, deep sleep perfect os usage very low also on b4 for me great kernel need to improve stability btw

Sended from my SGS2
[Galaxy S II Original Android Development] jmblazquezh:
But SU 2.3.6.1 does not show the message "xxxxxx has granted superuser permissions" with the applications that has su permissions.

Regards
[Galaxy S II Original Android Development] jimmy72:
setcpu and su

Hi all

For people who had issues with setcpu and su. You can try this method :

launch set CPU enter your settings and voltage ... tick use at boot. Quit setcpu. Install fixpermission from the market

in fixpermission force permission on setcpu.

And SHUTDOWN COMPLETLY your phone. Then boot in recovery go to advanced and fix permission it will take 2 to 3 minutes. Reboot your phone.

After booting watch if setcpu get su permission. If yes all is ok. If not open setcpu and apply your settings. And SHUTDOWN COMPLETLY again. Wait 1 minute and boot your phone.

It would be ok.

I got same issues with setcpu with 1.7.8 and. 1.7.8. 4b now with this method at each boot setcpu got su permission and keep settings. The important point is to set your settings and completely shutdown your phone. After a boot setcpu will keep your settings and get su permissions
[Galaxy S II Original Android Development] gokhanmoral:
I have uploaded beta5.

I have changed the rooting method again. I have been trying several different roms (more than 5 in last 2 days) and there are some weird behaviors...this method seems to work fine but even if you have superuser/root problems please install su package in CWM (link is in the first post)

sometimes rebooting once more or clearing dalvik cache helps.. try it before reporting a problem.

I think I will clear dalvik cache and reboot after installing root in the final version.

there are some changes in cpu scaling.. I hope this version is more stable.
[Galaxy S II Original Android Development] cez10:
Kept having same issues all night last night, unfortunately don't have an access to a pc to odin flash other kernel :-( so for now I won't use set cpu and UV profiles... I'm on 1.7.7
[Galaxy S II Original Android Development] gokhanmoral:
you don't need pc to flash.

use darkyrom2 tool from the market.

or cwm manager...
[Galaxy S II Original Android Development] cez10:
To flash a tar file?

/e true lol didn't notice it was available thru cwm

Thanks :-)
[Galaxy S II Original Android Development] gokhanmoral:
available through cwm manager not cwm :)

I mean the app.

there is an option to flash kernel. you select the tar file.

or better, use darkyrom2 tool. if you select zip it reboots and installs it through cwm, if the file is tar it detects if the file is modem or zip and flashes automatically.
[Galaxy S II Original Android Development] jsompis:
@gokhanmoral

I don't know what you do in b5, but deep sleep come back again.:D
[Galaxy S II Original Android Development] cez10:
Yes thanks :-) will try the beta now
[Galaxy S II Original Android Development] cbeckstein:
moved from 1.7.8b4 (with Superuser 3.0) to this one and no problems so far (Superuser 3.0 included)

looks good -- thank you!
[Galaxy S II Original Android Development] iakovl:
I have a small problem, flashed 1.7.7 and cris v22.

The phone freezes an reboots fron time to time, is it the kernel or the rom?
[Galaxy S II Original Android Development] shawnaye:
bfq with ondemand. If not noop with conservative.
[Galaxy S II Original Android Development] pikachu01:
The choice of governors are independent (and will not affect) the choice of I/O schedulers. :/
[Galaxy S II Original Android Development] poochewer:
using 2.4.2

Doing well!
[Galaxy S II Original Android Development] janreiviardo:
Guys, just want to share though I still need to know a lot about the kernel but I think I could help those new and would like to share it to others for testing and for their use. It is so far the best settings I have used to gain the best results for battery life.

Would like to give credits to geko95gek for the governor Match-up and for the GPU Settings. Also to Andreilux for the tweak posted by gokhan on his site. This script has been generated in vc and was just modified by me.

Summary/details of the script:

I/O: BFQ

Governor: Ondemand

CPU Range: 200-1000mhz

Voltages: 100-825, 200-850, 500- 875, 800-950, 1000-1050, 1200-1150, 1400-1250, 1600-1350

GPU Range: 114-267mhz

GPU Voltages: 800mV Low, 950mV High

GPU Tweaks by Andreilux

There are no charging current in the script as I personally believe using the default current is the safest.

If this settings will hang, feel free to up all voltage by +25 mv. Just do it though in the script.

I suggest that before you flash this script that you remove andreilux script if you have it and that you delete any boot settings done in VC. Though this script will execute later than VC Boot Settings. I still recommend just deleting them to avoid conflicts. As to GPU Settings, it will be somewhat broken in Voltage Control due to andreilux's script.

Any suggestions or feedbacks are accepted. Thank you and I hope I have somewhat contributed to the thread.

Link to Flashable zip: http://xdaforums.com/showpost.php?p=21970490&postcount=132
[Galaxy S II Original Android Development] omniwolf:
a couple of things.

first, the above GPU frequency isn't what AndreiLux recommended.

second, your script sets the GPU frequencies twice, and the final setting isn't what you said above, it is:

40 133 267

which is actually what AndreiLux recommended. I think you're a bit confused.. have another read of your script and make sure it does what you think it does. double check your settings after you have flashed the script by using cat in a console, eg to check what the current ACTUAL gpu frequency settings are, you would type:

cat /system/class/misc/gpu_clock_control/gpu_control

also, you set voltages based on a 2 step GPU, but you set it afterwards to a 3 step GPU (as above). So this won't be working as you expect either.

it's nice that you're trying to help, but it's probably a good idea if you learn how it all works before publishing things that might affect other's hardware...
[Galaxy S II Original Android Development] janreiviardo:
Like I've said I'm still new to this kernel and would have not posted this if I haven't tried it myself. I even asked my fellow friends to try it and all is good. I just compiled everything as 1 script as for what I have read in this thread basing on others posts that it is okay to use andreilux's settings on top of voltage control' boot settings. Knowing that, it have set my mind that putting it onto 1 script and just using delay to make andrei's be on top would be fine. So if ever that I have set the gpu twice. Still andrei's is what would take effect. Other than that I just putted the best UV settings my phone can handle though knowing not every phone has same capabilities in terms of this. Hence I mentioned if it would not work, just increase all voltages by 25mv. The best I could do may be is apologize for the incorrect information my original post has. Anyways, thanks for your remarks and everything's noted. Cheers
[Galaxy S II Original Android Development] XDA mark:
I see a lot of people using BFQ with ondemand. Reading the in dept guide about schedulers, I don't understand why. SIO is seen as the "best" one:

"However, considering the overall performance, battery, reliability and low latency, it is believed that SIO > Noop > Deadline > VR > BFQ > CFQ, given all schedulers are*tweaked*and the storage used is aflash device."

If anyone could explain to me why BFQ is chosen above SIO, it would be much apriciated! ;) Trying to understand what I actually do with my phone.