yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] neh4pres:
I'll start off by showing you where you went wrong.

"really?

I don't think so."

I feel that your Sincere about English not being your first language so you probably don't understand how a statement like that gets perceived. It comes off dismissive and rude. That alone probably would not be so bad if not for who it was to. Sixstring is one of the most respected and knowledgeable people in this community. The glitch team which includes sixstring, do an outstanding job maintaining their threads, answering questions, and teaching those who want to learn. so when someone posts something that sounds dismissive in response to their attempts to help and teach it will get people upset. Their advice should not be taken with a grain of salt.

I believe that you didn't mean to sound like that. Just remember English is not a straight forward language
[Galaxy S I9000 General] cba1986:
If what i said sound offensive i apologize. It was not my intention.

I certanly respect the opinion of someone that knows much more that i do. My questions were made from ignorance of not knowing that a simple video player need more stability than a stress test of even a full hd game.

I'm glad that we could solve this in a civilized manner. :)
[Galaxy S I9000 General] RootTheMachine:
What does it mean when the phone is essentially stable with screen on, but shortly after screen off, the CM boot animation that normally comes after the kernel splash will come on the screen very dark and it will be rebooted? I feel like it isn't because of the low frequency step voltages since the phone isn't actually going into a sleep death where it doesn't wake up. But I could be wrong.
[Galaxy S I9000 General] neh4pres:
It could be a problem with didle.
[Galaxy S I9000 General] JohnnieDarko:
Sixstringsg already mentioned that video uses more RAM, he's right but I'll be more specific.

Games use a lot of:

CPU, GPU and RAM.

But not much of:

Disk I/O. This means accessing data from the SD-Card, for example textures or sounds). Games load most of this data before they start, that's why you have loading screens.

Video uses a lot of CPU, GPU, RAM and Disk I/O. This is because it continuously needs more video data. Therefore video software decoding is even heavier than the games, and can be considered the ultimate stress test.
[Galaxy S I9000 General] cba1986:
Thanks for the explanation. In that case i have a pretty unstable phone. :D
[Galaxy S I9000 General] RootTheMachine:
Since the bus is overclocked the same on all steps, why do individual frequency steps need changes in int voltages? Say I'm using 114% and 1200Mhz step, what would be a good starting point for int voltages, compared to default voltages?

Sent from my CM9 ICS i897 Captivate
[Galaxy S I9000 General] JohnnieDarko:
For your first question:

I think it works with one fixed INT voltage over the whole range. I'm not sure what the default INT is for 1200MHz, is it 1200mV? My SGS got stolen ( :mad: ), so I can't find out, but you can set everything to for example 1200mV and it would work. (That is without LiveOC). However, for the lower CPU frequencies, less data gets sent from and to the CPU over the bus, so the required power and thus voltage, can be lowered. This would lead to less power loss, as

Power = Voltage^2/Resistance.

Second question.. yeah I really have no idea. But using the theory above you can go ahead with raising voltage to a fixed value. For example, set all INT to 1150mV, over the whole range, to get the 114% stable. If it's unstable, set it all to 1175mV.

When it's stable, you can try to lower some of the voltages again to save some power. Unfortunately I can't test the theory above, so it may be total bs. Use at your own discretion. ;)
[Galaxy S I9000 General] RootTheMachine:
Makes sense to me. Thanks

Sent from my CM9 ICS i897 Captivate
[Galaxy S I9000 General] FroyoBaggins:
i've had an issue with glitch and nstools. using live oc, i kept getting reboots right after the phone starts up, so i figured id go into recovery and reset nstools voltages. this would cause the phone to always reset into recovery, and never back into the phone. any quick fix for this?

edit: already tried wiping, clearing cache, reinstalling rom and kernel. still reboots right back into glitch recovery. only fix is to odin, which i've already done once, but this would suck if i have to do this everytime i wanna test new voltages.
[Galaxy S I9000 General] jrongi1:
Keep your rom handy and reflash it if you are stuck

vibrant icz

