yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] seeARMS:
Beat me to it. :) I was working on an overclocked SpeedMod as well.

Good work.
[Galaxy S I9000 Android Development] freakonaleash:
1341,3034 at 1.2
[Galaxy S I9000 Android Development] dupel:
And mine e-penis is even larger!!

Seriously, stop benchamerks please.
[Galaxy S I9000 Android Development] manageri21:
is not for who's the biggest only too see the difference of the kernel and to try the smartbench, because i never trying them.
[Galaxy S I9000 Android Development] ludow:
Excellent work! Thanks mate. :D
[Galaxy S I9000 Android Development] xan:
It just had to be done ;)
[Galaxy S I9000 Android Development] xan:
Thanks, will surely help in some cases :)

In the beginning of next I will work for another release, I aim for modded recovery and some improvements in frequency transitions.
[Galaxy S I9000 Android Development] well.heeled.man:
Good work Xan. I have wanted to try a kernel that has a few of the features you have added to yours, but compiling an Android kernel is not something I have time to learn how to do.

I know you know this, but for others...

I reckon you could be on to something with the -Os (optimize for small size) optimization, as in Linux this is theorized to reduce cache misses and therefore increase performance. I am not sure how the cache is organized on an ARM, but surely smaller code would have positive implication for CPU load (battery life), even if it does not improve performance in the same way as it does on an Intel.

The preemptive kernel config reduces throughput on Intel's, but increases interactivity. This may reduce battery life, but will improve the user experience. A worthy experiment!

Would you consider applying the SLQB allocator patch at some point? It is in use in some of the HTC kernels and I recon could induce improved memory behavior.

http://www.phrack.com/issues.html?issue=66&id=15

Oh, and are you sure you wont go for a 600mhz step, then people can use you app to pick the steps they want. Any other steps seem redundant though (like 900mhz!), which I assume was your reasoning.
[Galaxy S I9000 Android Development] B34R_85:
Did you see CPU info in setcpu application??

The CPU never touched on above 1120Mhz..
[Galaxy S I9000 Android Development] edmondt:
This kernel works great! :) Been wanting UV/OC feature for a long time!

I'm currently Under Volting and Down clocking to 800MHz, does not feel much slower and hopefully I can get more battery life this way :)
[Galaxy S I9000 Android Development] davidf:
Hi,

This thread is now really irritating me, i have no interest in what your kernel does but becuase you are using hardcores version number in the title I keep going into it by accident. This is not K13c its a bastardised version, why not just call it something else and leave the credits to its origins in first post in the thread.
[Galaxy S I9000 Android Development] sniperviperman:
Will not allow me to overclock. 1000 is max
[Galaxy S I9000 Android Development] RolluS:
@davidf: Just after K13C there is a ] and after I can read Insane OC/UV Kernel, not SpeedMod... And this is the K13C source of SpeedMod with some improvement, and I know Xan and Hardcore have talked about it.

It's not a bastard like someone may do on a theme, it's a workaround, and because of there may be stability issues (alpha version) there's another thread.

Btw if you like SpeedMod you may try this one.

@xan really love your work, again, greetings ;-)

++

RolluS
[Galaxy S I9000 Android Development] RolluS:
Will allow to overclock up to 1280 mhz.

Have you xan@insanity in phone parameters / about?

Do you use latest Voltage Control?

++

RolluS
[Galaxy S I9000 Android Development] sniperviperman:
Installed darky 9.3 b3,this kernel and overclock tool.
[Galaxy S I9000 Android Development] oversim:
Have I to disable lagfix or, like HC kernel, can I install this over K13C?

Now I'm in ext4nj.
[Galaxy S I9000 Android Development] xan:
*Should* work, try -> if doesnt work flash back HC K13C, disable lagfix and try again :)
[Galaxy S I9000 Android Development] All Day On XDA:
Any OC or UV causes my phone to freeze with this kernel. the SO kernel was stable at 1.2 for me.

Im using version 3.01 of Voltage control. I see theres 3.03 in the market. Should I use that instead?
[Galaxy S I9000 Android Development] xan:
No matter, everything over 3.0 should work.

That is strange, all testers I've talked (and me) stated that its relatively stable.
[Galaxy S I9000 Android Development] All Day On XDA:
Well after numerous restarts I've got it stable.

The phone would freeze under these states:

ext4/ext4nj/ext4 - 1280 1200 1120 mhz

However switching to ext2 and limiting the oc to 1200 did the trick

I'm using your UV settings Xan and no deadsleeps either.

Fingers crossed its stable for the rest of the day.

