yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] gokhanmoral:
it is fixed after patching \kernel folder but it is really hard to track it down to a single file because once you change something you have to change a header then you have to change another file....

I decided not to care about it too much.

and... I have updated the second post.

put something about "who should not use this kernel"

it is just an advice... of course everybody can use this kernel.

but sometimes it is so disturbing that some people are so ignorant and disrespectful.

I will add some more items to that part.
[Galaxy S II Original Android Development] Molitro:
I thought the second as soon as I read it, and got to say he has very good reason to do it.

People just don't read.
[Galaxy S II Original Android Development] gokhanmoral:
not all cpu's are the same.

and I am planning to let you access the internal reading about the grade of the cpu.

then, sharing UV values will make sense...

"my cpu is grade 7 and my UV values are blah blah..."

of course the stability doesn't only depend on the cpu but also the voltage regulator etc...

but sharing UV values will not be as meaningless as before...
[Galaxy S II Original Android Development] gokhanmoral:
silence is golden? :)
[Galaxy S II Original Android Development] bgx:
Have tested now 800@25mhz and it worked! Governor is sav2. But I raised to 672 and 872 MHz.
[Galaxy S II Original Android Development] kapa75:
Hi :)

Is the battery life really better when you add the 25 mhz step? :D

btw, you released 12 betas in 3 days, wow... you musn't be human :p

Great work :)
[Galaxy S II Original Android Development] spelaben:
Can anyone access CWM with home + power + vol up with beta 12?
[Galaxy S II Original Android Development] Piretia:
Someone can give me b12

Works with the latest rom 1.10.22 galnetmiui?

Thank you
[Galaxy S II Original Android Development] chadouming:
I can.

BTW, you have an idea why 2.1 is not working with galnet miui ?
[Galaxy S II Original Android Development] flo90:
I have a problem, with this kernel (2.0) my nenamark 2 result say 36fps !!! With the stock kernel i have 50fps !

What's the problem ??
[Galaxy S II Original Android Development] tolis626:
No,my phone decided to break my nerves.I tried to upload a screenshot with Tapatalk and it gave me an error,and then USB wouldn't mount and and and...Anyway,you get the point. :p

I ain't whining,it's all my fault.I'm ****ing a lot with it. :D

About time you started telling them off... ;)

And yes,the issue should be fixed from Samsung.It's their phone,it's their job to fix it.Anyway,good job again pal. ;)

Finally! :D

Now that's some breakthrough here... ;)
[Galaxy S II Original Android Development] DobermanS:
@ gokhanmoral

"we respect all religions but missionary acts are not welcomed in this thread"

great,superb, respect :)
[Galaxy S II Original Android Development] Nghtmare:
I have a questions for everyone, I know that we don't need battery calibration with our phone, even though there is a way which i saw in another threat about pulling out the battery and stuff, but that's not my point. When i had a SGS it was always recommended to flash a kernel with full battery for better battery performance, but since we don't need it with SGS2, does the battery level matter or make a difference?? Or i can just flash a kernel without worries?
[Galaxy S II Original Android Development] gokhanmoral:
v2.0 has old drivers.(update2)

v2.1 has the same drivers as the stock kernel. (update3)

that is why
[Galaxy S II Original Android Development] DobermanS:
Man,read the top of second post... :)
[Galaxy S II Original Android Development] karlesg:
the whole thread is getting more and more interesting... :)

but maybe now you'll have those who will ask you how to change the grade of their cpu and make it better :p Or complaining why they have the same grade with another one and don't get exactly the same results or performance or undervolting stability... :o

So you must always remind them that the whole issue is pretty complicated and doesn't depend on just a single factor. Because you are gonna have people whining again and again and again.... :D
[Galaxy S II Original Android Development] Entropy512:
Just flash a kernel without worries - although I'd recommend being over 50%, just due to the general "don't flash stuff at extremely low battery in case something dies mid-flash" rule.

Also, anyone who told you to always flash a kernel with full battery on the original SGS was blindly applying an HTCism to the phone - none of those devices have a fuel gauge that requires calibration/relearning.

http://www.maxim-ic.com/datasheet/index.mvp/id/6621 - this is the product page for the fuel gauge chip in all first-gen GalaxyS devices. One of the more important lines: "Unlike traditional fuel gauges, the ModelGauge algorithm eliminates the need for battery relearn cycles and an external current-sense resistor."