360° Productions
[Galaxy S I9000 General] cba1986:
It depends what max freq are you using. For example, i am using 123% Live OC with 1000Mhz as the max freq. And only tweaked the 800 and 1000 steps. The lower steps are generally overvolted and is better to leave them alone.

This is my voltage table:

FREQ---123%live OC---ARM---INT

1000----1230---------1350---1125

800-----984----------1275---1100

400-----492----------1075---1100

200-----246-----------950---1100

I skipped the 100Mhz because i don' use it.

Today i put my phone to the ultimate stress test. 49 minutes of video using software decoding. Now i can say that this phone is stable as a rock. :D
[Galaxy S I9000 General] fylim:
Thanks man. Your settings made my phone fly! Test 25% LiveOC with it now. Tq tq
[Galaxy S I9000 General] cba1986:
Glad that is working for you. My phone is somewhat unstable at 125% probably bus related.

Because i tried every combination but i always get the same result.
[Galaxy S I9000 General] fylim:
Also unstable for me at 125%. So I increased further 25mv for both arm/into for both 1000/1200 frequency and I am running stable at 126%!
[Galaxy S I9000 General] cba1986:
mmmhh. Maybe is not stable at that certain freq.

I will try that later. For now i'm more than happy with 123%.
[Galaxy S I9000 General] disellusional:
what scheduler/gov are you using?
[Galaxy S I9000 General] cba1986:
For the moment i am using conservative for testing. Because im test driving 128%. Normally i use Glitchondemand or glitchassv2.

For the scheduler for now i use fiops for testing, only because i heard that SIO corrupts files on high OC. Regularly i use NoOp.
[Galaxy S I9000 General] scottcwhite:
Gonna try these out. Thanks
[Galaxy S I9000 General] cba1986:
Just remember that every phone is diff, this values may not work for you.
[Galaxy S I9000 General] scottcwhite:
Yep, my current settings suck on my wife's captivate
[Galaxy S I9000 General] cba1986:
128% is too unstable. Works fine for a while but sometimes it reboots directly to the boot animation.

It seems that 123% is my limit-
[Galaxy S I9000 General] goob1284:
I just need to subscribe to this thread... sorry. is it possible that if the arm voltages are too high that it reboots to boot animation? cause im at the stock frequency and all my arm voltages are between 1225-1275mv.
[Galaxy S I9000 General] fylim:
Assuming you mean your lowest freq 100/200 - 1225mv and ur highest 1300-1400 - 1275mv then I think your lower freq volts is too high and higher freq volts too low.

Suggest that you set nstools to default freq voltages and set to not load settings and reboot. Those will your actual defaults. Different kernel hv diff defaults. I use glitch kernel v14b5 and I think his defaults are the best to start with.

Then try cba1986's oc setting several posts back. Works great and stable at 123% liveoc.
[Galaxy S I9000 General] electech13:
So what would u take?

I see this 123% live oc Max a lot in recent posts which is about right to me but always stated on lower steps, ie 800 and 1000...

So tell me what's better or what u prefer assuming both work great and stable. An increased gpu to 240 with live oc at 120% for a total oc of 1200 or just the 1500 Oct step with no live oc thus stock gpu too at 200? 1500 is a fair bit higher then 1200 but does the increased bus make that much diff?

I'm lucky as I can get 119% live oc on my 1500 step giving me a smoking 1.785Ghz on one of my Cappy's but the other is more typical and only gets good live oc on lower steps like most of u but the higher steps alone work fine so curious if better to take the higher bus at lower overall clock or no?

Sent from my SGH-I897 running Glitch v14 b5 @1.785Ghz stable: ICS 4.0.4
[Galaxy S I9000 General] fylim:
I think I would go with 1.5ghz. Not all apps will max out bus/ memory bandwidth or use hw acceleration. But most will benefit from CPU speed I think. Only way to find out is to test it out yourself and the apps you use.

Ur smoking crappy is unbelievable. Must be sgs3 in disguise! Mind sharing ur settings?
[Galaxy S I9000 General] Epikarus:
Hi guys.

