yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Fille84:
How much battery can you save using the AndreiLux settings? And can i use it with 2.6.7? Is there any special governor i have to use with the settings?
[Galaxy S II Original Android Development] poochewer:
It might sound like a very basic thing to say but, have you cleaned your battery contacts and simple things as such?

My wife uses lightning rom with siyah kernels and she has never had a problem.
[Galaxy S II Original Android Development] :
as far as i imagine you can use any governor of your choice. second yes i am sure you can use it with 2.6.7 and you do save battery with using the AndreiLux settings. Just try them and let us know.:)
[Galaxy S II Original Android Development] BatTusAi:
can anyone recommended version of siyah that works very well with VillainRom 3.0.. I prefer battery life..
[Galaxy S II Original Android Development] :
latest one with heavy usage i can get a day out of it.;)
[Galaxy S II Original Android Development] eladnava:
I will try that. It actually sounds like it could be the cause since it's always happening in my pocket when I walk around with it.
[Galaxy S II Original Android Development] adamski123:
Hey guys, im running checksrom, and i want to install this rom via the kitchen but everytime i try and download the kernel it says download failed:-1 and dosent download? Why is this?

Thanks :)
[Galaxy S II Original Android Development] barondebxl:
2.6.11 the latest one has the most amazing battery life on any kernel that have tried on any phone for real.
[Galaxy S II Original Android Development] veyka:
That's a kitchen issue, ask in the checkrom thread, or download from here and flash.
[Galaxy S II Original Android Development] AndroidFiber:
...

Download here www.gokhanmoral.com/ and flash thru CWM.
[Galaxy S II Original Android Development] poochewer:
I think it is different for everyone, cos I got terrible battery life with 2.6.11.

I get exellent batt life with 2.4.2.

It would not hurt to try both, it will of course take some time but its worth it to get the best for you.
[Galaxy S II Original Android Development] Entropy512:
It would be beneficial to discuss EXACTLY what battery issues you've had with 2.6.11 - If you don't give details on exactly went wrong and the situations in which it failed, and properly define "terrible", it becomes impossible to reproduce or identify the change.
[Galaxy S II Original Android Development] adamski123:
I tried downloading it but it says download failed: this content is not supported on your phone... :L

Any ideas?
[Galaxy S II Original Android Development] poochewer:
Yes I realise what you are saying is correct, but I am actually not complaining about the latest kernel, I am very happy with 2.4.2. I was just reporting my experiences to these guys:

originally Posted by BatTusAi

can anyone recommended version of siyah that works very well with VillainRom 3.0.. I prefer battery life..

2.6.11 the latest one has the most amazing battery life on any kernel that have tried on any phone for real.
[Galaxy S II Original Android Development] :
if you are trying to download old version of siyah GM has removed all links
[Galaxy S II Original Android Development] PedroMRP:
I think is nice people returning to a version of the kernel that its good to their phone but if everyone do that and don't report the problems that they have with new versions it's hard to gokhanmoral fix those problems.

When flashing a new kernel and if you have problems with it report the problem with details.

Not saying this to you but to every user that try a new version and go back to older versions and do not report the problem that they have.
[Galaxy S II Original Android Development] marioh:
Hi guys. I have 2.6.11 with Thunderbolt script, geeko settings CPU UC to 1000mhz and GPU UC to 200.

This is my battery situation (2000mah Samsung genuine battery):

After 24 huors with:

Wi-Fi ON 14 hrs

Awake 4,5 hrs

Screen On 2 hrs

Phone calls 15 min

5 sms

3 gmail push + 3 other accounts push + 1 Exchange account push

Facebook update every 1 hour

Viber - Gtalk - Whatsapp - always connected

I have 47% battery left.

Do you think it's good, or could I make better?
[Galaxy S II Original Android Development] adamski123:
Panic over i just downloaded it using maxithon browser and flashed ad per normal :) im hoping this kernel has amazing battery life
[Galaxy S II Original Android Development] :
for me it never disappoints.:D
[Galaxy S II Original Android Development] poochewer:
Originally Posted by Suarez7

if you are trying to download old version of siyah GM has removed all links
[Galaxy S II Original Android Development] fransarj:
I've found the settings and set my GPU control w/ the ff settings:

Low power state: 400mhz 1200mv

High perf stat: 400mhz 1200mv