While the MAX17042 in our devices does have a current sensor, right now that sensor is not being used. As a result, the 42 is behaving almost identically to the 40 in previous phones.

When we get ICS, battery calibration MAY begin to apply, as newer Linux kernels support the more advanced features of the 17042.
[Galaxy S II Original Android Development] gokhanmoral:
oops...

I made a mistake and written "who should not use this ROM" :D

this is a kernel :p

maybe I should not use this kernel neither :D
[Galaxy S II Original Android Development] Nghtmare:
Alright mate thanks a lot for clearing that up for me.
[Galaxy S II Original Android Development] _cummoo:
LOLz :D

..but post 2 is really funny..
[Galaxy S II Original Android Development] tolis626:
You made two mistakes...

I beat you in Quadrant! :D

I applied the Quadrant cheat myself,just for fun.I also used the same hardware cheat as you,because it's freezing cold outside these days.What do you have to say noww?My Quadrant is larger than yours!HAAAA! :D :p

Chadouming,eat this. :cool: :p
[Galaxy S II Original Android Development] shr33kant:
So can anyone report that this new beta is running ok on cm7? I kinda need usb lol. I'm not at home right now and can't really flash it..

Sent from inside a black hole.
[Galaxy S II Original Android Development] flo90:
Ok i have read this. But this score it's not quadrant and my game (doodle jump and other) have some lag...

Brief i have resolved my problem after setcpu installation ! ;)
[Galaxy S II Original Android Development] Entropy512:
BTW, I'm in the process of narrowing down why AOS reporting as a drainer disappears when patching up to .14

It still gets reported high in .10, moving to .12 to test next. (Yup, binary search...)

There's more and more evidence that .14 fixes nothing, but merely changes how it is reported. People have managed to have high drain even with AOS not reporting anything on .14-based kernels.

That said, here's what I know so far:

1) People experiencing extremely high drain that has high AOS percentages associated with it have, in every case where a proper investigation was performed, NOT been experiencing a kernel bug. In all cases, it turned out they had an app that was driving network traffic to their phone. An arriving wifi or cellular data packet will force the phone to wake up. If that packet requires almost no application time to process, most of the time is spent resuming/suspending, which is why the usage gets reported as Android OS even though it's the fault of an app. See http://xdaforums.com/showthread.php?t=1308030 for more info - If you're experiencing high drain being reported as AOS, and you are running Skype - remove Skype. It's a crap app that is totally unsuited to Android devices.

2) Any cellular data incurs a minimum 6 second wakelock penalty. Reduced clock speed (such as 100 MHz) may help in these situations. Note that you will not see drain improvements from 100 MHz operation reported properly in Settings->About Phone->Battery Use because power_profile.xml (inside framework-res.apk) is unaware of the 100 MHz speed step, so calculates current consumption assuming 200 MHz operation. Also, similarly - anyone overclocking to 1.4/1.6 will have battery usage underreported when at maximum clock, again because power_profile.xml has no entries for these speeds.

3) Our phone does take longer to resume from suspend than its predecessors, 500-650 msec instead of 100-150, but there is likely nothing we can do about it. Most of that time is spent waiting for the radio interface to resume - our radio interface is apparently now an internal USB device that takes forever to resume. (BTW, this long time is why it takes almost a second for the screen to turn on from suspend.) Unfortunately, the nature of suspend/resume dynamics means that this time is spent at 800 MHz right now. Ouch...