No matter what, if i OC, i always crash in chrome beta, specifically when i do a google search. I set it 1400ghz no live OC. on performance or ondemand, benchmarking runs perfectly, but when i do a google search i get crashes. Seems weird. Wondering if anyone with a stable configuration is getting this problem as well.

if i dont OC chrome doesnt crash.
[Galaxy S I9000 General] badboytn:
Can someone give me your OC and voltages for captivate,i use AOKP b28 and glitch v14b6
[Galaxy S I9000 General] exzacklyright:
me too.. but i'm on fascinate lol
[Galaxy S I9000 General] disellusional:
what exactly is too high of a temperature? i was playing a video in mobo, what temperature do you guys get? on zdbox it said it was around 48oC
[Galaxy S I9000 General] cilverjolt:
Yea I find I'm having the same issue with chrome on 1440 oc. every other app runs fine
[Galaxy S I9000 General] goob1284:
Alright, I'm sorry if this has been talked about or asked, but I went through 15 pages before I decided to ask. I found some relatively good settings (25% in 5 hours) but I had the charge of death or whatever that is called. I usually don't get that. I'll see if I can post my voltages, but I'm at 115% at 1000. there we are.

ALSO: I would like to know what are your average temps, cause I am using cool tool(monitors a whole bunch of stuff, but I use it for freq and temp) and its been hovering in the 100'F
[Galaxy S I9000 General] neh4pres:
That's about body temp, so it's good. Just remember there is no temp stat for the cpu, it's in the battery. So you're cpu will always be warmer than that app says, and there will be a latency in temp rise when benchmarking our stability testing as the heat will have to dissipate toward the battery before you see the rise. Don't quote me on this but i think i remember someone saying try to keep it below 45°C
[Galaxy S I9000 General] loonieryan:
Are the voltage value advices above for ARM or INT?
[Galaxy S I9000 General] RootTheMachine:
These are for int. Otherwise it would be very very hard to OC without breaking something

Sent from my Dark Knight ICS i897 Captivate
[Galaxy S I9000 General] loonieryan:
Thanks for confirming. It says to stay around 1225-1250 mV for the highest frequencies. I'm running 1100 mV INT for my highest frequencies (1200mhz, 1000mhz, 800mhz). Anything higher than 1100 mV and my phone crashes like crazy.

I didn't really need to change the ARM voltages except I set the 200mhz and 100mhz to 1000 mV.

Here are my screenshots:

And because I find that StabilityTest just doesn't stress the GPU enough to determine if the settings are stable, I use all of the following benchmark and stressing apps:

Stability Test

AnTuTu Benchmark

Electopia

KFS OpenGL Benchmark

Neocore

Vellamo

NenaMark1

NenaMark2

This is with IcyGlitch v14 B6 kernel, and Teamhacksung's CM9 build 17 ROM.
[Galaxy S I9000 General] cba1986:
You don't need to overvolt the 100 and the 200 steps. I remember back in CM7 I used to UV the 100 steo to 800mv.

The only step i overvolted are the 800 and 1000 step the lower steps are generally overvolted.
[Galaxy S I9000 General] neh4pres:
The best stress test is playing a high definition video with mobo player using software decoding
[Galaxy S I9000 General] loonieryan:
Mobo absolutely sucks and the ads are very annoying. It can't play a single HD video smoothly on my phone, with or without LiveOC. It can't even play the HD videos I record using the phone's camera.

MX Video Player is far better and even has a H/W decoding mode which works great for 720p videos.
[Galaxy S I9000 General] neh4pres:
I'm not talking about using anything as a player. I'm talking about stressing your phone to see if it's stable. And you don't want hardware decoding when doing so. You want to use the software decoding that's in mobo player. This is what glitch uses to break the phone when he tested leakages in the past. so that said, the fact you can't play a single video smoothly means you probably have done work to do on your voltages.
[Galaxy S I9000 General] zuN!:
You can use Software Decoding with MX Video Player as well and it will do the same thing. Save the trouble of having both MX and Mobo and just use MX for both watching and testing purposes.
[Galaxy S I9000 General] Adevem:
edit: new LiveOC Values, phone didn't like the old one very much. this is pretty stable so far! Tried a 720p Software decoding video off MX Player as well as Modern Combat 3. so much smoother gameplay on that one. flying phone.

