yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] masked_face:
MIUI 1.11.4 with Siyah 2.1.1 kernel

I've been using MIUI 1.11.4 with Siyah 2.1.1 kernel for last 2 days....excellent combo....didn't face any FC as you mentioned...smooth like butter...battery lasted for 40 hours with moderate usage and still 10% left.

If you use titanium backup to restore apps...restore only apps...not any data...that's the way it works for me...and afterwards u can use ROM Manager to fix permission.

hopefully that'll work for u. :)
[Galaxy S II Original Android Development] _cummoo:
I asked Gokhan because of the Siyah-Tool but this time he gave me no answer, so i think maybe he revoked it due to some issues with 1.1 but will release it when the time has come. :D
[Galaxy S II Original Android Development] energie:
i reinstalled all programs again, no backup restores or whatever :|

do you use setcpu or something?

i think most of the problems are setcpu related.

no uv
[Galaxy S II Original Android Development] cool_sid007:
no help?? :( anyone pls
[Galaxy S II Original Android Development] gokhanmoral:
I do not make any change in default settings that would cause worse battery life.

so, there is no need for two different kernels.

battery life can not be increased by small code optimizations. there are some parts that "may" affect the battery life, such as jhash or crc algorithms which are used maybe millions of times on a single charge... but apart from those algorithms, disabling or enabling logs or other changes will not affect the battery life noticeably. the effect may be 0.5% or maybe less and those who can notice it are either unique or lier.

battery life can be increased of course... by decreasing brightness, by using airplane mode, by decreasing voltage or frequencies or governors.

some advices are given in the second post.

and it is all up to you.

if I fix something, it will hardly effect the battery life.

battery life may be different between update2 and update3.

but normally, if a kernel is using default (stock) settings and using the same baseline (update3 for example) battery life between that kernel and another ARE THE SAME.

if you are using default values (default governor ondemand and default frequencies) there is not much you can control. deep sleep consumption cannot be optimized in any way. if you are using the same brightness level and programs, cpu scaling will be the same and so the power consumption will be the same...

those who claim that this kernel or another (as long as based on update3 sources) has better battery consumption with 200-1200@ondemand with stock voltages is either has no idea what he is talking about or is just telling a lie.

this kernel may be more responsive or has more features than stock but battery consumption will not differ that much with default settings.

sometimes I read posts like "oh my god!! 98% deep sleep!! good job!". that is not the success of the kernel (assuming that there is no serious bug in stock kernel and there is not in the latest version) but it is either lack of his social skills that prevents him communicating with people on the phone or he just doesn't use it and the phone has nothing running on it that causes it to wake.

I can bet on anything that if a phone is in deep sleep, the power consumption will not be different than the stock more than 5% and I just leave that margin because of the operator signal can fluctuate.

in short, you can optimize this kernel to have a better battery life.

maybe v1.8 has better battery because of different drivers or a bug in the latest version.

I am trying to make this kernel better, not worse. and making it perform better doesn't mean that it will have worse battery life.

if an performance optimization affects battery life, it will be optional and it will be activated manually (such as overclocking).
[Galaxy S II Original Android Development] hausmanis:
thx alot for the detailed explanation instead of just flaming me :)

And well the only other kernel ive ever had better batterylife with is infact also Siyah but the 1.8 version. I am very satisfied as i have it right now with insanity rom and Siyah 2.1 super undervolted.

thx for the great job and sorry if it sounded like i was flaming you i sure wasnt just that i was abit courious to why i had better battery with 1.8 it felt like you "optimized away" those batterysavings of 1.8 in 2.1 but now i know its possibly because of newer drivers.
[Galaxy S II Original Android Development] gokhanmoral:
Hellcatdroid is working on dual-booting so that decreased the priority on my plans about dual-booting.

I am now working on the tool and put some features such as rooting without booting and cpu/gpu clock/voltage modifications, but for now it looks horrible :)

