yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] :
Hi guys,

could someone briefly tell me how to flash this? Do I do it with ODIN3? If so, what section (PDA?, MODEM? etc.?)

Thanks!
[Galaxy S I9000 Android Development] raspdeep:
your zip file seems to be corrupted
[Galaxy S I9000 Android Development] raspdeep:
yes, shouldnt be a problem
[Galaxy S I9000 Android Development] raspdeep:
my first post stated to load my tar file in PDA.. leave the rest empty
[Galaxy S I9000 Android Development] DocRambone:
Its a a zimage file, just remove the zip extension
[Galaxy S I9000 Android Development] raspdeep:
our gpu is pretty fast..

only at 1.28ghz has slightly overclocked memory bus.. if you test only memory benchmark, you will see the rest of the clock remains pretty constant except @1.28ghz has it slightly higher
[Galaxy S I9000 Android Development] raspdeep:
ok, uploading now, give it another 10mins
[Galaxy S I9000 Android Development] DocRambone:
Thanks, this kernel seem somewhat different. Seems faster than the normal stock ones.
[Galaxy S I9000 Android Development] xedamen:
I think it's very good :)
[Galaxy S I9000 Android Development] stoneyfordni:
f£$k me thats sharp
[Galaxy S I9000 Android Development] dupel:
Tried the 1.20uv_nook kernel.

All works well and might be actually faster), except one thing - when I start playing music device stops responing in few seconds-few minutes. Every time with several players.

So, Not sure which part of kernel is to blame - will test other kernels.

UPDATE: Deadline seems to suffer from same issue, so for now I assume its undervoltage to blame.

Can we get a simple 1.20v3 but with nook?
[Galaxy S I9000 Android Development] raspdeep:
set it to performance @1ghz (stock voltage) and test if it has the same problem
[Galaxy S I9000 Android Development] dupel:
tried on uv_nook kernel. Worked without problems for some 10 minutes (havent tried longer).

But crashed again after setting lower.
[Galaxy S I9000 Android Development] MZWiZard:
Tried the 120_noop kernel a few hours ago, and rebooted a couple of times. So far its completely stable for me with no wakeup lag. :)

Im running JM5 - CFLagfix 1.70 - noled 0.7 - now added oc120_noop
[Galaxy S I9000 Android Development] MZWiZard:
Well, as that was completely stable, I'm now trying the oc128uv1 kernel ;)
[Galaxy S I9000 Android Development] MZWiZard:
And now it froze on me in quadrant and asphalt 5... Im back at 120_noop ;)
[Galaxy S I9000 Android Development] android53:
Got a second crash using your 1.28 kernel when listening to music and browsing the net, had to do a hard reset.

What is very strange is that it can sit stress testing for ages or playing games with no problems then it randomly hangs. Seems like a little more voltage is needed or something else is causing instability.

Also I am getting minor clock lag, a few seconds per day
[Galaxy S I9000 Android Development] raspdeep:
ok.. even 25mV lower makes a difference on your set.. I will try something later and see if it works better
[Galaxy S I9000 Android Development] raspdeep:
its hard to tell at which frequency your set is unstable.. if you say it hang randomly when in low load, it means the UV is causing it..

are you using setcpu? if so, see post #1 known issue for clock lag
[Galaxy S I9000 Android Development] android53:
I'm using overclock widget, set cpu always gave me problems on this phone.

I'll lock the cpu speed and do some testing

*Update*

Locking to 1280mhz running stress test (setcpu) while playing music in the background: crashed after about 10 minutes
[Galaxy S I9000 Android Development] dereknas:
Really want to try this but after reading what happened to FadeFx, I'm having 2nd thoughts now.
[Galaxy S I9000 Android Development] android53:
After testing 1.28 ghz for a while with stress test and music running in the background

1.28ghz : phone hang after 10 minutes

1ghz: fine

800mhz: fine

600mhz: fine

