I've noticed with this chevyno1 kernal for cyanogen rc2 I downloaded, my phone gets pretty warm. What temperatures are unsafe for a mobile cpu? I know 60 and above is bad for a desktop/laptop cpu, but I'm not sure if it's the same for cell phone's.
Sent from my Droid using XDA App
Well it depends, I've had mine get up to 135. The charger automatically shuts off at about 125 to 130 so it doesn't help to over heat it but also it seems to get a little buggy around 120 to 125. Normally the phone should shut its self down at a certain temperature also but you can set one you think is safe or precautionary if you don't like it that hot. Setcpu has temp safety settings where it'll either not allow the phone to operate passed a certain speed you specify once it gets to a certain temp. As far as bad I'm not sure but any overclocking will deminish the life of CPU just depends how fast you go and how hot you let it get. I ran chevyno1 4.6 and other roms but just switched to new sapphire rom using a 1 ghz kernel and haven't seen my CPU to go passed 110 yet. Its a very nice rom customizable fast and smooth.
Sapphire v1.0.0> 928Droid Black Glass Theme> Sholes 1.0 Ghz 7 Slot Kernel.
125 C...? Dear lord o_o
Sent from my Droid using XDA App
Somebody doesn't like the metric system...
I am only basing this on my phone and usage, I haven't gotten this data from anywhere; I am using a 7 slot 1.1GHz low-voltage kernel.
I have SetCPU to drop the clock from 1.1GHz to 900MHz when the CPU temp reaches 38 degrees C. I have it drop to 400MHz at 50 C, but have yet to reach that temperature.
Sent from my Droid using XDA App
Related
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Nerz said:
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Click to expand...
Click to collapse
i have never seen the cpu get hot in my phone. it gets unstable before any heat is detected, but my phone is not very overclockable, i can get 1.3 with much care to the uv settings. i wouldnt worry about heat until the 1.4 mark, even then you are probably fine. the newer qualcom chips have been set to run at 1.9ghz and dont burn up they are on the same size architecture as ours. these arm chips run at such low voltages that heat is not really a big problem. i dont think anyone on the board has killed a hummingbird from overclocking it.
I think your speaking pre-emptively about not burning up.
Just because the chip doesn't instantly melt doesn't mean your not risking electro migration.
Nerz said:
So i have been able to clock my captivate to a stable 1300 using suckerpunch #57. I'm wondering though how often do you think are phones actually use this frequency? i know when i'm running a psx emulator im sure that it probably has the cpu maxed out, which runs tekken 3 beautifully now at no lower then 48 fps, but i hope on not much else (would be nice to find an app that would put the cpu used clock speed on taskbar). Only reason i wonder is because of course phones don't have cooling systems like computers so i worry about cpu life.
Click to expand...
Click to collapse
this chip has a built in fail safe and can run as long as it can handle it automatically freezes or reboot your phone above its capable limit. If you want real time monitoring of your cpu clock speed/usage, ram usage and battery temp download Temp+CPU V2 widget from the market pretty good app. enjoy
Hi guys. I looking forward to ROM with can work at 1.2GHz. I think most of XDA users have modified ROM working at 1.2GHz, so everything fine? It's save to run Galxy Tab at 1.2GHz?
1.2 has been stable for me for well over a month now. I run 1.4 from time to time when I want to play games or just show off. Some tabs report overheating, but use setCPU profiles to alert you if that happens and you wont run into any problems. I have setCPU to warn me at 40 degrees and at 41 it goes down to 800mhz. Just keep your eyes on the temperature to be safe.
Its a popular misconception that the tab runs at overclock frequency ALL THE time. Unless the kernel (which I seriously doubt coz that would be stupid) is programmed to run at maximum clock frequency or you have set it up yourself (with setCPU or voltage control or w/e overclocking utility you use) which is basically an explosion waiting to happen (or at least crash). The tab runs at a RANGE of frequencies it runs at max frequency (1.2 or 1.4) on demand like playing a game or an HD movie or anything stressful.
DarkPal said:
Its a popular misconception that the tab runs at overclock frequency ALL THE time. Unless the kernel (which I seriously doubt coz that would be stupid) is programmed to run at maximum clock frequency or you have set it up yourself (with setCPU or voltage control or w/e overclocking utility you use) which is basically an explosion waiting to happen (or at least crash). The tab runs at a RANGE of frequencies it runs at max frequency (1.2 or 1.4) on demand like playing a game or an HD movie or anything stressful.
Click to expand...
Click to collapse
You want to say, like PC CPU, that Tab ARM Cortex A8 chip working on range of frequencies? It's possible because of battery save, but I think Tab's Cortex A8 is designed to work at 1GHz all the time without any problems.
Winudert said:
You want to say, like PC CPU, that Tab ARM Cortex A8 chip working on range of frequencies? It's possible because of battery save, but I think Tab's Cortex A8 is designed to work at 1GHz all the time without any problems.
Click to expand...
Click to collapse
DarkPal is right.
While you're theoretically correct too, in the sense that the Tab's Hummingbird is designed to be able to work at 1Ghz all the time, by why would you want to do that? It'll kill your battery if you set it to run at 1Ghz all the time, much less at the higher frequencies that these CPU were not rated to run. Not to mention the heat issues.
There's a reason these ARM-based chips scale up and down the frequency scale according to the CPU governors' settings and load demand, and that's why ARM-based chips are known for their battery savings.
galaxy tab 4G Lte runs at 1.2Ghz
http://www.gsmarena.com/samsung_galaxy_tab_4g_lte-3769.php
I've been running mine at 1.4 for about a month now but undervolted too. Perfectly stable. If you are using SetCPU app you'll be able to see how much time your tab spends at each level.
Sent from my GT-P1000 using XDA Premium App
Bit of a noob question but apart from games in what other areas does overclocking help?
I notice the difference with video. Crisper and smoother. It's not a big thing, but why not do it if you can?
purline said:
I notice the difference with video. Crisper and smoother. It's not a big thing, but why not do it if you can?
Click to expand...
Click to collapse
Because it does run your battery faster and hotter, as well as the processor itself...
Force a sprinter to run 5 miles, they can do it, but I bet they tear something along the way...
Oh yeah, thanks to the illustrious Rotohammer that's not a problem...
Ever since I upgraded to Roto's JMI ROM and a few other tweaks [ see my post: http://forum.xda-developers.com/showthread.php?p=12786456*** Galaxy Tab Master Tweak Thread*** ] the battery life on the galaxy tab has been absolutely insane. Even though the phone is overclocked to 1.4 Mhz.
I used to come home at the end of the day (before overclocking) and my battery would be approximately 15 percent, now it's always over 50 percent. I don't know what the black magic is, but it is good...
Sent from my GT-P1000 using XDA Premium App
Thinking if overclocking my captivate to 1.6 but will it shorten the like time significantly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
UV
Jusrertiner said:
Thinking if overclocking my captivate to 1.6 but will it shorten the like time significantly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
UV
Click to expand...
Click to collapse
What is your desire to oc?
Sent from my Captivate using XDA Premium
Very risky
Very.
Yes it will shorten the life on your phone no way to know how much though. unless you are into it and read a fair amount about it i would not oc. The benefits just are not that significant
Sent from my GT-I9000 using XDA App
start at 1.2 if your scared
It will not shorten the life to the extent that it will not last the update period
Miui Captivate
Oh well how long do u think it will last. N I want it for the extra speed in games mostly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
OC and UV
If you want some extra speed, still to 1.2 and below and try using Pimp My CPU to drop the voltage -50mV across the board (try messing around with it more to get more drops without charge deaths and etc). By doing this, I am running mine currently at 1.2 ghz with a -100mV voltage drop, which is the same as stock 1.0 ghz voltage level.
It's overvolting that kills a processor, not overclocking. More voltage means more power for the processor to dissipate as heat and some components are not spec'd to take more voltage than stock.
I hope this helps.
I have read that you should be safe up to 1300mv(not mhz). Usually 1200 mhz will run that. After 1300mv, you risk damage. It also can cause charging issues (phone uses more battery than it is charging).
Don't get me wrong, at one point I had my phone up to 1500 mhz, just to check kernel stability. Didn't stay there. Also remember that each phone is different when it comes to this. Some phones tolerate it better than others. That is why entered no definitive guide to it, only recommendations.
You shouldn't be scared to OC. but its your phones processor because everyones is different. My captivate can only get up to. 1.5. Then it freezes up. My inspire 4g can get up to 1.9 without a problem while others can only get to 1.6 or so. So try it out
Sent from my Inspire 4G using XDA Premium App
I overclocked to ,1.3 and my while screen turn purple and green n I had to pull battery. Is that a crash?
Samsung captivate
glitch kernel
cyanogenmod 7 #57
OC and UV
Hello
I recently acquired a nook color and i am going to install cynogen mod 7.1 and google apps from clock work recovery method, but i want to overclcok to 1.2 or 1.3 ghz, i understand that cynogen mod has an overclock facility built in, the part i am not sure about is to reach 1.2 ghz or 1.3 ghz do i have to use dalingrin overclock kernel to achieve these speeds, or is it possible in cynogen mod 7.1 without the kernel.
Any info would be appreciated.
Regards
Mark
Dal's kernel has been included in there for a while now. If you use 7.1 stable to later nighlies you are definitely safe.
ok, thats great, thanks for the reply, appreciated.
Regards
Mark
It appears the GPU may run best at 1200, even thou the CPU can do up to 1300.
It certainly seems to be true that going past 1200 can slow down graphic intensive operations. I am guessing that's probably because the graphics processor has to run at a ratio of the CPU and going past 1200 ends up with a lower graphics frequency.
But depending on the type of applications used there can be benefit in going higher and most Nooks seem to be capable of 1350. This can be seen in two different benchmarks. Quadrant gives significantly higher scores at 1350 than 1200 whilst the graphically more intensive Nenamark is slower at 1350 then 1200.
I ended up using 1200 anyway as it feels fast and probably also helps with battery life.
Check the voltage settings as well as these can normally be lowered a bit to help again with battery life. I use the one's originally quoted by Dal and don't have any stability issues. ( 09.25 / 1.05 / 1.2 / 1.275 / 1.325)
I did a comparison of 1200 and 1350 MHz with the Sunspider JavaScript bench. 1350 is faster but frankly I have a hard time telling the difference between even stock clock and 1350 in actual practical usage.
The most obvious speed boost I've found is running 16bit color. Big difference in browser scrolling performance.
Is overclocking it fully safe?
GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
From the standpoint that breathing in a metropolitan area is not fully safe, no it is not.
I use the stepper built-in to 7.1 stable and have never given it a second thought.
Try nook color tweaks.
Sent from my [R3] BLURR3D DROID BIONIC using XDA App.
GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
I have run at 1200 / 1350 for the last 4 months and it has been stable and I have not seen any real detectable difference in battery performance or in how warm the device gets. The governor means that a lot of the time the Nook is running at lower clock speed anyway.
I don't recollect seeing any reports of damage on this forum to the Nook through over-clocking. Increasing voltages from the stock values on the other hand is probably not a good idea. There may possibly be longer term effects from overclocking but I'd guess the effect on lifetime is small enough that most people will have changed their device before it is significant.
GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
Being that Nooks CPU is underclocked by default. It is very safe.
---------------------------------
Sent from my LG Optimus V using Tapatalk
I am using Carbon ROM 4.3 with Chronic kernal. The settings were at a min of ~1700mhz and a max of ~2200mhz. Before i set this I let the cpu temp cool to about 23 degrees Celsius. I then set the cpu governor to performance. Then I started running AnTuTu benchmark ver4. After the cpu integer test the cpu froze up. I was cooling my phone using a freezer with the phone on a paper towel which was on a bag of ice. The CPU crashed at the CPU float point test.
After another test I found that my CPU becomes unstable after 2160mhz.
The settings for the posted benchmark were CPU Min at 1674mhz and CPU Max at 2160mhz with the governor set at performance.
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Cloaker said:
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
eskomo said:
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I am aware of this. I did have it in the freezer until it cooled down enough. The problem was not overheating, it was the CPU becoming unstable at full load with the processor being overclocked. The phone was still cold but it went to a reboot or just turned off.
Gotcha. I missed that part. I wasn't fully awake yet at 4:30am.
Sent from my SPH-L720 using xda app-developers app
Ok buddy here is your issue buddy its all about volts and throttle limits ive been fine tuning oc steps on antutu, cf bench, geekbench2 and geekbench3. Im stable all the way up to 2106 so far I use ktoonzs kernel cuz it has more options in his app the control alot of the throttling and volts. Ok understanding what it means what the phone just shuts off or reboots when the phone shuts off and wont cut back on you either have to do pull the battery out or plug the charger in to get the phone to boot up that means you had a power overload it drawed to much power on the battery which means you neesd to drop volts on your max step. Now if the phone is just rebooting or if the app FC back to the home screen that means that you dont have enough volts for your max step you only have to add or substract volts on that one step not on the whole board the best way to do this is just by finding your volts for that max step first yes scores will be low but once you find the volts then you start adjusting the throttle limits that way you can control the heat of the cpu but once you find the sweet spot of that oc step move to the next one and start over again for the next oc step doing the steps I listed above I will post pics of what I gotten so far. On a further note I have found that the freezer trick hurts you more then gaining anything cuz if you cool the cpu and battery to much it will make the cpu run sluggish cuz its to cold to run and if the battery is to cold it makes the phone think it dont have enough power to run on that oc step and makes the phone reboot so bare in mine the freezer isnt always the best way to do this I found that if the battery is below 28c it will reboot the phone during benching and if the cpu is below 25c it sluggish as hell the best app to use is cool tool on the app store if you use kt kernel I can give you the direct path to monitor cpu temp like his app does hope this helps you understand alil better of whats going on if you need anymore info just pm me
The #1 misfit
of my crew of misfits
As you see in the 4 pic my score close to what the GT-I9500 are getting on antutu
The #1 misfit
of my crew of misfits