yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] gokhanmoral:
absolutely...

and it is probably your extreme undervolting settings...

aren't you the one who is still defending the necessity of battery calibration? :)

then, this kernel will never be stable for you...

speedmod is a good choice.

it is stable as it has almost no modification on the kernel source.

no UV makes it even more stable because people do not insist on using the lowest voltages and cry about having 800mV unstable while they were using it with another kernel...

I am thinking about releasing a special "placebo edition" with stable 600mV@1600MHz :)

sorry if I sound rude... but now I understand Hacre better :)
[Galaxy S II Original Android Development] Lownita:
Gokhan there seems to be a problem with your kernel and http://xdaforums.com/showthread.php?t=1312240 . It seems that it has something to do with cwm 5.0.

Perhaps you might consider taking a look at it, would be great!

greetings
[Galaxy S II Original Android Development] tolis626:
Yep.Hacre I think isn't as bad as it seems.But man,you must get yourself a post 5 like Hacre did.If you can't be bad,lemme do the dirty work for you! :p

Also,just a question of curiosity,when are you planning on making the bus control interface available?Will we have to wait?If yes,I'll just keep telling myself that patience is a virtue... :p
[Galaxy S II Original Android Development] gokhanmoral:
I tried to flash a zip with darky's tool and it works.

I don't think there is a problem with new beta..

I know that v1.7.8 or v1.8 had problems flashing zip's.. one of those versions wasn't rebooting and going into CWM recovery.

kitchen apps should work fine with v2.1 and cwm5
[Galaxy S II Original Android Development] kapa75:
Same here, my uv settings don't work really well (freeze and reboots) on the latest beta (even if it worked great on beta 2.)

Just one question => Do you advise not undervolting? Is it useless? :D
[Galaxy S II Original Android Development] ram3n:
+1

You know I actually love your kernel and your work. :)

For sure, I must admit my undervolting settings are really extremely low, but damn, it is running so fast and well on 2.0 !

I am sure that you will release another version as stable as 2.0 soon.

And yes, you're right, I don't want to pull my hair out anymore for a while, so the best is to stick at Speedmod'.

Anyway, your kernel remains for me one of the best of the very best off, no matter others say !

cheers dude !
[Galaxy S II Original Android Development] nerotix:
Btw, OP first post says it compatible with 2.3.4 and 2.3.5 roms etc but CM and MIUI are running on 2.3.7 nowadays, Will it also work with 2.3.7?

Thanks!
[Galaxy S II Original Android Development] gokhanmoral:
I still could not decide what kind of interface I will provide..

bus frequency is dynamically changed based on bus load and it is set to max for 1200MHz.

I can fix it to a specific freq, make scaling more aggressive or fix different values for different steps..

I don't want to provide all those 3 methods because it will make things complicated.

and of course, patience is a virtue :)
[Galaxy S II Original Android Development] wanam:
Great work man, i'm using your beta6 without any issue for now, and i think i will release today my new KI4 update with your beta6.

I understand you also, you must change your language :D.
[Galaxy S II Original Android Development] gokhanmoral:
wait for beta7 :)

it will be up in 10 mins.

but if your users doesn't modify the frequency steps you can use beta6...
[Galaxy S II Original Android Development] jonny68:
CheckRom Revolution 1.0 with Siyah 2.0 and my phone was deep sleep 98% last night and didn't drain whasoever, this is fantastic:D
[Galaxy S II Original Android Development] tvhak:
someone ..........
[Galaxy S II Original Android Development] nerotix:
@gohkan, any idea, pretty please?:) Would love to keep using this kernel, by far best arround!
[Galaxy S II Original Android Development] kapa75:
Yes it works!
[Galaxy S II Original Android Development] gokhanmoral:
undervolting may be useful if you use your device too much.

but even then, the screen dominates the usage...

although I have no scientific numbers, just based on my feelings I bet using 850mV@200MHz vs stock voltage would not make more than 10 mins of difference either with low or high usage...

and I don't think it is worth all those problems.
[Galaxy S II Original Android Development] bgx:
Ah OK now it works! Thx! It stays after reboot or need I a script?
[Galaxy S II Original Android Development] bala_gamer:
my lockscreen unlock issue has been solved in in beta 6. Gr8 going
[Galaxy S II Original Android Development] Gowind:
I'm still on v2.0. I don't know weather it's rom related or kernal related but I just cant flash anything right with cwm app. It use to work well till 1.8.