since this week is holiday in my country I will not be able to work on the tool. therefore I made some modifications on the kernel. next week I will continue working on the tool and hopefully release it in a week or so.
[Galaxy S II Original Android Development] chadouming:
Keep on the good work ^^ I love this kernel and I will stick to it as long as you provide update or I change phone.
[Galaxy S II Original Android Development] hausmanis:
Sounds awesome, would be super nice if you could modify the bus frequenzies with that tool aswell, then you would have 100% siyah controll :D
[Galaxy S II Original Android Development] dragon546:
I had this with Check V1.0 using Siyah 1.78 at the time this was happening when I installed the no overglow browser and when I surfing and playing audio. I changed to MIUI and not had the problem since for me I found 2.1rc 3 and 1.11.4 gives me the best overall so far without UV or OC' ing but that's just me..
[Galaxy S II Original Android Development] Bene2k11:
Happy Bajram mate. ;P
[Galaxy S II Original Android Development] chadouming:
Are you Uv'ed ? If yes, try to remove your UV first.
[Galaxy S II Original Android Development] lkhz:
Whats the recommended app to OC ?
[Galaxy S II Original Android Development] chadouming:
Plz, use the q&a thread for this kind of question.
[Galaxy S II Original Android Development] masked_face:
yup I use SetCPU...but most of the time I keep it at max stock speed (1.2)...I overclock it to 1.6 Ghz for benchmarking purpose only.

I'm sure you know all about clean install...still repeating what I did:

1. wiped data/factory reset

2. wiped cache

3. wiped dalvik cache

4. install!

5. Reboot and start the ROM

6. restore all my apps (using Titanium backup...only apps...without data)

7. fixed permission using ROM Manager

8. used it for a while

9. boot into recovery and installed Siyah kernel 2.1.1

10. reboot and use!

hopefully this will work for you buddy...
[Galaxy S II Original Android Development] frankcilo:
it is recommended not to use any applications, use only script for all!!

---------- Post added at 07:55 PM ---------- Previous post was at 07:21 PM ----------

new 2.2beta1 seems in upload!!

time_in_state is updated if you change freq_table ??????
[Galaxy S II Original Android Development] gokhanmoral:
I have updated the post.

cpuspy was not reporing the time in state if you have modified freq_table (for instance, if you modified 100MHz step and made it 25MHz)

now I update cpufreq_stats and cpuspy reports the correct times in states (there is a file in /sys named times_in_states)
[Galaxy S II Original Android Development] dtekkt:
So far 2.2b1 is working great :-)
[Galaxy S II Original Android Development] gokhanmoral:
as a user of this kernel, I think it is the best version until now :)

I have tested it a lot this time.

and good news for miui users: I will install miui tomorrow.
[Galaxy S II Original Android Development] camro:
thanks :)

on new kernel 2.2beta1 -> logging is working again :)

great thanks !!!!
[Galaxy S II Original Android Development] frankcilo:
You are the best!!
[Galaxy S II Original Android Development] dtekkt:
Its too early to judge it, but I think you are right. Hm thought about changing to Miui also but I quite like the custom roms based on stock. I hope for a great working dualboot solution soon so I can test it further.
[Galaxy S II Original Android Development] kwerdenker:
Just flashed it and got a question out of curiosity: did you somehow incorporated cache formatting into the tar version? Because I flashed it via CWM app, the reboot lasted longer than usual and so I checked via logcat and it looked like the usual cache buildup.

Just wondering because I never had this behaviour before:)
[Galaxy S II Original Android Development] gokhanmoral:
nope, I did not incorporated cache formatting or wipe in the tar version. I wish I could :) I can wipe cache but I don't know how to wipe dalvik-cache using tar.

it is strange. I did not notice that but maybe it is because I removed some fast-math and single-precision-constant etc. compiler optimization flags. but it is scary because a possible cause is a change in the checksumming algorithm and I don't remember that I changed that in this release..
[Galaxy S II Original Android Development] fasst:
How long time did it take?

Seems I get stuck on boot when I flash 2.2b1.tar with both CWM app and Odin. No such problems with 2.1.1.tar
[Galaxy S II Original Android Development] kwerdenker:
Ok, that's odd then. Do you want me to try to reproduce this behaviour and logcat it?

---------- Post added at 09:10 PM ---------- Previous post was at 09:05 PM ----------

Can really say. It took longer than the usual reboot after tar flashing (which is fast), so I checked it. All in all I would say the boot time was normal for a reboot after a cache/dalvik-cache wipe... a minute, maybe two or three. Sorry, I'm just bad with guessing time ^^

If you are near a pc with adb installed, connect your sgs2 via usb and run "adb logcat" from the commandline. If it's still doing stuff and not looping the same message over and over again, it's probably ok.
[Galaxy S II Original Android Development] gokhanmoral:
that would be great.
[Galaxy S II Original Android Development] kwerdenker:
Ok, so I did some flashes and this is what I noticed:

reflashing 2.2b1 over 2.2b1 -> normal fast reboot after tar flash

