Hi,
I read through approx. 50 pages of text and didn't find an answer:
Is there some kind of prevention to enter numbers like 6000mhz (eg when you meant 600) ?
Same with the voltage: could I enter and apply a critical value ? I tried it with "5" which lead to instant reboot.
Also: I can't find any explanation on what sd card speed fix does ?
Also: What does Jit do ?
THX
Low vsel will really cause reboot as it doesnt getr enough juice to run, on the other hand if you set it to 6000 but didnt change the vsel imo it would again reboot. That is if you accidentally put it, but if you deliberately want to try vsel 1000 @ 6000mhz, that I don't know,run test underwater to prevent meltdown. Good luck
Sent from my MB525 using XDA App
but it would immediately die and would not explode right ?
I think the VSel is limited to a max value of 78, or 80, or the limitation comes from the kernel, something like this.
Also there is a limitation from ARM to prevent hardware damage, there are a lot of failsafe mechanism built inside the hardware, beside the software.
maxi2mc said:
I think the VSel is limited to a max value of 78, or 80, or the limitation comes from the kernel, something like this.
Also there is a limitation from ARM to prevent hardware damage, there are a lot of failsafe mechanism built inside the hardware, beside the software.
Click to expand...
Click to collapse
No max vsel is 90. Max clock thats stable is 1380 MHz.
Sent from my MB525 using XDA App
Ok... so you can't really fry your hardware.
At worst it will die within a few hours/ days/ weeks ?
Related
call me a noob but i gotta ask, just what does the kernals do to the phone thats so special, and all the ghz talk means what. i rooted my device for the teather and customizing, and now i see all this talk of kernal this, overclock that, and different ghz people are getting can someone explain to me what this does for your phone, should i be interested???
popcorn kernals?
the higher your ghz the faster your phone is.
overclocking is making your ghz higher
and kernals is what allows you to overclock(sorta)
lol dude...you should prob. take your time with customization but ghz is in reference to the speed of the processor. So...theoretically the higher the number the better your phone should perform...t, eoretically lol. Note that with a higher ghz value the worse your battery life will be unless the kernel is written really well. Also the kernel is the code that controls the devices hardware. (brain)
The nice thing is that you can generally play with different kernels without having to wipe and redo your phone. Also, if you really want to play with the various kernels out there you should get setcpu from the market. It let's you set your phone to make use of the processor in an over clocked (OC) application but it can also let you under clock your phone when your not using it, such as when the screen is off. This will help you conserve battery life. But be careful, over clocking can lead to over heating and other problems if you''re not careful
sounds very interesting, hmmm. so in the coming months people could create kernals to acheive speeds to challenge dual core phones
the kernels already are challenging dual core phones. The thunderbolt currently has a 2ghz kernel. The motorola atrix is a 1 ghz dual core... Thunderbolt definately rivals it with overclock kernel
Sent from my ADR6400L using XDA App
A "kernel" is the OS layer that sits between the applications and hardware. So, when an application says "light up LED" it eventually goes through the kernel to do this, most likely by a request/system call.
The speed of a CPU is measured in hertz (frequency). So, a 1 Ghz CPU can perform over 1 billion operations in one second. The frequency can be increased (overclocked). When you do so, this can damage the CPU (most likely due to heat). Heat can also cause the CPU to run efficiently. So, if you overclock too high, you COULD end up running slower than if you had just left it at 1 Ghz. Changing the frequency can also hinder stability.
so with it being so dangerous how do u know what kernal to trust and whats a safe limit in hertz, do u stop at 1.5, because 2ghz sounds like pushing it
This thread is so full of misinformation it is comical. To start, higher clock speed does not always result in better performance.
Secondly, everyone has their own preference. The best bet is to find the perfect balance for your needs. For many people, overclocking the CPU is not very beneficial... since the device is already plenty fast at stock 1GHz speeds. A lot of users would rather use custom kernels to make their device more power efficient and use SMARTASS governors and lower voltages.
Mess around with kernels and see what you like the best! (always remember to create a backup before flashing... this allows you to easily revert back if something goes awry).
You mean they're not popcorn kernels?? Lol
bmcclure937 said:
This thread is so full of misinformation it is comical. To start, higher clock speed does not always result in better performance.
Secondly, everyone has their own preference. The best bet is to find the perfect balance for your needs. For many people, overclocking the CPU is not very beneficial... since the device is already plenty fast at stock 1GHz speeds. A lot of users would rather use custom kernels to make their device more power efficient and use SMARTASS governors and lower voltages.
Mess around with kernels and see what you like the best! (always remember to create a backup before flashing... this allows you to easily revert back if something goes awry).
Click to expand...
Click to collapse
Very well written and informative post, thanks brah!
skinien said:
A "kernel" is the OS layer that sits between the applications and hardware. So, when an application says "light up LED" it eventually goes through the kernel to do this, most likely by a request/system call.
The speed of a CPU is measured in hertz (frequency). So, a 1 Ghz CPU can perform over 1 billion operations in one second. The frequency can be increased (overclocked). When you do so, this can damage the CPU (most likely due to heat). Heat can also cause the CPU to run efficiently. So, if you overclock too high, you COULD end up running slower than if you had just left it at 1 Ghz. Changing the frequency can also hinder stability.
Click to expand...
Click to collapse
+1 ninja point for correctly saying "over 1 billion"
Sent from my ADR6400L using XDA App
It should be noted that most phones are definitely capable of being overclocked to a reasonable extent.
the majority of kernels we nexus one users play with, is undervolting the and playing with teh voltage tables to maximize standby battery life, at the same time overclocking the high end to improve performance. but really its about lowering voltage to improve battery life.
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
Flashed Faux123's Kernel acouple days ago and have a question.
Does this Application need to be running for the voltage changes to work? What about for the profiles set?
Thanks.
i don't know the answer because i haven't flashed a kernel. the quickest and best answer is to try yourself. setcpu is in the market.
I know, but it's hard to tell and I really don't want to undervolt too much more because I don't wanna see a crash, although I have yet to experience one. I have it set at
Respectively:
-100
-100
-50
-75
-300
-300
-300
Seems stable with and without SetCPU on while spamming Quadrant standard benches and I cannot tell if the voltages are working or not. Those extra volts being taken away can greatly help my battery life, but if it's not working without the program on there is literally no way to tell. I use Advanced Task Manager a lot and it takes out SetCPU all the time.
Maybe someone with more experience of the program can help me out.
why do people undervolt it? Why wouldn't Faux undervolt when he created it? I don't touch the voltages, but not sure how you test if undervolting would hurt performance.
There is a bunch of responses to undervolting in faux's kernel thread in the dev forum. But long story short u can't have more than 100 m's between jumps when setting your undervolting, or it simply wont apply it. Example.
75
75
75
75
125
200
225
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
There is a bunch of responses to undervolting in faux's kernel thread in the dev forum. But long story short u can't have more than 100 m's between jumps when setting your undervolting, or it simply wont apply it. Example.
75
75
75
75
125
200
225
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Really? I'll adjust my settings. Can you show me where it says that -100 jumps won't be applicable?
Probably going to adjust it to
100
100
75
75
175
275
300
edit: It's stable after around 10 Quadrant runs. I'd still like where you found that information though.
Thanks
Phoneguy589 said:
why do people undervolt it? Why wouldn't Faux undervolt when he created it? I don't touch the voltages, but not sure how you test if undervolting would hurt performance.
Click to expand...
Click to collapse
Well, I've been overclocking computers for years and something I've learned is that the lower your voltage is, the less degraded the processor will be after awhile. Such as, if you overclock the voltage too high, overtime you would need more voltage to obtain the same speed. Same thing applies when overclocking graphics cards.
Edit: Anyways, why are people dodging the main question
no you shouldnt have to keep setCPU running. i believe the app is just changing some sysfs files, so its one and done till the next time you open and change more values.
LivingChampion said:
Really? I'll adjust my settings. Can you show me where it says that -100 jumps won't be applicable?
Probably going to adjust it to
100
100
75
75
175
275
300
edit: It's stable after around 10 Quadrant runs. I'd still like where you found that information though.
Thanks
Well, I've been overclocking computers for years and something I've learned is that the lower your voltage is, the less degraded the processor will be after awhile. Such as, if you overclock the voltage too high, overtime you would need more voltage to obtain the same speed. Same thing applies when overclocking graphics cards.
Edit: Anyways, why are people dodging the main question
Click to expand...
Click to collapse
Probably going to adjust it to
100
100
75
75
175
275
300
Bro, this setting is left 770-470 = 300 or 770 - 300 = 470mv ?
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
Hello,
I installed cyanogenmod a few months ago and want to overclock now. Anybody who knows if it is dangerous? Is it possible that your cpu breaks down faster because of the overclocking? which are the acceptable cpu settings?
thanks
Lambo6 said:
Hello,
I installed cyanogenmod a few months ago and want to overclock now. Anybody who knows if it is dangerous? Is it possible that your cpu breaks down faster because of the overclocking? which are the acceptable cpu settings?
thanks
Click to expand...
Click to collapse
It's not that dangerous, but your cpu will wear out faster than normal, because a highter clockspeed means more heat. Acceptable cpu-settings? Depends... most phones seem to handle 691 without problems, anything above that is luck of the draw.
Set your desired cpu-settings (don't use set-on-boot)
If the setting is higher than your cpu can handle you will start experiencing crashes. If you have found a stable frequency for your phone, you can set it on boot so you don't have to think about that every time you restart your phone. If you set an unstable frequency and use set-on-boot, you will get a bootloop.
SmG67 said:
It's not that dangerous, but your cpu will wear out faster than normal, because a highter clockspeed means more heat. Acceptable cpu-settings? Depends... most phones seem to handle 691 without problems, anything above that is luck of the draw.
Set your desired cpu-settings (don't use set-on-boot)
If the setting is higher than your cpu can handle you will start experiencing crashes. If you have found a stable frequency for your phone, you can set it on boot so you don't have to think about that every time you restart your phone. If you set an unstable frequency and use set-on-boot, you will get a bootloop.
Click to expand...
Click to collapse
So the higher the frequency, the faster the cpu will wear out, just because of the heat. I will keep an eye on that.
thanks
Lambo6 said:
So the higher the frequency, the faster the cpu will wear out, just because of the heat. I will keep an eye on that.
thanks
Click to expand...
Click to collapse
When playing high-end games, I always put the cpu-clockspeed to 729 mhz...