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
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
Hello, I have an HTC thunderbolt, rooted with CM7, and installed setcpu and used autodetect and I put the CPU govern to "conservative" with minimum GHz 245 and maximum 1.8GHz and I am just wondering if this is safe? because I read some threads about Compatible kernels and I jave no idea what that means, they were also talkimg about undervolting, which agaim I do not know means, anyways thanks for reading
Watoy said:
Hello, I have an HTC thunderbolt, rooted with CM7, and installed setcpu and used autodetect and I put the CPU govern to "conservative" with minimum GHz 245 and maximum 1.8GHz and I am just wondering if this is safe? because I read some threads about Compatible kernels and I jave no idea what that means, they were also talkimg about undervolting, which agaim I do not know means, anyways thanks for reading
Click to expand...
Click to collapse
If your device will run reliably at 1.8GHz, then there's not much to worry about as long as the voltage isn't too high. High voltages and heat can shorten the SoC's life or kill it altogether. Generally, I don't recommend running that fast because the performance increase isn't as great from 1.6GHz to 1.8GHz as it is from 1.41GHz to 1.6GHz. These cores weren't meant to run any faster than 1.5GHz really, and anything past that doesn't increase the performance as much as the numbers might suggest.
Also, a conservative governor probably isn't ideal if you're willing to run a device that fast. That governor would seldom, if ever, use that kind of speed. I'd suggest smartass, smartassV2, ondemand, or interactive if you're looking to see a good boost in performance.
If you're looking for an app to view and adjust voltages, IncrediControl works well. For all the nitty-gritty of overclocking, I'd recommend reading my OC guide. It's in the "Second Post" of my Q&A thread. If you've got any questions, feel free to hit me up.
So does over clocking just speed things up? What are the real benefits
Boggus said:
So does over clocking just speed things up? What are the real benefits
Click to expand...
Click to collapse
I look at it like this. My screen eats up most of my battery. The less time it's on, the better. Overclocking uses more power for the CPU, but the display spends less time telling you it's waiting. It doesn't really add functionality, just speed and efficiency.
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
i was messing aroud with voltage control and cpu spy and i noticed that the cpu speed was only topping out at like 1ghz these phones come with dual core 1.5 ghz correct? mine has never seen that high of a speed is there a reason or am i missing something? on my s2 it had a 1.2 dual core cpu i believe and it said how long each speed had seen action and i even bumped it up to like 1.4. im nervous to mess around with the speed if its already 1.5 i was just gonna set it to like 1.6 or something.but it seems mine is running each core at just 1ghz can anyone lend me some light on this.
You have Power Saving ON , that limits max cpu speed.
ahh thank you so much another question on spu spy it says unused cpu stats im guessing is 1.1 and 1.2 is there a reason they are unused? also just a guess but looks like i cant go any higher than 1.5 with voltage control? is there another app that lets me bump it up to like 1.6? or 1.7?
Don't worry about it , cpuspy doesn't have full history of your cpu activity, cpu clocks up and down depending on load.
CpuSpy is not very reliable from my experience.
You need to flash a different kernel that will allow you to over clock the cpu. Voltage control will allow you to do this but you need a kernel that will let you over clock first.
Sent from my SPH-L710 using xda app-developers app
ok thanks.
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