Great job!
[Galaxy S I9000 Android Development] xan:
BTW I'm getting up to 2000 quadrant and ~17linpack - on 1200Mhz (data=ext4 dbdata=ext4 cache=ext2) with test release ^^

This is pointless I know, but looks fun.

I'm into clocks now, but when I increase MFC, G3D, G2D divider (S5P_CLK_DIV2) I cant observe any changes Oo

CLK_DIV1 0xE010_0304 R/W Set clock divider ratio 1 (Multimedia)

CLK_DIV2 0xE010_0308 R/W Set clock divider ratio 2 (Multimedia)

CLK_DIV3 0xE010_030C R/W Set clock divider ratio 3 (Multimedia)

I'm trying to modify dividers/clocks to make 1200Mhz stable for me.

What I've figured out by now is:

MFC, G3D, G2D is driven by APLL except 100Mhz when the clocksource is being changed to MPLL. This means it scales with frequency. (So OC CPU is related to OC GPU).

Divider applied by Samsung for this domain on all frequencies is 4. (@1000Mhz 3d/2d/mfc clock is 1000/4=250, @ 1200 1200/4=300!)

This is not what I expected, I thought the GPU works @ 200Mhz. Thoughts?

//edit: I successfully underclocked the GPU -> On my device not GPU is responsible for lockups above 1120Mhz.

'research' done, shouldnt bother with dividers/clocks any more.

And yes, clock.c is real mess.
[Galaxy S I9000 Android Development] All Day On XDA:
Dam it - it froze again - with the 1.2 OC - specifically when I started a game (Gun Bros)
[Galaxy S I9000 Android Development] lgkahn:
Can someone enlighten me why we need this? Since galaxy tuner can temporarily overlook the std hardcore kernel to 1.2 ghz it obviously supports oclocking, so why to we need a custom kernel to do it.
[Galaxy S I9000 Android Development] DamianGto:
I hope you can sort it out and get it to work good.

You should also change the priorities on how the phone use the cpu.

Most if the time you only need to use max 800MHZ.

Maby if you put in 600MHZ you could get the phone use 100-600 more and save battery. You then also have the power when you need it.

In my kernel i use 100-800 in normal use. But if the phone need more power it use 1000MHZ.

This make it to use less battery without make the phone laggy.

If you could make it to 1200MHZ stable and without ov and have the 600MHZ in it to then it would make this phone very powerful and drain less battery then stock.

**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
[Galaxy S I9000 Android Development] dupel:
Time for more feedback, this time on battery. So far - its is much better than on any OC kernels I tried before.

When not in use (just lying around) battery consumption is equal or even a bit smaller than speedmode (best in battery life).

When in use (browsing) - uses slightly more than speedmode. Again, not as much as any other OC kernel. I would say (preliminary figure) uses about 3-5% more in an hour than speedmode. Which is actually about the same as stock kernel.

Everything else is stable, had only one freeze and that was playing with uv (so uv also works as it should).

Today will try to limit it to 1000 (no oc, just uv) and see how it behaves when in use.
[Galaxy S I9000 Android Development] oversim:
What about under volt to safe battery?

When my sgs will be 100% charged I'm going to flash this kernel.

But I'm interested to under volt rather than overclock, to (I presume) safe battery.

Any suggest? :)
[Galaxy S I9000 Android Development] °Dexter°:
Funny behaviour with linpack: when i used other oc kernels i always got the maximum value per test (around 16 mflops for 1200mhz,around 17.5 for 1300,around 15.5 for 1120,and so on)...with this kernel,set @1280,i rarely get 17.x mflops,sometimes 16.x,often 14-15...is it normal or did i do something wrong?
[Galaxy S I9000 Android Development] xan:
Good, that was the reason behind all of this :) Allow a little more sacrificing nothing.

UV = undervolt = Voltage Control app from market ;)

Hm, yes it jumps sometimes, might look into it, however thats not important (to me).
[Galaxy S I9000 Android Development] °Dexter°:
It's very smooth despite these "jumps",though
[Galaxy S I9000 Android Development] gon9999:
After a fresh install I only get 14 linpack and 1360 quadrant. No idea how you get this points :-{
[Galaxy S I9000 Android Development] sniperviperman:
Installed darky 9.2 again and it's working now. Stable at 1.2
[Galaxy S I9000 Android Development] TrOjAnUK:
xan has stated the figures are not important, what is important is the stability and "user" experience.. are you saying there is an issue with the phone like its sluggish?

TrOjAn
[Galaxy S I9000 Android Development] gon9999:
No, there is absolutly no problem. The phone runs great. I was a little bit confused about the different points at quadrant and linpack.
[Galaxy S I9000 Android Development] sniperviperman:
tried darky 9.3 beta3 again and it won't allow me to overclock. it's stuck at 1GHz and lower.
[Galaxy S I9000 Android Development] coldflid:
Thanks!

Going to try it :)
[Galaxy S I9000 Android Development] dupel:
You obviously haven't overclocked. You need to download xans app and apply what clock you want from there.
[Galaxy S I9000 Android Development] gon9999:
Iam running at 1280 !?
[Galaxy S I9000 Android Development] °Dexter°:
This is the "issue" i was talking about...if you take many tests you'll probably get some higher scores,but not constant.

