yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] android53:
testing your latest release, 25mv UVLF is fine, 50mv crashes

Previous (experimental) release

Had some long term stability issues with setcpu and the interactive governer. It seems that it occasionally gets locked at 100mhz causing the phone to go very slow untill you re-open setcpu

Also had some issues with mobile data refusing to connect, phone occasionally not connecting to sim provider unless i do it manually and crashes every so often. Did not have this with the other 1.2ghz uv kernels
[Galaxy S I9000 Android Development] android53:
Also getting the sound glitch again in your latest version.

When using setcpu whenever the cpu frequency changes you hear a bit of static

To test this open music player (with headphones on) and run a track that has long silent or quiet parts then start opening apps and using the phone. Or open setcpu and start changing the frequency, you should hear it

*Edit*

Also getting crashes when changing the frequency in setcpu too much... even without UV

Is this a problem with setcpu or the kernel...

*2nd Edit*

Also happens when setcpu is removed and overclock widget is used.

I had this problem with some of your earlier releases, then it was fixed, and now it is back in your most recent one.

Going back to oc120uv1_noop
[Galaxy S I9000 Android Development] raspdeep:
if UV not running stable on ur phone, leave it at zero.. not all phones can take UV.. my phone can run 50 UVLF and 50 UVHF all day long if i run 1.2ghz... at 1.28, i can only run 50 LF and 25 HF

I dunno if ur phone will run stable on setcpu, u just hv to test it yourself. Test it with and without setcpu by using overclocking widget
[Galaxy S I9000 Android Development] raspdeep:
can u test without setcpu using overclocking widget?

i've changed cross-tool but i hope that is not the problem
[Galaxy S I9000 Android Development] android53:
Sending from phone now after reverting to 1.20uv noop

Sound glitch is 100% GONE

It's definitely a problem with your latest kernel.

My phone has no problem with 25 or 50mv undervolting but in a proper stress test will fail at 50mv

Try locking the speed in setcpu and run the setcpu stress test while playing music in the background for a while

*edit*

I dont know why running the music player at the same time as setcpu makes such a difference, without doing that i can run the stress test or benchmarks all day with no problems, but when used with music playing it is either causing instability or revealing it
[Galaxy S I9000 Android Development] raspdeep:
1.20uv noop only does 25mV UV..

let me build using old tool-chain and let u test.. give me 20mins
[Galaxy S I9000 Android Development] raspdeep:
try this and see if the music glitch go away
[Galaxy S I9000 Android Development] android53:
Ok will do later
[Galaxy S I9000 Android Development] HazzBazz:
Meh instructions how to undervolt anyone?
[Galaxy S I9000 Android Development] dupel:
I started thinking about the problem I have with uv (phone hangs while playing music) and I had an idea:

I think the problem is not in the CPU itself. I never had any problems with uv as most people I have seen here - all problems come from reading either from internal SD card or in my case external card.

What if problem is in some bus voltage/clock?
[Galaxy S I9000 Android Development] raspdeep:
do u hv adb? you can use adb to change the UV values

> adb shell

# echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV

the buses are not overclocked in 1.20uv kernels..

when playing music, what are the frequencies running?
[Galaxy S I9000 Android Development] HazzBazz:
yes got adb...

...#echo 25 uvs by 25 mV?
[Galaxy S I9000 Android Development] dupel:
From what I have been able to test (as playing music cant be really considered a test) it only crashes on less than 1ghz. However, I have no problems with any benchmarks, asphalt 5 or set cpu stability test.

I will probably try to test a bit more, now that I can remove uv by simply restarting.

Btw, what adb should tell after command/how to check that uv has been applied?
[Galaxy S I9000 Android Development] raspdeep:
cat /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV
[Galaxy S I9000 Android Development] dupel:
ok, ths. Should have though of it myself... =)

EDIT. Well, I can say that changing voltage by 10 crashes device immediately. Will try other even, but probabl wont work as you have said.

EDIT2. All other non 25 steps hang device pretty quickly...
[Galaxy S I9000 Android Development] OrionBG:
raspdeep, I have some questions!

1. Can somebody tell me when are uV values applied? (immediately or something must be done after editing the files)

2. After restart the two files are "0" again! What lines should be added to to what scripts for the values to be permanent?

3. What is the Default governor? Conservative or Interactive? (the uV values work only in Conservative right?)

4. If not using SetCPU (because of the hangs) how can the current governor be selected?
[Galaxy S I9000 Android Development] dupel:
1) Imminently.

2) If you have any of the lag fixes (one clock) than you should have the file mentioned in first post. Don't remember where it is stored, but if you search forum for it you'll find it.