Also one more thing may be offtopic but I apologize beforehand. After I have inserted a new external SD card chainfire 3d disappears as soon as I reboot but a dirty gray dysfunctional icon stays on the screen.

Cwm app backup of the rom is saved automatically in the external SD card which can't be flashed with the cwm app.

I used to flash a lot of kernels but after I tried one of the earlier versions of siyah, never felt like going to any other kernal even for testing.
[Galaxy S II Original Android Development] gokhanmoral:
beta7:

default governor: ondemandx 100-1200MHz

frequency table modification bugfixes...

some config changes (android logger as module, disabled some unnecessary networking options...etc)
[Galaxy S II Original Android Development] gokhanmoral:
it reverts back to defaults after reboot.

but this is a good idea. I can use a non-volatile space to store the values :)

even the undervolting and some other configurable values...
[Galaxy S II Original Android Development] bgx:
Do it! You're the boss! ;-) Would be fine! ;-)
[Galaxy S II Original Android Development] bandit79:
with the ondemandX govenor i have the same issue as in the betas. In Screen Off Mode the Phone freezes @ wake up and turned off
[Galaxy S II Original Android Development] kapa75:
i'm trying to download the latest beta, but the folder "test" is empty :confused:
[Galaxy S II Original Android Development] gokhanmoral:
do not use UV.

and try beta7.
[Galaxy S II Original Android Development] gokhanmoral:
reuploading.
[Galaxy S II Original Android Development] RRibeiro:
Where can I get Beta 7?
[Galaxy S II Original Android Development] BoneMo:
http://www.gokhanmoral.com/gm/public/#1
[Galaxy S II Original Android Development] fasst:
2.1B7 with KI8

I'm I the only one with USB problems?

Can't find device. Came from 2.0 without any problems.
[Galaxy S II Original Android Development] gokhanmoral:
download it again :)

that is why I reuploaded.
[Galaxy S II Original Android Development] _cummoo:
Revo HD is running perfect here with Siyah 2.1 b7 Kernel !!

Phenomenal work, it rocks !

(Gok it was a very good decision not to release the beta's here, so we can keep the thread clean of noobish postings !!)
[Galaxy S II Original Android Development] bala_gamer:
Had the same problem, it was solved in beta 6.
[Galaxy S II Original Android Development] bandit79:
Not for me. I changes the voltages to default, i think but it freezes again

wake: 100-1200mhz ondemandX

sleep: 100-200mhz ondemand

io: vr

voltages

1.400 - 1.300 mv

1.200 - 1.275 mv

1.000 - 1.175 mv

800 - 1.075 mv

500 - 950 mv

200 - 950 mv

100 - 950 mv
[Galaxy S II Original Android Development] redbullman:
How do we download the beta? When clicking on the link on my phone, it goes to a page saying Ajaexplorer the web browser - but nothing else happens. Thanks
[Galaxy S II Original Android Development] gokhanmoral:
why do you use sleep profile with ondemandx?

it already has a screen-off profile with max 500MHz.

and that value is also customizable...

don't use any profiles and you won't have lockups.
[Galaxy S II Original Android Development] _cummoo:
plz try another browser, the javascript on that hoster-side is very tricky.
[Galaxy S II Original Android Development] bandit79:
Because the OC Deamon is installed. Ok i will uninstall it and try again.

The voltages are correct?
[Galaxy S II Original Android Development] gokhanmoral:
I cannot comment on voltages.

as long as you are not using stock voltages you may have problems.
[Galaxy S II Original Android Development] kwerdenker:
Well, except the "where can I download the beta" questions that is ;)

And for all those with stability issues: I have been running nearly every beta between 1.7.X and the latest 2.1.x and I never had *any* stability issue and never had to change anything in my undervolting or underclocking scripts.

In most cases the old userhelpdesk proverb "90% of computer problems occur in front of the monitor" still stands. So if you have stability issues, first revert any underclocking/undervolting/changes-at-all you might have enabled and then check if the error persists before posting here about it.

Also please try to remember what beta means: unfinished piece of software in the process of testing.
[Galaxy S II Original Android Development] fasst:
Weird issues with CWM 5 in recovery

When I chose install zip from sdcard, choose zip from sdcard, browse and chose external_SD I get nothing, no files.