but my Antutu 3D benchmark results remain the same as the 267mhz default. why is this?
[Galaxy S II Original Android Development] wurzelsepp3:
Because the GS2 is limited to a maximum of 60fps.

Use a real graphics Benchmark like "Basemark Taiji" and you will see a difference.
[Galaxy S II Original Android Development] omniwolf:
good question, i'll try next time i have one (but since i downgraded to 2.6.9 i've had no SODs... i'll give it another few days before i declare that 2.6.9 is the solution, though).
[Galaxy S II Original Android Development] BatTusAi:
U using VillainRom too?
[Galaxy S II Original Android Development] kf0916:
gokhanmoral

Could you make s2 run full speed when finger touch the screen

back to normal freq when leaving finger on screen.

maybe this can make s2 smooth like ios system.

Thanks.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Any chance to support Tegrak Overclock Ultimate?
[Galaxy S II Original Android Development] ziroxs:
Hi. I assume you didnt uv the kernel so much. In this case the battery performance is good. I looked into my old results. After

24 hours beeing online with 5 emails accounts pushing and 2 hours display time i have ~ 65%.

Normally i can reach 5-6 hours display time and ~ 72 hours online time.

2.6.11 is a very good solution.
[Galaxy S II Original Android Development] keiemz:
Without 2nd core app, is default dynamic hot plug mode?
[Galaxy S II Original Android Development] pikachu01:
Yes. 10 char. :)
[Galaxy S II Original Android Development] :
Using XILA2 rom
[Galaxy S II Original Android Development] keiemz:
sys/module/pm_hotplug/parameters/freq_cpu1on value is 262144.. why?

Lulzactive's cpu freq default is 500000 when screen off. So I think that value is meaningless.

If I set the value 500000, what will happen?

Sorry for my poor English
[Galaxy S II Original Android Development] keiemz:
Thank you. I think agian and again. I know now but I didnt know "10 char" means.

I am not good at English
[Galaxy S II Original Android Development] DobermanS:
would you mind please to post your bootscript conf ?
[Galaxy S II Original Android Development] marioh:
Nice! What are your settings?

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] ziroxs:
You have a pm.
[Galaxy S II Original Android Development] marioh:
I yet tried your settings, but I have SOD. Thx anyway.

What room are you using.

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] :
latest results by using latest siyah with my configuration.

26hrs with heavy usage, wifi on all time(when screen off then wifi sleeps) xda browsing through app for nearly two hours, calls, whatsapp messaging, gmail to receive messages as they come and just playing games, total screen time 5hrs.

Latest XILA2 rom lite version and using stock battery. Looks like i am achieving the solid configuration after all:D

Looking forward to new version whenever that is out
[Galaxy S II Original Android Development] ziroxs:
Hi, i use Hyperdroid v6. Raise up the 200 MHz and 500 MHz Step for 25mV and try again.
[Galaxy S II Original Android Development] ricostuart:
I have tried this (using Syriah and Checkroom V4) and still doesnt work. Does anyone else have issues?
[Galaxy S II Original Android Development] doongoo:
I also would need it, if possible. But maybe other mates too here...
[Galaxy S II Original Android Development] ziroxs:
If my didnt work (look pm) and is too much uv ;) you can try geko´s stable config. I used it in the beginning as well.

http://xdaforums.com/showthread.php?t=1466017
[Galaxy S II Original Android Development] Visentinel:
The sod issue occurs for me aswell but actually its not a sod, it seems like it is but if it happens I just press power button to sleep the phone again and leave it for say ten seconds and try again and voila the screen works again.

Just have some patience its faster than a reboot. Seems like a screen driver issue, the screen fails to switch on on wake.
[Galaxy S II Original Android Development] f0rex:
What is your configuration? i'm quite new with kernel configurations..
[Galaxy S II Original Android Development] :
check your PM for a guide;)
[Galaxy S II Original Android Development] MistahBungle:
Can people please can the "Can you PM me your config" posts & simply ask for them by sending a PM to the person you're wanting the config from ?

We went thru this about 6-8 weeks ago :rolleyes:
[Galaxy S II Original Android Development] CamoGeko:
Lol, so true. Just post it and link it in your sig. Simple. :p
[Galaxy S II Original Android Development] Steven6489:
Hi geko95gek,

I saw your sig you are using Batista70 FoxHound v3.0 with Siyah Kernel v2.6.9..