3) I think by default (samsung standard) it is on demand.

4) I dont think you can. A few pages back someone mentioned another program, but I haven't used it, so cant really be sure.
[Galaxy S I9000 Android Development] rui.mamede:
I'm now testing oc120uv2.tar, you are working fast raspdeep :)

However my phone shuts down when i try to UV it by 50mV, I'm currently undervolting low freqs by 25 just as before and it seems ok...

I'll try do UV high freqs now as well (25mV ofc) and then report
[Galaxy S I9000 Android Development] OrionBG:
1 and 3 can't coexist! I mean that if On demand is the default governor the uV setting won't be active until you switch the governor to conservative! And how to use SetCPU to control everything when it crashes the device? Every time i leave the SGS on standby for a longer time it won't wakeup any more!
[Galaxy S I9000 Android Development] tristecire:
select cpu governor

To dupel

I use "j android hacker", paid app from market

You must open it after boot and select the governor you want.

Mine is always conservative by default.

hope this helps
[Galaxy S I9000 Android Development] OrionBG:
I'll take a look
[Galaxy S I9000 Android Development] rui.mamede:
Ok i guess the major problem with this new kernel is that we lose the UV configurations when we reboot the phone, and have to apply them again...
[Galaxy S I9000 Android Development] Unhelpful:
Just apply them in a user init script?
[Galaxy S I9000 Android Development] rui.mamede:
Could you pls help me do that? :confused:
[Galaxy S I9000 Android Development] xan:
oc120uv2-ctng

Test scenario 1:

I set like 100-100Mhz (min=max) using OC widget:

100 and 200Mhz stable @ -100mV (need further testing).

Test scenario 2:

I set like 100-200 (min-max)Mhz

Freeze @ -50mV

I feels like most freezes are when changing steps, not when running on one freq.

Governor isnt active when min=max, I just found this myself. I could set -100mV@1.2-1.2Ghz and run smoothly xD Didnt know that.

BTW

Simple app to set voltage incoming soon.
[Galaxy S I9000 Android Development] android53:
I too am getting strange results...

I can stress test for hours but playing a bit of music while using the phone causally causes lockups.

It may be an issue with when the cpu frequency changes
[Galaxy S I9000 Android Development] raspdeep:
hi guys,

to help me understand the problem, can you pls provide these information when you see a problem?

kernel version: (eg oc120uv2-ctng)

UVLF setting (if kernel supports): (eg 50)

UVHF setting (if kernel supports): (eg 25)

descriptions:
[Galaxy S I9000 Android Development] raspdeep:
that will be nice :)
[Galaxy S I9000 Android Development] raspdeep:
please wait for xan's app or if not, i will give another easier solution
[Galaxy S I9000 Android Development] raspdeep:
1. immediately

2. ask your lag fix author where is the userinit.sh file and add the echo command at the end of the userinit.sh. before you add the commands, make sure your UVLF and UVHF settings run without hanging, it will be a disaster if it doesnt run and cause hanging every bootup (which means you are screwed).. or wait for xan's app or i will come out with another better solution

3. default is conservative (so you dont really need oc apps if u dont want to)

4. only in conservative for now..
[Galaxy S I9000 Android Development] rui.mamede:
kernel version: oc120uv2

UVLF setting: 25 (50 makes the phone crash a few seconds after)

UVHF setting: testing 25 atm...

descriptions: 25 on UVLF works great for me, i just need to uninstall setcpu or use 400-1200 freqs. It's a shame that setcpu crashes the phone at lower freqs, i gave it a 1* star rank till they fix this
[Galaxy S I9000 Android Development] raspdeep:
you can try overclock widget since setcpu gave you problems?
[Galaxy S I9000 Android Development] rui.mamede:
I've tested it with oc120uv1 and it was the same thing, and its not setcpu either... Just got a crash with both uninstalled, although it lasted longer than before... It seems my phone just can't handle low freqs and undervolt
[Galaxy S I9000 Android Development] raspdeep:
can someone that recently done c language tell me what is the answer to this:

int x;

unsigned int answer;

unsigned int somenumber;

somenumber=1000

x= -50;

answer = somenumber - x;

what is answer?

sorry, it has been over 10 years since i last touch c programming so some details are forgotten :p
[Galaxy S I9000 Android Development] rui.mamede:
950 i guess? unsigned ints..
[Galaxy S I9000 Android Development] Unhelpful:
1050 on any reasonable platform with all values the same size. Addition and subtraction are entirely unaware of sign on most modern processors, sign only really matters when extending a small value to a larger size, or doing multiplication or division.
[Galaxy S I9000 Android Development] raspdeep:
the unsigned part is very clear extending the negative numbers to positive.. what was unclear is doing a minus negative value... answer = 1000 - -50..