When I chose install zip from sdcard, choose zip from internal sdcard, it actually shows external_SD with its folders.
[Galaxy S II Original Android Development] DimonDroid:
download stops at 4.6Mb :(((
[Galaxy S II Original Android Development] kapa75:
btw, which io scheduler do you recommand? :-)
[Galaxy S II Original Android Development] coolfire:
That's how it's meant to be, I guess. I get the same as well. :)

Sent from my SGSII
[Galaxy S II Original Android Development] bala_gamer:
Try removing the sleep profile. It might be the cause.
[Galaxy S II Original Android Development] bandit79:
Removing the OC Daemon and alls init files/ profiles and it wokrs now with ondemandX. Only Voltage Control without UV is now working.

Great work Gökhan! Thanks a lot
[Galaxy S II Original Android Development] fasst:
Ok, maybe a typo in CWM5 then, internal instead of external.
[Galaxy S II Original Android Development] tvhak:
so is there anybody how has changed 1600 to 1696. and how did you do it?

thanks tjeerdos
[Galaxy S II Original Android Development] psbt:
How should I understand this one? It means that we don't need to calibrate our battery or we just can't do it 'cause of the chip? Because in Calibration tab of Battery Monitor Widget the number it shows there seems a bit wrong to me, while they should be 1650, 4200 and 3330, they're just 1437, 4198 and 3440.
[Galaxy S II Original Android Development] gokhanmoral:
you should ask that question to google first.

my statement is clear enough. you DON'T NEED TO do any calibration.

but if you feel more comfortable do it...

I do trust maxim datasheets more than I trust battery monitor widget values...
[Galaxy S II Original Android Development] AndroidGX:
What's wrong with beta6 & 7 ? my confortable UV values always results a freeze 3 seconds after applying.

Back to beta2.
[Galaxy S II Original Android Development] tolis626:
Well,making scaling more aggresive won't do **** I think.It will worsen battery life and increase performance only a little,so defo not worth it in my opinion.

Fixing to a specific frequency...Well,won't that **** it up?We will either have to kiss battery life or performance goodbye,one in favour of the other.Not that I have a problem with sacrificing battery life for performance,but some will have.

So,that leaves us with the third option,which I think is the best.Fixing different values for different frequencies will let us pump performance up in high frequencies and boost battery life in low frequencies.

So,that is only my opinion,but please do consider it. :)

EDIT 1:Also,it'd be better if you make it a little harder to configure than CPU frequencies.That way,we'll avoid all those idiots asking why their phone freezes.

EDIT 2:Regarding undervolting stability.I too had some issues,which I narrowed down to being caused by the 200MHz step.All other steps are equally stable with 2.1 as they were with any previous kernel(Took a long time to find my devices limits,but it was worth it in the end),save for 200MHz which needed an extra 25μV.Stable as a rock now.Smartbench still tries to keep up! :D
[Galaxy S II Original Android Development] gokhanmoral:
somebody help me :)

I want to write Einstein's quote as an answer to your "my undervolting values are just great but this kernel has something wrong" question:

"It is harder to crack prejudice than an atom."

you should go back to stock.
[Galaxy S II Original Android Development] tolis626:
Which proves why Einstein was a genious.He had a good understanding of the idiocy of the world around him. ;)

Ignore these guys Gohkan.You can really spend your time doing something better than answering their questions.Leave insulting/answering to us! :D
[Galaxy S II Original Android Development] AndroidGX:
Just wondering why until your 2.1 beta 6 & 7 I never had this kind of problem.

I don't use SetCPU with profiles, just Voltage Control with UC. So the real question is : why on beta 2.1 b6 & 7 and not on any other versions of your kernel ? I have set some much agressiv values without getting any freeze until many hours, so yes definitely there is something to do with your kernel.
[Galaxy S II Original Android Development] Guetta1:
Gokhan, i thing now it's time for post 5 in this thread^^
[Galaxy S II Original Android Development] eukaryote:
Yep V2. I always underclocked it to 200mhz with ninphetamine, and managed 1% battery usage after 9 hours at night.
[Galaxy S II Original Android Development] yay1974:
well I don't know as much as you technically but the frequencies are different (150, 300, 500, 600, 800 900, 1000, 1200 mHz as default) and can be undervolted stably, it has good scores on benchmarks, has different kinds of governors as yours have. by the way he has released v 1.6 I don't know what is new there.

FOund it:

abyss 1.6 Changelog:

Add OndemandX Governor

Add Simple i/o scheduler

Add Tweak for Touchscreen
[Galaxy S II Original Android Development] gokhanmoral:
judge with the total usage time not by only overnight performance.

