Does anyone know if changes made to scaling governor or clock speeds are applied to all four cores or only to core #1? How would you verify that said changes have been applied to all cores?
I dont know much about this stuff and just assumed that it applied to all cores, but today i was just wasting some time with benchmarking apps and in the Device Details tab of the "Vellamo Mobile Benchmark" app, it showed only Core #1 was effected by any changes i made. The other three cores were unchanged...any thoughts?
I used "no-frills cpu control" to select governor and clock speed.
Thanks
I am certain that any change in governor for core 0 will affect the other cores equally.
Sent from my Nexus 4 using xda premium
I was messing around with this a bit ago. I use perfmon app. Any change in frequency or governor only seem to effect core 0. Also in that process I noticed my cores1-3 got stuck at only up to 1134 MHz. I can't seem to fix that anymore
Sent from my LG-E970 using Tapatalk 2
Related
Hi All,
I am writing this post to know what are the pros and cons for overclocking the phone. I know it helps to increase the clock rate, however if the phone can support it, why didnt the manufacturers made it that way.
And if we do it, are there any chances that the phone might blow up and stop working or something.
I tried to search on this topic but cudnt find anything.
please reply
Iam using LG Optimus One
Thanks !!
Hello.
The main plus is the increase in productivity phone.
The downside is that, theoretically possible to burn the phone, but I repeat it theoretically.
I myself have clocked the phone and nothing terrible has happened to him.
I don't think anything's going to burn as kermel always goes in panic if it can't handle it.
Sent from my LG-P500 using XDA Premium App
4silvertooth said:
I don't think anything's going to burn as kermel always goes in panic if it can't handle it.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
The processor won't burn, as 4silvertooth says the kernel will panic and you'll end up in an endless bootloop; 729 - 748 mhz is safe, 800mhz in most cases cause the kernel to panic.
Well oc has nothing to do with proceesor (don't laugh). Well at hardware level the clock (MHz) and processor are two different thing the crystal provides the MHz to processor and in return it computes at that speeds. So by oc we are telling crystal to oscillate at higher frequency. So if our processor can't handle higher frequency it tells kernel get lost I am not doing this for you as I am not able to execute instruction at such speeds. And all the governers are nothing but a rule for processors to execute tasks. Like if you select performance governer it tells CPU to execute at Max speed you have set. So what ever you set the min frequency it always uses Max speed no need to change min if u r using performance governer same for powersaving governer no matter what you have set for max it always work on min. So all the governers has different sets of rules.
Pros: CPU speeds up the execution
Cons: Crystal may get hot.
Bye.
Sent from my LG-P500 using XDA Premium App
22VIN said:
The processor won't burn, as 4silvertooth says the kernel will panic and you'll end up in an endless bootloop; 729 - 748 mhz is safe, 800mhz in most cases cause the kernel to panic.
Click to expand...
Click to collapse
No you wont go in bootloop.
Let me explain.
You will go in boot loop if you have set speed that processor can't handle and selected set on boot option. As the processor can't handle it and you are telling it to be always in that mode. Dont select set on boot. After reboot manually select oc. The second reason would be currepted filesystem as after kernel panic your phone has rebooted with unsaved changes chances are that filesystem table is currepted. Theres a command to check that I forgot name its like chkdsk for Linux. But no rom impliments that on unhandled reboots.
Sent from my LG-P500 using XDA Premium App
Good info
4silvertooth said:
Well oc has nothing to do with proceesor (don't laugh). Well at hardware level the clock (MHz) and processor are two different thing the crystal provides the MHz to processor and in return it computes at that speeds. So by oc we are telling crystal to oscillate at higher frequency. So if our processor can't handle higher frequency it tells kernel get lost I am not doing this for you as I am not able to execute instruction at such speeds. And all the governers are nothing but a rule for processors to execute tasks. Like if you select performance governer it tells CPU to execute at Max speed you have set. So what ever you set the min frequency it always uses Max speed no need to change min if u r using performance governer same for powersaving governer no matter what you have set for max it always work on min. So all the governers has different sets of rules.
Pros: CPU speeds up the execution
Cons: Crystal may get hot.
Bye.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Sent from my LG-P500 using XDA App
i'm more concerned about the processors life. can overclocking to 729 in long term kill the processor.
coolbuy said:
i'm more concerned about the processors life. can overclocking to 729 in long term kill the processor.
Click to expand...
Click to collapse
Even I am concerned about such facts, and also why didnt the manufacturers made it that way if it can support such speed without any problem.
Thanks for those who replied, Much appreciated
I just got my SGS2 today and was so eager I had it rooted within 2 hours of it being placed in my hands. I was messing around in quadrant and clicked System Information..I scrolled to the CPU section and by Cores it says 1..but my friends sgs2 says 2 cores. He has the Sprint model.
Now why does it say I only have 1 core when this phone has 2?
re: CORES
Ensomniacc said:
I just got my SGS2 today and was so eager I had it rooted within 2 hours of it being placed in my hands. I was messing around in quadrant and clicked System Information..I scrolled to the CPU section and by Cores it says 1..but my friends sgs2 says 2 cores. He has the Sprint model.
Now why does it say I only have 1 core when this phone has 2?
Click to expand...
Click to collapse
Because sometimes depending on the service providor some details
shown are not as specific as with other service providors.
Now if your friend was on AT&T like you you noticed
this difference then it would be a different matter.
Depends on your current frequency... when mine is 500MHz or higher, Quadrant returns 2 cores... when running low frequencies, it will return value of 1 core. If you load up a few apps, then jump over to Quadrant, it will most likely show 2 cores as your CPU frequency will be higher.
Sent from my SAMSUNG-SGH-I777 using XDA App
The exynos cores on our phones run asynchronous - when not needed one of the cores will power down, and as soon as it is needed it will ramp up. so just as the poster above posted when the first processor throttles down the second will shut off to save power, there is no need for two processors running using battery when demand for them is low.
Sent from my SAMSUNG-SGH-I777 using XDA App
DoctorQMM said:
Depends on your current frequency... when mine is 500MHz or higher, Quadrant returns 2 cores... when running low frequencies, it will return value of 1 core. If you load up a few apps, then jump over to Quadrant, it will most likely show 2 cores as your CPU frequency will be higher.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Not exactly depending on frequency... I don't remember the exact hotplugging heuristic.
But in general - The second core is shut off by default and only gets powered on when under load.
Note that some dual-core phones (like Atrix) always show two cores because they are unable to fully remove the second core from a system and completely shut it down to save power. (Well, I assume the Atrix - I know the Tegra in my Tab 10.1 can't hotplug the second core out/in.)
Running unnamed 1.2.0. Do I need set CPU to protect my processor? I appreciate any Input.
Sent from my SAMSUNG-SGH-I777 using XDA App
Protect your processor from what?
UnNamed sets the CPU to a conservative scaling profile. That is part of why it helps battery life. SetCPU doesn't necessarily "protect" for CPU from anything, it allows you to change the default profile and along with other settings to whatever you want within the capabilities of the CPU.
to set cpu to protect your processor? no...
if anything you'd cause damage.
to set cpu to OC or change governor? maybe you can change to on demand.
I see no reason to OC this. esp with unnamed its very snappy for me and I'd rather save the battery.
Thanks guys. I am really new to Droid and didn't want to fry anything is all.
Sent from my SAMSUNG-SGH-I777 using XDA App
Actually Unnamed defaults to ondemand - but technically, the processor should be able to survive extended operation at 1.2 GHz with the Performance governor even.
SetCPU is nice just to act as a barrier to rogue apps that attempt to eat your battery in the background when the screen is off. It also lets you tune the governor settings exactly to your liking.
Is it your kernel then that defaults it to conservative? Because I didn't think I had ever changed the profile and I know it is set to conservative.
Sent from my SAMSUNG-SGH-I777 using xda premium
I'm using CM9 RC1 on a Note right now and the default settings are 200 Mhz min and 1.4 Ghz max.
Is there any benefit to using a higher min like 500 Mhz or is it just a waste of power? I'd assume it would be slightly faster upon wake up.
You can always try, as long as you know what you're doing. Are you familiar with overclocking, and how to test higher clock speeds without having them set on boot until you have tested for stability. 200MHz seems a bit low for echo 0, but you can try to start bumping up echo table 0 values slowly and at small incremental increases. For instance, from 200MHz, go to 220MHz and test, then if stable bump up to 240MHz and so on. Jumping from 200MHz to 500MHz may not be the best idea without a "seasoning" of the CPU at echo table 0...
Sent from my MB865 using xda's premium carrier pigeon service
I've overclocked on PCs before but I'm not overclocking. I just want to know if there's any benefit to setting a higher min speed.
It probably will not yield any performance increase to clock your lowest frequently scaling higher, since likely your device's governor (I'm assuming) is set to mot_hotplug.
Unless you're using a governor setting of "performance" or the like, your CPU's governor will step down through the kernel's frequently tables as determined by the load. Again, unless you're running a governor setting that does anything but what is similarly done with mot_hotplug the CPU's core(s) will be turned off when not demanded.
Sent from my ME860 using xda premium
Ive been using android overclock. On demand. and staying at 350 to 1420 and its been working really well as far as battery usage
I´ve been using ondemand-noop min 245, max 1024
Ok. That was 2012. Now is 2020. Updates to minimum and maximum for Android 8/9???
quantum-codes said:
Ok. That was 2012. Now is 2020. Updates to minimum and maximum for Android 8/9???
Click to expand...
Click to collapse
Just to have said it: CPU speed affects performance of Android device, doesn't depend on Android version. The more a processor is stressed the more the battery is drained. IMHO CPU speeds matter less than they did in the past, thanks to the advent of multi-core processors as they installed in ( most ) modern phones. Multi-core processors always have a "mixed speed": Not all cores are stressed the same way. Also, note how these multi-cores processors are designed: Octa-cores for example aren't using all 8 cores at once. Octa-cores use 4 high speed cores and 4 low speed power efficient cores. An Octa-core uses the 4 power efficient cores most of the time, but switches to the higher speed cores as needed for power intensive tasks.
I don't think there is a way to configure each cpu-core's max /min speed separately. BTW: Even today most Android apps/games make use of 2 cores only.
Hey, i overclocked my ace 2 to 1100MHZ my question is, is it safe to keep it on maximum at all times?.
1100 MIN and 1100 MAX
Thank you.
That's probably something you shouldn't do as a "full-time" clock speed. Remember, your CPU's scaling frequency is determined upon load called upon from system process, applications, and so on. When load is minimal, the CPU scaling frequently will fall back to lower table speeds, and spike to higher when necessary. Having no "resting" frequency will cause: more heat generated from the lack of these lower frequencies, shortened battery life expectancy, and possibly shortened CPU lifespan.
Unless you're using a governor setting of "performance" or the like, your CPU's governor will step down through the kernel's frequently tables as determined by the load. Again, unless you're running a governor setting that does anything but what is similarly done with mot_hotplug the CPU's core(s) will be turned off when not demanded.
Be kind to your CPU, give it a break. I can't imagine any reason to clock to such high values to run all the time. Don't you put your phone to sleep ever? Why would you want the CPU running at 1100MHz while sleeping? Doesn't seem like a logical idea to me...
Sent from my MB865 using xda's premium carrier pigeon service
Thanks for replying, you are right i shouldn't have it on that frequency at all times when im not using it cause whats the point of that.
I am new to all this overclocking and rooting stuff, got a lot to learn haha.
iFrankie said:
Thanks for replying, you are right i shouldn't have it on that frequency at all times when im not using it cause whats the point of that.
I am new to all this overclocking and rooting stuff, got a lot to learn haha.
Click to expand...
Click to collapse
No worries. Just don't want to see you fry out your CPU by not giving it the ability to have 'downtime'.
Edit: You can even change the scaling frequency at echo 0 to a lower table value, to give even more ability to "rest". If you need any more info, don't hesitate to PM me. I've done a lot of experimentation with overclocking over the last several months...
Sent from my MB865 using xda's premium carrier pigeon service