yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ashwinds:
Update 1: Installed fine... -0.25UVL seems good!! Putting it thro' the paces before adding more.

Update 2: -0.25UVL and -0.25UVH looks good

Update 3: -0.25UVL and -0.25UVH with CPU = 1Ghz works fine too (no OC)... this looks good :D

Update 4: It was fine upto -0.75UVL and -0.5UVH. Froze at ---0.75 UVH. Will test this limit more

It was not stable at -0.5, -0.5 - died after 3 quadrant runs... maybe lowrider's thresholds are on target. I am going to stay at hfuv -25 and lfuv -50 overnight. Anyway - this is a whole lot more stable than 1 UV :)

A request - could you base this off hardcore's C2/D1 - those seem to be the smoothest.
[Galaxy S I9000 Android Development] android53:
If anyone wants to test if this is fully stable on their phone, download rockplayer and play a 720p film in software mode, it should play very slowly to get a good stress test going.

See if you can make it to the end of the film
[Galaxy S I9000 Android Development] dupel:
Another method is to play music from sd card. Froze phone without fail on eclair.

EDIT. Did -25 on lower, and seems to be working right now. I am to be honestly surprised - what changed since eclair than it failed there, but seems to work here?

EDIT2. -50 and still works... Something is just plain strange... Will try to undervolt 1 and 1.2 too, and play a movie in software-hardware mode...

EDIT3. No problems on -25 on high clock, but I did try software method in rock player and phone hanged instantly (720p mkv (anime) file). Than again same file worked with no problems in mvideo player. No issues apart from that. Will try to test it out more.

EDIT4. 720p crash in software mode in rock player (hd mkv) is unrelated to undervoltaging. Probably something to do with froyo or ram configuration.

EDIT5. I even started wondering if its working, but finally at -75 and -50 it crashed. Before that tried - 50 and -25 and found no app that would hang. Remember i couldnt even uv -25 on eclair (!).

EDIT6. Last crash corrupted data (probably databases). Will restore nanodroid backup now =)
[Galaxy S I9000 Android Development] bodivas:
Linpack version-1.0.8: 25 mflops*0.13 seconds:D
[Galaxy S I9000 Android Development] dupel:
What did you change that radically, that phone seems magically accept lower voltage much easier?

And what is PMIC? Power Management Integrated Circuit? (whats this about).

If only new version gave same results =))
[Galaxy S I9000 Android Development] ragin:
OCRF's are waiting tonguewagging for Moderate alpha, extreme beta, moderate beta, extreme theta, moderate theta... WHATS Z called as??? :D

WE LOVE this WORK.
[Galaxy S I9000 Android Development] HazzBazz:
Absolutely amazing...top notch! Keep pumping it out...maybe put a donation paid app on market? Easiest donating for many :)
[Galaxy S I9000 Android Development] dupel:
Aftet a lot of testing -50 and -25 seems to work for me.

I am just freakishly amazed.
[Galaxy S I9000 Android Development] bozdag:
What software would you reccomend to undervolt the CPU?
[Galaxy S I9000 Android Development] dupel:
The one in first post :rolleyes:
[Galaxy S I9000 Android Development] android53:
Try it without the overclock or under volt, it should work fine. Rockplayer system mode uses the cpu, other players use the gfx chip. Untill we get a proper stress test this is the only way to guarantee your phone won't randomly crash
[Galaxy S I9000 Android Development] dupel:
Well, there is the question of "what you need". Before I couldn't uv because when playing music it crashed. Had no problems with oc (everything other people mentioned worked for me).

Here everything works so far with oc and uv. And I don't use rockplayer, especially in software mode.

And on top of my head can't think of any other app that would utilize CPU that extensively (close to 100% constantly).

So for now it looks as if I'm set. (well, want oc-uv in kernel by hardcore, but it can wait).
[Galaxy S I9000 Android Development] android53:
Yeah, but the thing is at some point the phone will crash, it will happen sooner or later.

I tend to get about 5 lockups before the file system starts to corrupt.

It could happen during an important call!
[Galaxy S I9000 Android Development] Gh0stw4lk3r:
i used -50mv on HF and LF , but the phone froze when browsing the gallery.

will do without UV for the moment, as this seems to give me more problems then benefits.

the OC part works fine for me though :)

could it be possible to integrate BLN? (Backlight notifications)
[Galaxy S I9000 Android Development] bozdag:
Are we going to see the Galaxy S reach speeds of 1.4 or 1.6 soon?