Freq - 120% LiveOC - ARM - INT

1000 ------- 1200 - 1375mv - 1150mv

800 --------- 960 - 1225mv - 1125mv

400 --------- 480 - 1075mv - 1100mv

200 --------- 240 - 925mv - 1100mv

Your mileage might vary!
[Galaxy S I9000 General] neh4pres:
This is the first ive heard of how the selective live oc works. Good to know what steps are affected
[Galaxy S I9000 General] Epikarus:
Thanks for your response. I feel that this is a chrome issue and its something that we can't really report to google as a bug. I guess we'll have to wait out and see if they fix the issue as they move it out of beta eventually. I love chrome, but this issue is keeping me from using it as often.
[Galaxy S I9000 General] DerTeufel1980:
You can change the affected states yourself. This is just the default which I decided is the best.

Sent from my I9000 running Android 4.03
[Galaxy S I9000 General] kiez:
balanced settings

Hi, I'm back :)

ROM: ISCSGS 4.2,

Modem: KF1

Kernel: Glitch V14B6

Freq - 123% LiveOC - ARM - INT

1000 ------- 1230 - 1375mv - 1150mv

800 --------- 984 - 1225mv - 1100mv

400 --------- 400 - 975mv - 1100mv

200 --------- 200 - 900mv - 1100mv

100 --------- 100 - 875mv - 1000mv

@ all: Please post ROM, modem and Kernel Version and please don't post screenshots. Please also don't post settings you haven't tested properly!

@ Glitch team: again great work, thanks!
[Galaxy S I9000 General] fylim:
Back to v14b5 @126%.

The new liveoc targets giving me instabilities even with new nstools test version.
[Galaxy S I9000 General] kiez:
New nstools version freezes my phone, when changing any setting :eek:, but the offical 1.15 works fine for me.
[Galaxy S I9000 General] loonieryan:
ROM: CM9 nightly 2012-09-16 (Android 4.0.4)

Kernel: CM9 stock

CPU/Voltage control app: NSTools 1.16

GApps: 2012-04-29-ICS version

Other important changes: Froze default browser (Browser 4.0.3-eng.pawitp.20120307.105323) using Titanium Backup and installed Dolphin HD Browser. Default browser was unnecessarily hogging CPU and draining my battery.

Here are all of my (very stable) settings:

LiveOC: 120%

OC Target Low: 100 MHz

OC Target High: 1500 MHz

Min CPU freq: 240 MHz

Max CPU freq: 1200 MHz

Max ARM volt: 1500 mV

Max INT volt: 1300 mV

Frequency voltages:

Freq (MHz) ARM Volt (mV) INT Volt (mV)
---------- ------------- -------------
1500 1500 1200
1400 1450 1175
1300 1400 1150
1200 1375 1100
1000 1300 1100
800 1225 1100
400 1050 1100
200 950 1100
100 950 1000

I ran all of the following stress tests in the following order to successfully test the stability of the phone:

720p AVC (High@L3.1) 29.97 fps video within a MP4 container playing in MX Video Player using software decoder

Electopia

Stability Test (CPU/GPU Test, Classic Test)

AnTuTu Benchmark

NenaMark1

NenaMark2

Neocore

Vellamo

KFS OpenGL Benchmark

It's worth noting that setting my minimum frequency to 240 MHz provides a very fast and snappy UI, i.e. widgets refresh and redraw much faster and overall UI responsiveness is better. Setting my minimum frequency to 120 MHz (lowest setting) does result in some lag, which is why I tried the next frequency step up.

