I flashed Sebastion's overclock kernel and installed System Tuner. I see that I have option to set the CPU overclocked to 1.8 GHz, I didn't even know it could go this high. Then I see "CPU0" and "CPU1". Are these both cores? Because if they are, I only see "CPU0" being overclocked. Does this mean only one core is being used at such a high speed?
I've set it for 1.51GHz and "ondemand". That seems reasonable, right? Any other suggestions?
Some kernels allow you to clock to 1.9, but its not recommended as you can easily fry your chip. CPU 0 and CPU 1 are the two cores, you are correct. I'm not entirely sure if one or both cores are overclocked, but my suspicions would be only the first core, simply because the 'ondemand' governor only turns on the second core if the first one is unable to run process the load efficiently. 1.5 is pretty reasonable yes, but you can even make it lower an still get good performance, an lower clock speeds mean slightly better battery too. I'm running at 1.4 with a badass governor, which is better again for battery consumption.
Sent from my Sensational pokeball that caught Charmeleon 5.1.0!
Related
This is a question for those who have overclocked their Xoom. How much is overclocking to 1.5Ghz affecting battery life?
Overclocking would be the only reason I would root right now, and I am trying to make up my mind on whether to do it.
My battery life is better after using setcpu to overclock. The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom) with setCPU you are extending the top end of how fast the CPU can go. The clever bit is you can also tell your xoom to slow itself down and go very efficient when the screen is off or if the chipset gets too hot (which it never has). If you do go for it I recommend using setcpu using interactive scaling (prioritising the user interface) and whack the max speed up to 1500 and the min speed down to 217 mhz
I wouldn't recommend setting screen-off profiles at the moment. It seems to lead to some strange issues once in a while.
That said, because you're only going to 1.5 GHz when needed, battery life doesn't really suffer. Additionally, at least in my usage, my screen uses ~70-85% of my battery. This is even during heaving gaming, where the Tegra 2 really has to work hard.
I wouldn't worry about its effects, personally.
MrGinger said:
The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom)
Click to expand...
Click to collapse
All CPUs do this, not just Tegras.
Re scaling, never said otherwise I've never had a problem with screen off profile. Maybe just lucky
Right so my phone can get pretty hot some times and I was just wondering if I undervolt it will it reduce the heat of my phone?
Also how much difference does UV actually show
It can't, because you can undervoltage not much or your phone won't be stable anymore.I think the easier way is to downclock your cpu speed.
likuku said:
It can help in term of technical, but in actually at the rate you can see the different of it.I don't think your phone will still stable or functional.
Click to expand...
Click to collapse
That's really hard to understand what you're trying to say...
Sent from my HTC Sensation 4G using XDA App
likuku said:
It can't, because you can undervoltage not much or your phone won't be stable anymore.I think the easier way is to downclock your cpu speed.
Click to expand...
Click to collapse
Galaxa12 said:
That's really hard to understand what you're trying to say...
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
He means that you can use an app like SetCPU to underclock or lower the clock frequency of your phones CPU, this will leave you a slower but cooler phone.
yes, if you undervolt you reduce cpu "power consuption" as equally as how many volt you decrese.. but.. if you undervolt too much, you lose cpu stability, so, if you undervolt you have to underclock, the same for overclock, if you overclock you may overvolt
it's different for all peoples, some users could have a better cpu (with less impurity), it can be overcloccked better with less overvolt, some can have a bad cpu chip, it means they have to overvolt so much for a little overclock
i have a sensation normally with -75mV undervolt and stock clock, it's stabe, so, am i lucky?
Temperature is a function of voltage + clockspeed. It is recommended you stay at 1.2ghz for good balance b/w performance, temp, and battery consumption.
To easily find your optimal voltage threshold, globally undervolt in stages of 12.5mv until your phone because unstable. Then increase it by 1 stage and that is the optimal voltage your phone should be running at.
Of course you can even go as far as tweak voltages at different clock speeds. Usually there is much more room to UV the lower clocks (192 and 384mhz around 800 or 812.5mv) than the higher clocks.
Hope this helps
iba21 said:
yes, if you undervolt you reduce cpu "power consuption" as equally as how many volt you decrese.. but.. if you undervolt too much, you lose cpu stability, so, if you undervolt you have to underclock, the same for overclock, if you overclock you may overvolt
it's different for all peoples, some users could have a better cpu (with less impurity), it can be overcloccked better with less overvolt, some can have a bad cpu chip, it means they have to overvolt so much for a little overclock
i have a sensation normally with -75mV undervolt and stock clock, it's stabe, so, am i lucky?
Click to expand...
Click to collapse
Getting a Poco x3 pro soon and thinking about undervolting could you add me on discord and help me? If so add Gokn#4488
Hello!
as I finaly rooted my TF (after a year of stock ) I have already hit few obstacles while making it perfect. Now i have a question regarding overclocking.
My device: ARHD Rom with guevors kernel 21.4
I use my TF at 1,6ghz via SetCPU. In CPUStats it says it doesnt use 1,4ghz and 1.5ghz freqs at all as the time at those freqs is zero. But when I clock it up to 1.4 or 1.5, it does use them (note: when set to 1.5ghz, 1.4ghz freq is still not used). What could be the reason for that?
Thank you for your answers
miHah
Looking at cpu histories it usually defaults to the lower stuff except when you do complex calculations, in which it uses as much as it can until it's done. That's why it doesn't use those middle freqs as much, if that makes any sense.
I agree with Thing o Doom. A lot depends on what the processor/software decides it needs or wants.
I stopped using a wide range of frequency like 216-1200 and stuck with a straight 1200MHz only on the min and max.
Depending on the CPU load will determine whether it even hits a certain frequency and also based on the type of governor.
If you have a governor that is set for performance and your range is 1400 - 1600, the governor interacts with the rest of the system and may ramp straight up to 1600 without every hitting 1500.
Hope that expands on Doom's answer.
I use interactive gov. and usualy cpu clocks scale at every cpu freq described in kernels scaling. I use 216-1400 now and cpu uses all clocks in that range (depends on the need ofc). But if i use 216-1600 then not all of the freqs are used. I meant to say if u scale it to 216-1600 there should be some point where cpu would use 1400mhz freq, but mine doesnt at all. So the scaling goes from 1200 directly to 1600 and no in between resulting the cpu to be more time at higher clocks when not actualy needed (when it could just use 1400 or 1500mhz).
Anyway, i now use scale of 216-1400mhz and seems to be working great dunno why I even bothered with 1600, but this one thing not scaling at those two freqs did scare me as I thought there is smth wrong with my tf
I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
k-semler said:
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
Click to expand...
Click to collapse
uhh well.... yea and no. there are a few things you need to understand about microprocessors. no two are alike. they are built on a scale of a few nanometers and any difference causes a significant difference. to keep production numbers up there is a line they have to draw between performance potential and stability. more chips will be stable at lower clocks so they pick an speed they can get a high production number out of. sometimes a whole line of chips is produced with exactly the same core. chips that pass the highest get boxed as the highest performing and priced. chips that dont pass will either have specific features turned off, cores turned off or be underclocked and sold as lower models. in addition to that the top performing models are actually over priced, and often many more pass the tests than they need so perfectly good processors are intentionally disabled to fill the market for lower speed processors, so yes the cpu may be "underclocked" in a sense. but i don't know if that really applies to the infuse because i don't know if there are any chips in the same family that have a higher rated clock speed, if there are they aren't used in phones.
in example, on my pc i have a 3 core processor, it's actually a 4 core and i can even turn the 4th core on in bios, but a certain percentage of that particular model of chip will be unstable with the 4th core active.
another thing to understand is how the clock speed is set. there is a buss and a table of multipliers and dividers. so as one part of the chip oscillates at one frequency the multipliers and dividers say how may times per oscillation the other components go. the cpu speed changes by changing these multiplier values. the problem is that there are only so many multipliers the cpu is designed to use. this is a hardware limitation and can't be overcome so at some point the only way to get more clock speed is to change the buss speed which affects the entire system and will cause instability in most cases. occasionally you can get around this if you change the multiplier values for other componants as well but it's probably not a good idea to mess with it. the hummingbird chip only has multipliers to go to 1600mhz regardless of stability unless you mess with the buss, one developer got the galaxy s to 1700 with buss overclocking but some things didn't really work at that speed and it took a lot of changes to other system clocks. snapdragon chips can go to higher clocks and process numbers better but the hummingbird is better for graphics and multimedia which is more important on a modern phone imho.
so yeah 1600 is it, as far as practicality goes anyway. there are a few infuses that can only go to 1400-1500 as well and galaxy s phones which have the same clock limitations but are only rates for 1000mhz rarely go to 1600, but a few do, my captivate was absolutely peaked out at 1300, believe me i tried to get it higher, i tried a lot of things with voltages to try to get it stable, but even 1300 took some doing. it took a long time before developers even produced a kernel for the sgs that used clocks over 1200 because many of the early builds of the sgs series were much like mine and were not stable at high speeds.
Beautiful. :thumbup:
Sent from my SGH-I997 using xda app-developers app