I heard some controversy over the 1.6 benchmarks. Anyone can clear that up? The ocing threads for the Galaxy S varients is all scattered.
[Galaxy S I9000 Android Development] xan:
No, 1.4 or 1.6 is out of limits.

I'm afraid they didnt even raise clocks. They underclocked "the world", not overclocked the CPU.

I'm curious how many people got 1.2Ghz rock stable. (Rock stable = Rockplayer stable, lol). It could be neat to include some sort of stress test into Voltage Control, allowing it to save settings only after test being completed, although I'm not sure I could handle this task.

I came with an idea, maybe raspdeep could edit OP (to avoid fragmentation) or me could start a new thread as a pool, where users could vote if their overclock is stable (given certain stress testing method). There might be some other options, like how much UV their devices are able to take. This could bring some serious amount of feedback.

About donations, yes it might be a good idea to put this app on market. All credit/donations should go to raspdeep. Its his call.

About stability.. From my experience device needs to be 100% stable. I've had numerous situations, crucial moments when SGS froze with UV/overclock enabled. It could run for 24+ hours flawless, but at some point it crashed, during just random, but crucial tasks. This made the device not dependable.

Then what is the benefit of having faster/battery longer-lasting device if it fails it's purpose at crucial time?

Following this lead, Rockplayer testing seems to instantly reveal CPU instabilities, which makes us quite sure that OC is stable, making the device dependable.

And finally: my feedback.

I've started stability tests with Rockplayer software decoding. My device's figures are as follows:

@1.2 -> NOT STABLE, so I ticked 'no overclocking option'

-75 LV

-50 HV

All of this Rockplayer stable. These values seem to be better than the results I've been able to reach on eclair builds.
[Galaxy S I9000 Android Development] android53:
1.2ghz stock kernel voltage is not 100% stable for me, rockplayer crashes about 40 minutes in.

-25hfuv craps out in under 5 minutes.

Also be careful with high lfuv settings, I did some testing back on eclair a while ago and found that if the cpu governer jumps from 1.2ghz to a low frequency with a large voltage difference it will occasionally crash, even if it is stable when frequency locked
[Galaxy S I9000 Android Development] EarlZ:
Im a noob when It comes to CPU overclocking on a mobile phone but CPU overclocking on desktop computers is my hobby, Im just curious if 1.2Ghz is stable at stock voltages , If so why bother reduce the voltage ( aside from the power saving ) would it fry the chip ?
[Galaxy S I9000 Android Development] xan:
Power saving FTW.

Its both OC and UV kernel, u can chose to stick with UV and leave OC, use just OC and leave UV, or get best of both worlds :)

I doubt it will fry anything.

Does passing negative arguments increase the voltage? Or should I pass >200 value (cant remember what it was :()
[Galaxy S I9000 Android Development] EarlZ:
Im interested in the overclocking part, is there a way the OP could incorporate this to the D1-340MB kernel thats out ?
[Galaxy S I9000 Android Development] raspdeep:
thanks for all the feedbacks, it seems 2.0 UV is more stable to use. It is hard to know if the problem lies with the apps, kernel or hardware or combination of them. However, my target is not a 100% which i know is impossible but hitting 90% stability on the phones is good enough for me.

Some phones are just better in hardware so they can push the limit but some are not. The other factor to consider is heat as you do stress test, the heat increases and that can cause instability too. so some power management profiling will be good depending on usage pattern, UV based of what your hardware can handle. but having user configurable UV opens up the possibility :)

as suggested by peeps, i will play with rockplayer and see how bad it can get. yes, crashing can cause data lost, it depends when and where it crashes.
[Galaxy S I9000 Android Development] android53:
People should also note that setcpu's stress test is inaccurate.

You can be stable on that for hours and then simply playing an mp3 will make the phone crash. It likely only stresses the fpu
[Galaxy S I9000 Android Development] raspdeep:
no, not yet.. barely got it to run stable after a lot of testing so will give a few more days for testing before implementing such feature. but like i said, we are already at the limit of what the spec said so over voltage can be dangerous
[Galaxy S I9000 Android Development] glitterballs:
There's something interesting going on over in the Fascinate forums. Another claim ov overclocking to 1600MHz with an explanation and source.

That aside, I've run several tests with both -100UVLF / -75UVHF, and -75UVLF / -50UVHF. I've had no problems at all. I tested a roughly 2.5min. 480p video with Rockplayer and it went smoothly. I don't think I have anything higher resolution than that to test with Rockplayer at least, but I'm loading a full 2.4GB movie onto the SD card to see what happens. I played music* off of the SD card with the stock player. Ran stress tests with setCPU. Finally I played about 10min. of flash video, -100/-75 was a little bit choppier, but overall not too bad. Flash with -75/-50 was smooooooth. The hottest my phone got was about 44C.