Good luck, and please remember to press the Thanks button below if my settings and information helped you in any way.
[Galaxy S I9000 General] PatcheZ:
IcyGlitch v14 B6

@1000 (multiplier) with 123% OC

1000/1350/1150 or 1000/1375/1175 for 125% OC

800/1225/1100

I am not sure how you guys are testing your overclocks, but I test by multiplier on one set frequency:

1. set to governor to performance (to maintain max freq or test freq)

2. select multiplier to test (eg. 800, 1000, 1200)

3. select OC/Bus speed (eg. 110%)

4. stress test (eg. moboplayer on 720p works well)

5. a) if successful, increase OC in increments of 2% and repeat 4)

5. b) if crashes, restart phone and increase Arm voltage in increments of 25mV, and repeat from step 1). Repeat until OC can not be increased at that particular Int voltage.

6. increase the Int voltage in increments of 25mV and repeat from step 1)

7. select matching max OC's from the different multipliers.

I love graphs, so I put my results in Excel.

(my personal max voltages I was willing to use were 1425/1200mV for Arm/Int)

- it does show a linear progression for OC vs. Arm/Int voltages

- could not get OC higher than 117% on 1200 multiplier
[Galaxy S I9000 General] jcjcc:
My INT voltages are strangely not very linear...

+30% Live OC

1300	/ ARM 1400, INT 1175

1040	/ ARM 1225, INT 1175

400	/ ARM 1050, INT 1175

200	/ ARM 1050, INT 1175

100	/ ARM 950, INT 1000

Despite this weird curve, it's perfectly stable on my phone.

That's exactly how I test, except I decide on a Live OC target beforehand and not a max voltage. I also could not, no matter what I did, get 1200 multiplier stable on 120% or higher.
[Galaxy S I9000 General] djk21108:
I'm having a real difficult time with NSTools on my fascinate.

I'm on a phone that originally what would be considered "High Leakage"

I can't get any voltage settings that allow my phone to run smoothly. I get a lot of freezes when I wake up my phone from a lock. A lot of freezes during intensive applications, and a lot of random restarts.

Anyone have a very stable set of NSTool settings I can copy? Or maybe someone could help teach me which settings lean towards stability, so I know what to play around with? Thanks.
[Galaxy S I9000 General] thisguy23:
You must remember that more volts aren't always more stable. Sometimes in my case less is more.

With that said use the test build:

http://xdaforums.com/showthread.php?t=1333696&page=75

It will allow you to control the Live OC target low to 800. This will allow more stability overall and save the Live OC for the highs when you really want it.

So with that said here's what I've been running for 4 days 100% stable. No crashes, No overheating, No problems just speed.

Arm Speed Arm Volt Int Speed Int Volt

1000 1325 1000 1100

800 1200 800 1100

400 1050 400 1100

200 900 200 1100

100 900 100 100

I'm using a 117% Live OC giving a 1170MHz MAX and 200 MHz MIN.

You're milage will vary. I CANNOT achieve stable results higher than 117%.

Once you achieve stable results please post. You just may be able to help someone else.
[Galaxy S I9000 General] XblackdemonX:
I don't understand why you people don't undervolt the INT ?

I'm currently with these settings and it's running great! (i'm not done with pushing it to it's limit yet!)

Arm

1000-1225mv

800-1100mv

400-1000mv

200-900mv

100-875mv

INT

1000-1050mv

800-1025mv

400-975mv

200-950mv

100-925mv
[Galaxy S I9000 General] vitoski:
Totally agree. Mine LiveOC became stable after I undervolt INT for 1000 mhz

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 General] Darkangels6sic6:
I want to start off by saying thanks a lot everyone here and there. Glitch is just amazing!

My issues seem to be that only on cm7 can I get stable oc. On CM7 I am almost constantly at 1.5ghz perfect unless i am trying to save battery. I even hit the 1.7ghz once before, but that seems to not be as cooperative now. Before this I thought i would never reach there. On other roms(mainly ICS) most oc's reboot me. Even in the 1200mhz-1300mhz areas. And 120% in increments is almost unobtainable. Not to mention many other areas even around 112%-118%. This also includes trying like 800mhz and then an ok stepping level.To finish up anywhere out of normal based oc and light use of stepping even with numerous(mind you not vast)voltage tweaks is an instant reboot....This along with no dtmf and what not I went to cm7. Always true to glitch though :)