400mhz: fine

200mhz: fine

Maybe its because you overclocked the memory bus? or a little more voltage is needed. going back to 1.20 noop for now
[Galaxy S I9000 Android Development] raspdeep:
what exactly happened to fadefx?
[Galaxy S I9000 Android Development] raspdeep:
1.28ghz is just not for all device.. my phone run very stable at 1.28ghz so i thought it would be a try to release and see how well it works for others
[Galaxy S I9000 Android Development] dereknas:
Have a look at his thread.

http://xdaforums.com/showthread.php?t=764884

Not sure if it is really related to the OC kernel or really the hardware problem.

Which of the OC kernels do you recommend?
[Galaxy S I9000 Android Development] FadeFx:
I dont think the oc kernel did this to me, i guess this is a hardware defect i was already carrying arround since i bought the device. I remember i had sometimes problems that the phone did not give option to mount the sdcard when im did connect, despite it was set to masstorage mode in usb settings.
[Galaxy S I9000 Android Development] MZWiZard:
Ok, a small report back on the uv120_noop:

Its been completely stable after 24 hours usage. I did some asphalt, emailing, texting, browsing, recording hd video, etc... Not a single crash.:D

Temperature was at max 56 degrees celcius. Thank you so much, raspdeep!!:D:cool:;):D:D
[Galaxy S I9000 Android Development] android53:
56 is pretty hot, is that while charging?
[Galaxy S I9000 Android Development] rui.mamede:
uv120_noop crashes for me after a while in normal usage... guess my set doesn't like the undervolt? when i say crash i mean my phone hangs on the same screen unresponsive, then i press power for a bit and it reboots... happened twice, once reading mail and another time checking cpu history in systempanel

what kernel should i try?

btw, i'm using setcpu scaling conservative and now trying ondemand, using performance only for benchmarking (min 100 max 1200). shall i change something?

thanks
[Galaxy S I9000 Android Development] supercurio:
oc128uv1 [Experimental] works pretty well here

I can comment the undervolting part only, I did not tried to overheat the phone ^^

But sometimes being stable at undervoling is even trickyer than overclocks.

Well done

raspdeep. Do you have burn and other tools to validate stability at high clocks and varying frequencies ?

If not, we can take a look at the cross-compilation of existing cpu stability tests.
[Galaxy S I9000 Android Development] FadeFx:
if your device freezes it is moist likely that the cpu does not perform well with 1200mhz uc, so try oc120v3 (wake lag fixed) and see if this works good. if not you could still try oc112v1.2 (wake lag unfixed) and see if the device can cope with that. if so youd still have to wait untill raspdeep compiles a version without wake lag.
[Galaxy S I9000 Android Development] MZWiZard:
Actually, no. It was sitting in my car that was heated by the sun. Its usually around 39 degrees. :)
[Galaxy S I9000 Android Development] MZWiZard:
I would try uninstall setcpu as it did cause trouble on mine - and use overclock widget instead.
[Galaxy S I9000 Android Development] :
So, has anyone measured battery performace with a UV build? I have installed uv120-noop. Underclocked to 100-800Mhz - hoping for increase in battery life.
[Galaxy S I9000 Android Development] Unhelpful:
UV does not have an impact on performance, only on stability...
[Galaxy S I9000 Android Development] :
So UV isn't supposed to increase battery life? I wondered, because surely it simply draws more current if the CPU is undervolted?
[Galaxy S I9000 Android Development] dupel:
I dont think that undervoltage would change a lot. I mean cpu by itself eats not that much compared to antennas and especially display. And considering that undervoltage is pretty small and that cpu can save power pretty smartly - it probably causes more pain than gain.
[Galaxy S I9000 Android Development] katsuru:
im running XFJM6 atm, which kernel should i get to revert to stock ? :rolleyes:
[Galaxy S I9000 Android Development] rui.mamede:
uv120_noop crashes for me with both setcpu or overclockwidget, it does not crash in performance mode tho (1200mhz only). so it must be a UV problem

