Updated 1/17/2012
- Busy with college work until 1/20/2012, then I'll update benchmarks
- Benchmarks now much more accurate.
- Planning on including AnTutu Benchmark results! In the midst of running benchmarks, check back later for a more details !
Okay, so the Samsung Galaxy Player 5 is now supported with Tegrak's overclocking application!
__________________________________________________________________________
ADJUSTING THE CPU CAN "POTENTIALLY" BE DANGEROUS. PLEASE MAKE SURE YOU KNOW WHAT YOUR DOING BEFORE TESTING ANY CLOCKS HIGHER THAN THOSE CONFIRMED BY MYSELF OR OTHER MEMBERS. I AM NOT RESPONSIBLE FOR ANY ISSUES THAT OCCUR DUE TO OVERCLOCKING.
Read below to see what's been tested along with some benchmarks + info on each test! If you have any information you'd like to share, let me know and I'll edit it into this post!
Thanks and happy overclocking! Push it to the limit!
__________________________________________________________________________
Tested Clock Frequencies so far...
[1.0GHz] - Stable (It's stock)
~ Average Q-Score: 1445.2 (Out of 5 tests) {Known to flucuate from 1400-1600}
~ AnTuTu score: 3064 (one test so far)
[1.1GHz] - Stable
~ Average Q-Score: 1593.2
~ AnTuTu score: 3192 (one test so far)
~ Significant battery life reduction? : Untested, post if you have tested this!
~ Any noticable issues come up? : Not yet, post if you have had one!
[1.2GHz] - Stable
~ Average Q-score: 1761.5 (Thanks to Meticulus)
~ Significant battery life reduction? : Untested, post if you have tested this!
~ Any noticable issues come up? : None so far, post if you have had any!
[1.3GHz] - Stable (Haven't tested for a long period of time though)
~ Average Q-score: 1856.7 (Thanks to Meticulus)
[1.4GHz] - Seemed Stable (Haven't tested for a long period of time)
[1.5GHz] - Seemed Stable (Only spent about 5min at this frequency)
~ AnTuTu score: 3713
[1.6GHz+] - Haven't tested yet.
GOING TO UPDATE THIS WITH MORE ACCURATE INFORMATION:: Please check back later!
1.0GHz [Stock] - 1.275V
- Average Quadrant: 1445.2
AVERAGE:
_____________________________________________________________________
IF YOU TRY OTHERS: Please let me know so I can update this post!
~ Zane
Well, been messing with it a little with my 4.0 U.S version, and I really don't feel good about going over 1.2 ghz, but it is cool. I would like to know how this thing scores so much higher with quadrant than the original galaxy s, even without overclock, weird. The biggest problem I experience with this is the stupid lack of ram! It is supposed to have 512, witch would be okay, but for some stupid reason it only has 300 something! Really, this thing doesn't need ovrclock, it needs more ram.
Here is the link to tegrak's guide to overclocking...
translate.google.com/translate?&sl=auto&tl=en&u=http%3A%2F%2Fpspmaster.tistory.com%2F98
Sent from my YP-G70 using Tapatalk
ZaIINN said:
Okay, so the Samsung Galaxy Player 5 is now supported with Tegrak's overclocking application!
So far I've tested clocking it to 1.252GHz and it seems to raise the Quadrant score over 1000, but it gives the option to adjust the voltage and raise the cpu to 2GHz (max setting). I don't have much experience with adjusting voltage at all, so if anyone is curious and wants to try, please share! I'm hoping it runs 1.5GHz fairly stable, 1.2GHz seemed perfectly fine (and snappy! =) )
Remember, this requires a root!
Here is what I've found so far! [5 tests per clock speed per tune]
Quadrant (free) scores:
It didn't adjust the voltage when going between the 1.05 -> 1.3GHz tests, I don't know if that's bad or not.
_______________
1.0 GHz
- 831
- 937
- 815
- 835
- 901
= 863.8 <AVERAGE>
_______________
1.052 GHz
- 1008
- 1017
- 993
- 835
- 916
_______________
1.10 GHz
- 1198
- 1251
- 1310
- 1344
- 1383
_______________
1.152 GHz
- 1441
- 1338
- 1348
- 1331
- 1400
_______________
1.20GHz
- 1388
- 1369
- 1313
- 1347
- 1401
_______________
1.252 GHz
- 1376
- 1403
- 1373
- 1412
- 1374
_______________
1.3GHz+
UNTESTED
IF YOU TRY OTHERS: Please let me know so I can update this post!
~ Zane
Click to expand...
Click to collapse
It's strange, I can get around 1400 in quadrant without overclocking. How come your scores are so low?
great news!
I really need overclock!
Just bought ultimate version, soon I'll test it!
You have pretty low scores on Quadrant, I get 1400 stock and 2000+ at 1.3 ghz. I want to know if there is a point to overclock because I am fine with stock speed, fasters speeds would be better but it looks like the cons outweigh the pros on overclocking.
<user removed this post due to old info>
Quadrant testing using Tegrak Overclock Ultimate.
Notes:
1. Player is rooted
2. Chainfire3D pro installed but default settings are in place.
3. Model: US YP-G70CWY/XAA
4. Mhz and voltage changes are made after a reboot.
5. Quadrant Standard Edition Version 1.1.7 Revision 1518
6. SetCPU used to verify speed.
7. Scaling = ondemand.
8. Tegrak Overclock Ultimate 0.9.1
Stock: 1ghz (1275v) - Best: 1676 | Average: 1589.3
1. 1301
2. 1436
3. 1590
4. 1665
5. 1583
6. 1657
7. 1676
8. 1665
9. 1656
10. 1664
1.1 ghz (1275v) Best: 1784 | Average: 1693.9
1. 1387
2. 1596
3. 1646
4. 1758
5. 1772
6. 1760
7. 1711
8. 1753
9. 1772
10.1784
1.2 ghz (1275v) Best: 1910 | Average: 1761.5
1. 1504
2. 1670
3. 1855
4. 1864
5. 1869
6. 1686
7. 1910
8. 1769
9. 1752
10.1736
1.3 ghz (1275v) Best: 1966 | Average: 1856.7
1. 1561
2. 1701
3. 1720
4. 1963
5. 1894
6. 1949
7. 1966
8. 1965
9. 1961
10.1887
So that's my test. I'm going to try out higher speeds later. Let me know if you are getting significantly more or less. Please note any programs you may be using that may be influencing the results.
<user removed this post due to old info>
I have not tested it but doesn't SuperOneClick 2.2 (or later?) have Unroot button?
If you used supeoneclick, it has an un-root option. The others may as well, I haven't checked.
ZaIINN said:
Damn, are you sure you were getting 1676 stock? I'm definitely returning this device... is there a way to un-root?
Click to expand...
Click to collapse
Don't return the device, i have results similar to you (about 1400 with 1,2 clock).
It may depends on backgrounding apps or something else, the important fact is that device is faster with overclock.
tapioco2000 said:
Don't return the device, i have results similar to you (about 1400 with 1,2 clock).
It may depends on backgrounding apps or something else, the important fact is that device is faster with overclock.
Click to expand...
Click to collapse
Er I meant return it for a new one haha, I'm still under the return thing until Jan 21st (or so) with Bestbuy. And if others are getting 1400 stock and near 2000 oc'd, I'd assume there is something wrong with the hardware =( I just hope that kind of thing will work with the "Geek Squad" or if they'll just laugh at me.
ZaIINN said:
Er I meant return it for a new one haha, I'm still under the return thing until Jan 21st (or so) with Bestbuy. And if others are getting 1400 stock and near 2000 oc'd, I'd assume there is something wrong with the hardware =( I just hope that kind of thing will work with the "Geek Squad" or if they'll just laugh at me.
Click to expand...
Click to collapse
I've understood, quadrant is not Bible, it give just indications.
Now i'm testing 1.3 Ghz and 1.375 V (so overvolt) , very fast and no freezes.
Does it work with my french SGS wifi 4.0?
I've just tried : yes, it works.
1524 : my first Quadrant with 1152 MHz.
wow
I had mine up to 1.5ghz... Ran smooth but obly had it thre for like 10 minutes... Ran like tow benches. 1st was 1997 second was 2019. It didnt heat up or anything, but i would prefer not to burn out my chip. Only reason I went so high is because the galaxy s has been clocked to 1.6 .
I think at 1.5 i could max at 2200-2300 with the stock rom. I got 1400 stock... Yp-g70
Well, here is some undervolting results I got:
Mhz - CPU volt - Internal volt
- 100mhz 750 mv 770 mv
- 200mhz 780 mv 870 mv
- 400mhz 870 mv 870 mv
- 800mhz 1020 mv 940 mv
- 1000mhz 1090 mv 940 mv
Maybe this values are useful for someone.
I tried 1.5GHz and it seemed to make the Android notification bar lag, what did you change your voltages to?
* Double post, idk how to delete it >_>
tcb4 said:
I had mine up to 1.5ghz... Ran smooth but obly had it thre for like 10 minutes... Ran like tow benches. 1st was 1997 second was 2019. It didnt heat up or anything, but i would prefer not to burn out my chip. Only reason I went so high is because the galaxy s has been clocked to 1.6 .
I think at 1.5 i could max at 2200-2300 with the stock rom. I got 1400 stock... Yp-g70
Click to expand...
Click to collapse
I tried mine @ 1.5GHz, but it seemed make the Android notification pull-down bar lag, what did you set your voltages to?
Related
tegrak promised he was going to upgrade his tegrak overclock app to work with all kernels and it looks like he's delivered! (see http://forum.xda-developers.com/showthread.php?t=1101355
I'd installed the free version as tegrak suggested a couple months back to see if it would work with my phone. It didn't, but yesterday, it upgraded to version 0.6.0.9. I had a bullet kernel that allows OC to 1.2 ghz with no voltage adjustments. The free version doesn't OC but will let you know if the paid version will work with your phone.
The paid version ($2) works. At least on my phone it does. Maybe no need for special kernels anymore. I haven't tried it with a rom that doesn't support OCing and overvolting yet but I'm going to do that this weekend.
The higher speeds need overvolting and there's no directions on how to do it. tegrak overclock will officially only let you go to 1.3 ghz but if you select the fine "optimization" you can go way up beyond that. I immediately zoomed it up to 1600 mhz with no voltage adjustments and the phone locked up and started buzzing. I had to pull the battery and reboot. Don't do that! Go up a little at a time and then let the stability test run (pull down notification screen to see how many seconds are left.)
There are buttons to adjust by small amounts. You should be able to set it at 1.4 ghz with a little overvolting without too much trouble. Right now my phone is stable at 1524 mhz and core voltage of 1361 mv using an "on demand" profile of 100-1524mhz and it's not hot. Quadrant score at that setting was 3201. That's pretty good for a kernel that only supports OC to 1200 mhz.
I couldn't get to 1600 yet without locking up the phone -- needs more overvolting I figure.
If you have sgs overclock, after you up the speed, it will have the top speed bar at the bottom 100mhz and you will have to drag it up there. I don't know why this should make a difference but my quadrant score was in the 2700s before I did it.
Write down your figures 'cause if the phone locks up and you have to pull battery and reboot, the phone will ask you if you really want that speed that didn't work, and when you say "no" you'll be back at the beginning again.
There is more discussion in the 19000 forum on tegrak's 2.3.4 kernel (for I9000) and the OC app. according to tegrak's guide, the Galaxy S can be stably undervolted using his utility at various speeds and I guess save battery life:
speed standard core voltage undervolt
1000mhz 1275 mv 1225 mv
800mhz 1200 mv 1125 mv
400mhz 1050mv 950mv
200mhz 950mv 825mv
100mhz 950mv 800mv
There is a dialog in the app to set the voltage for each of these speeds in addition to setting the OC speed and voltage. I'm not sure whether tegrak has tested this on the various flavors of Galaxy S or whether he means the I9000. I'll just have to see.
here is his figure for a 1200mhz OC.
speed standard core voltage overvolt
1200mhz 1275 1310
Seems to be working good!
All nonsense and misspelled words courtesy of my unsupported samsung device.
This is my first thread in development area as I was always a more tester/user, now I'm on developer/tester level, hope in future to become a real developer.
My intention here is mainly to share all my findings and also clear some doubts with the help of other testers.
_________________________________________________________________
I will be editing this thread along the day as I have lots of things in mind right now and I'm pretty sure i will forget to put something here, .
This is my last tested table for UV, i have completely no FCs, this was tested always trying to force any possible FCs/WLODs that could ever happened.
I will be detailing here the best procedure to be sure that the freq./UV works before testing a full day and how to test freq by freq.
NEW:
128Mhz | 825mV
192Mhz | 825mV
245Mhz | 850mV
384Mhz | 850mV
460Mhz | 900mV
576Mhz | 975mV
614Mhz | 1000mV
652Mhz | 1000mV
691Mhz | 1025mV
729Mhz | 1075mV
768Mhz | 1075mV
806Mhz | 1100mV
844Mhz | 1125mV
921Mhz | 1175mV
998Mhz | 1225mV
1036Mhz | 1250mV
1075Mhz | 1300mV
1113Mhz | 1325mV
1152Mhz | 1350mV
1190Mhz | 1375mV
1228Mhz | 1400mV
OLD:
128Mhz | 850mV
192Mhz | 850mV
245Mhz | 850mV
384Mhz | 850mV
460Mhz | 900mV
576Mhz | 975mV
652Mhz | 1000mV
768Mhz | 1075mV
844Mhz | 1125mV
921Mhz | 1175mV
998Mhz | 1225mV
1036Mhz | 1250mV
1075Mhz | 1300mV
1113Mhz | 1325mV
1152Mhz | 1350mV
1190Mhz | 1375mV
1228Mhz | 1400mV
EDIT:
I got one shutdown( NO WLOD and neither heating ) while the phone was deep sleeping, so i guess is something regarding the lower freqs. will check more during the weekend.
[how to test uv freq by freq]
Well the need for testing freq by freq is that you have to make sure that the freq. you are undervolting is perfectly working and that if you get any WLOD or FCs(i just got one FCs during the testing any error ended on WLOD) the error is on the freq. you are testing and none of the freq. higher or lower is affecting it.
Governor:
POINT: The only governor should be used in the initial testing procedure is the performance governor.
REASON: Because it will only use the freq. you testing, nothing lower and nothing higher.
PS: You have to always set the max freq. to the one you are testing.
1) Find the freq. you want to test(Let's say 128MHz)
2) Go to setcpu or CPU Master and set min AND MAX to 128MHz (i know the rom will be very slow on this point, don't complain about it) and set governor to performance mode(it won't make a difference, but just you get used to it).
3)Go to IncrediControl and set 128MHz voltage to 1000mV if it is already working lower it to 950mV it should work( DO NOT CHECK "SET ON BOOT" )
4)Go to Linpack and keep running test, at least 5 times, if you get wlod make the voltage higher and repeat this step, else go to next step.
5) Go to Quadrant and do at least to runs, if you get a wlod it will be most likely right on the start of 2D scenes, if you get wlod raise the voltage and repeat this step, else go next.
6) If you didn't get any WLODs during these tests, lower the voltage.
7) you can do this from the first to the last voltage, all freq should work from 128MHz to 1228MHz.
PS: Setting the screen to always ON may be needed as some rooms will change you governor to interactive if the screen goes OFF.
PS2: testing above 998MHz should not be done for more than 30min for security(not breaking the phone) reasons.
Advises:
Always take a note in a table of everything that happened, wlods, FCs, noting the freq, it happen and how much battery you had when that happened.
Run this tests with the battery lower than 50% with everything ON(bluetooth, wifi, data(will not be used if wifi is on), gps,... everything you can think of, is better, because it will reduce variation due to higher or lower battery % or battery consumption that could affect the tests.
Applications used in the tests:
IncrediControl
AND
Linpack
AND
Quadrant
AND
CPU Master (Free)
OR
CPU Master for Root Users
OR
SetCPU for Root Users
FAQ
Q? :Should these voltages work on any x10 phone?
A! :NO, every phone is nearly the same but always different, everything is always different.
Q? : Why did you post if this shouldn't work in the same way for others?
A! : Because the voltages may work or not, but the test procedure for sure will work, and also this voltages can be used as the base for testers given the start point.
Q? : Will this work on any Kernel?
A!: This should work on any kernel/rom that can support UV.
Q? : I got stuck on loading the OS, right after the OS starts, it locks giving wlod or rebooting right away, what did I do wrong or what should I do now?
A! : I told you not to set in on boot before really testing the voltages, i will try to get a way to prep a guide in case this happen, but normally incredicontrol will recognize the wlod and set the voltages to default.
Q? : Do you have any? Let me know.
A? : I will give any answers as soon as possible.
This last one should be enough.
undervolting gives me worse results , device heats up more quickly than stock voltages and Stock voltages gives me better battery life than undervolted voltages , there's something wrong in this concept , esp for our X10 . I tested them.
n4naveen said:
undervolting gives me worse results , device heats up more quickly than stock voltages and Stock voltages gives me better battery life than undervolted voltages , there's something wrong in this concept , esp for our X10 . I tested them.
Click to expand...
Click to collapse
Are you using an addon module for WB rom? or something like that? or a custom kernel?
I had a similar issue using the addon modules before the kernels were released, nothing similar to it anymore.
For me the only times that i get battery draining is if for some reason i get wlod, than it will drain like 1% of the battery.
Getting less battery on UV is actually impossible, it only means that your UV or the rom you are using is having some sort of errors.
so many developers popping up, I hope to be able to feel the best results that they have created, and I pray you will be a developer with great skills, keep up the good work... because people like you who make our novices into smart sorry for bad language...!!!
A very good guide...This is exactly what I do but I never thought to write it down...just thought all testers knew what they were doing, but now I read your post I realise that some "testers" just download, flash and complain within the space of 10 mins and dont really do the testing....
Well done...
once u have arrived on stable voltages, min/max CPU freq, governor, i/o scheduler combo (phew thats a lot of tweaking ) for ur device u can simply use init.d startup scripts to set those values... no need to use multiple apps
here is something that should be helpful:
http://forum.xda-developers.com/showthread.php?t=1236446
indhimaga said:
so many developers popping up, I hope to be able to feel the best results that they have created, and I pray you will be a developer with great skills, keep up the good work... because people like you who make our novices into smart sorry for bad language...!!!
Click to expand...
Click to collapse
Next month i will start learning Java Introduction classes and then right next I will be going to an Android development class, so be prepared, because for now I'm just a novice, but some day i'm going to join the great guys here.
10assaye said:
A very good guide...This is exactly what I do but I never thought to write it down...just thought all testers knew what they were doing, but now I read your post I realise that some "testers" just download, flash and complain within the space of 10 mins and dont really do the testing....
Well done...
Click to expand...
Click to collapse
Yeah most people download everything from the post, not read anything in the FAQ and neither on the how to, and start commenting errors that sometimes even exist before using what they downloaded.
This only causes confusion for Devs delaying even more the good stuff.
DooMLoRD said:
once u have arrived on stable voltages, min/max CPU freq, governor, i/o scheduler combo (phew thats a lot of tweaking ) for ur device u can simply use init.d startup scripts to set those values... no need to use multiple apps
here is something that should be helpful:
http://forum.xda-developers.com/showthread.php?t=1236446
Click to expand...
Click to collapse
Don't know yet how to set that on the init.d dir, though it should be very simple, will try to search for this tonight.
Good addiction to this guide.
Thanks!
TheRuan said:
Next month i will start learning Java Introduction classes and then right next I will be going to an Android development class, so be prepared, because for now I'm just a novice, but some day i'm going to join the great guys here.
.
Click to expand...
Click to collapse
yeah looks like a hardwork... BTW the tutorial like Overclock in my AMD Phenom, but different methode... Reserved...!!!
TheRuan said:
Don't know yet how to set that on the init.d dir, though it should be very simple, will try to search for this tonight.
Good addition to this guide.
Thanks!
Click to expand...
Click to collapse
Here is a startup script for init.d, which sets the VDD levels at boot.
It's the one I use but you can edit/add/remove any values you want.
Get it from [. . .]!
You're welcome!
Very nice but a waste of time to show this because every phone handles different settings differently. If these settings works for you it do not mean it works for someone else.
the way u test is a good way but the voltage do not work for everone.
robertberma said:
Very nice but a waste of time to show this because every phone handles different settings differently. If these settings works for you it do not mean it works for someone else.
Click to expand...
Click to collapse
robertberma said:
the way u test is a good way but the voltage do not work for everone.
Click to expand...
Click to collapse
I never meant to tell that this will work for everyone, though i believe that a very similar configuration will work for mostly everyone.
The intention on this is to show how you can get the basis for a test.
Because, just because you could set a voltage without getting the phone WLODing for you right after that will not mean that the voltage you set really will work, it only means that you have still to stress it to test.
By the way, this configuration will work for most people, most people can use the 128MHz but just doesn't know the correct voltage for that.
The thing is, if you can set the voltage for 128MHz at 800 without it rebooting right after that, stress a bit the processor, if it doesn't reboot try for some time, using on demand mode, so you will get it jumping a lot of times between lower freq. and higher freq.
Most people do the following:
Set 128MHz for (let say 900mV), 900mV and leave the next freq at 1000mV or more, this will cause problems and most likely WLOD, I have tested this and almost always a big variation generates WLOD, so it must be gradual or won't work, for this reason i created this so everyone can calculate the best basis for their phones based on their freq, not in mine.
The only thing I really believe will work for everyone is the math, rate 0,58 per 1MHz, this have worked, as far as i can see.
TheRuan said:
Next month i will start learning Java Introduction classes and then right next I will be going to an Android development class, so be prepared, because for now I'm just a novice, but some day i'm going to join the great guys here.
Click to expand...
Click to collapse
That's merely app development.
Mayazcherquoi said:
That's merely app development.
Click to expand...
Click to collapse
which can be used for developing apps for tweaking the x10's voltage
Had a lot of time yesterday. So here are my Voltages (no overclock though)
128Mhz | 825mV
192Mhz | 825mV
245Mhz | 850mV
384Mhz | 850mV
460Mhz | 925mV
576Mhz | 950mV
614Mhz | 975mV
652Mhz | 1000mV
691Mhz | 1025mV
729Mhz | 1075mV
768Mhz | 1075mV
806Mhz | 1125mV
844Mhz | 1150mV
921Mhz | 1200mV
998Mhz | 1250mV
Currently capped at 768mhz to try out battery life
Haven't found any negative points till now.
Insanity uv
So i been trying to under-volt mi phone, i have stumbled upon something really weird:
so i have been making test and lowering mi v on each frequency this is what i got so far 2+ hours tested no wlod or crash only up to 768 (cap) interactive.
5 runs on each frequency on linpack and 2-3 on quadrant.
first tested on IncrediControl then patch-it with my uv modified script, to make sure it was getting set to 750.
'128000 750'
'192000 750'
'245760 750'
'384000 750'
'460800 750'
'576000 750'
'614400 750'
'652800 750'
'691200 750'
'729600 750'
'768000 750'
IncrediControl reports 750 on all those freq.
reinstall this script init.d-autorunner-v01.zip
everything is still working correctly .... so ... anyway to test this is real and not just mi imagination ?. because i don't believe this myself...
Phone x10a
Firmware wolfbreak 4.0.4c
Kernel Doomkernel v04x
patch with vdd-doomkernel-v04-init.d-script-X-v02
then further modified using "TheRuan" guide "thanks by the way"
Also check on data\local\tmp\ and i get confirmation init.d is working.
just my observation: Quadrant run for touchpad only gives score of around 2400... my nook color with 1.3ghz single core gives score of over 2600 all the time!!! i looked into the device info, it seems like it only using 1 core!!! does cm7 only recognizing one core??? what r ur guys thought??? is there a fix for it or any kernels that utilize both cores of touchpad!!!
The Quadrant results on the TP are skewed because the GPU code has not yet been implemented (or optimized) which primarily affects the FPS section (looks like is is only doing about 4 frames per second) where all the other graphics demos (especially the planet one) do 20-60 frames per second which is a 300%-600% improvement over the Nook Color running 1.2GHz.
I would be interested in other benchmarks that are not dependent on the GPU code.
try using Antutu - free from market
it separates the scores according to each test
(also shows total)
i got around 5000 - OC 1.7 ghz
Maybe it is because we are running an un-optimized alpha build...Don't worry about synthetic benchmarks anyway.
Both cores are already being used, what is your processor clocked too?
I'm completely aware benchmarks don't really mean much, but for curiosities sake, out of 3 runs, I averaged 3228 in quadrant. I am overclocked to 1782mhz ondemand.
I suggest you run SunSpider also.
So I followed Droidstyles "how to" guide on how to put ics on my phone.( http://forum.xda-developers.com/showthread.php?t=1238070 )
I love it so far but now it leaves me wanting more from my phone. Im trying to learn how to overclock my cpu.
I currently have Teamhacksung 6.1 on my phone. And in my "about phone" section my kernel version reads
3.0.8-g0d5605e-dirty
[email protected] #1
Not too sure if those are the same thing. Can i overclock my CPU with the current kernel i have or do i have to put another one on my phone?
Thanks alot for any replies!
Djp2012 said:
So I followed Droidstyles "how to" guide on how to put ics on my phone.( http://forum.xda-developers.com/showthread.php?t=1238070 )
I love it so far but now it leaves me wanting more from my phone. Im trying to learn how to overclock my cpu.
I currently have Teamhacksung 6.1 on my phone. And in my "about phone" section my kernel version reads
3.0.8-g0d5605e-dirty
[email protected] #1
Not too sure if those are the same thing. Can i overclock my CPU with the current kernel i have or do i have to put another one on my phone?
Thanks alot for any replies!
Click to expand...
Click to collapse
Flash Glitch v14 located in the Development forum.
Please Remember to use nstools for overclocking.
Sent from my SCH-I500 using XDA App
Wow thanks for the fast reply.
Do i have to uninstall any of the other kernels I have or go back to any versions?
Or can I download glitch v14 and use odin to flash it from the version im on?
Djp2012 said:
Wow thanks for the fast reply.
Do i have to uninstall any of the other kernels I have or go back to any versions?
Or can I download glitch v14 and use odin to flash it from the version im on?
Click to expand...
Click to collapse
Flash via CWM.
Hold power button
Select 'Reboot'
then select 'Reboot Recovery'
Then flash.
No Odin needed.
That's it.
You cant uninstall a kernel, it boots the phone. You can flash different kernels though. (e.g Glitch Kernel)
Be careful when overclocking. Especially with LiveOC.
If you do not know how liveOC works, please, do not use it.
Have fun
Sent from my SCH-I500 using XDA App
Wow so i got it to work just by doing what you said. I know there is benefits for overclocking as well as some consequences if i dont do it right.
Is there anywhere i could go to read up more on how liveOC works on the fascinate? Like i said, i really want that extra edge that I can get from doing so
Also I downloaded NSTOOLS to get me started
Djp2012 said:
Wow so i got it to work just by doing what you said. I know there is benefits for overclocking as well as some consequences if i dont do it right.
Is there anywhere i could go to read up more on how liveOC works on the fascinate? Like i said, i really want that extra edge that I can get from doing so
Also I downloaded NSTOOLS to get me started
Click to expand...
Click to collapse
Here's the thread (quoted it to save you time)
Tk-Glitch said:
LiveOC and Custom Voltage guide by TkGlitch
for Glitch kernel V14
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warning!
Overclocking is dangerous and is meant only for experienced users!
1- Introduction :
The "normal" overclocking system on SGS til now was the addition of some frequency steps past the stock 1GHz step. V13 kernel was using 7 overclocked steps
to push the maximum selectable speed to 1.7GHz.
In V14, less overclocked steps are present, but you can still overclock to 1.7GHz if you want (and if your phone is able to do it), and even up to 2.25GHz as a maximum.
You will need NSTools to use LiveOC and custom Voltage features in Glitch kernel V14.
To begin with, I'll explain you some basic things you have to know.
2- Clocks :
The CPU speed is the result of a bus speed and a multiplier.
Bus speed is linked to and equal to GPU and RAM speed.
The multiplier is per step and hardcoded by the kernel developer.
It does look like that : CPU speed = bus speed x multiplier.
Here are my values in V14 :
1500 MHz = 200 x 7.5
1400 MHz = 200 x 7
1300 MHz = 200 x 6.5
1200 MHz = 200 x 6
1000 MHz = 200 x 5
800 MHz = 200 x 4
400 MHz = 200 x 2
200 MHz = 200 x 1
100 MHz = 100 x 1
LiveOC gives you the access to direct and on-the-fly bus overclocking by 1% steps (150% being the maximum available). I'll say it again : BUS overclocking !
Though, it'll overclock the bus on all the steps at the same time, for the same percentage.
We'll talk about that later.
So if I want to overclock my 1GHz step to 1.1GHz, I'll have to select 1GHz as max frequency, and push LiveOC to 110%.
My bus speed beeing overclocked by 10% will give the following :
220 x 5 (1GHz multiplier) = 1100 MHz.
If you want to go higher than 1.5GHz, it's the same :
Set 1500 MHz as maximum frequency (for example), and push LiveOC. Let's say to 110%. You will get the following :
220 x 7.5 (1.5GHz multiplier) = 1650 MHz.
Pushing it to 114% will give 1710 MHz (228MHz bus) and so on, up to 150% giving 2250 MHz running an inachievable 300MHz bus.
3- The limits :
THE MAIN LIMIT AND PHONE KILLER IS HIGH TEMPERATURE. WARM IS OK, HOT IS TOO HOT. DON'T PLAY STUPID.
Obviously, so much control over the bus speed, frozen til now to what the kernel developer set, will also give you the ability to find the limits of your chip.
The main clocking limit is generally the RAM, corrupting itself when the bus speed is too high. And since the GPU uses the RAM as well, it'll become crashy too. That's why I have decided to add some steps with a bigger multiplier, to lower the bus for a higher CPU frequency.
The bus speed limits for you will be anywhere between 240 and 270 Mhz, depending on your device potential (higher and lower exists but rare).
Average is 240 MHz.
The CPU speed limits will be anywhere between 1300 and 1800 MHz (higher and lower exists but rare as well).
Average is 1400 MHz.
With that in mind, I wouldn't go too far past 130% (giving 260MHz bus speed).
4- The sweet spot :
What you want when overclocking is to get the best balance for each part. Since the bus is linked to RAM and GPU, you obviously want it as high as possible for gaming, video playing, web browsing etc. (even more now with GPU acceleration in Android 4.0+). Though, as you know already if you've read this guide til now, all steps in V14 are using the stock 200MHz frequency.
So what to do if I want a lower CPU speed with a higher bus/GPU speed ? Simple ! Just select a lower frequency step as starting point.
Let's say we want 250 MHz bus speed, so we'll use 125% LiveOC :
Using 800MHz step, you'll get 1GHz.
Using 1GHz step, you'll get 1.250GHz.
Using 1.2GHz step, you'll get 1.500GHz.
Using 1.3GHz step, you'll get 1.625GHz.
Using 1.4GHz step, you'll get 1.750GHz.
Using 1.5GHz step, you'll get 1.875GHz.
5- The issues :
With a new overclocking system obviously comes some new problems related to it.
With the ability to fine tune the frequencies, you'll find that some frequencies are buggy somewhat, giving low performances. For example, using 115% Live OC with the 1.3GHz step will give some poor performances, when 114 and 116% won't. It could be a NSTools issue, but I think it has more to do with the hardware. It's well known that on CPUs some frequencies or even frequency ranges can be buggy, unstable, or slow. If you encounter that, try to add or remove a percent to LiveOC.
As said earlier, LiveOC will overclock the bus for all steps at the same time by the same amount of %.
Knowing that, you'll have to adapt your voltages for all the frequencies to stay stable, and this for any sensible change on LiveOC percentage.
6- Custom Voltage :
What would be LiveOC without Custom Voltages ?!
I did add leakage values to Glitch kernel features when I saw that some phones were overclocking much better with the right balance between ARM and Int voltages, depending on the phone, with very different results. The leakage value was basically that : balance between the two.
Well, as you probably know if you did read the changelogs, you have now the capacity to overvolt/undervolt both the ARM voltage (the CPU voltage you know well already), and the Int (internal) voltage. The last one is the voltage going to the GPU/memory controller, and will need to be tweaked accordingly to your phone.
As a starting point, here are the Int voltage values I was using for each leakage, adapted for V14 new frequency table :
HIGH LEAKAGE :
1500 : 1.225
1400 : 1.200
1300 : 1.175
1200 : 1.150
1000 : 1.125
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
MEDIUM LEAKAGE :
1500 : 1.200
1400 : 1.175
1300 : 1.150
1200 : 1.125
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
LOW LEAKAGE :
1500 : 1.175
1400 : 1.150
1300 : 1.125
1200 : 1.100
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
Of course, using LiveOC will force you to change these voltages accordingly.
Here are some advices about this :
- Try to stay around 1.225 - 1.250V for your highest frequencies;
- Try not to ever go past 1.300V if you don't want to kill your phone quickly;
- Be VERY gentle when tweaking it as it is VERY sensitive;
- Try to follow a more or less linear curve for Int voltage on OC frequencies;
- Going below 1.000V on 100MHz step will generally kill stability with no battery gain.
This guide may change depending on my decisions related to the Glitch kernel development, or to polish / add things to it.
Thanks to Ezekeel from Nexus S section for these awesome tools.
LiveOC : http://forum.xda-developers.com/showthread.php?t=1288015
Custom Voltages : http://forum.xda-developers.com/showthread.php?t=1331610
23/01/2012 - UPDATED TO REFLECT V14-B1 CHANGES.
09/02/2012 - UPDATED TO REFLECT V14-B3 CHANGES.
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
Yeah the guide is highly confusing but ill attempt to decipher it lol. As of now though ill just run the liveoc at %110
And once again thanks for the help, trying to figure it out on my own was driving me nuts
Djp2012 said:
Yeah the guide is highly confusing but ill attempt to decipher it lol. As of now though ill just run the liveoc at %110
And once again thanks for the help, trying to figure it out on my own was driving me nuts
Click to expand...
Click to collapse
I use 110%, stock voltages, and the 1200 max step
Sent from my SCH-I500 using xda premium
whats the downside to just using voltage control and keeping it simple?
droidstyle said:
whats the downside to just using voltage control and keeping it simple?
Click to expand...
Click to collapse
No downside that I can tell
Terminators run on Android
The downside is that it's just utilizing extra frequency steps for CPU overclocking as opposed to being able to fine-tune BUS (CPU+GPU+RAM) speed.
droidstyle said:
whats the downside to just using voltage control and keeping it simple?
Click to expand...
Click to collapse
A bottleneck in the buss.. The old glitch v13 overclocked the buss for you. Check the op in the v13 thread. In this kernel by just overclocking cpu I'm sure your bound to not have an efficient setup as the gpu and buss and ram will be stock
Sent from my SCH-I500 using xda premium
Think of a Manure spreader flinging crap against a brick wall, you're manure is your data, the brick wall is your bottle neck.. Well your bottle neck had a 1 foot hole in it. That's your throughput. You speeding up your spreader without making that hole bigger gives you a wall o' ****.
Just because your overclocking to 1.5ghz dont Mean you'll process any more any quicker.. I can use a performance governer and oc to 1.8 GHz then lock my screen.. What does that give me? A battery sucker that is not throughputing the amount of info the step I'm on suggests i could be
Sent from my SCH-I500 using xda premium
currently 14hrs run time @ 42% battery, 2hrs screen on time. seems fairly efficient and fast idk. I was running nstools and using live oc with no issues previously, but i noticed no improvement over using voltage control. i guess ill switch back to nstools and give live oc another go.
droidstyle said:
currently 14hrs run time @ 42% battery, 2hrs screen on time. seems fairly efficient and fast idk. I was running nstools and using live oc with no issues previously, but i noticed no improvement over using voltage control. i guess ill switch back to nstools and give live oc another go.
Click to expand...
Click to collapse
To tell you the truth, i don't think any overclock will make a noticeable difference. These ics roms with the glitch kernel are so fast to begin with. But when it comes to heavy apps i know you won't see the performance of v13 just using vc. Because v13 overclocked the buss/gpu.
And i had 84% battery after 10 hours today. With at least an hour of screen on. But I'll keep track tomorrow with some screenies if you want to compare
Sent from my SCH-I500 using xda premium
I'm wondering what settings people are using for undervolting. I'm running Neutrino v2.5 GT with the patch and supercharger. Seems like if I set anything above 50 I get a reboot. Kinda a total noob when it comes to UV so any help would be appreciated
I would like to know this too please.
Sent from my MB860 using XDA
I'm currently running this:
1300: -150
1200: -100
1100: -50
1000: -50
800: -50
456: -100
216: -150
I've tried lower but I started getting reboots, at these voltages it's been good for a few days now.
Every Atrix isn't the same so while one set may work for one persons phone it may not on yours. One thing, though. DO NOT break the 100mv limit. Meaning if 1GHz is at 1000mv, then the step below it (912MHz if you're on a 1GHz kernel) shouldn't go below 900mv. This is a limit on the Tegra 2 set by Nvidia and going passed the 100mv limit cancels out undervolting across the board. Meaning if 1GHz is at 1000mv and you set 912MHz to 875mv or lower, it won't matter what the undervolting application says. Your phone will NOT be undervolted. I'm able to under volt fairly well and I usually stick to 1GHz kernels to save on battery. If you're using a 1GHz kernel, try leaving the first two frequencies alone (don't change 1GHz or 912 MHz). Here's what I've been using on CM9 with faux123's 1GHz kernel:
1GHz - no change
912MHz - 25
750MHz - 50
608MHz - 95
456MHz - 105
312MHz - 115
216MHz - 135
This has been stable for me since I got my Atrix and works really well on a couple of my friend's Atrix. If this causes reboots then set 912MHz back to no change at 950mv and I can almost promise you the problem will be fixed. Also, if you're a battery saving whore like I am and you're on AT&T, flash the N_01.100.00R European radio. This will allow you to set your phone to GSM Only by dialing *#*#4636#*#* and changing GSM auto (PRL) and use the EDGE (2G) service providing you with MUCH better battery life. If you need the higher speeds then switch back or simply reboot the phone. Hope this information helps.
On a side note, underclocking is another useful way to conserve battery. I never did this on GB ROMs as everything became terribly slow, but on ICS, underclocking barely hinders performance. I have mine underclocked at 750MHz and in terms on scrolling, opening apps, playing games, web surfing, even moving through homescreens, it still outperformed any GB ROM I've used at 1GHz and even 1.3GHz. Even benchmarks are fairly the same. Going on 53 hours with HEAVY usage. e.g. Web browsing all day, texting, few phone calls, and playing games.
Sent from my AT&T CM9 MB860 on EDGE
I'm on Turl's CM9 build v9 with faux123's 1GHz kernel and I undervolt to:
1GHz - 950 mV (-50)
912 - 930 mV (-20)
750 - 830 mV (-70)
608 - 730 mV (-120)
456 - 630 mV (-170)
312 - 530 mV (-245)
216 - 430 mV (-320)
I tried an extreme that someone else had on their Atrix with 216 MHz at 400 mV, and 100mV increment up and my phone became unstable (with 912 MHz at 900mV). Following some other people's advice to undervolt less at 912MHz I arrived at my current setting that is stable for my phone.
I'm using Neutrino 2.2 with the latest faux kernel because I couldn't get phone to deep sleep with 2.5 even with the update installed.
I used pimp my cpu and managed these undervolts, it wouldn't let me go past -250mV is that normal?
1300Mhz -125 mV = 1175 mV
1200Mhz -100 mV = 1100 mV
1100Mhz -50 mV = 1050 mV
1000Mhz -50 mV = 950 mV
800Mhz - 175 mV = 725 mV
456 Mhz - 200 mV = 600 mV
216 Mhz - 250 mV = 500 mV
I was quite surprised of the jump in mV to 1000Mhz, it just wouldn't take any lower voltage without freezing. But I have extended my battery life loads by using pimpmycpu its cool as. Also from the above post does that mean my 800Mhz undervolt is ok or not?
Enkidu1978 said:
I'm using Neutrino 2.2 with the latest faux kernel because I couldn't get phone to deep sleep with 2.5 even with the update installed.
I used pimp my cpu and managed these undervolts, it wouldn't let me go past -250mV is that normal?
1300Mhz -125 mV = 1175 mV
1200Mhz -100 mV = 1100 mV
1100Mhz -50 mV = 1050 mV
1000Mhz -50 mV = 950 mV
800Mhz - 175 mV = 725 mV
456 Mhz - 200 mV = 600 mV
216 Mhz - 250 mV = 500 mV
I was quite surprised of the jump in mV to 1000Mhz, it just wouldn't take any lower voltage without freezing. But I have extended my battery life loads by using pimpmycpu its cool as. Also from the above post does that mean my 800Mhz undervolt is ok or not?
Click to expand...
Click to collapse
Your phone isn't undervolted at all since you broke the 100mv limit. Might show that you are, but the phone is still running with high power consumption.
Also, if you wanna go lower, get SetCPU. Goes all the way down to -500mv and doesn't lock you to increments of 25. You can set any value such as -69mv, -146mv, etc.
Sent from my AT&T CM9 MB860 on EDGE
I'm using the 1.3ghz kernel anyone got safe recommendations not breaking the 100mw rule
Sent from Atrix 4g Neutrino 2.5
I'm running faux 1.3 too n that's wat I'm trying to figure out too. Because according to what you're saying I'd only be able to UV at lowest 2 or 3 speeds
squee666 said:
I'm using the 1.3ghz kernel anyone got safe recommendations not breaking the 100mw rule
Sent from Atrix 4g Neutrino 2.5
Click to expand...
Click to collapse
As I stated earlier, not ever phone is built the same. What works for someone else may not work for you.
CREAPFACE said:
I'm running faux 1.3 too n that's wat I'm trying to figure out too. Because according to what you're saying I'd only be able to UV at lowest 2 or 3 speeds
Click to expand...
Click to collapse
The best idea is to do minimal undervolting on higher frequencies as they need more power and do the more intense undervolting on lower frequencies.
I changed mine up, a bit. This is what I'm working with, now:
1GH no change = 1000mv
912MHz -25mv = 925mv
750MHz -50mv = 850mv
608MHz -100mv = 750mv
456MHz -150mv = 650mv
312MHz -225mv = 550mv
216MHz -300mv = 450mv
To me, undervolting is a way to mainly save power, further, when the screen is off while conserving as much as I can when I'm actually using the phone.
Sent from my AT&T CM9 MB860 on EDGE
Pretty sure it just the rom. Switched to redpill to test it and with undervolting I had %60 battery left after all day of heavy use.
Im on jokersax 0.33, installed setcpu, but i dont see voltages menu at all.
Can somebody guide me pls
Sent from my MB860 using XDA
Its the 3rd tab at the top. It says main, then profiles, then voltages. Not sure if its on there if your not running a custom kernel
CREAPFACE said:
Its the 3rd tab at the top. It says main, then profiles, then voltages. Not sure if its on there if your not running a custom kernel
Click to expand...
Click to collapse
Thats y maybe,.. i am on kernel which comes with jokersax ROM, so probably i cannot get it ;(
EDIT: Yes, i installed http://www.jokersax.com/upload/Atrix-CM9-Kernel-025b-ext4-1.00GHz.zip and i got Voltage tab.
I am testing Neroga settings now.
akyboy said:
Thats y maybe,.. i am on kernel which comes with jokersax ROM, so probably i cannot get it ;(
EDIT: Yes, i installed http://www.jokersax.com/upload/Atrix-CM9-Kernel-025b-ext4-1.00GHz.zip and i got Voltage tab.
I am testing Neroga settings now.
Click to expand...
Click to collapse
Phone froze 2 times and restarted, restoring from standby.
Any ideas what i should change?
Tnx
You have to start out pretty low and work ur way up til u don't get any reboots. Also I'd try faux123's kernel the 1.3 is where its at
I couldn't find any voltage tab
I've tried the standard kernel that comes with the neutrino and faux 1,45ghz for cm7...
Any suggestion?
Neroga said:
Every Atrix isn't the same so while one set may work for one persons phone it may not on yours. One thing, though. DO NOT break the 100mv limit. Meaning if 1GHz is at 1000mv, then the step below it (912MHz if you're on a 1GHz kernel) shouldn't go below 900mv. This is a limit on the Tegra 2 set by Nvidia and going passed the 100mv limit cancels out undervolting across the board. Meaning if 1GHz is at 1000mv and you set 912MHz to 875mv or lower, it won't matter what the undervolting application says. Your phone will NOT be undervolted. I'm able to under volt fairly well and I usually stick to 1GHz kernels to save on battery. If you're using a 1GHz kernel, try leaving the first two frequencies alone (don't change 1GHz or 912 MHz). Here's what I've been using on CM9 with faux123's 1GHz kernel:
1GHz - no change
912MHz - 25
750MHz - 50
608MHz - 95
456MHz - 105
312MHz - 115
216MHz - 135
This has been stable for me since I got my Atrix and works really well on a couple of my friend's Atrix. If this causes reboots then set 912MHz back to no change at 950mv and I can almost promise you the problem will be fixed. Also, if you're a battery saving whore like I am and you're on AT&T, flash the N_01.100.00R European radio. This will allow you to set your phone to GSM Only by dialing *#*#4636#*#* and changing GSM auto (PRL) and use the EDGE (2G) service providing you with MUCH better battery life. If you need the higher speeds then switch back or simply reboot the phone. Hope this information helps.
On a side note, underclocking is another useful way to conserve battery. I never did this on GB ROMs as everything became terribly slow, but on ICS, underclocking barely hinders performance. I have mine underclocked at 750MHz and in terms on scrolling, opening apps, playing games, web surfing, even moving through homescreens, it still outperformed any GB ROM I've used at 1GHz and even 1.3GHz. Even benchmarks are fairly the same. Going on 53 hours with HEAVY usage. e.g. Web browsing all day, texting, few phone calls, and playing games.
Sent from my AT&T CM9 MB860 on EDGE
Click to expand...
Click to collapse
Can you explain exactly how you set your phone to 2G only? Reason I'm asking is 'cause I flashed the radio you mentioned and tried to use 2G only, but it keeps resetting back to gsm/cdma (prl).
Switched to neutrino EE n haven't had a problem since. Battery will last me 2 days