So the asterisk - I tried this kernel on my Captivate. Sound didn't actually work with any of the video/flash/music, and I was assuming that the sound was being decoded but not put out anywhere.

I've had a Vibrant and a Captivate, and it seems to be a common theme that there are small differences intra-model of the phones, some can handle OC/UV fine, others cannot. That said, I'd be very happy if you released the source for 2.0 as is (especially if it's as easy to patch in as the OC!). And I think there would be a lot of people in the Captivate forums happy as well. I think the kernel would have to be called R^2, raspdeep * reoriented. :)

Excellent work rasp.

edit - Forgot to mention that I was OC'ed the whole time to 1200MHz.
[Galaxy S I9000 Android Development] EarlZ:
They have a 1.6Ghz by why is the result of their linpak significantly lower, oh and with stock volts is the 1.2Ghz not 100% stable on all phones?
[Galaxy S I9000 Android Development] dereknas:
I've used the voltage control to set UVLF ~ 50 and UVHF ~ 25. Everything seems ok. However, I tried to change the Launcho Pro number of views from 3 to 1, got a FC.
[Galaxy S I9000 Android Development] raspdeep:
thanks!

sure, i will release the source code when i get off work
[Galaxy S I9000 Android Development] glitterballs:
The Linpack is lower because they're still running on a Eclair kernel.
[Galaxy S I9000 Android Development] android53:
You need to play a movie for longer then 2 minutes in rockplayer system mode, 20 minutes at least, and preferably HD
[Galaxy S I9000 Android Development] EarlZ:
OIC, I never noticed the diff from 2.1 to 2.2 in terms of linpak I always thought it was 14 on both ends.
[Galaxy S I9000 Android Development] xan:
Another thought crossed my mind...

Does builtin CWM run on stock speeds/without UV?
[Galaxy S I9000 Android Development] EarlZ:
Cant wait for this to go to beta or release state so it can be combined with the latest development on the 341MB kenrel
[Galaxy S I9000 Android Development] ashwinds:
+1 - D1 was very smooth for me - would be great to see these 2 merge.
[Galaxy S I9000 Android Development] glitterballs:
Well, if Rockplayer is the metric we're going by, it's done very well for me. I would've thought being able to handle flash video would have been a better metric as that is generally considered more CPU intensive.

By the way, does everyone know there are different version of Rockplayer for different architecture ARMs? I didn't know what at first.

With the ARM7 optimized Rockplayer, I went through a 23min 720p video with no problems with -75UVLF / -50UVHF. At the end of the video, setCPU still reported temperature about 36C. I went back and set UV to -100UVLF / -75UVLF, and played the same file. Still no problems.
[Galaxy S I9000 Android Development] ashwinds:
I think the point about the voltage diff playing a part is spot on.

I could never get to 100 UVLF-25UVHF - but now I am on 100UVLF-75UVHF and it seems fine - not been using it long though. The delta between UVLF and UVHF seems important.

Edit: all this is with no OC ... and as I post that, the phone dies on me :P 75-75 it is next :D Still trying to get to a combination of OC, UVHF, UVLF which is stable.
[Galaxy S I9000 Android Development] android53:
Rockplayer testing MUST be done in software decoding mode

You should be using a film high resolution enough to cause visible lag when it plays.

All other video player tests can be ignored as they use hardware codecs by default, which runs on the gpu.

It should be more demanding than flash
[Galaxy S I9000 Android Development] raspdeep:
Did u download the latest rock player app? It suppose you resolve crashing problems
[Galaxy S I9000 Android Development] android53:
It never crashed for me at stock speeds
[Galaxy S I9000 Android Development] glitterballs:
But again, was it the ARM7 optimized version of Rockplayer? If you're trying to run a synthetic stress test on a universal processor version of Rockplayer, I don't think it's an accurate reflection of the UV reliability. I think if any of these reports of instability of Rockplayer are to be useful, we need to all need to be using the same version at the least, and probably be all be using the ARM7 version. The market has v1.2.20 of the Universal processor version. The rockplayer site has an ARM7 optimized version which is version 1.1.47.

As an aside in v1.1.47 the system mode and normal mode buttons (software accelerated / hardware accelerated) seem to be switched because system mode plays without lag, while normal mode does. But I had no problems with with either of the UVLF/UVHF settings I previously talked about with the ARM7 optimized version of Rockplayer.

setCPU seems to cause the system to hang with screen off profiles set, but, that's been reported with other kernels as well, so I don't think we can say that it's the UV profiles causing it.

rasp - did you use cortex-a8/NEON optimizations when compiling?
[Galaxy S I9000 Android Development] glitterballs:
Which kernel do you have?
[Galaxy S I9000 Android Development] ashwinds:
Raspdeep's kernel is based on JPM, 2.6.32.9.
[Galaxy S I9000 Android Development] glitterballs:
I know that. I'm asking which one dirk1978 is using.
[Galaxy S I9000 Android Development] ashwinds:
well.. i was inferring since he is on this thread he is using raspdeep's kernel :)

PS: I do get it now that he could possibly be on eclair and posted it here by mistake.
[Galaxy S I9000 Android Development] xan:
Yes, good place. Ur problem might be lack of root access or u didnt flash proper kernel.

Anyway, heres bugfix release which will try to handle it nicely, saying it hasnt got root access to ur device :)