flashed oc120v3 a minute ago, hope it stabilizes :)
[Galaxy S I9000 Android Development] raspdeep:
in attempt to answer some of the questions:

1) operating temperature of our CPU spec goes from -25c to 80c

2) ondemand is not stable

3) i will try to build 15mV uv kernels for testing and hope at least 90% of users can use it without problems

4) i will build a 1.12ghz version with uv
[Galaxy S I9000 Android Development] rui.mamede:
raspdeep after some tests i think that my instability issues are due to setcpu at lower speeds and not because of the UV. I'm working with 400-1200 conservative now for a while without a problem. You did warn us about this setcpu low freqs problem but it would be nice to put it in first post, i had to read 48 pages to find about this ;)

PS: i'm not complaining, i love your work mate
[Galaxy S I9000 Android Development] android53:
Operating temperatures for the cpu may go up to 80c, but what about the rest of the components? Most pcb's and motherboards cant take much over 60c

I know for a fact that our battery temp reading isnt the battery. Question is where exactly is it reading from
[Galaxy S I9000 Android Development] raspdeep:
no problem, i've updated the first post..

i planned on trying something on the uv so i will probably release experimental binaries again.. i hope more can test and tell me how well it works.. i release something that works on my setup but i cannot tell how well it works on yours if you dont tell me..

also, i saw some freaky benchmarking using my oc1.28ghz kernel (3200ish). Sweet!!! since i flash my set constantly, i've given up on setting lagfix, etc, is 3200ish normal for 1.28ghz? i can raise it higher but i think the "dropout" rate for running stable will go up exponentially.. lol

adding more voltage settings are necessary for higher clock but it involves a lot of changes to the current code so i'll wait a little before doing.. also our spec says max voltage should be 1.31v so that doesnt sound promising at all :(
[Galaxy S I9000 Android Development] raspdeep:
most electronic components can take the beat, the heat generated from the cpu will heat up the components surrounding it but advance cpu usually has temperature sensor that throttle itself if the temperature gets too high.. ive not seen that on the datasheets but hey, its over 2400 pages so i will update if i find anything

how u know that our battery temp reading isnt from the battery? newer batteries with temp sensor readings are not unheard of
[Galaxy S I9000 Android Development] dereknas:
Sorry to ask again, but can I apply this OC kernel based on my current setup below? Plan to update with the oc120uv1_noop.

Samset 1.9F with Ryanza's one-click lag fix

Just want to know whether it will overwrite the Samset kernel or cause any problems because I do not update with fresh stock XWJM5.

Thanks again.
[Galaxy S I9000 Android Development] raspdeep:
if you use samset kernel with a2sd, you should stick to his kernel but if you just do his mod without the kernel, my kernel should work just fine.. i've sent him my oc build with his changes but he did not get back with me if he wants to release it.
[Galaxy S I9000 Android Development] dereknas:
Actually I used his kernel but without applying the AD2SD lag fix but replaced with RyanZa's one-click lag-fix instead.

So, can I say that I can update the OC kernel safely?
[Galaxy S I9000 Android Development] raspdeep:
if you used his kernel, the answer is no, u wont be able to boot.. but you can try.. if doesnt boot, then reflash back with his kernel
[Galaxy S I9000 Android Development] darkstar2k77:
Hi Raspdeep,

Thanks for all the good work, I been eagerly testing all the kernel and the deadline kernel crashed and I had to reflash.

I have a small request for a universal tun.ko kernel module. I could use some ssl vpn connectivity on the Galaxy S.

Cheers
[Galaxy S I9000 Android Development] jackiechan8:
Tried the oc120uv1 and oc120uv1_noop kernels, and both are very stable with my phone :) No problems during stress tests or playing games, nor running 100-800 mhz. So the uv works great on my device. Also didn't notice the clock lag (1-2 secs off, but that's normal)