4) In a few cases, people can find themselves permanently wakelocked with a fuel_alerted wakelock. See https://github.com/Entropy512/linux_kernel_sgh-i777/commit/fc9eb85807302583259e27013ed184a43107bb67 for the fix
[Galaxy S II Original Android Development] stuliv12:
Im on insanity 47 and usb doesnt work :( could be just me though.
[Galaxy S II Original Android Development] AndreiLux:
I don't understand the people raving about the 25MHz thing. The lowest stepping should be at the performance level needed for the highest common denominator task while the screen is off, and that would be MP3/audio playback. I didn't test yet what you'd need for that; you'd have to lower both the first and second stepping and monitor usage with CPUSpy and see where they switch between states and use something slightly above that as the lowest state. Using anything lower is stupid as in deep sleep most of the CPU isn't clocked, and when it does wake up, race-to-idle conditions apply and even if 25MHz uses less power, it's still more than deep sleep, and theoretically finishing the task at 100MHz faster and sleeping will use less power than quadrupling the processing time... I'll be testing this, but call me skeptical.
[Galaxy S II Original Android Development] bgx:
Can we add the lower MHz step in the framework? And when yes, do you think this will help?
[Galaxy S II Original Android Development] chadouming:
You make me laugh , i will put my new bench result when ill be at home xD And the worse thing is that i dont need the freezer ^^
[Galaxy S II Original Android Development] tolis626:
F*cker... :mad:

Well,I lived my moment of glory... :D :p
[Galaxy S II Original Android Development] chadouming:
Haha :P
[Galaxy S II Original Android Development] Entropy512:
100 may help with that stupid 6-second svnet-dormancy wakelock for cell data.

25 would in theory help, except that at 25 MHz, leakage current and such may be dominant. e.g. as clock gets lower, the static non-clock-dependent draw becomes more important.

100 MHz could be added, except that unless someone has a good way to measure current draw at 100 MHz, the current consumption estimate for 100 MHz would be a guess. I know from reading through other power_profiles that the classic "power draw goes up with the square of the voltage and linearly with clock" seems to hold at higher frequencies but not lower ones. (Assuming power_profile is even correct - on the Infuse, Samsung just copied it straight from the I9000 despite having a completely new wifi chip and such.)
[Galaxy S II Original Android Development] spradling:
Siyah rocks!!! Best kernel by far!! Thanks a lot gokhanmoral !! :D

Charging current modification is a God-sent! I can't live without it!!

BTW, can anybody share their GPU clock/voltage settings please? TIA :)
[Galaxy S II Original Android Development] desmes:
Hi guys ,

Is it possible , changing the "freq_table" , to have 25 , 100 , 200 Mhz , cause 25 MHz are not seen in CPU Spy , they , as if , only replace the symbol for 100Mhz. On the other hand "Time in State" of SetCPU shows old frequencies - 100, 200, 500 ...

So ... are 25MHz for real or just on paper ?
[Galaxy S II Original Android Development] AndreiLux:
Ugh, I forgot about that. I'll actually lower it and see if it breaks anything (the wakelock), someone's got to test it. I'm also not arguing the 100MHz, but anything lower is to be tested.

Even if it is 30-40% less instead of the theoretical half, it'll be something that would get you into the ballpark of what it really consumes. But as you said, I think the real killer is the 800MHz lock.
[Galaxy S II Original Android Development] spelaben:
I hate to post the same **** again and again but I would really appreciate it if someone could help me to fix this issue. I'm using CM #92, today I flashed Siyah 2.1b12 and now I'm stuck with the bootlogo where the yellow triangle appears.

What I tried already:

-Removed the battery

-Get into CWM with home power vol up, doesn't work

-Flash the same beta again with Odin

-Flash the stable 2.0 with Odin

Anyone, please?
[Galaxy S II Original Android Development] gippy2:
Im on Insanity 48 and usb is working (well intenal sd ) and also adb is working
[Galaxy S II Original Android Development] crypticc:
Can you get to recovery? No? I had this. I flashed CFROOT temporally via Odin and then wiped cache and flashed cm and booted.

Did you wipe all the cache locations?

Did you flash cm twice?
[Galaxy S II Original Android Development] SupraN0va:
Set CPU 200-500 work activated gpu, and everything ruins very smooth.
[Galaxy S II Original Android Development] smaberg:
i must disagree.... as its more to it.....trust me, :D

i always use GPU activated, this kernel runs perfect.. havnt tried rc1 or 2 yet though
[Galaxy S II Original Android Development] kwerdenker:
I'd say your arguing on thin ice. On paper your asumption may make sense, but it doesn't take things like leakage current in account which definetly increases as soon as there is more of the die active. Though this depends on how the second core gets shut off. If only its clock supply is cut off there still will be drain through leak currents. If on the other hand its voltage supply gets cut it most definetly saves battery. The other point is: how do you know smartass will let one core scale to 1000Mhz before it re-activates the second core?

Also I have no deep slepp issues with this kernel and 100 stepping active.

Sent from my secret moonbase via space carrier pidgeons
[Galaxy S II Original Android Development] uronfire:
can i use this kernel with the latest 2.3.5 K13 stock?

thanks
[Galaxy S II Original Android Development] SupraN0va:
AT 100 mhz I got a freeze after some time in deep sleep. I saw that the cores are switching at quadrant benchmark in system info . That would explain the lags that I got time after time. For me its seems that is just a minor improvement compare to stock. I've just compared screen on time.
[Galaxy S II Original Android Development] asphaltkiller:
please guyz any idea??

