yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] MZWiZard:
Seems like its almost there :) How about a 25mV bump in voltage at 1,2GHz ?
[Galaxy S I9000 Android Development] android53:
wake up lag fixed yet?
[Galaxy S I9000 Android Development] stoneyfordni:
i re flashed to 2.3 , quadrant score is roughly the same , give or take 20 points , but the main thing i will look out for is to see if it freezes when typing a txt message , my SGS has been doing this a lot since the OC kernel was put on the phone

il keep the site updated

and many thanks matey for getting right back into it

Stephen
[Galaxy S I9000 Android Development] dupel:
No problems in market or anywhere I could find (and I had before with swype).

Only problem (apart from wake up lag) - from time to time, when I left my phone to be idle for some time (few hours) it would just stop responding completely. To any actions. I had to remove battery to reset it.

Thats with 1.20v3 Will try 1.12 tomorrow (for now reverted back).
[Galaxy S I9000 Android Development] stoneyfordni:
phone became unusable today , if left for anything longer than 5minutes in idle it would refuse to wake up and needed a battery out reset. reflashed with stock jm5 now and alls sorted - no OC tho :(
[Galaxy S I9000 Android Development] raspdeep:
is oc112 any better?

im trying with different configurations of crosstool, kernel configs and see if wake lag can be fixed.. will report if i find something
[Galaxy S I9000 Android Development] FadeFx:
also expirienced this yesterday using 1.20.v3, then i uninstalled overclock widget, and everything back to normal... however, there is no possibility to use any overclocking tool anymore...
[Galaxy S I9000 Android Development] raspdeep:
wake lag fixed!

to those that use setcpu, do not set frequency too low especially when profile like power off.
[Galaxy S I9000 Android Development] bullemina:
Thanks... It´s works perfectly.... no wake up lag anymore.
[Galaxy S I9000 Android Development] Tayutama:
is the wake up lag also fixed in the unhelpful patch version? Or only in oc120v3?
[Galaxy S I9000 Android Development] FadeFx:
Too bad I'm at the lake atm, so no PC to flash...
[Galaxy S I9000 Android Development] xan:
Flashed oc120_unhelpful_patch over Rooted and Clagfixed JM5 with 30+ apps.

SetCPU 100Mhz - 1.2Ghz conservative.

Preliminary tests:

No wakeup lag.

Quadrant Scores around 2450.

Will see about stability.

Kernel version

2.6.29

jw@jw-ubuntu #3
[Galaxy S I9000 Android Development] dupel:
v3 seems to work fine so far. My guess is thats somewhat slower than earlier versions, but seems so far to be more stable.

Will report my findings in day or so.
[Galaxy S I9000 Android Development] android53:
Oc 120 unhelpful is AWESOME!

Phone feels so fast
[Galaxy S I9000 Android Development] bratfink:
Could you please release and UV version of your latest kernel that still has a top clock of 1ghz. Would be great to improve battery!
[Galaxy S I9000 Android Development] Mycorrhiza:
Does this work with the new, official jm1?
[Galaxy S I9000 Android Development] android53:
How about a 1.3 ghz kernel with wakeup fix! 1.2 works great
[Galaxy S I9000 Android Development] steffe.jst:
As a semi hard core overclocker on desktop all this does indeed interest me a fair deal. Out of curiosity though, what kind of temp increases are we looking at between stock and 1.2? For natural reasons mainly interested in the load temps.

Cheers.
[Galaxy S I9000 Android Development] supercurio:
Thanks for the sources

Edit : sources are incomplete :(
[Galaxy S I9000 Android Development] android53:
It would be a good idea to set a standard for temperature testing, i recommend setcpu stress test while not charging.

I get just under 50 degrees Celsius after 20 minutes at 1.2 ghz

Battery was cold to the touch so the temperature must be reading from the cpu?
[Galaxy S I9000 Android Development] stoneyfordni:
is this latest release 100% stable with no lag , I had to completely re flash my phone earlier after problems , odin wouldn't let me reapply a stock kernel after i reapplied the OC version . the phone just hanged on the Galaxy S start up screen.

I had to re flash completely to JM5 , apply root and lag fix etc then redo all applications/contacts

just don't want to have to this again on the back of another dodgy OC

look forward to comments

Stephen
[Galaxy S I9000 Android Development] dupel:
So, whats the difference between v3 and unhelfup mods?
[Galaxy S I9000 Android Development] stoneyfordni:
and can they both be used on v2.3 lag fix
[Galaxy S I9000 Android Development] dupel:
yes. Kernel and lagfix do not interact in any way.
[Galaxy S I9000 Android Development] raspdeep:
because the past kernels are overclocked on the buses too so causing instability..
[Galaxy S I9000 Android Development] raspdeep:
should work on stock eclair 2.1 ROMs
[Galaxy S I9000 Android Development] raspdeep:
other than the changelog. try and tell me if you do any benchmarking but i think the performance increase is negligible in real life usage.

coming up with a kernel that will support samset latest ROM
[Galaxy S I9000 Android Development] mekwall:
Clock wtf?

Okey, I'm having issues with the internal system clock with the unhelpful kernel.

I had the CPU underclocked to 100-600mhz with conservative governor while in sleep. This night I had it set at airplane mode and wheh my alarm went off the clock was off by 1460+ seconds (used ClockSync to compare and sync with atomic clock), which means the clock must have gone slower! So I turned off the underclock profile and set it to 100-1200 with conservative governor att all times. Checked it again, and it was off by 360+ seconds but this time FASTER!

This leads me to believe that the CPU clock is controlling the internal system clock as well why my clock is going slower when underclocked and faster when overclocked. Kinda funny eh? Just like the old computers :D

Does this have to do with the BFQ I/O perhaps? Because I didn't have this problem with the old v2 kernel. Haven't tried this with the v2.3 yet, but can do so later today...
[Galaxy S I9000 Android Development] DocRambone:
Confirmed: clock has strange behaviour with unhelpful kernel.....
[Galaxy S I9000 Android Development] mekwall:
Good that I'm noot alone!

I just did another quick test with the clock set to 100-1000 and it's still going too fast... Gonna see if it's SetCPU that is screwing with the clock.
[Galaxy S I9000 Android Development] DocRambone:
Seems as the oc120v3 have the same issue with clock lag... Screen lag became clock lag ;).

Edit: i am not using setcpu, i use

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;

to set max clock
[Galaxy S I9000 Android Development] mekwall:
Confirmed: It's when you turn off the screen and the phone enter sleep mode the clock will act weird. Just tried this and ended up with +4.7 seconds directly after waking it up.
[Galaxy S I9000 Android Development] raspdeep:
just tried v3 and it lag about 1-2 secs... then i flashed back to stock kernel and it also lags 0.5-2 sec.. doesnt really bother me if the lag is just 2 secs tho

but unhelpful patch was kinda way off.. need to check if he has the same problem or i missed something on the patch cos i removed some of the patches that changes the sound files which i dont think is relevant for our device
[Galaxy S I9000 Android Development] DocRambone:
Its an issue but lets hope it can be solved. Thanks for great work :)
[Galaxy S I9000 Android Development] mekwall:
Not correct. Do some more tests and you will notice that it offset by 3-4 seconds everytime you wake it up from sleep.