And who reach 2.25ghz because that's effin epic!
[Galaxy S I9000 General] pizz0wn3d:
So... What's your question?

Herp derp Captivate XDA Premium
[Galaxy S I9000 General] izmena:
my rockstable settings:

liveOC - 112%, 1344MHz

Arm

1200 - 1300mV

1000 -1200mV

800 -1100mV

400 - 900mV

200 - 800mV

100 - 775mV

INT

1200 - 1100mV

1000 -1075mV

800 - 1050mV

400 - 1000mV

200 - 975mV

100 - 950mV
[Galaxy S I9000 General] XblackdemonX:
Competition lol!

I set my ARM to the same thing as you but INT -25MV on everything :p

INT

1000 -1050mV

800 - 1025mV

400 - 975mV

200 - 950mV

100 - 925mV
[Galaxy S I9000 General] Darkangels6sic6:
Oh wow. Sorry. My questions are does this happen a lot? If so has anyone found ways around it? I'm not expecting miracle answers or handouts.
[Galaxy S I9000 General] Darkangels6sic6:
Also who has that 2.25GHz? Could we see a video or benchmark? Just sounds outstanding.
[Galaxy S I9000 General] RootTheMachine:
I doubt it's possible. That means an unlikely 300 Mhz bus

Sent from my CM9 i897 Captivate
[Galaxy S I9000 General] Darkangels6sic6:
Yeah. I'm just meaning by the way they said it I thought they meant that one had achieved it
[Galaxy S I9000 General] pizz0wn3d:
(moving our discussion here)

250mhz is a really high bus speed, which is why you're probably having so many issues with stability (default bus speed is 200mhz).

I'm running mine at 117% on the 1GHz step (selective OC ftw!) and thats only 234mhz bus speed. Also, my phone almost literally flies.

Herp derp Captivate XDA Premium
[Galaxy S I9000 General] Darkangels6sic6:
But on cm7 and now team kang based I am at 1.5GHz with the 250mhz bus speed flawless. Its with live oc that even light bus speed increases are unstable
[Galaxy S I9000 General] pizz0wn3d:
How are you increasing the bus speed without LiveOC? LiveOC is what increases the bus speed. At least on Glitch.

Herp derp Captivate XDA Premium
[Galaxy S I9000 General] Darkangels6sic6:
Because in the Gingerbread kernel the bus speed was linked to the CPU speed.. well rather the other way around. So overclocking to 1.5GHz automatically brings bus speed to 250MHz
[Galaxy S I9000 General] pizz0wn3d:
Um, not unless the kernel dev manually set the bus speed for the 1.5ghz step to 250mhz and adjusted the multiplier accordingly. The cpu speed is defined by the bus speed times the multiplier.

From the OP:

Herp derp Captivate XDA Premium
[Galaxy S I9000 General] sixstringsg:
I don't know of any kernel that had a 250 bus at 1.5ghz, either GB or ICS.
[Galaxy S I9000 General] Darkangels6sic6:
Isn't that how glitch v13 worked? It was hard coded that way so that different CPU oc's had certain bus speeds. 1.5ghz had the full 250mhz. While say the 1.7ghz had 243mhz.
[Galaxy S I9000 General] pizz0wn3d:
Nope. If that were the case, most people wouldn't be able to touch that step without an instant reboot.

Herp derp Captivate XDA Premium
[Galaxy S I9000 General] Darkangels6sic6:
It specifically states that the gpu speed is linked to the CPU speed.
[Galaxy S I9000 General] Darkangels6sic6:
Thats what it states that most phones would fail at that point and that's its high and risky. They say the gpu is linked to the CPU and show the chart for what CPU speed has which gpu speed