flashing 2.1.1 over 2.2b1 -> longer reboot like after dalvik wipe (sorry, no log because of the disabled logcat in 2.1.1)

flashing 2.2b1 over 2.1.1 -> longer reboot again (link to log)

I did a quick scan of the log but I'm not used to reading that so nothing jumped at me. Hopefully it helps you :)
[Galaxy S II Original Android Development] ram3n:
Latest beta works very well !

Siyah-v2.2beta1-CWM.zip

http://www.multiupload.com/H10WC6S18L

Maybe could help some of you :D
[Galaxy S II Original Android Development] :
There is definitely something weird going on with 2.2b1, clean install ROM with 2.2b1 zimage replaced, boots normally, but when flashing CSC (which is cache.img and hidden.img) the phone gets stuck on Samsung logo (before boot animation). Tried to reproduce same thing with speedmod and it works normally.
[Galaxy S II Original Android Development] fasst:
It seems like it's looping. I don't have the skills to interpret what the logcat tells so here it is, if someone could see whats going wrong.

As I mentioned earlier, stuck on boot with 2.2.1b.tar from within CWM-app and Odin. And the same problem with CWM-version.

2.1.1 gives me no such problems.

2.2.b1 is the fist time I have experienced such problems. Hopefully it's just me?
[Galaxy S II Original Android Development] hausmanis:
about adding a 25mhz step, will that save more battery than having 100mhz as your lowest step ?

and about what app to use to set cpu voltages ect, if you dont like fiddeling with scripts i find voltage controll to be a great app, it even has special siyah stuff like gpu UV ect in it.
[Galaxy S II Original Android Development] kwerdenker:
Yes, there is definetly something wrong here. Could you try to flash 2.2b1 via CWM and then wipe cache and dalvik-cache manually and see if this fixes anything?

It could save battery under certain conditions: if you for example often have wakelocks where the system/an app is waiting for data via 3g and does nothing else, it might save battery. But if you use your phone these savings might be negated, because 25Mhz is a very low frequency and the load will skyrocket and so the governor switches to a higher frequency more often. Higher frequency + higher voltage = more energy drain.

I would encourage you to just test it and see if it works for you or not. Everyones phone is different and everyone uses it differently, so it's hard to come up with the ultimate truth in battery saving. Well, except for "don't use your phone or just switch it off completly" ;)

If you don't want to sink your teeth into init-scripts, voltage control is you best bet since it's the only app at the moment that supports this kernel more advanced features. But speaking from personal experience, these scripts are no black magic and if you know just a tiny bit about unix shell you'll have them up and running in no time :)

P.S.: IT'S OVER 9000!!!!!! sorry, just couldn't pass that one up :P
[Galaxy S II Original Android Development] fasst:
I tried but it doesn't help. Stuck again.
[Galaxy S II Original Android Development] cheewaca:
Lag come back in menu transitions with samsung stock rom and siyah 2.2 b1. Siyah 2.1.1 hasn't lag.
[Galaxy S II Original Android Development] :
Something's fu*ck up with cache.img.. If I install only .tar without wiping cache it works. If I reboot to recovery and wipe cache or flash cwm version it gets stuck.
[Galaxy S II Original Android Development] rauschkugl:
Installed cwm over 2.1 rc3 and everything was working like always. No problems for me.

2.2b1 seems really fast so far. The only thing i found was that the screen on animation doesn't look like before. Seems a little bit messed but i don't care...

Sent from my GT-I9100
[Galaxy S II Original Android Development] frankcilo:
Great Kernel, great great kernel!!!

A little donation for you!!

80V53967ER970354G
[Galaxy S II Original Android Development] hausmanis:
As always a good explanation from Kwerdenker, i thank you for that. Guess im better of with 100mhz but i will indeed test it out, still working on my biggest problem tho...how to prevent my phone from eating up my battery mega fast when im at work due to that heavy concrete roof :P

EDIT: a question: Before when i used TW roms i always disabled fast dormancy and it gave me a noticable boost to batterylife especially since my provider dosnt support fast dormancy, im now using the CM based insanity rom and the service code dosnt work, anyone know a alternative way of disabling fast dormancy ?
[Galaxy S II Original Android Development] frankcilo:
Now cpuspy not work, it not read real frequency value:confused:
[Galaxy S II Original Android Development] lpsi2000:
I have never tried to use any of those codes on CM based ROM but I think this question will be much more suited for the insanity thread.
[Galaxy S II Original Android Development] crypticc:
+1