How is it possible to check that GPU clock or voltage have been really modified?
[Galaxy S II Original Android Development] Muskito87:
3hrs and 36min onv3.5 of Check ROM with 1.7rc1...

Only 90%!!!!!!!!

im loving 1.7!!!!!! Will post back full usereport 2morrow :)
[Galaxy S II Original Android Development] brack11:
Hmm, somehow I didn't get good battery from this kernel. So far the most economical for me was dead Jeffrey speedfrey kernel, but the dead is dead. Ragemod is the closest to Jeffrey. I just wasn't able to use uv and smartassv2 was not really stable for my phone

Sent from my GT-I9100
[Galaxy S II Original Android Development] SupraN0va:
Screen on time????
[Galaxy S II Original Android Development] xinfinityoO:
the beta version seemed better..or i could be wrong..

the smartass2 is changing frequency more often in the rc1 while in the beta it was a bit slow..i prefered that and i didnt feel any lag also..( i was using nexs tweaks)

can anyone please post the last version before rc1 came out..i deleted mine

thanks

anyone ??
[Galaxy S II Original Android Development] asphaltkiller:
here it is

http://www.2shared.com/file/pJf9ruje/Siyah-v17beta2.html
[Galaxy S II Original Android Development] kwerdenker:
Yes, you'll have to reboot to apply any changes to the scripts in the ini-folder. You can check the current settings via terminal emulator or adb shell and

cat /sys/devices/virtual/misc/gpu_clock_control/gpu_control

or

cat /sys/devices/virtual/misc/gpu_voltage_control/gpu_control
[Galaxy S II Original Android Development] raziel19:
wasn't it v1.7beta3 :confused:
[Galaxy S II Original Android Development] xinfinityoO:
thx mate

will flash this back
[Galaxy S II Original Android Development] raziel19:
again i read your post and want to ask:

why don't you test rc2 first?

it's running fine for me :cool:
[Galaxy S II Original Android Development] kwerdenker:
Did you use UV with the 100MHz stepping? If so, you schould raise the setting for the 200MHz step. That cured any wakelocks I had with the newer versions of this kernel.

The lower stepping will probably not save you that much battery while screen is on since you are doing stuff when the screen is on and thus the higher stepping will probably be used more. It should however help in the screen-off cases, when an app wakes the device to check for some data or something like that.

All in all, this is very usage dependant.
[Galaxy S II Original Android Development] asphaltkiller:
thanks m8 I have checked and modifications to the 99GPUV script (400Mhz and undervolting) are not applied!!!

example of my 99GPUV FILE

where do i made a mistake?

how to do this?
[Galaxy S II Original Android Development] chiggah:
Never tried rc1 but just want to report I had excellent battery life with 1.7 beta 3 and villainROM 2.5

I think I lost about 2-3% overnight in 8 hours
[Galaxy S II Original Android Development] gokhanmoral:
I forgot to take the lowest freq back to 200MHz in rc2 (it was 100). that may be the reason of the lockup.

I have deleted rc2.

I am uploading rc3 right now.

I cleaned up the code. rc3 also has another tweaked smartass2 governor. I hope that it will make everybody happy. at least pretend to be happy, I'm tired already :)

rc3 will probably be the release version. therefore I have turned all the optimizations on.

get it and if it works fine on your device don't come back to this thread again :P
[Galaxy S II Original Android Development] beaver2233:
Using rc1 and whenever I try set min to 100mhz is always freezes my phone and am forced to hard reboot...no I'm not UV 100 at all, I didn't have time to before it froze :P
[Galaxy S II Original Android Development] BoneMo:
i am on nightly 92 and usb working...i can mount internal storage+external SD :)
[Galaxy S II Original Android Development] nerotix:
beta 13 is out ..:D:D
[Galaxy S II Original Android Development] tolis626:
Well,I tested 25Mhz on my phone,so I have some results.

First off,I can tell you that 25MHz is just too ****ing low.I was listening to some music(Trivium in particular if it matters :p ) and it made some stutters.Unless Trivium's new album is bad enough to make the phone malfunction,I can safely say 25Mhz isn't enough.Plus,maybe the very high load on 25MHz causes the phone to use higher frequencies when it doesn't have to.