if what you said is what i think it should do, having negative values in the UVLF or UVHF will do an overvolt.. which was my intention without controlling the negative values for overvolt.. but that is also dangerous some users may damage the cpu if they go crazy overvolting pushing way over the electrical specification of the chip that i did not explain in post #1..
[Galaxy S I9000 Android Development] Kryston:
oc128uv1

using this since yesterday, works like charm, tempreture has not much increased, no freezes till now, quadrant works fine, no clocklag.

So in conclusion this works prettey good, i will stay on that for now. =)
[Galaxy S I9000 Android Development] raspdeep:
voltage wont change when you are set on one frequency. For instance, the voltage at 1.2ghz is 1.3v, if the frequency does not change, the code that does voltage scaling doesnt get called so voltage stays as is.

Another scenario that 100mhz and 200mhz is running at .95v (stock voltage table) so changing frequencies between 100-200mhz will not cause voltage to change also because it checks previous voltage vs new voltage if equal, it wont adjust voltage.

i hope that explains what you saw from your test
[Galaxy S I9000 Android Development] xan:
Yep it does, indeed.

I've made BASIC app to control voltage settings with provided commands.

You can set voltages by just moving a slider and applying them.

It is not able to read current voltage vales.

It cant save settings as user init.

My first app, expect many bugs.

I declaim any responsibility, blah blah. - usual drill.

Works for me™

NEW VERSION http://xdaforums.com/showpost.php?p=8014572&postcount=594
[Galaxy S I9000 Android Development] raspdeep:
sweet! it works.. maybe cat the values and display on slider during program start?

i will add this to first post!
[Galaxy S I9000 Android Development] xan:
I was working on this a lil, but I got problems getting console outputs...... will try again.

(any advice appreciated)
[Galaxy S I9000 Android Development] android53:
Finally got round to testing that kernel you made me.

Sound glitch is fixed on it, haven't undervolted yet though
[Galaxy S I9000 Android Development] HazzBazz:
quiet.....
[Galaxy S I9000 Android Development] DocRambone:
Raspdeep: time to implement the new lagfix in your oc kernels...?

Please ;)
[Galaxy S I9000 Android Development] mekwall:
+1

This is the only thing missing now!
[Galaxy S I9000 Android Development] xan:
Hm, u might actually try the following:

-flash voodoo kernel.

-power on and wait till migration is done

-power off

-flash raspdeeps kernel

-see what happens ;]

These kernels have EXT4 support, so it could work. Or I'm simply wrong, what is more probable.
[Galaxy S I9000 Android Development] Unhelpful:
That isn't going to work without the modifications to init. A kernel with a stock init will rewrite the partition table, and will see what appears to be a valid RFS filesystem, but when it is mounted on /data there will be one huge file that takes up all of the space. It won't work, but boring another kernel will not lead to the loss of any data.
[Galaxy S I9000 Android Development] raspdeep:
i believed need to trick the vold manager to do that

i can check with supercurio and see what are the changes.. Also need to check with him if he's ready to release to public because he stated that it still in beta and for beta testers only.

meanwhile, can anyone pull /init.rc with adb and send me through PM?
[Galaxy S I9000 Android Development] Henrik313:
+1

with voodoo-kernel :D
[Galaxy S I9000 Android Development] mekwall:
http://github.com/voodoo-project/lagfix

Isn't this what you are looking for?
[Galaxy S I9000 Android Development] raspdeep:
i've spoken to supercurio.. i wont be releasing his fix until he approves it.. i will hv a build tonight for testing so if u want to try, go on irc :D
[Galaxy S I9000 Android Development] flyguy729:
hey thanks for the reply. But i have ext4 because im using samset's apps2SD fix kernel. My mem card has ext4 and fat32 partition. I dont see why i cant boot up.
[Galaxy S I9000 Android Development] INeedYourHelp:
the apps2SD fix is the not the same thing as mimocan's mod.

Are you using the standard JM2 firmware/rom, or with Samsets 1.8? I doubt it will work with Samsets roms. You will have to wait for the dev to add it to Samset.
[Galaxy S I9000 Android Development] flyguy729:
Oh, im using Jm2 with samset's rom and kernal... hmm.. ill try flashing to stock JM2 and add this kernal then, just to try it out. (:
[Galaxy S I9000 Android Development] raspdeep:
updated oc113v1.tar so u can try.. that is the basic kernel with oc, no ext4 support
[Galaxy S I9000 Android Development] android53:
1.2 overclock does not work. same linpack scores.