Stock kernel does not. However, ClockSync can show wrong so reopen a couple of times to be sure...

Sent from my GT-I9000

Edit: Sorry for being short-worded ;) was typing fast on the phone while commuting. Also would like to thank you for your time and efforts in creating this kernel!
[Galaxy S I9000 Android Development] FadeFx:
I'd also like to know that, and what's the advantage of unhelpful...
[Galaxy S I9000 Android Development] hubaaa3:
+1 :D

or is UV in oc112v1.2 or oc120v2.3 included ?
[Galaxy S I9000 Android Development] jodue:
@raspdeep: i am wondering what you did to fix the wake up lag? any special options in the kernel config? would be nice if you could share that because i have built my own kernel and have the wake up lag :D
[Galaxy S I9000 Android Development] setenza01:
You need to build with toolchain : ct-ng or buildroot
[Galaxy S I9000 Android Development] jodue:
hm, okay...i did use the toolchain from codesourcery (like probably everyone else) because they recommended it in the readme :D .. thank's a lot!! i will try this later... :)
[Galaxy S I9000 Android Development] OGC313:
What does the patch do?
[Galaxy S I9000 Android Development] raspdeep:
no yet.. will try later
[Galaxy S I9000 Android Development] raspdeep:
dont have to do anything on the patch.. its for those that want to build their own kernel
[Galaxy S I9000 Android Development] raspdeep:
i'll see if this can be fixed but based on another thread, stock kernels also have same problem?