Also,it doesn't work with voltages lower than those I need for 100Mhz,so on my phone it's completely useless.Maybe for some it'll give them the opportunity to undervolt 25mV further,but that's insignificant.

Just my 2$. :)
[Galaxy S II Original Android Development] BoneMo:
i did the same today and no problems...

i had Villain ROM 3.0.....so went to CWM and there

1. wipe data/factory reset

2. wipe cache

3. wipe dalvik cache

4. twice flashed nightly 92

5. booted to CM7

6. back to CWM

7. flashed Siyah 2.1 b12 + gapps

8. booted to CM7

9. everything works,can mount both storages to PC,,,can go to recovery,, reboot ...whatever
[Galaxy S II Original Android Development] spelaben:
I can get to the recovery mode (vol down) but not the CWM (vol up). I wiped the cache before flashing #90 which I flashed twice.

Today I updated to #92 but didn't flash it twice.
[Galaxy S II Original Android Development] :
Might have to flash with repartition
[Galaxy S II Original Android Development] BoneMo:
.

well it seems that double-flash is a significant step to succesful boot :)

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

try to flash siyah .tar via odin...and then i hope you wil get to cwm....just idea

---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------

WOW BETA 13 ONLINE

tar: http://www.gokhanmoral.com/public/files/siyahkernel/test/Siyah-v2.1b13.tar

zip: http://www.gokhanmoral.com/public/files/siyahkernel/test/Siyah-v2.1b13-CWM.zip
[Galaxy S II Original Android Development] crypticc:
That'll be why then. Exactly what happened to me. You have boot.img from cm and no /system or zimage. that's it. Try what I did to get recovery back by flashing cfroot tar via Odin in bootloader mode (note bootloader, not recovery is Vol down). I think cfroot tar does some things Siyah doesn't.

Update just racking my brains. I also did a download mode followed by cancel and a bit of a reboot to break cycle of not booting. Failing that you're lucky you have download because worse comes to worse you can flash an intratech tar file to stock. And then same with repartition as a last resort.

(Update: fixed typo "repartition")
[Galaxy S II Original Android Development] spelaben:
Tried to flash 2.1b12, 2.0 and now the newest b13 with Odin but it won't let me access CWM.

Trying to flash cfroot with bootloader update now, thanks crypticc. :)
[Galaxy S II Original Android Development] DobermanS:
Sh*t :) BETA 13 :)

And i wanted to go to bed already :)
[Galaxy S II Original Android Development] Entropy512:
Well, depending on what the CPU's static leakage current is, 25 MHz may help even at the same voltage. Dynamic current is a linear function of frequency - but by 100 MHz you may be at the limit where static current dominates. It's really indeterminate.

Forcing 25 MHz would be a bad idea - as Andrei said, if you're pegging the CPU, it's better to ramp up, "git er' done" and then enter deep sleep faster.

25 MHz would only help in those cases where the CPU is waiting on a long wakelock that is bound by some I/O event and not waiting for the CPU to finish doing work. Prime example I can think of right now is the 6-second svnet-dormancy wakelock - but going below 100 MHz here may not really benefit you at all, since any time that wakelock fires, the radio is going to be active and drawing current, so probably it'll dominate current consumption.

Another observation on power_profile.xml - It's indeterminate whether the current consumption numbers are supposed to be per-core or total - it's obvious that Samsung assumed total, but if it's supposed to be per-core, all CPU battery usage will get reported in battery usage as twice that of reality.
[Galaxy S II Original Android Development] nerotix:
Version 2.1b13 working fine so far on 'Official' MIUI 1.10.21.
[Galaxy S II Original Android Development] spelaben:
Okay I managed to fix my problems. Flashing CM builds twice from now on. The weird thing is that the second flash of the zip always takes longer, as if the first flashing "forgets" some parts. My phone is now also booting with b13. ;)
[Galaxy S II Original Android Development] BoneMo:
beta 13 ok ? no problems like usb etc ?
[Galaxy S II Original Android Development] gokhanmoral:
strange but I had the same problem with CM7.

every time I try to flash it, I have to flash it twice to get it booting.
[Galaxy S II Original Android Development] crypticc:
Good for me back on ki8 now.

I thought I had faulty windows drivers so this is a plus.
[Galaxy S II Original Android Development] crypticc:
I lost an afternoon trying to get mine back. It's as though cm kernel only gets it right first time.
[Galaxy S II Original Android Development] crypticc:
if you watch you see that it fails after wiping partitions and flashing boot.img