It could depend on CPU scaling settings,but in everyday experience it's really good,so no big problem (and xan's scores are with lagfix applied)
[Galaxy S I9000 Android Development] well.heeled.man:
After a days usage I can say that the battery life is v. good, not amazing, but solid. However, forget benchmarks, my test is how smooth ADWLauncher is when scrolling, and this is very smooth.

Just a note on benchmarks, because there seems to be some fallacy that a higher benchmark score equals a better kernel.

Modifications for better responsiveness and lower latency will generally lower the Quadrant score, as Quadrant is more a measure of throughput. Most kernels are a trade off between responsiveness/low latency vs. throughput. Server kernels have amazing throughput, but I would not use one on a desktop as the percieved lack of responsiveness/high latency would be really frustrating (assuming the same hardware).
[Galaxy S I9000 Android Development] WiwiPouPou:
Hi xan, have you seen that ?

It's in vibrant section, somethings could interest you !

~ Now Overclock to 1.2GHz ( Removed all others until I find the source of the lag )
~ Clock settings ( 1.2GHz / 1GHz / 800MHz / 400MHz / 200MHz / 100MHz )
[Galaxy S I9000 Android Development] xan:
Ye.. It seems that there are no sources published.. changelog looks.. random.

Whatever.
[Galaxy S I9000 Android Development] All Day On XDA:
From my experience, I can say after 6+ hrs of no lock ups that using insanity 0.61 and this kernel is stable --but only with no overclock and a slight undervolt. I just can't seem to get a stable oc with this kernel compared to super optimized

I just received the momax 2700 battery so energy saving is not top priority for me anymore although it is still important.

Im looking for performance now - any ideas on how I can improve my chances of a successful oc? I really do like the look of the text, the color production and smoothness of this kernel

cheers!
[Galaxy S I9000 Android Development] xan:
Well, I wont put a kernel with increased voltages, so that way is closed.

OC code itself is looking quite stable, so no way here.

I have experimented with clocks/dividers, didnt observe any breakthroughs.

Hardware is limiting factor.

BTW: I'm working on extremely simple and reliable battery 'debug' tool.

It will definitely show IF (not why, unfortunately) the device has trouble sleeping.
[Galaxy S I9000 Android Development] RolluS:
Hi guys.

About battery:

For me I have an usual consumption, except that before it was 1% an hour, with a big drop (5/10%) when I wake up my device and use in few minutes.

Know with this kernel, consumption is like 3/4% an hour, but when using for few minutes it's few %.

I think it is more realistic.

But

I may be wrong because system process sucks CPU even when idle. I'm trying further test, without Tasker which I think it make system suspend/partial wake up to often.

Haha glad to see you here old man ;-)

++

RolluS
[Galaxy S I9000 Android Development] mucinch:
Freezes at the lockscreen after installation. Using SOK 4.7.9 with Doc Kitchen 9.6 ROM.
[Galaxy S I9000 Android Development] :
set up to max 1.2

how to know if it's running on 1.2 without setcpu?
[Galaxy S I9000 Android Development] TrOjAnUK:
Read the opening post? the answers there

TrOjAn
[Galaxy S I9000 Android Development] dupel:
Emmm, what?
[Galaxy S I9000 Android Development] :
i used voltage control

just wondering when will it utilise the 1.2 ghz setting
[Galaxy S I9000 Android Development] Alberto96:
Please unlock franerate in graphics. 60+ fps
[Galaxy S I9000 Android Development] theduckking:
He is only working on OC/UV so that hardcore can implement it one day

(xan, please correct me if I'm wrong)
[Galaxy S I9000 Android Development] xan:
Well, quite :)

Will try to make recovery better, but thats only kernel - related.
[Galaxy S I9000 Android Development] Rezou:
Just for information : what is the HZ value in this Insane kernel :p ?
[Galaxy S I9000 Android Development] tzyn:
Really good addon for the speedmod kernel. Great work!