http://xdaforums.com/showthread.php?t=762337&page=2
[Galaxy S I9000 Android Development] lsevald:
RockPlayer seems to run stable under oc120v3 and wakeup lag is gone, thanks!
[Galaxy S I9000 Android Development] DocRambone:
I used the 1.2v3 kernel for some time, seems ok (no lag, clock or wake) when i use it without setcpu...
[Galaxy S I9000 Android Development] Laum:
And you used setcpu to overclock the cpu?
[Galaxy S I9000 Android Development] DocRambone:
Yes, setcpu shows 1130, but know from kernels for Nexus and Desire: what setcpu shows is not always true.
[Galaxy S I9000 Android Development] android53:
testing this, unsure if its actually working.

From my limited understanding the cpu clock will only work at specific frequencies (100,200,400,800,1000) using a multiplier. is this frequency supported?
[Galaxy S I9000 Android Development] madduckuk:
takes an age to come out of standby :(
[Galaxy S I9000 Android Development] riwarren:
thats not entirely true. The cpu frequency is determined by the front side bus (fsb) multiplied by the cpu multiplier. so increasing the fsb effectively increases the cpu multiplier. increase it too much and you'll need an increased voltage to the cpu. What you effectively want to do for maximum performance, is to drop the cpu multiplier, and increase the fsb dramatically. however, this is very difficult to get stable and requires increasing the voltage to the cpu, but, the overall performance is much better at lower cpu multipliers.
[Galaxy S I9000 Android Development] riwarren:
You also want the ram frequency to be in sync with the front side bus for maximum performance.
[Galaxy S I9000 Android Development] Tundraswan:
*cough* Benchmark! *cough*
[Galaxy S I9000 Android Development] android53:
benchmarks haven't changed. it didn't work

All it did was cause the screen lock lag like the samset kernel

Setcpu shows the new speed, but it has no effect

Linpack still 8.5 max

Quadrant still 1700-1800
[Galaxy S I9000 Android Development] android53:
the kernel screen lock lag is still there even after a nandroid recovery...damn!

re flash time
[Galaxy S I9000 Android Development] raspdeep:
Not sure if the mod for M110S actually work? I changed it to 1.2Ghz per the post and rebuilt

Added JM2 stock kernel for reverting
[Galaxy S I9000 Android Development] INeedYourHelp:
is there a program besides setcpu that tells the ghz of the cpu?
[Galaxy S I9000 Android Development] raspdeep:
there are information in /proc/cpuinfo

so apps just read from there i supposed
[Galaxy S I9000 Android Development] DocRambone:
Still no performance increase with the latest kernel.

BUT, the wake up delay seem gone :)
[Galaxy S I9000 Android Development] INeedYourHelp:
Are you saying that 200mhz results in absolutely no improvements in benchmarks? not even by 1 point?
[Galaxy S I9000 Android Development] flyguy729:
why my phone stuck at the boot screen after flashing this kernal? :(
[Galaxy S I9000 Android Development] INeedYourHelp:
are you using JP2 or JP3? Froyo firmware will not work with this kernal.
[Galaxy S I9000 Android Development] flyguy729:
JP2! but im using samset rom wf his apps2sd fix kernal... any effects?
[Galaxy S I9000 Android Development] INeedYourHelp:
This kernal is not for JP2 at all. doesn't matter what rom you are using.
[Galaxy S I9000 Android Development] flyguy729:
So sorry. What i meant was JM2! Im using eclair not froyo. When i flash this kernel i got stuck at bootscreen. When i flash back to samset's custom kernal it boots back. I flash to the stock kernel also works. but not this kernel.
[Galaxy S I9000 Android Development] raspdeep:
in OC113v2 and up, i've added ext4 and mimocan's mod which requires an ext4 partition.. If you don hv that, it will hang..

u hv to use OC113v1 which i've took out, i'll post it up in 10 mins
[Galaxy S I9000 Android Development] raspdeep:
good to know, i've updated first post to indicate this
[Galaxy S I9000 Android Development] dupel:
Indeed works without any problems so far. Use setcpu.
[Galaxy S I9000 Android Development] xan:
After some more testing I noticed that gpu part might not be as stable as we thought. Launching Asphalt wjth 1.2 causes freeze after 0.5 secs of rendering. 1.0 works ok. Same with Quake3 port.

Update:

Lol after I woke up I noticed the clock being to early - 2hours! Wtf xD May be not related, but I'll keep an eye on it.
[Galaxy S I9000 Android Development] justin82:
I can confirm this. It seems pretty stable (some random lockups, but not much), but it always freezes when using Google earth. Skies of glory on the other hand runs stable...

Using JM5 and OC120V3
[Galaxy S I9000 Android Development] mekwall:
No I'm afraid it's not the same problem. The clock is getting a positive offset by 3-4 seconds every time the phone is woken up from sleep. This means that if you lock, wake up, lock wake up, lock wake up ... will have a positive total offset of around 12 seconds or more...

If it stays in sleep for too long it will instead go slower then the normal clock resulting in a negative offset.
[Galaxy S I9000 Android Development] raspdeep:
which kernel? please read post #1 for known issues
[Galaxy S I9000 Android Development] raspdeep:
which kernel? ive checked that without setcpu, the clock lag is pretty much gone.
[Galaxy S I9000 Android Development] mekwall:
Well I had the problem with both the Unhelpful one and v3

I've just flashed to JM6 so can't test to confirm if removing SetCPU will solve the problem. Would you mind compiling the JM6 kernel with your patch? :)
[Galaxy S I9000 Android Development] DocRambone:
After almost a day without setcpu and with 1.2v3 kernel: no time lag. So far so good

