Database Info

Just showin off a bit : )

So after reading nearly 5 hours and spending my time in the wee hours of morning, I finally did all the "stable" mods for the phone... If you haven't been reading, make sure you guys check out the stuff in the development forum.
After all modifications, I was able to get 2701 points in quadrant benchmark. What mods did I do?
-i9000 eclair flash (JM5)
http://forum.xda-developers.com/showthread.php?t=734871
-Alternative mimocans lag fix
(one click installer http://forum.xda-developers.com/showthread.php?t=749495)
-One click root (googled it for i9000)
-Overclock kernel 1.0Ghz to 1.2Ghz
(http://forum.xda-developers.com/showthread.php?t=746343)
This stuff really does help out your phone folks. Bench it now with quadrant, then take a peak at the other stuff and make magic happen. If anyone needs any additional help setting up their captivate, I'm more than happy to help.

I agree those fixes help speed a lot. But the quadrant score is meaningless. the speed hack creates an io loopback. The loopback just tells quadrant what it wants to hear.

Does your BT work on the european ROM. For me all people hear is a gargeled mess on there end?
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Can you post the results of these tests:
Neocore
Linpack
CPU Benchmark

I keep hearing about this quadrant, does it actually improve real world performance? Or is just for the sake of scores?

jhego said:
I keep hearing about this quadrant, does it actually improve real world performance? Or is just for the sake of scores?
Click to expand...
Click to collapse
Quadrant is just benchmarking software that takes the cpu, gpu and memory read/write speeds into account. It runs a series of tests and spits a score number out at the end, so you can compare your device to others (like comparing boner sizes, but less gay).
It doesn't actually do anything to speed up the device though.

modest_mandroid said:
Quadrant is just benchmarking software that takes the cpu, gpu and memory read/write speeds into account. It runs a series of tests and spits a score number out at the end, so you can compare your device to others (like comparing boner sizes, but less gay).
It doesn't actually do anything to speed up the device though.
Click to expand...
Click to collapse
This is correct and to be honest there is way to much weight in the I/O tests. That is the only reason that the stock Droid X bests the Gal X. It has more weight than cpu and gpu so you can't put to much into those scores. They really don't mean anything more than bragging rights. What I am interested in is real world usage.

Real world use with the hack provides amazing speed gains opening and switching apps. Io heavy apps are very much improved while open too. It's finally as fast as the iphone.

Whats your battery life like after the overclock?

The score ended up getting lower and lower every time i used quadrant. 2701 is the highest I was able to get so far, but that's with a fresh install of the rom and all the stuff before I started loading on apps. Everytime I ran the benchmark, I of course killed the apps beforehand.
The battery life is the same- to be honest. This is me comparing a rooted stock ROM to the somewhat fresh install of the eclair i9000. The phone is very snappy. I came from an iPhone 4 and one of the biggest eye sores to me was the less-fluidness of changing programs, response to buttons (homescreen-back button) and pinch to zoom. After all these changes, it's a whole different story. Browsing is very appealing, especially since pinch to zoom isn't jagged or slow. The smoothness of this functionality is on par to an iPhone. And there is no waiting when I press the home button or back button.
True, maybe these numbers aren't considerably accurate (as far as the lag fix and EXT2) but at least it shows raw computing capability in it's current state... meaning, the usage of a virtual EXT2. Never the less, the phone is still all around faster, even if it isn't exactly the proper way of going about it.
The only problem I've seen so far is that it likes to randomly shut off. Won't respond to anything unless if I soft reset it. I haven't really found what causes it, since the consistency of it happening goes about in a non set pattern.

I didn't see any real world increase .. so I reverted back in about 4 hours.... I'd rather have the memory than a number that don't transfer to real world speeds...

Mini Overclocking Guide

Mini Overclocking Guide​
NOTE: The Steps Below were Tested on Froyo Roms. I have found different and perhaps better ways to test stability with CM7 Roms so I added a section for that too.
You can still use Stability Test but I don't use it too often anymore for CM7.
Programs Required for testing:
#1 Stability Test
#2 Neocore (please note that some kernels are not FPS unlocked meaning that the frame rate will not go over 56fps so make sure to compare apples to apples when testing different kernels).
For overclocking/undervolting you can use either Pimp My CPU or Voltage Control
Intro:
I posted this Guide in ROM thread but decided it might help someone trying to get a head start overclocking...just a reference not a bible.
First of all, please realize that no two CPUs are created equal. Just like with PC Overclocking, there is the luck of the draw involved here so just because one person can do 1.4Ghz it does not mean you will be able to do so nor it means that my UV settings will work for you.
Achieving 1.2Ghz should be feasible for almost all users since most of the code for it was already done by Samsung themselves. After that point though, it is a matter of luck. Many users can do 1.3Ghz but getting into 1.4Ghz the chances of stability drop dramatically.
Please note that with CM7 Roms it seems a LOT more people is able to hit 1.4Ghz and even 1.5Ghz fully stable. 1.6Ghz is also working although not as common. It is easier to use it if you select 1.6Ghz as the ONLY frequency but of course battery life will be affected.
So, start at 1.2Ghz and try to achieve stability with the lowest possible UV settings you can get to improve your battery life then when fully stable, go for a bit more speed if you like until you find your limit.
Process:
The following is the process I use to get 100% stability. Of course, you can use your own or tweak as you like as this is hardly the ONLY TRUTH of overclocking…I just hope it gives you a good idea on how to achieve stability.
I normally use these settings for 1200Mhz:
1200Mhz @ -100
1120Mhz @ -100
1000Mhz @ -100
900Mhz @ -100
800Mhz @ -100
400Mhz @ -100
200Mhz @ -100
100Mhz @ -100
After setting those up , click the Apply Now button but do not save to the Boot settings until you are sure they are stable for you.
To check stability I first run the Stability Test program and let it loop about 30 times or at least 20 of the CORE (not the RAM).
If it fails give it another shot if it fails again then it is time to adjust the voltages for 1200Mhz.
My experience has been that Stability Test crashes to the home screen when it needs more voltage so if it crashes for you change the UV to -75 and test again.
When you are able to pass that test , you can go to Neocore and try looping Neocore and let it running for about 5 to 10 minutes.
If Neocore freezes, at least for my phone, it means that voltage is too high so I need to drop the UV.
Right there is where the whole trick is. Trying to find what UV voltage is enough for Stability Test to pass but still low enough so that Neocore does not freeze.
This takes a lot of trial and error specially when going for 1.4Ghz!
Another thing is that the UV setting for the frequency below the one you are going for, like 1120 and 1000 for example, do have an effect on the stability you are trying to achieve on 1200Mhz because the phone does not seem to like big voltage jumps .
Some times changing the voltage for the frequency below the one you are adjusting is a good way of achieving stability.
This becomes more important when for example you find out that changing 1.2Ghz to -50 gives you stability for Stability Test but then you need -75 in order to pass Neocore test. What do you do then? What I have done with relative success is , use -75 but then increase the voltage to the frequencies below 1200.
For example if I had
1200Mhz @ -75
1120Mhz @ -100
1000Mhz @ -100
I would change it to:
1200Mhz @ -75
1120Mhz @ -75
1000Mhz @ -75
then test Stability Test to see if those changes help you pass it without having to increase the voltage for 1.2Ghz directly thus avoiding the Neocore freezing issue.
Another process some users are doing is just run Neocore for about 30 minutes and it seems to be a good alternative for some. Guess it all depends on your particular phone.
So, as you can image, this means a LOT of trial and error and restarts of your phone. For 1.2Ghz it should be painless but if you want to go higher, prepare to do a lot of the steps above.
Another thing to consider is that some phones seem to work better with kernels that only have one top speed after 1Ghz as opposed to kernels that offer multiple speed options so this is yet another variable to work with.
Also, remember that to restart your phone, there is no need to pull out the battery. Just press and hold the Volume Up and Power button and it will restart.
I am sure this guide can be done a lot better and will be glad to add or edit with any recommendations you can offer.
I hope this helps some of you trying to push your phones to the limits and have fun!
UPDATE for CM7 Users
With CM7 what we considered THE holly grail of speeds, 1.4Ghz with Froyo Roms suddenly became a VERY common thing.
I have no explanation as to why but a LOT of users are able to get 1.4Ghz and even 1.5Ghz perfectly stable on CM7 and the phones just fly at those speeds. Some are also able to get 1.6Ghz stable but that is harder.
Setting only one speed like 1.6Ghz dramatically increased the stability as well. Just a hint for you guys wanting to do some benchmarks.
You can use a program like Pimp My CPU or Voltage Control to set the voltages and the Maximum and Minimum speed.
Now while the Steps at the beginning of the guide (for Froyo roms) should be fine for CM7 as well ...I have noticed, at least with my phone , that a video player called Moboplayer is VERY good for stability testing CM7. In fact, I do not even use Stability Test any more since I moved to CM7.
When the voltage is a bit low on my screen it creates some artifacts, usually green spots that come up and go in random areas until it freezes.
My actual favorite player for CM7 is Dice Player because for me it plays 720p files better but I like moboplayer a lot as well specially because of the artifacts it shows when I am not stable so it is a quick way to tell the settings are not going to work.
Another thing I love to use if the Riptide Game (tegra 2 game) with Chainfire 3D plugin to make it work on our phones. That game will just close without warning when my speed is unstable. So I just let it running the demo on its own for about 10 minutes.
So basically, I use Moboplayer and Riptide to test my stability and with those tests my system is ready to go and takes less time than the steps I used to do.
Of course you can come up with your own preferred tools since our phones are quite unique and seem to have their own personalities.
It seems some users are having luck with my settings so here are my settings for 1.6Ghz This is for GLITCH kernel (V10C VC). Remember that each kernel has different voltages so instead of giving you a minus value like -100 I will give you the actual voltage I am using for each speed.
1.6Ghz - 1425mV
1.5Ghz - 1400
1.44 - 1325
1.4Ghz - 1325
1.3Ghz - 1275
1.2Ghz - 1275
1.0Ghz - 1200
800Mhz - 1100
400Mhz - 950
200Mhz - 850
100Mhz - 850
For Governor I normally just have Smartass and the Scheduler is NOOP.
Not that while for 1.6Ghz my current setting is either -50 or -75, if I were to select only 1.6Ghz as my max and minimum speed, I am then able to lower the voltage to -100 perfectly stable. Just an interesting thing for you to play with.
Important Note for CM7 users getting many FCs like google service or android service.
CM7 has a much smaller data space for application installs and every time I get to that limit my phone gets crazy with FCs. You can check that by going to your applications and launching the TERMINAL application then type df (in lower case) and pressing Enter.
Look at the top table listed for /datadata and make sure you have some available space.
As long as I keep that from filling up (in fact I prefer to keep it around 60% max to give me some room) my phone works like a charm.
You can use an app like APP2SD to move application data to the SD card to free up space.
Have fun and enjoy your pumped up phone!
UPDATE 12/30/2011
CyanogenMod 9 (ICS) users with Glitch kernel using LiveOC you can use my settings as a starting point.
This is what I use for 1603Mhz
Voltages:
ARM voltage
from 1500 to 1200 = 1.5V ; 1000 = 1.375V ; 800 = 1.250V ; 400=1.100V ; 200=950mV ; 100=900mV
Int from 1400 to 1200 = 1.2V ; 1000 = 1.15V ; 800 = 1.125V ; 400=1.100V ; 200=1.100V ; 100=1.000V
Then 123% LiveOC using 1300MHz step (giving you 1.6GHz)
Governor I am still testing but usually Smartass V2
You can of course use it as a starting point for lower speeds if you like.

Nice man. Saves alot of frustration with this.

Awesome! Thank you!

You are the OC master, Shaolin.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

I wish I was a master indeed but I just have a lot of patience I guess to test ..and test...and crash..an test some more

I think I saw a post that said that any temperature below 56 degrees Celcius is fine for the captivate. I still start to worry though if it reaches 50 during a stability test, what's your opinion?

I noticed that mine when it its 50C or so for any reason (battery temp IIRC) it stops charging so that is where I normally draw the line. If I cannot keep it under that I dont feel comfortable.

That 50 is pretty high, at least for me. Even with stability test going for an hour or so at 1400, I only hit 46. Haven't seen anything higher
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Depends on ambient temp of course...you cannot compared devices temps without knowing the ambient temp. In any case, I saw that when I was using the first Trident kernel. That one even made my screen feel very hot...kinda scary lol
Right now, the only app I have that makes my phone stop charging, even when temp is low, is the Justin TV viewing app....weird. I even ran the phone at 600Mhz only to make sure.

AReynante said:
That 50 is pretty high, at least for me. Even with stability test going for an hour or so at 1400, I only hit 46. Haven't seen anything higher
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I was testing out 1500 1400 is fine for me with -100 for each value. 1500 is a different story since I haven't managed to find a stable combination yet (that doesn't reach 50 degrees Celcius).

Sweet. Are you getting to 50C with a specific app? I only get there with some streaming apps but I really only use 1.5 for fpse emulator for example.

I don't have an app that tells me the temperature so the only time I know is if I do a stability test. I'm not sure if I really have a need for 1500MHz since I don't use emulators much but it's more of a "yea my phone can do it" kind of accomplishment - unless I'm missing out on some other benefits of 1500Mhz over 1400Mhz besides possibly more smoothness.

zuN! said:
I don't have an app that tells me the temperature so the only time I know is if I do a stability test. I'm not sure if I really have a need for 1500GHz since I don't use emulators much but it's more of a "yea my phone can do it" kind of accomplishment - unless I'm missing out on some other benefits of 1500Ghz over 1400Ghz besides possibly more smoothness.
Click to expand...
Click to collapse
Lol 1.5 terahertz I want that phone!

studacris said:
Lol 1.5 terahertz I want that phone!
Click to expand...
Click to collapse
Wow didnt notice that....thats Fing awesome!

Stability Test question
Hey Shaolin,
Just a quick question here, when you mention running stability test through 30/50 runs, are you referencing the RAM runs or the core runs? Just checking, since the RAM runs complete within a few minutes whereas the core runs take closer to half an hour, etc.
Thanks for posting the guide, much appreciated!!!

Since the new version I am only doing 30 of the core runs since it seems to take longer than before.
You are welcome amigo

shaolin95 said:
Since the new version I am only doing 30 of the core runs since it seems to take longer than before.
You are welcome amigo
Click to expand...
Click to collapse
Hey mate, maybe you can add this to your guide as I thought before that stability test and several runs of new core, nenamark, etc...that after passing those tests you're probably stable but what I found out that I can pass those tests without problems and just recently those test are not enough for you to be sure if you are really stable what I have found is to run or record in your phone video cam in its highest resolution about 720p for 200mb worth of data if your phone won't freeze then it's pretty stable you can delete those files afterwards.

Indeed each phone and user can find specific things that work for them, for example with my phone I can just use mobo player and play some videos and I get artifacts when voltage is low or I had a game that with low voltage will always freeze at the same spot yet some user do not have the same effect.
I guess I can add a small list of other possible quick tests like that video one you mentioned as alternatives

I found out another way to test stability which is to do a batch operation of backing up apps with TiBu. I'm not sure what it implies if it crashes though

Hi shaolin95, can I link this post in my VoltageControl thread? (with credits ofc)

Linpack updated

Just got the update for linpack and now it supports multithreaded cpus. I got only 118 so far.
Will get a link in a bit.

I just scanned the market today to see that it was updated, gave it a go, and got 117.6 mflops. Much higher than the ~55 I would get on previous versions.
Running EB Froyo, OC'd to 1.5ghz min/max (just for testing the app), all data connections turned off to avoid pesky text messages
Can't wait until this phone starts really covering some ground in the development area. I got the Vibrant when it was brand new, and had to wait for the snail's pace development on that thanks to Samsung's bullcrap. Now, I get to pace this phone's progress to see how it measures up.

Hmm....Im having trouble breaking 100 even w/ Multithread. I just barely break 100 when I OC to 1.5Ghz

Max'd out at 116 on 1.5Ghz.

Stock cm kernel, said inconsistent result.
Sent from my HTC VISION using Tapatalk

Benchmark tests

Is there a benchmark test out there that can accurately judge a phone's performance vs another's? I continually see that people disregard quadrant, but i still want to be able to reliably test my phone's capabilities against someone else's.
Sent from my Desire HD using XDA Premium App

rant/
meh....all of it is almost completely useless.
ill tell you this. ive flashes every single rom on here, overclocked all the way up to 1800 and underclocked down to 700. ran every where in between for multiple days, ran every precievable benchmark test i could get my fingers on. getting scores as horrible as 1200, up to 3200 in quadrant. linpack from 20 to 60
and you know what? it has made absolutley ZERO impact on how the phone works with every day use.
when i realized this, was because i THOUGHT i had my phone set to 1800mhz, but didnt actually check the "apply on boot" box, and i was running at 1000mhz for two weeks thinking "wow this overclock makes my phone fast!"
yeah. the only time i see the difference is when performing tests.....oh and underclocking at 700 made the phone laggy, 1800 made it prone to lock up. but i can not tell a differnece in the actually function of the phone in day to day use between 800 and 1600 mhz if its on a good rom.
i get the fun of seeing the scores. but it really is completely useless. i was all about overclocking to see that high linpack and quad score....but now i run steadily underclocked, get crappy scores, and my phone functions flawlesly.
/rant

Look up cf-bench in the market it is supposed to be the most accurate least biased benchmark out there. There is also a thread on it in the general android app section.
Sent through the power of Cthulhu!

Thoughts on OverClocking Sensation

Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt

I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.

I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt

I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.

mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App

Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707

I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...

So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt

I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?

i think at LeeDroid 1.2 you must not use setcpu but Demon control?

BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.

Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.