How is your battery usage?

I'm using the same ROM with you but with Siyah Kernel v2.6.11 + MagicConfig v0.3.1(NOOP / CONSERVATIVE,tried BFQ / ONDEMAND). I'm experiencing bad battery consumption.

Idle for 8 hours with data/wifi off drain around 10%..my record is 0/1% battery drain during my sleep hour..

Any idea on that?
[Galaxy S II Original Android Development] CamoGeko:
Hmm.....check your apps for partial wakelocks using betterbatterystats app found here on XDA.

I found the drain to be slightly higher on .11 anyways than it was on .9, so maybe it's worth it for you as well.

:)
[Galaxy S II Original Android Development] Bec07:
"changed some mali internals (set staycounts for steps to: 0-1-1 and down threshold for second step is set to 35). I did not use AndreiLux’s settings for not breaking the compatibility with voltage control app but I highly recommend you try it because it can save a lot of battery juice."

Source: http://www.gokhanmoral.com/gm/2012/01/26/siyahkernel-v2-6-11/
[Galaxy S II Original Android Development] :
to be honest i actually have found battery drain a bit more than previous versions. Not saying that new version is not good **** it is one of the best. But still when actually using the phone it gets drained quicker than anything else. So reverted back to 2.6.9 to
[Galaxy S II Original Android Development] Steven6489:
Check the apps for wakelock..all seems good..

Will try to revert back to 2.6.9 to test it..Thanks anyway.. ;)
[Galaxy S II Original Android Development] veyka:
10 is the minimum number of letters that needs to be in a post for it to send, so when you just want to say yes, you put in 10chars etc at the end to bump the number up so it will send.
[Galaxy S II Original Android Development] PedroMRP:
Did you check partial kernel wakelocks and kernel wakelocks since charged?

Do you have automatic sync on? Maybe do you have some app that keeps trying to sync.
[Galaxy S II Original Android Development] CamoGeko:
Hope you get it sorted mate, I'm pretty positive something is keeping ur phone awake.

Would be helpful if you could post screenshots next time mate, screen on time and battery graph. ;)
[Galaxy S II Original Android Development] pikachu01:
It's just that I need 10 characters to post :)

Just to say yes, then I added the 10chars :P
[Galaxy S II Original Android Development] kilian7th:
+1 but I came back to 2.6.9 ... i just regret the redpill recovery ...

2.6.7 and 2.6.9 are very stable ...and the best battery life kernels with Miui roms ...
[Galaxy S II Original Android Development] torres76:
Resurrection v8.1 xxlp6 will you support this plz battery life isn't great with the supplied kernel
[Galaxy S II Original Android Development] lpsi2000:
No support for ICS right now until source code is available.
[Galaxy S II Original Android Development] Entropy512:
gokhanmoral should update the FAQ to indicate that ICS will not be supported until source code comes out.
[Galaxy S II Original Android Development] Igor 3:
my battery is wrong measured, it says that i lost like 8% i one hour, that two hours later its 1% Itgoes form 100% to 90% and then back to 95% and so on. I did the calibration and few charging cycles. Didnt help. Is this kernel problem? I use UV.
[Galaxy S II Original Android Development] chadouming:
I still dont understand how people can think that kernel author can make an ICS kernel. This was stated a lot of times + we dont have ICS source + no custom kernel for ICS exist, this should wake up some people, no ?
[Galaxy S II Original Android Development] CamoGeko:
Did you try to charge to 100%, take your battery out for at least 90 secs then put it back in?
[Galaxy S II Original Android Development] Igor 3:
Yes, i did the calibration. Used battery to the end, charge it to 100%, took it out and after a while put it back in and turn on the mobile.
[Galaxy S II Original Android Development] ozzyita:
My screen did not come on today, had to take battery out. Using .11
[Galaxy S II Original Android Development] kilian7th:
Franco kernel on galaxy nexus with ICS ... :-) so in theory it can be done ...
[Galaxy S II Original Android Development] Entropy512:
That's odd... It shouldn't be rising significantly when at high charge levels. The exception might be if you overclock and stay at OC frequencies for extended periods - this excessive load is likely to confuse the fuel gauge.

Apparently not...

As others have said - sometimes if you just wait 20-30 seconds it'll wake properly the next time. I believe (but am not sure), GM himself is able to reproduce this one.