Nice work :)
[Galaxy S I9000 Android Development] raspdeep:
All the i9000 eclair 2.1 firmware uses 2.6.29 so u are good with current built kernel
[Galaxy S I9000 Android Development] raspdeep:
i've started going without setcpu and it solved the system clock lag problem..
[Galaxy S I9000 Android Development] raspdeep:
UV kernel uploaded for testing. Any suggestions how to test power consumption?
[Galaxy S I9000 Android Development] xan:
Unhelpful's
[Galaxy S I9000 Android Development] FadeFx:
hmm, i got absolutely no problem with this, either google earth nor asphalt 5 crashes for me at any time.

also i did not realize any time lag, but could be since i use overclock widget instead of setcpu...
[Galaxy S I9000 Android Development] xan:
Oc widget has issues detecting clocks. After setting it to 1.2 I got same asphalt/q3 freeze.
[Galaxy S I9000 Android Development] raspdeep:
did u flash it to oc120v3 or latest uv kernel? i cant do much on unhelpful patch kernel
[Galaxy S I9000 Android Development] xan:
Flashed:

oc120uv1

Wakeup lag present.

400,600,800,1000 stable.

1.20Ghz unstable.

Will flash other one.
[Galaxy S I9000 Android Development] FadeFx:
raspdeep

do you think it is somehow possible to adjust voltage according to cpu frequency?

e.g.

100-1000mhz - uv

1200mhz - orig. voltage