One interesting thing i found with the gpu from messing with setcpu that its quite cpu limited. Also we have a 56fps Vsync

In some of the quadrant benchmarks we will pull 56fps though even with the cpu at 400mhz. i wonder what our true neocore score is...
[Galaxy S I9000 Android Development] INeedYourHelp:
did you force it via setcpu to stay at 1.2ghz? (set it 1.2ghz for min and max)
[Galaxy S I9000 Android Development] raspdeep:
it could also be that our display is already cap ~56fps? maybe hv to try a benchmark solely on cpu integer / floating pt performance like cpu benchmark?
[Galaxy S I9000 Android Development] jaapschaap:
That's weird a 60Hz screen (on my computer) kan handle hundreds of FPS (i have a really good GPU) ;) The screen (Hz) has nothing to do with the FPS...

I think it is limited by software somewhere, or (gpu) drivers...
[Galaxy S I9000 Android Development] Laum:
It's called vSync. If screen fps is bigger than the refresh rate (Hz), tearing will appear. Galaxy S is fps capped because otherwise there would be tearing.

I simply hate tearing and use vsync always with my desktop.
[Galaxy S I9000 Android Development] karakake:
For those of you didn't get any improvement from benchmarks, you guys must did something wrong, as I saw people scoring over 2000 fron Quadrant after they applied OC to 1.2ghz + SDfix.
[Galaxy S I9000 Android Development] DocRambone:
No, quadrant can get over 2000 without any oc.

Better to use Linpack or BenchmarkPi to test pure cpu performance.

This OC kernel do not function properly.

I know there was a similiar issue with some Nexus kernels: set cpu shows oc without any performance increase. It was solved in some way i don't remember.

An idea for TS would be to contact some other dev:

http://xdaforums.com/member.php?u=397438

May give some help
[Galaxy S I9000 Android Development] karakake:
Just curious, How do you get over 2000+ without OC?? (and, of course, without froyo)

Plus, FYI, SGS scored around 10.2~10.5 from Linpack, according to those people who did OC to 1.2Ghz.

This OC thing originally came from a Korean dev forum, and I guess their kernel is working properly...? But their kernel is not working on our SGS since their model # is different. (i9000 vs SHW-M110S)
[Galaxy S I9000 Android Development] bratfink:
Voltage

Is anyone going to look into changing the voltages etc etc to increase battery life?
[Galaxy S I9000 Android Development] DocRambone:
But this kernel gives only 8,5 in linpack (with setcpu showing 1200mhz) so its clearly to fully functional.
[Galaxy S I9000 Android Development] android53:
You need to find out the speeds the processor supports. You can't just pick a number and expect it to work. There was a thread about this for the nexus one
[Galaxy S I9000 Android Development] INeedYourHelp:
Well that's depressing.
[Galaxy S I9000 Android Development] raspdeep:
try v1.1, linpack 10ish :)
[Galaxy S I9000 Android Development] android53:
If its the same 1.2 ghz kernel I tried a day or two ago, it doesn't work. atleast not on samset (without apps2sd)
[Galaxy S I9000 Android Development] raspdeep:
i've not tried the latest samset so i dunno what the problem.. im using stock firmware (JG8 atm) with root for testing and the v1.1 works..

benchmark:

linpack from 8.4 -> 10.2

cpubenchmark from 815ms -> 687ms

i will work on a fix later on custom ROM after i know it works on stock firmwares
[Galaxy S I9000 Android Development] android53:
i will try it. but i have flashed so many roms the past few days...

does it cause the screen to stay black for 3 seconds when waking the phone up from sleep like the previous kernel did?

Maybe its just a samset thing, can you try it please. then ill test it for you :P
[Galaxy S I9000 Android Development] dupel:
Any chance of getting a PM with new kernel (promise not to share with everyone). As I don't really use irc...
[Galaxy S I9000 Android Development] emelie:
Removed - wrong info in the wrong thread
[Galaxy S I9000 Android Development] redbull320:
hi,

i habe the jm6, and i dont want the oc bacause i want to amke the voodoofix, can i use the "Stock XWJM5 kernel for reverting"

or can someone give me a link for the stock jm6 kerneL?