Exact same errors as per your logcat. no difference for me flashing either zip via cwm recovery, or tar via cwm app.

Edit: removed extra garbage
[Galaxy S II Original Android Development] dody79eg:
bootloob after insert external sd

and restore my app

firmware 2.3.5

at 2.3.4 no problem

no answer???????
[Galaxy S II Original Android Development] incubus_fr:
Works fine for me on custom frequency values.

Thanks Gokhan!
[Galaxy S II Original Android Development] fasst:
gokhamoral,

It seeems that a few are experiencing boot stuck with 2.2.b1. It happends both with flashing or tar and CWM from within CWM-app, and ODIN.

I'n no expert in intreprete logcats but it looks like it has something to do with audio drivers.

Info if neded: stock XWKJ2, CF-root, modem KI4.

Logcat attatched.

I know this week is for holiday for you. So take your time "living". The consern I have is that this problems could be dragged into future releaes for us experiencing this problem. For now I'm living ok with 2.1.1
[Galaxy S II Original Android Development] peachpuff:
Does the faster usb charging work on samsung roms? I noticed that the voltage control app doesn't show the charging controls, so i flashed the script from the first post and edited it but it doesn't seem like the charging current increased at all.
[Galaxy S II Original Android Development] marcelotorres:
Amazing Kernel!

I'm using since 4/11 and yesterday i play some games on device and online games, surf the web and in the night i don't plug the phone on charger. When i go to bed, battery display 49% and 8h after 45%

I'm using only 1 profile in SetCpu that is screen off max 800mhz min 200mhz.

Thanks for all!
[Galaxy S II Original Android Development] timberwolf60:
I was facing this problem before, My method:

Firstly copy out CWM.APK from system/app folder to a save location for future used. Then fellow below:

1) used S2 root 1.5.1 to unroot your phone, it will cleanup all the SU and BB rubished.

2) used Odin to flash an insecure kernel.

3) used S2 root to root your phone. It will installed a fresh SU and BB.

4) Used CWM application, just clicked the CWM icon. Scrolled dowm to choose flesh kernel option to flash siyah 2.2 beta1.tar. Or you used DarkyROM2 to flash the siyah kernel.

Links for S2 root: http://xdaforums.com/showthread.php?t=1125414&page=32 downloaded from first page.

And insecure kernel: http://xdaforums.com/showthread.php?t=1101671&page=27

Odia just uploaded secure and insecure kernel for xwkj2.
[Galaxy S II Original Android Development] YaocH:
Just flashed it without any issues of bootloop or taking much longer to boot as experienced by some users. Must say that it's much smoother than 2.1.1 while browsing web and also the homepage fluidity is also greatly improved. Great Job! Now on to test the battery consumption(:
[Galaxy S II Original Android Development] antt00:
After seeing the problems here, I tried flashing the zimage directly with CWM app. My situation was similar to kwerdenker . Boot took longer than normal (at the animation screen) but not as long as wiping dalvik cache. But device does start up and now let see how this one performs.
[Galaxy S II Original Android Development] frankcilo:
I have modified freq table and it worked well, but not anymore.
[Galaxy S II Original Android Development] :
Exactly. As long as you don't wipe cache everything works.
[Galaxy S II Original Android Development] bgx:
Hey gokhan! Thank you for this nice kernel! I have changed the init script for my supposed! And also need tasker for it. Stock Speed I have 25-1000mhz when watching video speed will increase to 1200mhz; when on tapatalk speed will decrease to 500mhz; when the battery falls under 50% decrease to 800mhz; in the night between 23 and 6 clock or when battery falls under 25% busfrequ is changed to 25,150,350,648,800 screen off is then 25-350 conservative ; normally screen off is 25-500 conservative!

Really, really nice B-) thank you again!
[Galaxy S II Original Android Development] crypticc:
You sure you have this kernel?
[Galaxy S II Original Android Development] cool_sid007:
no I havent Uv'ed my fone.. any other ideas?
[Galaxy S II Original Android Development] crypticc:
Morning.

I got loop even without wiping cache or maybe I didn't wait long enough ( 15 mins )?

The log suggests a class is missing from one of the jar files. Probably not the only one.
[Galaxy S II Original Android Development] :
Hmm strange. Flashed speedmod and than b1 again to test again and working fine. You are using tar version, right? Stock rom?
[Galaxy S II Original Android Development] itzankov:
Audio driver seems to initialize OK.