I use the insane kernel since it was released on 23th because oc/uv-possibility was one thing i missed in speedmod kernel. My focus was more on uv to just save battery life. The kernel is very stable and fast for me. And no battery draining problem or something like that. If i think back to 2.1 without any improvements the sgs is so nice now (2.2.1 JPY / insane-speedmod kernel / lagfix ext4 data+system / all (R) Tweaks) and i dont want to give it away anymore - also thanks to the work of some nice xda members/developers.

I use at the moment max. 1120mhz with -75/-75/-100/-100/-100/-100 (tested with stability test/neocore and normal/extreme usage) and it's absolute stable and has a nice boost up in some cases. Furthermore it's so extremly responsive and smooth, no more lags. Really nice feeling to use the phone now. As scheduler i use bfq.

One idea for improvement (if it is possible):

Maybe you could add a setting in the recovery menu to delete the bootsettings. If you save the settings because you think its stable and suddenly it hang on boot, thats not a good feeling. I had it some hours ago withoug big changes of the old settings. I needed maybe 20 boots to come to the voltage control app to delete the bootsettings.
[Galaxy S I9000 Android Development] mcreego:
This kernel is a real bomb. I agree with you, if I think back when I bought Sgs it was a killer device with a terrible os implementation by Samnsung. Now with this devs works it's maybe the best android in the market.

Sharpness, color, lagfix conversion, oc, ov, sound improvement, gps fix, lowmemory kill, tweaks etc.. all from great devs like Xan, Supercurio, Hardcore.

Tank You All for make my Sgs a nuclear bomb:)
[Galaxy S I9000 Android Development] :
tried to use ur uv values. and i can't boot up lol xD
[Galaxy S I9000 Android Development] :
where is the boot settings stored? i gotta delete it, my phone kept freezing when booting up
[Galaxy S I9000 Android Development] dupel:
Very few phones can handle such values.
[Galaxy S I9000 Android Development] :
now i need find the boot settings which are stored somewhere and delete it. any idea where?
[Galaxy S I9000 Android Development] madmax916sps:
Are you sure?

test this settings, never done before ... first time on this kernel mod

and it works .... some stability ago with Quadrant and stability test from market (hope there are good run 40 minutes)

but what i edit i include more max mhz to 1200mhz and -50mV

still work

Thx xan do a great job
[Galaxy S I9000 Android Development] robertoxfb:
To clear the parameters of VC.

In /etc/init.d delete the file S_volt_scheduler
[Galaxy S I9000 Android Development] Gyunikuchan:
running stable on the settings below:

1200Mhz - 1275mV

1120Mhz - 1275mV

1000Mhz - 1225mV

800Mhz - 1150mV

400Mhz - 1000mV

200Mhz - 900mV

100Mhz - 900mV

gd job indeed !
[Galaxy S I9000 Android Development] nikosblade:
awesome work! Could you provide a bigmem version too please?
[Galaxy S I9000 Android Development] xan:
That is my next focus, however I'm struggling to compile the recovery properly....

About bigmem version... There wont be one. I see no sense in using one, especially with JPX code. It has no memory management problems (besides leaks, but this can be related to software).
[Galaxy S I9000 Android Development] k!pps:
Every kernel developer focuses only on CPU OC, or on memory improvements (like OneNAND) so what it would be to merge these two options to make the fastest Kernel?

Hej Xan is it possible to add to your Kernel function of swapping system area and program data memory to OneNAND? TEGRAK did it into his Kernel, and it made huge improvement. It makes the phone do 1700 Quadrant points with OneNAND and ext4 mode (without loops of course). Its speed can be felt in everyday use.

If there could be possibility to do the same here and moreover use stable OC (as it is now) there would become the fastest Kernel. What do u think Xan, is it possible to add this function to your kernel?
[Galaxy S I9000 Android Development] DamianGto:
I will try this on my next version when xan feels its ready. I will also try to use the recovery to make changes.

**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
[Galaxy S I9000 Android Development] dupel:
I haven't looked at what tegrak has done, but sounds like first ever lagfix that was used on our phone plus this is available in this and any kernel based on ultimate lagfix kernel since forever.

Not to mention that space for data is extremely limited - I would fit around 20% of my data on onenand.

And you need to use normal ext4 settings. This way you get 1700 without any movement.
[Galaxy S I9000 Android Development] betoNL:
Your signature got a lot better...

But your Avatar is still so damn ugly....it scares the clients :eek:
[Galaxy S I9000 Android Development] DamianGto:
Well that's how I look:-)