Guess I'm just lucky to have one of those phones that handle the tweaks well :P
[Galaxy S I9000 Android Development] android53:
Well run setcpu stress test for an hour, get the 'battery temp' up to 50c then remove the battery and feel how cold it is! My battery is never warmer then ambient unless charging from 0%
[Galaxy S I9000 Android Development] justin82:
I tried all the new kernels. Here are my results:

Procedure: flash kernel --> boot --> fast reboot --> quadrant 3x --> fast reboot --> linpack 5x --> market download --> Google earth (my location and scrolling around for a minute or so) --> asphalt (1 lap) --> flash new kernel

Using fast reboot before benchmarking gives me the most consistent results.

Stock (JM1 rev3, one click lagfix APK 1.5, no OC programs)

Quadrant: 1990, 2217, 2138

Linpack: 7.282, 8.144, 8.239, 8.239, 8.228

Google earth: stable

Market: stable

Asphalt: stable

Oc112v1.2

Quadrant: 2374, 2456, 2429

Linpack: 8.376, 9.148, 9.195, 9.224, 9.229

Google earth: stable

Market: stable

Asphalt: stable

Oc120V3

Quadrant: 2420, fail (3d benchmark), 2412

Linpack: 9.778, 9.747, 9.819, 9.802, 9.817

Google earth: unstable

Market: stable

Asphalt: unstable

oc120uv1

Quadrant: 2392, 2543, 2142

Linpack: 9.787, 9.822, 9.819, 9.745, 9.841

Google earth: unstable

Market: stable

Asphalt: unstable

oc128uv1

unstable (it boots and freezes at pin entering screen)

Could you make the oc112 kernel with lag fix?
[Galaxy S I9000 Android Development] dupel:
Yeah, 112 and 120 but without uv (or lets try smaller uv) and with noop too.
[Galaxy S I9000 Android Development] redbull320:
Question

Hello I've a question.

my englisch is very ehmmm bad.

What is the newest kernel? Or the best?

Sry but I don't understand same futures!

Can someone translate it in german please?

Greetings and thanks
[Galaxy S I9000 Android Development] HazzBazz:
Enjoying this. On Uv 1.2, the bfs didn't seem perfect but I think its the way to go. Look forward to stable further undervolt with dynamic overclock when required forty gaming etc. but kudos on a great job so far, maybe speak to kingklick about the battery improvements, he made my nexus run smooooooooooth all day.

Just push the two projects and try them together, but undervolt will go down a treat what with thee pour poor battery life, and dynamic clocking for lower processes like browsing!

Sent from my Samsung Galaxy S using the XDA App.
[Galaxy S I9000 Android Development] MZWiZard:
I have now run the uv120_noop kernel for 2 days. Its still working like a charm. Battery life seems a bit improved :) No reboots and I just ran 3 quadrant tests (attached one). Score sits around 2400 - and im running no taskmanager or overclock tools.
[Galaxy S I9000 Android Development] KLoNe1:
Can you use this use this kernel over the SAMSET kernel? I assume it writes over the SAMSET and it goes back to default (or whatever OC/UV kernel sets).

Thanks.
[Galaxy S I9000 Android Development] raspdeep:
just upload oc112uv1 and oc120uv1.1 for those that have uv kernel issues, please try and let me know if this works better
[Galaxy S I9000 Android Development] raspdeep:
try any stock kernel, it should not matter much
[Galaxy S I9000 Android Development] raspdeep:
i just answered this question on previous page
[Galaxy S I9000 Android Development] rui.mamede:
As i said i'm now using uv1_noop without a problem. I didn't uninstall setcpu, I just set my range of speeds from 400-1200 and that solves my problem. I guess it wasn't UV related after all... But i need more hours of testing and then i'll report here.

What improves are there on oc120uv1.1 ? Would it be possible to release one with noop?