Also, why did you remove the battery? Did long-pressing power to reset fail? This is ideal as it doesn't wipe the /proc/last_kmsg buffer in the case of a full-blown SoD.

That's completely different hardware. Here's the rule of the GPL:

If a company releases a binary of the kernel, they must release source to whomever they provided the binary to. As the GNex has an ICS binary provided by Samsung, Samsung had to provide source. Plus, being a Nexus, Google makes a point of providing source code (in fact, even a detailed git repo) even for components they are not legally required to. In addition, TI is, in general, very open-source friendly, and as a result, the OMAP4's support in even the mainline Linux kernel is way ahead of the support for other CPUs. (Exynos support in mainline is ****tacular - mainline cpuidle doesn't have ANY AFTR or LPA support for example.)

With the case of leaks - Samsung never "provided" the binary to us, people intercepted it when it was being provided to its intended recipients. So they're able to legally get away without providing source.

If less manufacturers used TI's security functions to lock their bootloaders, I'd probably be actively seeking OMAP devices instead of buying Samsungs. Unfortunately most OMAP4 devices are locked. GNex and Kindle Fire are two of the only exceptions I know of (except for the PandaBoard, but that's a development board and not a phone.)
[Galaxy S II Original Android Development] XDA mark:
I changed to 2.6.9, based on feedback from a few people. Will test it out, Im curious if I get better results then on .11

Can't wait for future updates :)
[Galaxy S II Original Android Development] :
mate i even rolled back to 2.6.7. was getting decent battery with latest but like yourself wanna see if it is true and older versions you get better battery... bit odd though if you ask me..any reasons why you think people might have reverted back?
[Galaxy S II Original Android Development] Steven6489:
Kindly help to check the screenshots below..
[Galaxy S II Original Android Development] :
first of all get rid of Juice Defender. That drains more battery than it is suppose to be saving. Second. Use widgetlocker instead of Go Lockscreen. From what i can see that kinda sucks a bit of battery to.

Also there is an alarm wakelock there so try and search through the threads here and i am sure i read somewere that they have found a fix for that as well.

Hope that clears some of your questions. And message Geko for his settings. I know the flying wizard is on cm9 now but i am sure he would gladly help you out with that
[Galaxy S II Original Android Development] XDA mark:
Since the only differences between the latest version are Ondemand (and maybe other gouveners) changes I think those little tweaks could be the reason you get a bit better batterylife on one version then another. Since there are so many tweaks and stuff being changed in this kernel, I bet it's even hard for the pro's sometimes to find out what can cauza that better or worse battery life.

I have a feeling the next Siyah updates are going to be great, dont know why :P It's amazing what kind of fantastic things are created here on XDA! And that most of these roms/kernels/tweaks are all free... awesome stuff:D
[Galaxy S II Original Android Development] :
could not agree with you fella. i am now on 2.6.7 and i will compare the two. being honest i did not had a problem with latest version. far from it. but thought i go back to old ones and compare and see if there is anything different regarding the juice life.;)

as for future updates. oh boy oh boy i am looking forward to it....problem is though i have got the bug of cm9 now and when the new builds are out i will be flashing away...

trust me you notice a massive difference
[Galaxy S II Original Android Development] Steven6489:
1 thing I keep Juice Defender is because it can auto off data when my screen is off wherever I don't have wifi..is that great feature? or any other alternative can do that? or everytime I need to off data manually when there is no wifi connection?

Previously widgetlocker sucks a lot of battery, thats why I use GoLocker, maybe recent version fix that..I will give it a try later..

You mean my alarm wakelock? what is the problem it could be? :eek:
[Galaxy S II Original Android Development] :
Have a search either this thread or just Google it to find out. Also regarding juice defender I can only advise you on what I know and encountered myself.

With widgetlocker no problems what so ever so yes I recommend it
[Galaxy S II Original Android Development] Entropy512:
Not enough wakelocks to explain your awake time - you didn't show kernel wakelocks though.
[Galaxy S II Original Android Development] olifee:
I tried again right now and it (still) works for me.

Although I have updated Orbot at least once since the time I copied the binary over, it strangely still is the same file.

As there was no update to droidwall.free, my ugly "workaround" should still work. Did you already try clearing the data of Orbot or completely removing and reinstalling Orbot?

Can you try the steps I tried (running iptables without any options) and post any output that is different? Can you also post the output of