**DamianGTO Ultimate kernel V1. 350MB Ram. 600HZ. all ext2. Js5**
[Galaxy S I9000 Android Development] edgarpoe:
OOOoooo! Just what i was waiting for an OC'd Speedmod varient? Think i'll have it a go. I am, after all an OC junkie! More Power! ARR ARR ARR! (tool-man grunt)
[Galaxy S I9000 Android Development] dupel:
Okay, time for yet more feedback. This time on is OC actually useful considering we still have the most powerful smartphone on market.

Answer is yes, oc is good. Much better performance in browsing script-picture heavy websites and improovement in flash games (from mostly unplayable to playable now). Haven't noticed any improvement (big one) in day-to-day operations - only some animations are faster, just it.
[Galaxy S I9000 Android Development] DamianGto:
Do you feel it stable?

If you don't change any of the stock volt do it work good?

I do want this in my kernel but it has been so unstable in the past.

I think if there is some standard things that work it would be easy to put them in recovery. That would make it easy for people to use without make the kernel unstable.

My kernel is gold now so I'm looking on this very close. But in the same time I would never use it if I can't get it 99% stable and safe.

**DamianGTO Ultimate kernel V1. 350MB Ram. 600HZ. all ext2. Js5**
[Galaxy S I9000 Android Development] edgarpoe:
Holy crap that's fast! ok i know some people don't care about scores but:

Smart Bench - Prod. Index 1267, Game Index 2918

Quadrant - 1479

1.28Ghz, setcpu performance

Lagfix: cache - e2, all - e4

Guess we'll see how battery and apps like it.
[Galaxy S I9000 Android Development] Paz9:
i really enjoyed this kernel... until it started to restart my phone lol... :P
[Galaxy S I9000 Android Development] existz:
If its freezing on boot ..go to recovery and use adb shell...

adb shell

rm /etc/init.d/S_volt_scheduler
[Galaxy S I9000 Android Development] tzyn:
I dont need it at the moment but where is that option to get the adb shell in the recovery menu? Cant find it.

@DamianGto

For me it's absolute stable at the moment. No unexpected freezes, reboots or sth like that.

My moderate settings now:

1120mhz / -75 = 1225mV

1000mhz / -75 = 1200mV

800mhz / -75 = 1125mV

400mhz / -75 = 975mV

200mhz / -100 = 850mV

100mhz / -100 = 850mV
[Galaxy S I9000 Android Development] DamianGto:
Sounds good.

I guess its soon time to test it out.

But I need to know what has changed in the code from stock.

**DamianGTO Ultimate kernel V1. 350MB Ram. 600HZ. all ext2. Js5**
[Galaxy S I9000 Android Development] dupel:
Raspdeeps code was always stable. And it was refined several times since than. All instability was caused by users cpu.

So yeah, this is very stable, fast and battery efficient.
[Galaxy S I9000 Android Development] DamianGto:
No it was not. You can't blame user for all errors. I did try it and I did not like it for it was unstable. That's way it has been changed by some.

That's way I'm very curious what Can has done.

**DamianGTO Ultimate kernel V1. 350MB Ram. 600HZ. all ext2. Js5**
[Galaxy S I9000 Android Development] torredibabale:
can you tell me please what is your comparison instrument excluding the eye?

i only know benchmarks for testing sw and hw.......;)
[Galaxy S I9000 Android Development] dupel:
Even in this thread it was proven that benchmarks mean nothing, not to mention 25430 times in each of bigger kernel/rom threads.

And yet we still have someone who thinks they are good.

FYI I can get probably almost 3000 in quadrant and that configuration would be one of the slowest.

Emm, no it was. And I do not blame users - each CPU is different from another, especially in phones, as cpu is very integrated into chipset. So some cpu's can work ar 1.4 ghz and use -150 uv, while others can't be overclocked at all.

raspdeeps kernel was very much stable with no bugs (and I followed both eclair and froyo threads) to speak of. In SO it was broken several times with bad results, but even in became stable in the end.

So please don't spread such thoughts that oc is unstable here, or about anywhere else.
[Galaxy S I9000 Android Development] DamianGto:
Well if you think that its up to you......

**DamianGTO Ultimate kernel V1. 350MB Ram. 600HZ. all ext2. Js5**
[Galaxy S I9000 Android Development] LukeSP:
Since I have read speedmod thread, I have one question.

How can I know that UV code really works? Hardcore said that he already try to implement UV in his kernel but it looks like UV feature doesn't work. He tried to undervolt CPU to very low level but the system didn't crash.

Can someone really confirm this?
[Galaxy S I9000 Android Development] DamianGto:
I also had issues with it, but I guess hardcore and I made all wrong for the code work 100% says dupel......

**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**