Greetz
[Galaxy S I9000 Android Development] MZWiZard:
Well... oc120_uv2 works just fine by itself here. Ill try the undervolt app and see how it goes. :-)
[Galaxy S I9000 Android Development] rui.mamede:
what is the server and # ?
[Galaxy S I9000 Android Development] dupel:
Im pretty sure voodoo kernel will simply rewrite kernel, thus you wont have oc anymore.
[Galaxy S I9000 Android Development] dupel:
@ freenode - #project-voodoo
[Galaxy S I9000 Android Development] st3chn0:
what we be the best kernel to use on xwjm5 with samset 1.9f with Tayutama update zip ext4 mod too many to choose from dont know which to pick
[Galaxy S I9000 Android Development] raspdeep:
u can use jm5 for reverting and if u want to do voodoofix, then use voodoofix kernel will overwrite oc kernel
[Galaxy S I9000 Android Development] raspdeep:
xan's app works, u just hv to find the right uv for ur phone that works well
[Galaxy S I9000 Android Development] raspdeep:
use the latest oc120uv2 and xan's app to control ur UV.. try small steps until u find the sweet uv that ur phone likes without hang/crash..

with 50mV UV on UVLF, i get about 0.5% drop every hour when sleeping. my device used to average 1% during sleep time.
[Galaxy S I9000 Android Development] HazzBazz:
What settings worked for people? all crashed with me but I was messing around with things so I might try a fresh flash with some other settings
[Galaxy S I9000 Android Development] raspdeep:
every phone is different... if you set at 25 and still crash/unstable, there is nothing much we can do about it..

did u use xan's app to set? i would strongly suggest using that because at least i know you've put in the right value instead of wrong values causing it to crash
[Galaxy S I9000 Android Development] xan:
Ok another version of Voltage Control.

This time it CAN read currently used undervolt. More to come.

UPDATE: new version http://xdaforums.com/showpost.php?p=8033981&postcount=599
[Galaxy S I9000 Android Development] dwillMUFC:
Currently running JM7 with voodoo lag fix would i need to remove the voodoo to flash this kernerl?

Dan
[Galaxy S I9000 Android Development] xan:
Yep, you'll need to.
[Galaxy S I9000 Android Development] MOUSEY:
You can't flash this over at voodoo beta 1. You need to disable voodoo before applying this. Otherwise all your data would be stuck at the ext4 voodoo had created.

To disable voodoo, you need to create an empty file called disable-lagfix (with no extension) at the /sdcard and reboot. The reboot would take long as voodoo would restore and moves all your files over from the prior ext4.

Hope this helps those who are moving from voodoo (Actually I am doing the same thing now)
[Galaxy S I9000 Android Development] raspdeep:
this works nicely
[Galaxy S I9000 Android Development] xan:
And here goes another version. Same functionality as last time

+ now it can determine and set currently used scheduler!

EDIT: New version: http://xdaforums.com/showpost.php?p=8220475&postcount=738
[Galaxy S I9000 Android Development] raspdeep:
Thanks Xan, please put version number to your apk so its not confusing

Screenshot added
[Galaxy S I9000 Android Development] auggie2k:
Hi guys, any word of an overclock for for JPC Froyo 2.2 Build leaked recently?
[Galaxy S I9000 Android Development] FadeFx:
this wont happen as long as samsung does not release the source code, which will surely happen after official release of 2.2... so no luck for jpc for now
[Galaxy S I9000 Android Development] mafiaboy01:
Will this work on the Bell i9000?
[Galaxy S I9000 Android Development] dupel:
Cant wait to see a kernel that includes this awesome OC, noop (or any other that people think is better, I use noop for now), voodoo beta 2 and BackLightNotification. That would be SO awesome =)

Cos would really like the option for OC back, but just can't say no to voodoo.
[Galaxy S I9000 Android Development] FadeFx:
+1

have my galaxy sent for repair atm, but cant wait to get it back and test voodoo. hope there will be a oc kernel with voodoo support when i get my phone back...
[Galaxy S I9000 Android Development] raspdeep:
the app that xan wrote has I/O scheduler that you can use to change to noop.. VD2 will be in when curio_ release his build.. about backlightnotification, not sure if he will release his source code tho, i hv not tried it but if its a kernel binary, it should comes with source
[Galaxy S I9000 Android Development] raspdeep:
Voodoo beta2 out for testing!
[Galaxy S I9000 Android Development] MOUSEY:
I just flashed voodoo beta 2 and now can OC/UV it ! Wonderful ! Thanks ! :)
[Galaxy S I9000 Android Development] cba1986:
I have already installed voodoo beta2.

can I flash the voodoo beta 2 OC kernel over this?
[Galaxy S I9000 Android Development] MOUSEY:
I went from voodoo beta 1 to voodoo beta 2 before applying this. Everything seems to be ok though. If in doubt, do a backup first...
[Galaxy S I9000 Android Development] raspdeep:
yes, it should work
[Galaxy S I9000 Android Development] cba1986:
Thanks.

There is any wake-up lag in this one?
[Galaxy S I9000 Android Development] raspdeep:
wakeup lag has been gone for a long time :)