>1200mhz ov

sorry if this is absolutely impossible, but i dont know a thing of kernel compilation...
[Galaxy S I9000 Android Development] tristecire:
Hi

Everyone here talks about fixes with Setcpu. I'm using J android hacker ( market-root needed), a paid app that i like very much, it can't boot anything but conservative, but once booted, you can select anything else, performance or ondemand, without any bug or surprises ATM.

I use it since about one full month, surprised anyone don't seem to

know it.

I like the way it displays what time your CPU spends in each frequency, too.

Hope this helps.
[Galaxy S I9000 Android Development] DocRambone:
No need to use setcpu other oc app. Install the kernel and oc will be automatic. Works beautifully :)
[Galaxy S I9000 Android Development] raspdeep:
setcpu has the info too on cpu time, those information is readily available in /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[Galaxy S I9000 Android Development] raspdeep:
possible but not necessary for the time being. i'll look more into that later
[Galaxy S I9000 Android Development] raspdeep:
Uploaded deadline and noop scheduler for testing
[Galaxy S I9000 Android Development] DocRambone:
I guess this is valid for android schedulers?

http://www.redhat.com/magazine/008jun05/features/schedulers/

Some more testing:

http://xdaforums.com/showpost.php?p=4810429&postcount=14

http://xdaforums.com/showpost.php?p=4813959&postcount=21
[Galaxy S I9000 Android Development] raspdeep:
cfq is better for harddrives but not necessarily better on NAND devices since we do not have the seek-time disadvantage that harddrives have. i think noop maybe a better choice
[Galaxy S I9000 Android Development] raspdeep:
i think the benchmarking is not accurate as it should be many small writes and reads.. like writing and reading 100 small files, etc.. in a real life system, there will be many reads/writes...

maybe try benchmarking using benchmark by softweg found in market place.. will need some time to test them all.. lol
[Galaxy S I9000 Android Development] stoneyfordni:
just flashed with the deadline version and scores are back up to 2500 circa points in quadrant with very little or no lag or crashes

so far so good

excellent work

EDIT in linpack how are people getting MFLOPs scores of 14k plus , mines currently doing 9.7k
[Galaxy S I9000 Android Development] android53:
15 + only possible with jit
[Galaxy S I9000 Android Development] FadeFx:
i guess this results from using jiteclair, the jit enabled dalvic vm for eclair...
[Galaxy S I9000 Android Development] android53:
unless someone has released a new version, the old one (nexus one port) made 90% of apps force close when used on our phone
[Galaxy S I9000 Android Development] android53:
just flashed 1.20uv deadline

seems fast, benches the same as unhelpful, no wake lag, unable to check clock lag yet

Does the stock kernel scale voltage? i would hope it does

I like the idea of it being undervolted at certain speeds, what i would really like to see:

100mhz-800mhz - undervolted

1ghz - undervolted slightly

1.2ghz - stock voltage

It would be really handy if we could eventually get a choice of voltage settings for those who need more voltage or those who can get away with less, would also like a 1.3ghz one to try
[Galaxy S I9000 Android Development] FadeFx:
hmm, didnt try it yet, but maybe linpack worked... afaik the jit in the jp(x) builds is not running propperly and so they dont score that either...
[Galaxy S I9000 Android Development] android53:
yeah the ported jit did work in linpack, that was about all it worked in. internet, quadrant, swype, everything else fc's
[Galaxy S I9000 Android Development] zimphishmonger:
The seems to be occuring for the Vibrant OC too, but I dont have SetCPU installed. Was there anything in the kernel that was changed to eliminate the "system clock" issue, where it was either too slow or fast?

Its occuring using JAC's OCv3 kernel, and Im assuming it uses a similar OC code.

Did anyone find a slolution besides removing SetCPU, because I already did that (Wasnt using it in the first place actually). ;)

