Related
I just overclocked my droid using the tazkern 1.1 Besides being miserably slower than before when I boot up, It doesn't even give me the option to go up to 1.1 ghz. Any suggestions?
suggestion:
and don't take this wrongly in any way..
Stop overclocking so much!! It's a damn phone, not a gaming rig. That and also you really risk of damaging of your CPU and other internals...
My Milestone is running stock. It stays cool and is fast enough. This is after i tried some weeks running it on 800 Mhz. It gets too hot and that also during conversations.
I get where you're coming from but still, I was just getting a lil tired of the the thing lagging every time i opened the app drawer or market. I actually fiddled with it a little after I posted that and got it to run perfectly. And I think Im fixing to try out a 1.2ghz kernel just to see what happens. So far there's been no overheating or crashing.
ECC is kicking in and making your phone slower. Use a lower clock, your phone doesn't support it.
Actually its running quite smoothly so far. Ive been running it for around 30 mins now and its super fats, smooth, and appears stable. Ive tested it on youtube tho and its getting pretty warm.
Mines runs all day, every day at 1.2ghz. The quirks are not from the overclock. Thbey were always there.
Thats what Im on now. I think Im using the slayher 1.2ghz kernel.
Droid or Milestone?
If Droid, you're in the wrong forum. This is the Milestone one.
I have mine at 720mhz overclocked and it works fine,i dont have any heat problems,i always check the battery tempeture via SETCPU app,always is at 30C to 32C,not more than 32C!!!
I love it more tha my iphone
I think people need to learn the risks of overclocking.
You may say its stable and running fine and "just a little warm" but you are infact destroying your CPU.
If you touched your computer case and "it was a little warm" you would be worried.
Consistently hot systems aren't expected to last anywhere near as long a cooler systems. Thermal fatigue in silicon results in cracks in transistors, and transistor mounting failures, in particular. Of course, just one transistor failure on a complex system such as a motherboard or graphics card can result in the entire system failing. And a replacement board being an appropriate fix.
Source: http://ezinearticles.com/?The-Effect-of-Heat-on-CPUs-and-Computer-Systems&id=2310508
For computer CPUs, but you get the idea.
Oh dont worry. I turn my phone by the time it burstsinto flames. And btw i apologize but i did post this in the wrong forum. Oops.
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
DannyDroid said:
words
Click to expand...
Click to collapse
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
1xinfusion said:
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
Click to expand...
Click to collapse
The OMAP 3430 is a 65nm chip while the 3630 is a 45nm chip. Newer smaller manufacturing processes = cooler chips. They are NOT the same chips by far.
Furthermore, you realize that many memory chips are made equally. Then the memory manufacturers go and test out different batches. The ones that clock higher can be stamped as higher clocking or faster timing memory. They may be made the same, but usually the better made batches go to the higher end parts. The same goes when Intel makes CPUs. The crappy CPUs with some problems become Celerons. It might've been a Core 2 Duo or i7 or whatever, but Intel goes and disables cores/cuts off memory if it was not a good batch.
You can't look at models and go "well that CPU can do it, why can't mine."
If people have knowledge of CPU overclocking here where you understand that people look for certain serials/batches of Core i7s for best overclockability. Even though to Intel they all meet i7 930 specifications, there's still separation within the i7 930 crowd. Certain batches are better. Maybe not good enough to be an i7 950, but still better than the worst i7 930.
The other question is: What is stability? How do YOU determine what is stable? apps not crashing? In the overclocking world we run Linpack tests for like 24 hours before calling computers stable. Just because you can boot into Windows or Android or play Angry Birds for 3 hours doesn't mean much. It doesn't mean you don't suffer from bugs from overclocking. It's hard to say unless you do a full stress test on your CPU.
The 3600 OMAP is clearly superior to the 3400 series, but I do think that the latter is more overclockable.
I've had no overheating issues at 900MHz, 56 vsel, don't feel the need for higher frequency.
Will, this is all starting to go over my head. I'll just sit in the corner n twiddle my thumbs.
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
applebook said:
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
Click to expand...
Click to collapse
I was just trying to get at the same idea
I might have been too exact in my words but this is what i meant
and something fyi is that the OC capability of both chips are "capped" at 1.2ghz ... its just dangerous and unstable after that.
heat wise ? I'm inclined to believe that heavy wifi / 3g usage provides a higher source of heat than our petty oc-ing. Our cpus are clearly capable of this. true you make a good point. smaller architecture = cooler and less power. but the heat is probably out of the question. i use setcpu to display my temp. it never goes past the rated temperature. in fact it always stays at around 35c
when using wifi/3g on the other hand.. no need to say. the fact that these chips have no thermal barrier between them and the fact that the heat is able to be felt on the surface on your phone... in such close proximity to the radio chips, the cpu is not going to be heated by oc but by these other factors.
its safe to say you should lower your 3g / wifi usage to reduce thermal stress on your phone
stability wise... I'm not the one to stress test or w.e for long periods of time, but the link i've attached to my previous post shows a lot of people who have.
maybe you should check that out. I'm just here to relay information.
I have mine overclocked to 800 and it stable and quicker than stock its not all cpu its the amount of free memory you have at any given time
here is another very interesting page. this time regarding the droid
http://www.droidforums.net/forum/droid-hacks/20406-max-temp-while-overclocking-12.html
be aware that a lot of the temperatures are in fahrenheit.
highest temps of these guys average around 40-50 Celsius, way below the rated temp
Actually, mine has been running smooth this past week or so with no abnormal heat or crashes.
Sent from my Droid using Tapatalk
Have been reading through this (and GTab) forums about how others have been overclocking their units. Been a tad leery of doing this on either of my NCs as heat is one of the biggest "killers" of hardware. Now going from 800 to 1.0 or 1.1 isn't a tremendous jump I grant you but with only that small perforated port on the back, one wonders if that is enough area to dissapate the increased heat generated from an overclocked cpu. Over time that is.
Anyone concur or have other input on this? Most curious. Thanks all!
I've OCed mine and have yet to see or feel any damaging effects.
Sent from James' OCed Nook Color
I think alot of people worry way too much about this, for no reason.
Two things to keep in mind - the TI 3630 (which our chip the 3621 is based on) is rated to run at 1Ghz by default; so it isn't suprising that our chips are hitting 1.0-1.1 with no problem.
Next - we are bumping the clocks a bit, but we are not really raising the voltage, which is normally the major source of chip killing heat.
As such, the onboard temp sensors that we do have, have never given me a reason to worry, so i don't Yes, a chip that could probably run for 20 years, now may only run 18, but that really isn't a worry...
Great question. I've been thinking about that myself and am happy to hear a confident answer.
Sent from my NookColor using Tapatalk
Thanks Mr. Mudcat Appreciate the input. True, voltage is the heat demon but given how compact the NC is, one wonders if the restricted space might be a factor albeit negligible. 18 years on our NCs? The concept is boggling!
I've been OC'd to 1gHz since day one. I see more heat from charging than from heavy use at that speed.
sent from my rooted NC using XDA Premium.
I had the same fears when I got my Droid (stock 650 I believe) and after hours of forum reading and a friends advice, I OCed it to 800 to 1Ghz and have never had a problem in a year and a half.
I OCed my Nook right away to 925 and it runs soo smoothly!
im sorry for kinda going off topic but i cant overclock it the most i can go to is 528 which is lower then before.
My number one complaint so far about the nook is our OC speed... i think we can go higher.... heck my Droid 1 is at 1300 right now
Sent from one of those missing Droids
I haven't had any issue with OC to 1ghz. Been running strong with no real noticeable heat issues.
altimax98 said:
My number one complaint so far about the nook is our OC speed... i think we can go higher.... heck my Droid 1 is at 1300 right now
Sent from one of those missing Droids
Click to expand...
Click to collapse
Some nooks can go up to 1200, but not all. Maybe more voltage will help,but there comes a point where it is a risk where it can get too hot..
My OG Droid has been running at1Ghz for over a year now w/out problems. And that nearly 2x over stock speeds. I'm not overly concerned.
Heat management is the only concern, but I have yet to feel my NC get even remotely warm like my Droid does on occasion.
I have CM7 installed and mine won't run with less than 1.1ghz. I get fc's if I run stock clock speed. And I agree, I haven't noticed anything resembling excessive heat
I run OC'd on demand scaling with my max usually set to 1.1ghz, runs great I get no heat issues. I did nhave some stability issues, but updatiting the dalingren OC kernel for Froyo to I think the 2/25 version fixed that.
I use CPUtuner (free app on market); it works great, and has a good profiling system.
What are the benefits of OC/UV (particularly for CM7)?
I know of improved performance due to OC, but what does UV do in regards to performance. Also, how does an OC/UV kernel compare to one without the option?
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
xredjokerx said:
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
Click to expand...
Click to collapse
You can do either or both but don't have to do both. At some point UVing will cause a crash. Right before that point it can cause performance issues. See the link below for instructions on how to find an optimal UV level to maximize battery savings and performance.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
OCing improves speed but can also cause stability issues. For a captivate this usually isn't a problem until you get past 1.2 ghz. After that, it depends on the kernel but I have yet to find a kernel that is completely stable past 1.2 ghz under stressful conditions. Samsung designed the processor to handle 1.2 ghz and in theory it can go up to at least 1.6.
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
venomio said:
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
Click to expand...
Click to collapse
Odd as it sounds, my battery life on CM7 is close to 50% better when it is OC'ed to 1.2 ghz and UV'ed than it was on the froyo ROMs under the same conditions.
That really is odd :S I think I'll try it myself.
hey everybode!
i wanted to know i have rocket rom and i want to use setcpu to overclock my kernel
and sebastian is max to 1400 is thers good kernel that i can play with it till 1700mghz or 1900?
but it need to be stable
Abyss goes to 1700. My CPU can't take it, sadly
bubu23 said:
but it need to be stable
Click to expand...
Click to collapse
The stability is dependant on your hardware; some chips can only overclock to 1500Mhz and some can overclock all the way to 1900Mhz. It is not something the kernel has a say over.
Don't all of the notes have the same cpu? Why can some be overclocked and others not?
Sent from my GT-N7000 using Tapatalk
kkg720 said:
Don't all of the notes have the same cpu? Why can some be overclocked and others not?
Click to expand...
Click to collapse
They all can be overclocked, but how much is a different thing altogether. It's quite simple really, not every chip manufactured is of equal quality; some chips have more imperfections. The more imperfections the less it can be overclocked before it becomes unstable. It's the same thing as on PCs, too.
Stable is it when you do nothing and use it in originally form. Overcklocking need more Power more power is less time you enjoj your note!
Generally these chips are made to tolerate a certain speed, and because of variability, the manufacturer drops the speed tolerance to ensure overall quality. Some will still be able to manage 1500, 1700, or even 1900 (although rarely, I'd say). Just about all of them tolerate 1400, so very few are defective at the stated tolerance. With 5 million, you will get a few, however.
This is one of those rare occasions when statistics have a benefit in the real world!
jeromepearce said:
Generally these chips are made to tolerate a certain speed, and because of variability, the manufacturer drops the speed tolerance to ensure overall quality. Some will still be able to manage 1500, 1700, or even 1900 (although rarely, I'd say). Just about all of them tolerate 1400, so very few are defective at the stated tolerance. With 5 million, you will get a few, however.
This is one of those rare occasions when statistics have a benefit in the real world!
Click to expand...
Click to collapse
I will keep mine at stock speeds because ignorance is bliss
bubu23 said:
hey everybode!
i wanted to know i have rocket rom and i want to use setcpu to overclock my kernel
and sebastian is max to 1400 is thers good kernel that i can play with it till 1700mghz or 1900?
but it need to be stable
Click to expand...
Click to collapse
There are many out there that will let you overclock. Search the Android development forum.
Like most, I have flashed heaps of times, probably at least four or five times a week when I first got this wonderful Note, but in the last month or so have only been tempted to stray three or four times. Personally Franco 6 is best for me, because I favour battery life and stability rather than overclocking (1400MHz is not bad as a standard!!)
I would encourage you to try a few for a few days, as long as you backup often you should have a great experience!
Are all kernels capable of overclocking?
Is there one that overclocks the best?
How do you tell how high you can go?
Do you jusy keep overclocking until the NOte stops working?
If so, there must be a fine line.
jeffs99 said:
Are all kernels capable of overclocking?
Is there one that overclocks the best?
How do you tell how high you can go?
Do you jusy keep overclocking until the NOte stops working?
If so, there must be a fine line.
Click to expand...
Click to collapse
Stock kernel isn't capable of overclocking.
One way to tell is to download things like SetCPU which detects the range of the clockspeed. Another way is to simply read the description of the kernel thread.
How high your phone can go is an individual thing. You need to overclock in slight increments (say 50mhz at a time) and run a stability test to see if the phone crashes or not.
You DO NOT pull the slider all the way to 1.9 ghz and "see" if anything happens. If you fry your CPU, do not come to us for help.
This is why I don't like overclocking, it's a waste of time to run the stability tests, etc.
In summary, you need to raise it a little bit, and run stability tests and repeat the process until your phone crashes. At that point, you'd know the last safe-stable clockspeed that your CPU can take.
PoisonWolf said:
Stock kernel isn't capable of overclocking.
One way to tell is to download things like SetCPU which detects the range of the clockspeed. Another way is to simply read the description of the kernel thread.
How high your phone can go is an individual thing. You need to overclock in slight increments (say 50mhz at a time) and run a stability test to see if the phone crashes or not.
You DO NOT pull the slider all the way to 1.9 ghz and "see" if anything happens. If you fry your CPU, do not come to us for help.
This is why I don't like overclocking, it's a waste of time to run the stability tests, etc.
In summary, you need to raise it a little bit, and run stability tests and repeat the process until your phone crashes. At that point, you'd know the last safe-stable clockspeed that your CPU can take.
Click to expand...
Click to collapse
Thanks!
What do you recommend for a good stability test?
I'm on franco.kernel v10 and OC to 1600 using Tegrak. Tegrak runs the stability tests automatically and reverts to stock 1400 if unstable or a reboot occurs.
I tried 1700 but Note rebooted after about 2 minutes. Booted right back up at 1400 with no problems. Re-set to 1600 and running smoothly.
kraz
Sent from my Beautiful, White GT-N7000 using xda premium
Set CPU has a CPU stress test
Sent from my GT-N7000 using xda premium
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Shadow Life said:
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Click to expand...
Click to collapse
Yes you can, depending on the kernel you use, oc your phone even up to 1.5 ghz.
Flash Glitch, MNICS, Devil or Semaphore Kernel for ICS roms
Do so with care as OCing WILL degrade your processor faster.
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Oc SGS 1.2Ghz
nwsk said:
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Click to expand...
Click to collapse
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Shadow Life said:
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Click to expand...
Click to collapse
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
upichie said:
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
Click to expand...
Click to collapse
+1