Related
So I am working on undervolting the atrix, and right now its stable with a -500mV setting to the 216, 456, 608, and 750MHz speeds. Why is the stock voltage set so high?
I noticed that also.....kinda crazy.
Sent from my MB860 using Tapatalk
What, other phones usually run much lower?
Viamonte said:
What, other phones usually run much lower?
Click to expand...
Click to collapse
im not sure, but its just that it is stable at much lower speeds then the stock settings
Viamonte said:
What, other phones usually run much lower?
Click to expand...
Click to collapse
Honestly I forgot the exact amount my sgs ran at but I could UV it by like -125, -100, and -50 from slowest to fastest so -500 seems like a pretty extreme UV...its like 60-70% undervoltage...
Sent from my MB860 using Tapatalk
xnickx5757 said:
So I am working on undervolting the atrix, and right now its stable with a -500mV setting to the 216, 456, 608, and 750MHz speeds. Why is the stock voltage set so high?
Click to expand...
Click to collapse
I think you should go compare the values of other tegra 2 devices to see if it's common across tegra or specific to the atrix. That's first place to start.
But yes that is amazing that you got -500 mV stable.
PM me if you need some other tegra 2 repository links.
I'm curious as to which voltages people are using who choose to undervolt their device. I know I've seen some scattered posts around but am yet to see a thread, if I'm wrong feel free to close this one and direct me to the thread.
Mine are:
1200 mHz
1200 mV
1000 mHz
1100 mV
800 mHz
1000 mV
500 mHz
900 mV
200 mHz
900 mV
I made very small drops over stock as I'm pretty new to it so I didn't want to risk going to low.
I'm on UnNamed 2.2.1 with Entropy 12/08/2011 and CPU set to 1200-200 mHz on demand.
I'm trying to get an idea for what people run for the best mix of battery life and performance.
1700Mhz @ 1500mV
1400Mhz @ 1275mV
1200Mhz @ 1175mV
1000Mhz @ 1075mV
800Mhz @ 975mV
500Mhz @ 875mV
200Mhz @ 850mV
I havent done a whole lot of tweaking to find my optimal settings. Im hoping to have time to play with Zep's 3g turbocharger to see what i can squeeze out of my data with different modems. Im also about to move to UnNamed 2.2.1
http://forum.xda-developers.com/showthread.php?p=19826653
Is probably what you want.
penguinlogik said:
http://forum.xda-developers.com/showthread.php?p=19826653
Is probably what you want.
Click to expand...
Click to collapse
That is a good one, thank you.
But I'm hoping to get a voltage specific one. Your link is a full SetCPU thread.
Sent from Tapatalk using my Samsung GT-I9100
1200mhz - 1250mV
1000mhz - 1125mV
800mhz - 1025mV
500mhz - 900mV
200mhz - 850mV
100mhz - 825mV
I'm thinking I could go another -25mv across the board still.
There isn't a thread because you are supposed to figure out the settings yourself. EVERY DEVICE IS DIFFERENT. What works great for one person may crash another's device, what is just barely stable on one person's device may be far from optimal on another.
If every device were the same, THE STOCK VOLTAGES WOULD BE LOWER.
I was about to say the same thing ^^
Sent from my SAMSUNG-SGH-I777 using xda premium
What app do you use to undervolt? Set CPU?
Sent from my ST18a using XDA App
chrikenn said:
What app do you use to undervolt? Set CPU?
Sent from my ST18a using XDA App
Click to expand...
Click to collapse
Voltage control
Sent from my SGH-I777 using xda premium
Entropy512 said:
There isn't a thread because you are supposed to figure out the settings yourself. EVERY DEVICE IS DIFFERENT. What works great for one person may crash another's device, what is just barely stable on one person's device may be far from optimal on another.
If every device were the same, THE STOCK VOLTAGES WOULD BE LOWER.
Click to expand...
Click to collapse
These values provide a baseline for others to start from. I never guessed I could go down to 825mv until I saw another thread on the i9100 section. But I understand your point of view as well.
Sent from my SGH-I777 using Tapatalk
I agree with Entropy but like the previous post said, I'm hoping for an idea of where people are at with theirs. I'm not hoping for 100% definitive values that work all the time every time.
Sent from Tapatalk using my Samsung GT-I9100
Yeah, still useful and interesting to observe others' settings in my opinion.
Sent from my Galaxy SII
Seems to be working smoothly for me. I have 1600, 1400, and 1200 disabled
Sent from my SGH-I777 using xda premium
currently running aokp 29bigmemtest on my phone and recently installed nstools. im new to the overclocking stuff and wondering if anybody could give me some numbers to input on a good safe oc that wont crash or reboot my phone. simply want to make it run faster etc. thanks in advance
Tag the glitch v14 op, there is a link to a oc guide
Sent from my SCH-I500 using xda premium
neh4pres said:
Tag the glitch v14 op, there is a link to a oc guide
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Found it...thanks
Sent from my SCH-I500 using Tapatalk 2 Beta-5
although that thread is for the i9000, not the fascinate. the settings they give crash my phone. so if anybody has a stable settings they have been using ?? if not, i guess OCin might not be for me !!!
yeahdude38 said:
although that thread is for the i9000, not the fascinate. the settings they give crash my phone. so if anybody has a stable settings they have been using ?? if not, i guess OCin might not be for me !!!
Click to expand...
Click to collapse
The hardware is the same.. However they phone is slightly different. Try 110% live oc and 1200 max step.. That's a pretty safe start.. If you crash try bumping init for 1000 and 1200 steps by the smallest amount i think it's quarter milivolt
Sent from my SCH-I500 using xda premium
Max freq: 800. (1000 effective)
Min: 100
Live oc range: 400-1000
Governor: conservative
Live oc: 24%
It's basically stock speeds with a 25% gpu boost on the higher steps. Conservative governor keeps it from crashing. ;-)
Sent from my SCH-I500 using xda premium
that doesnt crash your fascinate ?? as soon as i hit ok for 24% oc its an instant crash.
It will crash me on the 1000mhz step but not on the 800mhz step. Set 800 as max prior to setting the live oc. In fact, set everything else first and then set the live oc last.
Sent from my SCH-I500 using xda premium
bobloblaw1 said:
It will crash me on the 1000mhz step but not on the 800mhz step. Set 800 as max prior to setting the live oc. In fact, set everything else first and then set the live oc last.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
yeah...still a no go =/
yeahdude38 said:
yeah...still a no go =/
Click to expand...
Click to collapse
Ya trying to copy other people's settings doesn't really work all the time, all our phones are different! Personally my stable settings are 1000Mhz with a 110% LiveOC - rock solid.
Most phones do 110% with no voltage tweaks, but not all. And remember with huge live oc you may need to bump arm voltages as well, specially on higher steps. Think about it, 120% your 1000mhz step becomes 1200. So logically use the default 1200mhz arm voltage for your 1000mhz step as a start.. This should be obvious. And stock voltages on init are medium or low leakage.
These are close to high leakage
100 1000
200 1050
400 1075
800 1100
1000 1125
1200 1150
These are what i use with 110% and 1200 max
Low target 800
High target 1500
I can go higher using just a little bit of common sense and some math.. I have had 125% but got about a reboot a day. But you need to use common sense in your arm voltages. Init are not quite as important
Sent from my SCH-I500 using xda premium
My chip set sucks but I seem to have good luck and speed with:
IO Scheduler: Deadline
Gov: Smoothass
Min CPU: 200
Max CPU: 1200
oc: 108%
Target low: 400
Target high: 1300
Voltages
ARM
1500 1500
1400 1450
1300 1400
1200 1350
1000 1275
800 1200
400 1050
200 975
100 950 <---not that that one matters
INT
1500 1200
1400 1175
1300 1175
1200 1175
1000 1150
800 1125
400 1125
200 1100
100 1000
This set up is more akin to a high leakage phone with a bit more voltage to compensate for the live OC.
Will def check this out. Thanks
Sent from my SCH-I500 using Tapatalk 2
neh4pres said:
Most phones do 110% with no voltage tweaks, but not all. And remember with huge live oc you may need to bump arm voltages as well, specially on higher steps. Think about it, 120% your 1000mhz step becomes 1200. So logically use the default 1200mhz arm voltage for your 1000mhz step as a start.. This should be obvious. And stock voltages on init are medium or low leakage.
These are close to high leakage
100 1000
200 1050
400 1075
800 1100
1000 1125
1200 1150
These are what i use with 110% and 1200 max
Low target 800
High target 1500
I can go higher using just a little bit of common sense and some math.. I have had 125% but got about a reboot a day. But you need to use common sense in your arm voltages. Init are not quite as important
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
How's your heat with these settings? I max out with 44c with 117% 1170mhz
Sent from my SCH-I500 using xda premium
Well what are you over clock preferred settings. Mine are min: 1.024 and Max: 1.92 governor: smartassV2 I/O scheduler: deadline.
Sent from my Liquud ICS HTC Thunderbolt on Tapatalk 2
I run 1.22 Max and 245 min. Its bad for the CPU to be clocked the way you are.
Sent from my Thunderbolt using Tapatalk 2
Max 1.4 gHz - Min 250 mHz
jonah1234 said:
Well what are you over clock preferred settings. Mine are min: 1.024 and Max: 1.92 governor: smartassV2 I/O scheduler: deadline.
Click to expand...
Click to collapse
What's your battery life like? And as stated above, that can't be good for the processor.
Excessive heat is the worst thing you can do to a processor.
Sent from my Thunderbolt using Tapatalk 2
ArmyAg08 said:
Max 1.4 gHz - Min 250 mHz
What's your battery life like? And as stated above, that can't be good for the processor.
Click to expand...
Click to collapse
Its been pretty bad I guess that's why I just changed to Max 1.408 and min: 368
Sent from my Liquud ICS HTC Thunderbolt on Tapatalk 2
jonah1234 said:
Its been pretty bad I guess that's why I just changed to Max 1.408 and min: 368
Sent from my Liquud ICS HTC Thunderbolt on Tapatalk 2
Click to expand...
Click to collapse
Oc really isn't even necessary on liquid ics. You'll never notice the difference if you out it back down to stock.
Sent from my Thunderbolt using Tapatalk 2
disconnecktie said:
Oc really isn't even necessary on liquid ics. You'll never notice the difference if you out it back down to stock.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
How is he overclocking on a ics rom anyways since we dont have kernel source I didnt think we could overclock ics roms yet.
I overclock to 1.2 ghz max and minimum either 245 or 368 mhz.
My battery life is pretty good, I'm running AOKP
droidjunkie said:
How is he overclocking on a ics rom anyways since we dont have kernel source I didnt think we could overclock ics roms yet.
Click to expand...
Click to collapse
The kernel is a modified gb kernel. It has oc capabilities.
Sent from my Thunderbolt using Tapatalk 2
disconnecktie said:
Excessive heat is the worst thing you can do to a processor.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
I've heard that's actually second to voltage.
Duely blundered from my thunderdolt.
Dannar said:
I've heard that's actually second to voltage.
Duely blundered from my thunderdolt.
Click to expand...
Click to collapse
Yea I could see voltage being a major issue for a processor. If the voltage is to high it would heat the processor up though. Soooooo..... you're right back to heat being a huge factor.
Sent from my Thunderbolt using Tapatalk 2
What speeds and settings could I safely use to conserve battery?
I'm new to clocking.
I just want long lasting battery life.
Sent from my ADR6400L using xda premium
Leave the speeds stock and undervolt. When undervolting don't ever check save for boot or whatever until you are certain those settings won't cause you problems. If you undervolt to low it will reboot your phone. Go to high and it could overheat but I doubt you will need to do that for any reason. I would start with a -50 uv and see if it is stable for a few hours. If you think its good -25 to all for a few more. I usually can't get below -75 across all voltages but every phone is different so some people can go -100.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Leave the speeds stock and undervolt. When undervolting don't ever check save for boot or whatever until you are certain those settings won't cause you problems. If you undervolt to low it will reboot your phone. Go to high and it could overheat but I doubt you will need to do that for any reason. I would start with a -50 uv and see if it is stable for a few hours. If you think its good -25 to all for a few more. I usually can't get below -75 across all voltages but every phone is different so some people can go -100.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Can I do this with setcpu?
Or would you recommend a different app?
Because when I started setcpu, it set me on 1036MHz max and 245MHz min. and the governor is set on lagfree, and then the scheduler is set on deadline.
Not really sure what to do here... lol.
Forgive me... like I said, I'm new to clocking.
I haven't touched anything since I started the app.. I was too concerned to.
It's not set on boot yet.
There's also a page for profiles and another for the governor... both of which are have me looking at them as if I were one of the three stooges looking at a supercomputer.
I have no idea what to do.
Sent from my ADR6400L using xda premium
Use incredicontrol. It's easier to use and profiles don't help much anyway. I would setup as 1024 max 245 min smartassv2 governor deadline scheduler -50 - -75 undervolt across the board.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Use incredicontrol. It's easier to use and profiles don't help much anyway. I would setup as 1024 max 245 min smartassv2 governor deadline scheduler -50 - -75 undervolt across the board.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
It's not giving me a 1024 max.
It jumps from 960000MHz to 1036800 MHz max. and then the min. is set to 245760MHz.
Next tab (SVS) has 850 in the box on the right all the way from 24576MHz to 245760MHz. Has 875 in the box beside 368640MHz, then 900 beside 768000MHz and so on.
Are you saying that in those small boxes on the right beside the xxx MHz I should lower that number by 50 all the way down to what I set the max to be?
Say from where it says 850 all the way from 24576MHz to 245760MHz, I should change that 850 to 800? And just -50 from every one all the way up the the MHz that I set as the max?
Wow, I hope I didn't just confuse you.
Sent from my ADR6400L using xda premium
What kernel are you using? The CPU and voltage table will vary with kernels.
Sent from my ADR6400L using Tapatalk 2
I'm running Gingeritis 3D v1.2 and running ziggy's kernel that comes with it.
Sent from my ADR6400L using xda premium
I am over locked to 1400 Max and 245min. Gives me nice battery life and great speed. ESP with the new Liquid ICS v.1.5 MR3
Sent from my ThunderBolt using xda app-developers app
Running Jester's AOSP ICS MR3 ROM, with SetCPU allowing from 245-1408. I have a custom profile for screen off to allow only up to 768 as well.
I just wanted to ask people because many kernels force 1.15 GHZ frequency and I wanted to ask people what do you think about it,is it safe or not and did anyone do stress test with SetCPU and is phone overheating with it.
Thanks,XperianPro.
It can do damage after a certain time. If you have it set for a long time on that frequency it will overheat! It is safe but as long as you don't use always use it. You should use it only to speed up some tasks! There is a reason why they have chosen not to set it as max frequency on stock rom.
Sent from my ST25i using xda app-developers app
Andrewasth said:
It can do damage after a certain time. If you have it set for a long time on that frequency it will overheat! It is safe but as long as you don't use always use it. You should use it only to speed up some tasks! There is a reason why they have chosen not to set it as max frequency on stock rom.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
the same ideal with u, i dont think it wll be safe for a long -time using.
I think Your CPU will be damaged when u used 1.15Ghz for a long time day to day
if the voltage used for getting 1.15ghz is the same as 1.0ghz then there is no difference...any heating up will be a minimal increase over the stock, if any
if voltage is higher...then i would imagine it would have an affect after some time as others stated
15% overclock is a joke, my Galaxy Mini was overclocked over 40% (from 600MHz to 864MHz, but i used 800MHz almost all the time), was hot like hell and still works fine now after almost 2 years and shows no signs of stopping
Unless you want your phone to last 20 years, YES, 1.15GHz is perfectly fine by me.
domcale said:
15% overclock is a joke, my Galaxy Mini was overclocked over 40% (from 600MHz to 864MHz, but i used 800MHz almost all the time), was hot like hell and still works fine now after almost 2 years and shows no signs of stopping
Unless you want your phone to last 20 years, YES, 1.15GHz is perfectly fine by me.
Click to expand...
Click to collapse
thats because Galaxy mini was Downclocked by samsung
other samsung devices wich have exactly the same cpu gpu are 800mhz at stock
and they can be ocd to 970MHz
galaxy mini can run those 800 mhz freqs easily because they downclocked the device
Sent from my S500 using xda app-developers app
SpaceCaker said:
thats because Galaxy mini was Downclocked by samsung
other samsung devices wich have exactly the same cpu gpu are 800mhz at stock
and they can be ocd to 970MHz
galaxy mini can run those 800 mhz freqs easily because they downclocked the device
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
That CPU on that board was designed to run at 600MHz, so you can't call it a downclocked CPU. Galaxy Ace and Mini had the same chipset, but the CPU itself wasn't completely the same. Not all Galaxy Minis where able to go 800MHz+
Same could be said for our Xperia U, Galaxy S2 has a dual-core Cortex A9 CPU running at 1.2GHz, so does that make our CPU downclocked? Ofcourse it doesn't, because the SoC is completely different, although the cores might be the same.
SpaceCaker said:
thats because Galaxy mini was Downclocked by samsung
other samsung devices wich have exactly the same cpu gpu are 800mhz at stock
and they can be ocd to 970MHz
galaxy mini can run those 800 mhz freqs easily because they downclocked the device
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
I have some Questions
How can u call it a downclock when it supposed to be 600 mhz as I know
And why could Samsung downclock the phone it is better to make it 800MHZ then
I think overclock is different between all chipset
Just like snabdragon and and our ****tyThor cpu
And sorry for my English
Mtakween said:
I have some Questions
How can u call it a downclock when it supposed to be 600 mhz as I know
And why could Samsung downclock the phone it is better to make it 800MHZ then
I think overclock is different between all chipset
Just like snabdragon and and our ****tyThor cpu
And sorry for my English
Click to expand...
Click to collapse
the phones with same cpu are all running 800mhz at default but because mini and fit where low end phones they downclocked the cpus
so the people who wanted faster phone buyes phone with more mhz
Sent from my S500 using xda app-developers app
SpaceCaker said:
the phones with same cpu are all running 800mhz at default but because mini and fit where low end phones they downclocked the cpus
so the people who wanted faster phone buyes phone with more mhz
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
That's how you make money! :sly:
Sent from my ST25i using xda app-developers app
domcale said:
15% overclock is a joke, my Galaxy Mini was overclocked over 40% (from 600MHz to 864MHz, but i used 800MHz almost all the time), was hot like hell and still works fine now after almost 2 years and shows no signs of stopping
Unless you want your phone to last 20 years, YES, 1.15GHz is perfectly fine by me.
Click to expand...
Click to collapse
B**** please, my Galaxy 3 was overclocked from 667 MHz to 1400 MHz and it still works
Sent from my Xperia Sola using Tapatalk 4 Beta
it is safe enough, my old xperia play was running at 1.8 ghz all the time, and it just works fine, till the screen broke (dropped the phone)
that cpu was designed to run at 1,0 ghz.
nickholtus said:
it is safe enough, my old xperia play was running at 1.8 ghz all the time, and it just works fine, till the screen broke (dropped the phone)
that cpu was designed to run at 1,0 ghz.
Click to expand...
Click to collapse
Well my old live with walkman worked to on 2.0 GHz but I could feel overheat remember that this is Novathor not Qualcomm.
So anyone brave enough to test phone with stresstest on 1.15 GHz for about two hours?
Sent from my Xperia U using xda app-developers app
There are kernel that boost cpu to 1.3 ghz... so 1.15ghz is safe for me
I read somewhere, that max safe frequency for NovaThor U8500 is 1,2 Ghz. So 1,15 Ghz should be safe enough.
Xperia [email protected] 2
It's safe i'm using my phone for almost 2 weeks at 1,15 Ghz and not a signle problem, not even overheat! I say it's 99.9% safe.
I am using 1.15ghz from about 3 months and no problems at all
I have been using 1.15 ghz for months now and I play games quite frequently and it has been safe and stable for me
I Think that the Novathor U8500 in focus, can be easly OC to 1.15 GHz without having particular trouble in fact of stability or hw issues, as it is capable of a theorical max of 1.2 GHZ ( as seen in some websites on fast google search "NovaThor U8500 max freq" )
.Hoping this is real, remember that this may affect nor the voltage but the steps that the governor has to do before reach the 1.15 GHz. Some good kernel, as most of the JB Designed kernel are set by default to max 1.15GHz.