No need to update if you dont have FCs, and if you do, it wont fix them. It will go over them, saying what is wrong.
[Galaxy S I9000 Android Development] zenkinz:
here's what I further observed (not via raspdeep kernel but I believe the end result is the same)

low frequency (100 and 200 MHz) one can suppress the voltage level by as much as 100mV.

For mid frequency (400 and 800MHz) one can only do moderate optimisation. The furtheest I can do is 50mV, anything more, Rockplayer will hang.

For the high frequency (1G and 1.2G), I tried just 25mV reduction, and the whole system feels jittery.
[Galaxy S I9000 Android Development] dirk1978:
It's the v2 OC kernel from this thread.

Correct, I'm not here by mistake ;)

I'm using this v2 kernel which should be pre-rooted AFAIK. I flashed it before using your GUI and Quadrant certainly seemed quicker!

I'm using JPO, was previously on the 1000Hz 341MB kernel.

Thanks.

Edit: Actually, you're right. I don't have root. I thought all the custom kernels now were pre-rooted?
[Galaxy S I9000 Android Development] xan:
Nope. Just go to CWM and apply root there. :)
[Galaxy S I9000 Android Development] dupel:
Just had the usual crash during the music playback. I guess -50 is pushing it for my cpu.
[Galaxy S I9000 Android Development] ashwinds:
You need to run the Superuser script - think its in the Unlagfix menu in recovery.
[Galaxy S I9000 Android Development] dirk1978:
Bah brainfade. I remember doing it the first time I installed stzupy's kernel now.

Thanks!
[Galaxy S I9000 Android Development] vuk88:
quadrant score 2450 :)
[Galaxy S I9000 Android Development] dirk1978:
How?
[Galaxy S I9000 Android Development] raspdeep:
yes, these flags are used when compiling

not all phones react the same as your phone hence there is the need for user configurable uv settings

do you have Superuser apk?
[Galaxy S I9000 Android Development] slider2828:
Anyone having issues with the modem after flashing this kernel? For some reason it wiped my modem and I tried using odin to put JPM back on it, but its not working....

Any ideas anyone?
[Galaxy S I9000 Android Development] ashwinds:
No - not with this kernel. Presume it says Baseband Unknown? Last time I flashed a kernel (not this), around the same time I had updated Doc Rambone's ROM which corrupted EFS. Had to restore it from a backup.
[Galaxy S I9000 Android Development] dirk1978:
Sorry, I was asking how the poster above was getting 2450 on Quadrant.
[Galaxy S I9000 Android Development] zenkinz:
Its true that the two phones may not react the same, but it's more likely due to other factors/configuration/usage, since in terms of hardware it's the same.

I prefer/rather like to find out the real cause of the instability, than use a different parameter set to avoid the problem.

not trying to undermine the value of configurable UV though. hope you don't misiunderstand.
[Galaxy S I9000 Android Development] hytin:
crash during google earth evryting else is fin i on latest JPA vid Voodoo pre 6
[Galaxy S I9000 Android Development] loco-:
What are the kernel tweaks doing?

I just activated all, but i cant feel any difference, but i have 300 less quadrants.
[Galaxy S I9000 Android Development] raspdeep:
you can find the answer here:

http://xdaforums.com/showthread.php?t=813309
[Galaxy S I9000 Android Development] Neris:
That's what I asked for in the Eclair Kernel thread by raspdeep. Would really love to see an optimized Kernel with Overvoltaging function.

Like I asked for in my Thread.

I would do it myself, but I don't know anything about Kernel programming and don't know how and where to start learning.

Sent from the Galaxy S
[Galaxy S I9000 Android Development] raspdeep:
xan,