Thanks raspdeep :)
[Galaxy S I9000 Android Development] xan:
raspdeep, since u uploaded SGS kernel patched by Unhelpful, could you update it to patch-1.2 please?

Dying to see that interactive governor in action and to check clock-bug.
[Galaxy S I9000 Android Development] KLoNe1:
Thanks raspdeep, sorry for wasting your time.
[Galaxy S I9000 Android Development] raspdeep:
ok, interactive governor added
[Galaxy S I9000 Android Development] tristecire:
interactive governor added

thank you very much, raspdeep.

then, i left the fully working 1.28 for this brand new one.:)
[Galaxy S I9000 Android Development] xan:
Thank you!

testin: oc120uv1.1

Same 'asphalt and ****' problem. Interactive governor seems to work, it feels like device is runnin @ 1.2 all the time..

There is some interesting thing goin on about GPU clock tweaks.
[Galaxy S I9000 Android Development] dupel:
Both kernels when set at 100-800 conservative crash when playing music. So no change for me.
[Galaxy S I9000 Android Development] android53:
the interactive governor seems really snappy
[Galaxy S I9000 Android Development] raspdeep:
i cannot seem to download from github, can someone download the source and put up a mirror so i can build a unhelpful patch v1.2?
[Galaxy S I9000 Android Development] xan:
Benchmarks!

I did some benchmarking, using SetCpu, Linpack and Quadrant.

CPU set to desired frequency by SetCpu (eg 200mhz) by setting min and max @200mhz.

So...here are the results:

https://spreadsheets.google.com/pub...MEU4VmlhMkVZSVE&single=true&gid=0&output=html

Conclusions? Nice linear scaling. No bottlenecks. Maybe DRAM performance.

CPU doesnt go 100mhz? Scores for 100 and 200mhz almost identical.

UPDATE:

phone has random freezes, after more than 24hrs of use I noticed 3-5of them. One - refusing to wake up after long sleep (well, just after I woke up :P), and rest of them absolutely RANDOM.

I can run SetCPU stress test for minutes (and hours I guess, but what for?) and have no single freeze/error. I suspected this may be related to some lower freqs, but I tested ALL of them for some minutes. Maybe its related to clock change mechanics? Device seems to freeze more often at UI interaction than long, hard task.
[Galaxy S I9000 Android Development] justin82:
Cool!!!

The graphic benchmarks shouldn't scale linear unless the CPU was limiting the graphics.

This would mean that the frequency of the GPU goes up with the CPU and would explain why my phone is stable at 1200 MHz except in 3D applications. Isn't it possible to separate these the OC of the CPU and GPU?

BTW: oc120uv1.1 isn't stable for me(3D again), oc112uv1 is(at least with the couple of test I ran)
[Galaxy S I9000 Android Development] xan:
I think unhelpful has some insight in GPU clocks.

I wish I could compile his latest kernel for SGS, but we gotta wait for someone with greater knowledge.
[Galaxy S I9000 Android Development] Unhelpful:
Stock 100MHz reduces GPU from 200MHz => 100MHz, as well as reducing some of the busses and the voltage for peripherals. I/O and 2D/3D benchmarks will probably all suffer. I find the drop in SetCPU's marks a bit more curious, since those are CPU only afaik.
[Galaxy S I9000 Android Development] scheichuwe:
Using oc112uv1 my Galaxy freezes after entering the PIN. No response after minutes.

Tried oc120uv1.1, works very well so far.

