Related
Hey everyone. I realized today that my phone is one of the few that can handle almost all clock speeds (1.6GHz with Trinity VMax causes a reboot on setting it) so I decided to do some Quadrant tests and show you. My process was simple: Flash the kernel, boot, set the clock speed and run Quadrant until the scores stopped going up. All the tests were done on CyanogenMod7 nightly release 29. Here are my results:
Netarchy 1.4GHz BFS (7 tests)
2703, 2843, 3174, 3209, 3216, 3248, 3297
Netarchy 1.4GHz CFS (4 tests)
2775, 3248, 3276, 3308
Trinty Max 1.4GHz (3 tests)
2820, 3474, 3476
Trinty Max 1.6GHz (1 tests)
3891
Trinty VMax 1.4GHz (5 tests)
2854, 3227, 3525, 3550, 3694
Trinty VMax 1.5GHz (4 tests)
2819, 3416, 3667, 3773
PS: The only reboots suffered during these tests were when I set the clock speed to 1.6GHz on Trinity VMax.
I guess no one was interested in this. Mods can close.
I guess it goes to show that quadrant isn't really a good testing mechanism. The results are rather skewed. Although I do see the Trinity performing a bit better than netarchy under similar clocking speeds.
Sent from my Nexus S using XDA App
When I installed the Trinity Kernel v1.1 on my N/S my phone bugged out.
My phone can't go over 1.3 but yet to try the trinity kernels without facing difficulty although i did get 3500+ quadrant scores with 1.4 BFS.
Is anyone else having an issue with custom kernels? My Tbolt only seems to run on the stock kernel/voltage. When I flash an oc kernel sometimes it will load and then freeze the system.
Sent from my ADR6400L using XDA App
All phones are NOT created equally. Your phone may just not be able to handle it while others could.
I realize every cpu used is not the same and can't handle being overclocked to the max, but come on, I can't overclock it at all without it freezing shortly after the Rom starting. Don't you think that's a little out of the ordinary?
Sent from my rooted Tbolt.
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Yeah that does sound kinda sketchy. Which kernels have you tried? Have you tried running one that wasn't undervolted? I've heard people having issues with the UV kernels.
Wkd1 said:
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Click to expand...
Click to collapse
I know what you mean. I had the 1.2 GHz uv kernel from adrenalyne and the phone ran like crap. What's the point of over clocking if real world results are worse. Smart-Ass would stutter while it was ramping up and gun bros ran like crap until I reverted back to the stock kernel.
I'm hoping somebody makes an OC kernel that isn't under volted.
Sent from my HTC Thunderbolt using Tapatalk.
I'm running Imoseyon's version 3 of the lean kernal, 1.4 ghz, undervolted. it seems much faster and more responsive, and has yet to cause me any problems. Right now I'm running on 20 hours off the charger with 45% battery life left (extended battery, so assuming stock would last around 9 hours).
The only kernel that works for me is adrenaline's 2.6.32.21 battery is life kernel. I've tried his other kernels, imoseyon's lean kernels, and a few others all with the same result of freezing up the Tbolt.
Sent from my rooted Tbolt.
Have you tried adrenalynes newest kernel? I'm using version 4 right now with no problems.
Yeah, another vote for Adrenalyne's kernels here.
I'm running the version 4c, and it's flawless on my phone. (4b locked up at higher speeds.) But the other tweaks he threw in there kick ass. Louder audio, faster charging and, I think, most significant, a potential fix for the GPS issues a lot of people are experiencing. Granted, mine was not too bad -- I could usually get a lock within a minute or two, but now it's locking in under ten seconds.
Can't quite comment on the battery life yet, but it's probably pretty damn good, especially with a minimal overclock or even staying at 1Ghz.
Running one of Ziggy's...so far so good...
I ran Drod's 1.5 kernel with no problems overclocking. When I switched over to Ziggy's or Adrynalyne's overclock kernels, I am unable to overclock with out my phone freezing and going into constant boot loops. Kinda weird but I have no real need to OC so I just went with Adrynalyne's stock kernel and been fine ever since.
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)
I been flashing Franco's kernels since 12.x and loving them. And I been tweaking voltages for optimum performance/efficiency each time as well. Franco just release 16.2, so I flashed it via his updater app. I noticed right off the bat that the voltages he chose for this kernel are absurd. They are ridiculously high for all slots. Also, they are not in increments of 25 as in previous kernels (not that this might necessarily matter, just pointing it out). I gave it a benchmark (Antutu) just to see how it'd do with those V (using francoGazelle), and sure enough, it dropped 2000 points to ~5000. So I started tweaking them, dropping them around to where I had them on previous kernels. I got 1350 to 1175mV without reboot. I moved to 1200 and got it to 1175 as well, but the benchmark suffered greatly, so I tried going up. I tried 1225...set a new benchmark record of 7065 COOL! So I tried 1250 and it froze in the middle of the benchmark test. I ended up pulling the battery so it didn't cook it self to death. Then it boot looped for a while ("set on boot" was NOT set in setCPU/Franco kernel/AOKP ROM...i don't know why it boot looped). I kept pulling the battery and it kept boot looping. This kept happening for a good 30 minutes till it finally booted. But not it started re-activating like I just wiped. My apps are still there, but many of them wont open. Its running very VERY sluggishly and I'm getting tons of errors and FCs. Widgets are messed up and most defaults are erased. What happened!? Is it screwed up? The voltages Franco had the kernel set at were higher than 1250...all the slots were around 1300+ mV!!! Why did it take a dump at only 1250?
The benchmark crashed right the middle, possibly created a huge file for benchmarking purposes, so the app partition is full which could make apps crash...
Just an idea.
In case of emergency: REFLASH
Hy guys!
I own an i9023, and I'm a frequent reader of XDA's Nexus S section. A week ago I've decided to change the stock kernel. I choose the newest Matr1x kernel, i found this the most sympathetic, after reading through several [kernel] threads. So i tried the 19.5 BFS/CFS, and now my device is on 20.0 CFS with stock rom 4.0.4. I've installed NSTools too. And using smartassV2/noop 100/1000 DIDLE, and no OC, and default voltages too.
I am absolutely statisfied with the kernel, it is much smoother than stock, and has a great battery life, and gets better with every update. At least in case 19.5 to 20
But here is my problem:
Almost in every boot, my phone reboots once during boot. After it is rebooted, works like a charm, no freezes, nor reboots. Fast, reliable, anything you want.
I noticed the device boots without any problem after flashing kernel, before applying any NSTools settings, or if I use resetnstools.zip.
So i am thinking, maybe NSTools can be the source of this reboot.
Here is my NSTools settings:
All tewaks off, 97%, noop.
CPU: smartassV2, 100/1000
liveOC: 100%, 800, 1000
DIDLE: ON
SmartassV2: awake ideal 1000, sleep ideal 100, sleep wakeup 600, min load 70, max 85, ramp down 200, up 200, down rate 49000, up 48000
volt: default
Settings: set on boot
So any idea what is causing this reboot? Or this is normal? I think it is not, but it even could be
Thanks the answer.
Matr1x is undervolted by default. Try upping them a bit or reverting to stock voltages.
Harbb said:
Matr1x is undervolted by default. Try upping them a bit or reverting to stock voltages.
Click to expand...
Click to collapse
This. My phone hates undevolting and I had to return all the voltage settings to the stock Nexus settings if I want to use his kernel. Since I changed them, I've had no reboots or freezes.
Thanks the fast answer Harbb and chronophase1!
Looks like mine hates the UV too Raised the voltages a bit (didn't changed the INT, and that ARM, what was already on Nexus S default), look like good at first look. But requires further testing, to say the problem is gone. Thanks again.
Yeah. All phones aren't the same sadly. If it makes you feel any better, I've been running the kernel for almost 100 hours straight and no issues. Before, every time I hit about 95 hours up time the damn thing would freeze with the UV settings. So I'm still running the test but so far so good on my end.
Looks like the problem is solved. After several voltage settings, I had to return to default Nexus S voltages, even on 1Ghz. The reboot during boot disappeared.
I lost the UV, but I gained OC, now stable on 1.2GHz/1350mv/1150mv. And battery is still good, hope it will remain that way.
Did you change the INT VOLT settings first? Or did you revert all to the stock levels.
I suspect reverting only INT VOLT to the Stock levels will fix those problems. If anybody is willing to try that would be nice ) (I only experienced reboot once with default Matr1x values so no point in my trying)