need your help on a new version update. basic command:

echo "25 50 25 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

column 1 is for 1.2ghz, 2 for 1ghz, 3 for 800mhz, 4 for 400mhz, 5 for 200mhz, 6 for 100mhz

the values are in mV

with this, you will have full control of UV or OV on all frequencies. Yes, negative values will do OV but dont support OV in the app cos i dont want peeps damaging their phones when they do something stupid

i will release new update soon.
[Galaxy S I9000 Android Development] xan:
Reoger :-) easier (for meh :-) ) would be to have 1 sysctl per freq, but if u started like that its ok :-)
[Galaxy S I9000 Android Development] joedon3:
A few of us running Tayutama's ROM on a Captivate are having issues with the settings reverting back to 0,0,cfg after a reboot. Has anyone else seen this?
[Galaxy S I9000 Android Development] xan:
Boot settings depend on support of init.d scripts, does kernel provide it?
[Galaxy S I9000 Android Development] joedon3:
It apparently does, users running Doc's ROM don't have the issue with the same kernel.

EDIT: arrfer is working with the kernel builder in the Captivate forum if anyone has any ideas, they're appreciated:

http://xdaforums.com/showthread.php?t=828052&page=20
[Galaxy S I9000 Android Development] ashwinds:
I think sztupy added it to his kernel.
[Galaxy S I9000 Android Development] raspdeep:
if the kernel supports init.d, the next thing to check is busybox is installed properly
[Galaxy S I9000 Android Development] raspdeep:
xan, 2.1uv debug is out for your testing.. use dmesg to check that the app is working
[Galaxy S I9000 Android Development] MZWiZard:
Well... I have my SGS running at 1,2GHz again on froyo thanks to you, raspdeep. As used to, it runs nicely at -25mv from 100 to 1200MHz. :)

Donated 5$ for a beer :p
[Galaxy S I9000 Android Development] MZWiZard:
oops, forgot the very important ;) Quadrant score of 2237 :p
[Galaxy S I9000 Android Development] dereknas:
Xan, any news on your updated voltage program control incorporating the latest kernel?
[Galaxy S I9000 Android Development] xan:
Updated version should be posted on Monday(that is 99% sure). I'm currently out-of-time for this weekend.
[Galaxy S I9000 Android Development] dupel:
btw, can you remover sheduller option? As we now have bfq, it will be reset to cfg when we set uv (or will it be?)
[Galaxy S I9000 Android Development] xan:
It will be set to the one you've selected in VC. It will be all fixed in the upcoming release.

I've started new topic on Voltage Control (want to keep this thread cleaner)

Here we go: http://xdaforums.com/showthread.php?t=829731
[Galaxy S I9000 Android Development] dereknas:
@rasdeep, if i install 2.1 without any settings, what would be the default be? can i just install and wait for xan to come up with the updated voltage control software?

echo "50 50 150 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

for the 800Mhz, do you mean 50 instead of 150?
[Galaxy S I9000 Android Development] raspdeep:
thanks for the beer \o/
[Galaxy S I9000 Android Development] raspdeep:
the default values are all zeros means no UV

the setting depends on your phone and if it runs stable why not?

ya, i purposely put in 150 so you need to know what you are doing or it will hang

generally, at higher clock rate, the UV will be lesser than the lower clock rate. my phone runs ok with 50 100 100 100 100 100 but your phone may not
[Galaxy S I9000 Android Development] raspdeep:
thanks man, i've update my first post to link to your thread
[Galaxy S I9000 Android Development] ashwinds:
Seems fine with a very conservative "25 50 50 50 50 50" and no OC... OC was making the phone really warm so I turned it off.

btw - does this break init script support sztupy had added? I am trying to plug in the UV setting in a script in /etc/init.d/ - it used to auto-run those scripts, but doesnt seem to be doing that anymore... does anyone else have this issue?
[Galaxy S I9000 Android Development] kendalfung:
how to type the cmd with

echo "50 50 150 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

adb shell ?

cannot create /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table: directory nonexistent

Thx
[Galaxy S I9000 Android Development] MZWiZard:
Actually, its still functional after flashing v2.0 raspdeep kernel on top of Tayutama's 1.0.2 i9000 optimized firmware, which includes that script, i think. I'm running ext4 on everything with ext2 loop on DATA. :)
[Galaxy S I9000 Android Development] raspdeep:
post your script, did you chmod 755?

which version are u running?

the script is created by using xan's app and check "set on boot" option. but you have to modify it a little as i've change the sysfs location and format