if you calibrate your battery it is possible that you will lose even 1% overnight, but after the calibration you may use 3% the next night.
[Galaxy S II Original Android Development] eukaryote:
Yea i usually get 1-2 days out of ninphetamine with a few hours of screen time. I'll find out in a day or two which one is better.
[Galaxy S II Original Android Development] gokhanmoral:
I will not increase frequency steps as he did. it has both advantages and disadvantages but I want to stay close to stock.

now in rc1, my kernel can be undervolted stably as well :)

adding governors are easy but tweaking them are hard and takes time.

I can add 10 more governors but I don't have time to tweak them all now.

I added ondemandx before but it wasn't so stable. maybe I will try to add it back since the performance was great.

smartassV2 is my favorite..

we also have SIO.. and also touchscreen tweaks to increase sensitivity.

well.. I don't follow his thread but obviously he is following mine ;) ondemandx..?. good choice...

however, I won't have respect for anyone who is hiding the source code and pretend like he owns the kernel...
[Galaxy S II Original Android Development] gokhanmoral:
if you find out that the battery consumption is the same with both kernels with the same configuration, can you also try to lower the CPU freq to 100MHz and underclock the GPU to 100MHz@850mV?
[Galaxy S II Original Android Development] :
Just keep up the great work and don't mind others. And keep tweaking smartassv2 ;).

I'm still waiting for someone to make a BFS kernel, I'll test it to hell and back :)
[Galaxy S II Original Android Development] sasho36:
Thanks for your great work! Much more stable now, 100Mhz@825mV and no lockups!

Just a little question, is it normal that this file (scaling_available_frequencies) isn't present anymore? It's needed by some apps like Daemon controller (easy for changing governors and min/max freq). It was there in beta2.

It's not a big deal, because it could be done with another app or script, but just wanted to know why it is missing.
[Galaxy S II Original Android Development] eukaryote:
Already doing that ;)

Not GPU underclock though. That can wait a day. Can't change too many variables at once otherwise it could be GPU making all the difference
[Galaxy S II Original Android Development] gokhanmoral:
let me check it... thanks for reporting.
[Galaxy S II Original Android Development] yay1974:
OK i see bro, can you please make a comparison of smartass v2 and ondemandx?

Can anyone answer please?
[Galaxy S II Original Android Development] gokhanmoral:
good idea :)

I will do it soon. very soon...
[Galaxy S II Original Android Development] Flasher8:
98 is kickass kernel..couldn't find 74 & 75...
[Galaxy S II Original Android Development] gokhanmoral:
if you use your device so much use smartass.

if you don't use your device much and don't want to have any lag at all use ondemandX (or ondemand with screen-off profile. they are the same) if you use your device much ondemandx will consume more battery power.

in any case, if you want more battery life use smartassv2 (my personal idea and experience).
[Galaxy S II Original Android Development] :
GREAT !!!
[Galaxy S II Original Android Development] skylinestan:
Not sure if this your kernel problem..i'm on cognition 1.5.1,when everytime i try to open root explorer the screen will just stay there & i can't touch the screen (totaly not functioning) have to restart my phone..have a quite few times in an hour..try others kernel but dont have this problem..& some more when i charge my phone the temp will rise to 44 degrees celcius...WTF...never have this prob in ragemod kernel or ninphetamine....hope u have a fix for it
[Galaxy S II Original Android Development] yay1974:
thank you so much for the explanation gokhan :)
[Galaxy S II Original Android Development] gokhanmoral:
kernel version, UV OC settings and any other customizations please?
[Galaxy S II Original Android Development] :
Check if you still have root, sometimes happenes. RootExplorer working fine over here.

Charging temp is normal, I used to get 52 celsius on Ninphe..
[Galaxy S II Original Android Development] kwerdenker:
After some tinkering here is a new beta-ish version of my undervolting script. I have rewritten to include a bit more of safety checks and to actually count the amount of speed steps, so it's little bit more robust to changes like the one in beta3. It's beta-ish because 1) I didn't have time to check it against all know kernel out there and b) it currently skips UV settings for the abyss kernel because that one has some very strange speed steps.

Would be great if some of you would be so kind to test this and report back if it works.

[!!]Always remeber to adapt the voltages to the ones suitting your setup[!!]

#!/system/bin/sh

#customize voltages to you values
#All Steps in MHz
#Steps are: 1400 1200 1000 800 500 200
NORMAL_STEPS="1275 1175 1075 975 875 875"
#Added Step is for max_step higher than 1400Mhz
HIGHER_STEP="1425"
#Added Step is for min_step lower than 200Mhz
LOWER_STEP="850"