I like the interactive governor. Thanks.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] xan:
Funny thing is: Got myself NFS:SHIFT - working good @ 1.2.
[Galaxy S I9000 Android Development] justanothercrowd:
nvm found a different issue
[Galaxy S I9000 Android Development] ardowz:
Not entirely happy with setcpu because my phone keeps turning off occasionally.. wanted to revert back to the original kernel but i dont know which one should i download from the 1st post of this thread. My phone's baseband version is DXJG4 so i dont really know which kernel should i use.. thanks!
[Galaxy S I9000 Android Development] gore1985:
oc120noop is killing my battery. had a drop over night from 70% to 40% without internet turned on. I'm using OverclockWidget and the 1.28GHz kernel works very stable without draining battery.
[Galaxy S I9000 Android Development] dupel:
I usually use mimocans kernel. It works with any firmware from what I have seen.
[Galaxy S I9000 Android Development] ardowz:
where do i find this mimocans kernel?
[Galaxy S I9000 Android Development] dupel:
Its the first topic on this forum =))
[Galaxy S I9000 Android Development] AndyCr15:
I'm a little confused by the list of several files at the beginning. In theory v3 is the latest and best? This doesn't mention uv though, is it undervolted?

(I'm on JG5 at the moment if it matters.)
[Galaxy S I9000 Android Development] xan:
I believe this is current:
[Galaxy S I9000 Android Development] dupel:
Most stable - 120v3. uv does not work for all perfectly.

New kernels are added on top of old, eg:

New

older

oldest
[Galaxy S I9000 Android Development] xan:
oc120uv1.1 - phone dies in standby. No matter what governor, interactive or conservative.

Reverting back to stock kernel.

(ir posting a lot here, hope its not confusing)
[Galaxy S I9000 Android Development] rui.mamede:
set the speeds to 400-1200
[Galaxy S I9000 Android Development] dereknas:
Shouldn't we be not using setcpu to control the speed and just let it run its own?

Btw, for the 120v3, it is running on stock voltage right to achieve the overclock and not higher voltage?
[Galaxy S I9000 Android Development] raspdeep:
new rev up with user configurable UV
[Galaxy S I9000 Android Development] dupel:
Just to clarity at the moment 120uv2 has

1) unhelpgul patch

2)interactive governer.

3) stock voltage, which we have to modify by ourselves

Im asking because dont really need uv and would like to have stock voltage.

BTW, can you add deadline scheduler to this kernel? From what I have read and tested it works best on our phones..
[Galaxy S I9000 Android Development] raspdeep:
yes stock voltage..

i've test deadline vs noop and deadline is slower by quite a margin.. did you do I/O test?
[Galaxy S I9000 Android Development] dupel:
got my answer to interactive governer (deleted that part from post).

ok, thanks for answering. You mentioned that voltage steps are 25. Is it okay to test, for example, 5 or 10? Cos I would like to find some uv that actually works for my cpu.

Another question about uv - is cpu undervoltaged only with "conservative" governor? Or with all?

I havent performed specific tests. Only "real life" usage. They seem pretty close (okay, nook is faster, if only by a bit), but I think deadline uses much less battery.

But havent performed tests, so its almost speculation on my part.
[Galaxy S I9000 Android Development] raspdeep:
any values out of the 25 steps may hang.. i suspect is the limitation in hardware resolution thats why samsung has voltage table for voltage range

only mod for conservative, interactive is not suitable for usage as it jumps constantly to max frequency.. unhelpful patch on interactive gov is not exactly accurate but i dont hv time to look into the details

noop uses least cpu because its simple fifo so theoretically yield better battery life
[Galaxy S I9000 Android Development] Unhelpful:
Yes, but the difference in CPU usage its not that significant, and anticipatory or cfq will handle multiple processes better.
[Galaxy S I9000 Android Development] raspdeep:
agree that antipatory (CM uses that iirc) or cfq is better for multi I/O requests but noop seems better in other ways depending on situations

power drain is significant over time.. for example using interactive gov, battery went from 80% to 40ish just letting it sleep overnight as cpu cycle drain battery.. maybe not significant for short time but it does over long time..
[Galaxy S I9000 Android Development] OrionBG:
Is it OK to use SetCPU again? You mentioned that some releases of the kernel have problems with SetCPU!