md5sum /data/data/org.torproject.android/app_bin/iptables
md5sum /data/data/com.googlecode.droidwall.free/app_bin/iptables_armv5

They should be of the same value, and both show "50e39f66369344b692084a9563c185d4" if our versions are similar.

I am currently on Siyah 2.6.11, also (still) using CheckROM RevoHD 4, so it 'should' work for you if you are using the same versions.

Good luck!
[Galaxy S II Original Android Development] Uss_Defiant:
Unless you have proof to this effect, i see no reason for this to be true.

For ics, all you need is a 3.0 kernel. There was a 3.0 kernel for galaxy s way before ics came out. Further, there is an ics build running for the galaxy s despite the fact that no sources have been released.

As such, there is no reason to believe that you NEED sources to have a custom ics kernel
[Galaxy S II Original Android Development] pikachu01:
There are currently two streams of ICS right now, the stock one and the CM9 based ICS.

The stock one requires source code. The CM9 ICS is based off of AOSP, which already has its source.

So the notion of requiring source to build is still true. Please research some more before saying something inaccurate :)
[Galaxy S II Original Android Development] veyka:
The cm9 kernel is a hacked up stock ics leak kernel.

The main thing with the nexus s is that the user space stuff is os so its easier to hack around the lack of kernel source.

Trying to, reverse engineer the inframfs changes needed, along with everything else thats done to the kernel to make it work with the binary blobs is something called a almost imposable nightmare (eg audio, a como of alsa, binary blobs and hellish config, grathica drivers which have a small kernel part and a large binary part that does all the acceleration).

Whatever is happening in galaxy s land is helped by the Nexus s, which is very similar, so they can build off each other.

No src, no custom, built from source, kernels, afaik.
[Galaxy S II Original Android Development] h3llboy911:
Just flashed touch recovery for sgs2 which koush released on his website minutes ago. It didn't work. I still have the redpill kernel recovery.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
HELP with cpu_freq....

I'm using XWKL1 stock ROM with latest SiyahKernel.

I got a problem where I can't echo (using script) the cpu_freq.

I don't know what is wrong with my script, but it seems that everything is running OK except the CPU freq and max/min scaling freq. The UV_mV table is echo-ed correctly, but since the max_freq is still 1600 and the UV is in effect, it would immediately freeze the phone, forcing me to reboot.

Here's my script:

#!/system/bin/sh

sleep 2

echo "1204 1152 1100 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1204000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1200 1175 1150 1100 1000 900 875 850" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo lulzactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "100 160 267" > /sys/class/misc/gpu_clock_control/gpu_control
echo "850000 900000 1000000" > /sys/class/misc/gpu_voltage_control/gpu_control

echo "0 0 0 1 1 2 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
echo enabled > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

echo 3 > /sys/module/cpuidle/parameters/enable_mask

echo bfq > /sys/block/mmcblk0/queue/scheduler

echo 35 > /sys/module/pm_hotplug/parameters/loadl
echo 90 > /sys/module/pm_hotplug/parameters/loadh
echo 60 > /sys/module/pm_hotplug/parameters/loadl_scroff
echo 90 > /sys/module/pm_hotplug/parameters/loadh_scroff

echo 2 > /sys/devices/system/cpu/sched_mc_power_savings
[Galaxy S II Original Android Development] pikachu01:
You do know that Nexus S ICS sources are out? :/

Isn't that what you could call a "source"?

Also AOSP source is also released. That is the source. CM9 is based on AOSP, no?
[Galaxy S II Original Android Development] thracemerin:
CM9 is AOSP based but the kernel for SGSII comes from samsung, the kernels being released by samsung in the leaks do not come with source code so the kernel currently powering the SGSII CM9 is essentially a rooted stock kernel (think CFRoot), without sources it is essentially impossible to build the features that exist in CM7 or even CM9 on some other devices into the current build. Nexus S sources may be available but it doesnt use the same CPU and GPU as the SGSII so that wont help very much if at all, hopefully samsung sources for SGSII will be out soon given the progress the seem to be making on the pre-release builds which will allow devs here to continue their work for the ICS based roms.
[Galaxy S II Original Android Development] MistahBungle:
Excellent answer, simply/beautifully explained ;-) Bet we still get a stack of "Can we use Siyah with ICS alpha builds ?" tho :p #NoobsLearnToRead