echo "kwerdenkers kernel adaptive UV init-script active. Checking kernel for UV support..."
#Checking stuff
if [[ -e /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ]]; then
echo "Kernel supports undervolting! Checking frequencies table for number of speed steps..."
UV_COUNT=$(cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table | wc -l)

case $UV_COUNT in
6)
echo "6 speed steppings found"
echo $NORMAL_STEPS > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
;;
7)
echo "7 speed steppings found"
echo $HIGHER_STEP" "$NORMAL_STEPS > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
;;
8)
echo "8 speed steps found. Checking for Siyah kernel..."
if [[ $(uname -r | grep Siyah -) ]]; then
echo "Kernel found. Safe to use 8 step UV settings."
echo $HIGHER_STEP" "$NORMAL_STEPS" "$LOWER_STEP > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
else
echo "Other 8 step kernel found. Skipping UV for now for security reasons."
fi
;;
*)
echo "[!!] Found number of steppings with no correlating UV settings: "$UV_COUNT". No UV will be used! Please repot your kernel and the steppings to the author of this script."
;;
esac
else
echo "Kernel does not seem to support UV settings. Skipping UV."
fi
[Galaxy S II Original Android Development] eukaryote:
Don't have any instability issues here. Keep on going Gok!
[Galaxy S II Original Android Development] chadouming:
When we ignore , they ask there question again xD
[Galaxy S II Original Android Development] gokhanmoral:
because there was a bug in beta2 and that was making your device more stable while preventing the use of 100MHz most of the time.

I do not claim that beta6 and beta7 are bug-free.

I am really bored with all these UV whining...

if you have a crash blame your UV values first.

if you still have crash with stock values, then tell me.

I can just increase all voltages by 50mV internally and you won't even notice it...

maybe I should do that just to prevent this mess...
[Galaxy S II Original Android Development] ram3n:
Man,

I have been wondering the same question too,

so I did a thread about battery calibration, you should take a loot :

http://xdaforums.com/showthread.php?t=1312273 :)
[Galaxy S II Original Android Development] AndroidGX:
Ok I understand better, thanks for the answer :)
[Galaxy S II Original Android Development] ram3n:
Dude,

you're not the only one who has problems with UV settings using last betas.

Just let's hope It will be fixed soon.

If not happy, feel free to use another kernel until the next beta who will i'm sure rock !!

:p
[Galaxy S II Original Android Development] tolis626:
Yes,that's why I said we should start insulting people.Did you ever see how much idiotic posts decreased in Hacre's thread after he introduced post 5?Only fear of ending up in post 5 prevented many idiots from posting. :D

Exactly what I was saying man! :D
[Galaxy S II Original Android Development] karlesg:
+1

You might have a point there :p

Seriously now... no... You know that it would be wonderful to have a GUI for all that. I really hope that the voltage control guy keeps updating his app with all these new features. And as for the people who keep having problems and simply don't know **** what all these things stand for, they can always use a perfect kernel for them. CF-Root....
[Galaxy S II Original Android Development] AndroidGX:
But gokhanmoral is not idiot enough like you to do this. You are not in your own thread here, since when are you (and others) giving him orders ? If you want taking a laugh like a children, just go to post5 of Hacre's thread yes.. and don't stay here (please god).

Thanks for understanding.
[Galaxy S II Original Android Development] tolis626:
Φιλαράκι έχεις δίκιο,αλλά έχουμε γεμίσει μαλάκες εδώ.Χειρότερα από την Ελληνική βουλή θα γίνουμε! :p

Anyway,yes,you are right.It would indeed be cool to have a GUI to do these things.But bus frequency control is a more delicate matter.It's not CPU overclocking,it's overclocking every last chip inside the device.So that better be out of reach for those who can't even understand the simple things about CPU overclocking/undervolting. :)
[Galaxy S II Original Android Development] chadouming:
+1 for 5th post. Gok already have it ^^. Time for geek revenge on idiot people :D
[Galaxy S II Original Android Development] tolis626:
I wasn't speaking about you man,chillax.You asked one thing,but others have been asking about things that were answered just two posts before their posts.This is a plague for XDA.Don't take it personally,it was mere coincidence that Gohkan had quoted your post when I said what I said.My problem does not lie with you,so I am sorry if you were offended. :)
[Galaxy S II Original Android Development] AndroidGX:
Ok I thought you were attacking me ;)

No offense then, forget my post.