Thanks!
[Galaxy S I9000 Android Development] raspdeep:
the cpu supports dynamic voltage scaling so i'll need more time to study how it works
[Galaxy S I9000 Android Development] raspdeep:
im not sure JAC is using who's kernel code. My code and unhelpful is different (see the patch source). there are some standard similarity but he added his tweaks like thresholds while mine is mostly stock.

a good test will be using my oc patch on stock files and compile to test..
[Galaxy S I9000 Android Development] zimphishmonger:
Thanks for the reply, raspdeep :). JAC actually used unhelpful's patch as well (as far as I know), so the issue may be the same. Did you figure out what was causing clock lag? I'd love to pass that info along to JAC if you've managed something, as few Vibrant users are experiencing it, so its hard to diagnose. (may also be because the OC kernel is fairly new)
[Galaxy S I9000 Android Development] raspdeep:
i would say just do the OC without tweaks and start testing from there..

the problem maybe inherently in the stock source code cos users were reporting clock lag on stock kernels (but very minor) and it got worst on froyo (but we all know froyo kernels are alpha quality)
[Galaxy S I9000 Android Development] zimphishmonger:
Ya, Im not counting the Froyo issues either, as its still super alpha. I also noticed a VERY slight lag using JAC's non-OCed kernel, but its extremely minor (+/- .7 seconds), so I am counting that as accurate. I did a few test to see how accurately I could reproduce the issue, Posted them at the below link. Probably all old info for you, but it was mainly to show the Vibrant folks whats happening.

Link: http://xdaforums.com/showpost.php?p=7829749&postcount=488

I posted the test in the Vibrant Kernel forum, so hopefully JAC will take a look at it.
[Galaxy S I9000 Android Development] raspdeep:
OC1.28Ghz uploaded. Last 1.28ghz attempt failed miserably.. Hope this is stable enough
[Galaxy S I9000 Android Development] xan:
1.28Ghz - freeze just after bootup (slide to unlock... freeze).

I had problems on 1.20, so it might be my particular device has no OC headroom...
[Galaxy S I9000 Android Development] raspdeep:
can u try the oc112 version? yes it has wake lag but i'd like to know if it works fine for u (except for the wake lag)
[Galaxy S I9000 Android Development] DocRambone:
The latest jm1 seem to have a new kernel. At least it wont work with the oc kernels.
[Galaxy S I9000 Android Development] gore1985:
1.28 works. no FCs. Quadrant 2800points
[Galaxy S I9000 Android Development] xan:
About 1.12 - works, no FCs no freezing in asphalt.

2400 quadrant.
[Galaxy S I9000 Android Development] android53:
2800 max quadrant with the 1.28 kernel

Im getting some strange results however, psx4droid hung once yet setcpu stress test gets no errors, could be that it was the emulators fault

I am also getting strangely low temperatures even when locked at 1.28ghz, are you certain you didn't drop the voltage at all speeds?

With your 1.20 deadline i was getting 45C working temps

now i am getting 41C
[Galaxy S I9000 Android Development] DocRambone:
Raspdeep: any chance you can make one more restore kernel?

I attach the zimage from I9000XXJM1 v3.
[Galaxy S I9000 Android Development] xan:
I got no problems with 1.20 Ghz in normal usage/stress tests, but some graphic-intensive apps like asphalt hang - so this might be GPU part related problem.
[Galaxy S I9000 Android Development] android53:
Maybe, but i dont think psx4droid actually uses the gpu much. its very unoptimized at this point...

Lol i can run asphalt 5 practically full speed at 200mhz, all that cpu power going to waste...

Raspdeep, does your OC kernel effect the bus speed, memory timings/speed or gpu speed?
[Galaxy S I9000 Android Development] lsevald:
oc120v3 was stable for two days for me (not a single glitch). Just tried oc128uv1, and instant freeze in RockPlayer, and Quadrant crashed 1 out 2 times.
[Galaxy S I9000 Android Development] dereknas:
Hi raspdeep, just to clarify. Currently I'm on Samset 1.9f without applying the lagfix but using ryanza's one click apk lagfix. Can I flash these OC kernels?