The SIGSEGV in zygote is the reason for the crash.
[Galaxy S II Original Android Development] dody79eg:
bootloob after insert external sd

and restore my app

firmware 2.3.5

at 2.3.4 no problem
[Galaxy S II Original Android Development] fasst:
Thank you for taking your time trying to help out timberwolf60.

I follow your instructions but saldly it didn't work for me. Still the same symptoms after flashing 2.2.b1.

---------- Post added at 10:00 AM ---------- Previous post was at 09:47 AM ----------

For better understanding I made a google search for SIGSEGV, and it's understandable. The same thing for ZYGOTE. Understandable too, but not in this context :D

Edit: Or maybe it is, causing an abor** on my phone :eek:
[Galaxy S II Original Android Development] BoneMo:
Bootloop,stuck on boot etc problems mentioned are with all roms...or only samsung based? CM7 ? MIUI ?
[Galaxy S II Original Android Development] dody79eg:
bootloob with samsung based 2.3.5
[Galaxy S II Original Android Development] fasst:
We have no indications that this happens with all stock roms. And for me there is no bootloop. But the logcat shows looping when stuck on boot.
[Galaxy S II Original Android Development] BoneMo:
i hope i will not stuck on boot with CM7 :o:p
[Galaxy S II Original Android Development] Molitro:
I'm on 2.2b1, and flashed fine from both 2.1.1 and speedmod k2-16.
[Galaxy S II Original Android Development] hausmanis:
CPU with the app setCPU, GPU with scripts to be found in this post.

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

Anyone that UV:ed gpu ? would love to se what low numbers people are using stable to save battery, to compare with my own
[Galaxy S II Original Android Development] kwerdenker:
Voltage is capped at 800mV, so you can't go lower than that. From what I remember throughout this thread, smartassV2 has a target frequency and always tries to scale as fast as possible to that frequency and then only scales further if the load makes it necessary. Difference between screen-on and -off is the target frequency (800 while on and 100/200 while off or something like that I believe). You can already control all voltages and frequencies via init-scripts, no need to wait for an app ;)
[Galaxy S II Original Android Development] xeq544:
Yeah I already did for the gpu, and used setcpu for cpu cause Im lazy ass ! :p
[Galaxy S II Original Android Development] enebro77:
Battery drain in the night

Dear Sir,

I am using your Kernel (with smaberg´s x-power ROM) and I am really happy with it.

There is only point I would like to ask about nightly battery comsumption.

From 12 to 8 am with everything disconnected (BT, Wifi, phone , ...) and 100Mhz minimum it takes 4% of the battery.

¿ Is this normal ?

Many thanks in advance
[Galaxy S II Original Android Development] frankcilo:
What is the script for AC and usb charging?

Can you put it on first page?

Thanks

I use this kernel with ki3 2.3.5 and work greatly!!

Smartassv2

Min 200mhz max 1000 with screen on

Min 100mhz max 500 with screen off

Gpu clock standard, but uv to 875mv and 975mv

I not use setcpu, but my modified script of daemon dualcore tweak...more fast to change value!

http://forum.hdblog.it/f393/[mod-app]-oc-daemon-e-dualcore-scripts-45670/
[Galaxy S II Original Android Development] monkeydrufy:
sorry guys,

is this kernel compatible with tegrak?

thanks
[Galaxy S II Original Android Development] xeq544:
No it isnt.
[Galaxy S II Original Android Development] vandanh15:
How long shall be used when the battery 100%
[Galaxy S II Original Android Development] Mayday_XL:
My S2 runs 3 days very fine with my UC settings, but today i had sudden reboots, now i am back to the stock settings and everything is good. :cool:
[Galaxy S II Original Android Development] harrynghiem:
that's good. What is your expectations? please enjoy now
[Galaxy S II Original Android Development] gokhanmoral:
V1.7.1 is up.

I did not remove the older version. If you have any problem with the new version please revert to the old one.
[Galaxy S II Original Android Development] ehmi:
Gpu 100/267 750000/800000

cpu:

100/800

200/850

500/875

800/950

1000/1050

1200/1150

smartass v2

Charge current 1000/1000/1000

No problems since 2 days.
[Galaxy S II Original Android Development] asphaltkiller:
GPU is working fine : 160@825 and 267@925 (400mhz is stable @1050)

i hope it would help

how to check stability of each frequency one by one???

very strange but your values for GPU seems to work on my sgs2...I was unable to get 267@800 before, with the couple 160Mhz 267MHZ my lowest value for 267 was 925...strange