I have downloaded SetCPU in my SGS2 and capped my processor to max-1200mhz and min-600mhz. Will it harm my phone if I switch to performance mode which is max & min at 1200mhz (full capacity).
Well I think it depends on the hardware. But I would never recommend to push it at the max frequency, first of all you will decrease your battery life as well as your CPU lifetime since it will produce more heat.
Obviously it can depends of how many times a day you are using your phone to that max clock. If you are experiencing spontanous reboots that means the clock is too high, if not, well.. up to you to keep it like that.
I overcloked my Hero at 710 Mhz for about 2 years (the max capacity it's 748Mhz) and my CPU suppose to run on stock at 525mhz. I can feel my phone been a little hotter compare to the original clock but it has survived until now. (finger crossed)
But seriously.... ask yourself do you REALLY need all that power from your phone?
Related
Does anyone else think the CPU running at 480Mhz-800Mhz screen on is a bit too high? It's more than capable running at a 122Mhz minimum - heck, even 19Mhz, although it doesn't spend much time at 19Mhz. Also, if perflock is enabled, it locks itself to 245Mhz only when screen off - still seems a bit too high for me, considering there's lower selectable frequencies.
Anyone who's temprooted their device: Are you using SetCPU to change the CPU frequencies/disabling perflock? I have my Chacha running at 800Mhz max / 122Mhz min perfectly fine (running my battery down for a while to see if the battery life benefits) - although occasionally, it still locks itself to 122Mhz even after turning the screen on for about a minute, which I believe is a kernel issue
For reference, the frequency options are: 19Mhz, 122Mhz, 128Mhz, 245Mhz, 480Mhz and 800Mhz.
128Mhz doesn't actually work, and if it's selected, it uses 245Mhz instead even though SetCPU says "128 min"
Unfortunately I can't help you, but I'm totally interested on the subject!
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
really need low cpu frequency?
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Alex C. said:
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
Click to expand...
Click to collapse
True, setting the frequency too low is bad for some devices, but in my personal experience with my Chacha, I can actually run mine at 19Mhz min/800Mhz max and have little to no problems, since it doesn't spend much time at 19Mhz anyways. (I use no SetCPU profiles, as I feel they have little to no benefit on battery life.)
All of this is just a thought though, since HTC set the minimum to 480Mhz with the screen on which seems way too high to me :/
Also, locking the CPU to a single low frequency was actually a bad thing on one of my old devices, a Desire Z, which usually caused wake problems, etc.
semanty said:
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Click to expand...
Click to collapse
600Mhz is possible indeed - the MSM7227 processor that the Chacha uses is actually rated at 600Mhz, but HTC factory overclocked it to 800Mhz. It would require a custom kernel to have 600Mhz added back in
anyone thought of a way to undervolt???? i mean use less voltage for each frequency..am trying to search for kernels to flash but cudnt find any
Hello all
My Galaxy Note runs hot.
Can someone tell me, preferably in methodical order, the steps that should be followed to sort out overheating issues.
If you watch the Australian Open tennis then you will see how hot it gets here in summer at the moment!
1. Root
2. Install SetCPU
3. Set some temperature profiles so when your Note reaches a certain temperature the clock speed is automatically dropped
4. Close unused apps and stuff
5. Don't use 100% brightness
If I was you, I would use, in fact, lowest brightness when indoors, and underclock the CPU (even when it's not hot, as opposed to what vantt1 says).
I underclocked my Sensation from 1'5 Ghz to 1'0 Ghz (both cores). And boy, It's running smooth with ICS, no lag at all.
In fact, my settings are:
Min clock: 192 Mhz
Max clock 1005 Mhz (or something around that)
Governor: Ondemand
But your CPU is probably different than mine... Keep in mind that I underclocked around 30% of it's total capacity. You might want to do the same.
Also, direct sunlight causes overheating. (Might be obvious, but when the sun hits our skin, the body starts several cooling methods, so that you only start to notice the overheating around 30 minutes of direct exposure... And 30 mins of direct sunlight for a phone is a total kill, so also one more tip for when you're on the beach: cover it with clothes, or something. It will also decrease posibilities of thieves )
My Galaxy S2 doesn't really overheat when clocked at 1.4 GHz ondemand. It's the maximum safe clock for the Exynos 4210 found in the S2 and Note. The speed is there when I need it (but that's only 2% of the time) and when I don't, it's around 200-800 MHz. I have a solid aluminium case on it, so when left on the table it can go down to 25°C. In my pocket it's a bit higher at 34°C but it's acceptable. When I play GTA3 though, it can go up to 56°.
Sent from my GT-I9100 using XDA App
force reboot of phone isn't always overheat. the kernel also depends on how high you can overclock.
It seems like every phone can handle a different clock speed, is there is a tried and true way to find the optimal clock speed for your phone?
No as u say every phone acts on hes own so i dont think there is any software for this ( optimal overclock) but there is software for ocing it easy like setcpu or nstools... you can oc your cpu by raising it, and using it with multitasking and if it doesnt reboot in hour or two of heavy usage then go step higher. When it reboots try with step or two higher voltages and so on until you get highest cpu with moded voltages (not more than 2 steps) stable with no reboots. Ofc i wouldnt recommend this as you are not getting anything special from it and you risk your phone... btw optimal cpu speed is its own stock speed that is just pure logic xd
Though there is no agreed upon definition, to me the optimal cpu speed is not the stock speed, the stock speed is the standard safe speed. When a CPU is manufactured it invariably has defects, the number of defects dictates the speed at which it can run. For example, when they manufacture the i5 and the i7 they probably just take defective i7 chips and turn off two cores and call it an i5. (I don't know if they actually do this with the i5 and i7 but it's been common practice with just about every processor in the past.)
I guess I should use a different term like, maximum safe speed.
Trial and error is the best way to my knowledge, haven't heard of any phone apps adjusting clocks on the fly based on temp, inaccuracies, etc, like on a computer. You can feel the temp of the phone and it'll reboot at the smallest sign of instability, just don't set test profiles to set on boot.
And what you say is correct. Processes with similar imperfections are grouped, tested and sold under a given name with the benchmark being stock frequency and voltages. Common practice and very often you get some chips you can over clock til it expands out of its bracket and others which fail at everything but stock.
This is my third time typing this... (This website should really have an auto-save draft feature)
I recently installed the application "CPU Tuner" because I've always wanted to utilize my newly rooted phone. The phone is running Cyanogenmod 7.2 Stable, and currently overclocked at 1.5GHz. My main concern is overclocking my phone that high. Now, I didn't really choose that option, SetCPU automatically set it to that when it loaded a configuration. I'm a beginner to overclocking, and this is my first time doing it for anything. I've heard rumors of people melting their processors from overclocking it, so I want to know if it's okay if its overclocked to roughly twice the stock frequency of 800MHz. If it IS safe, then why isn't the phone automatically set to 1GHz to compare to it's twin, the Evo 4G? Or perhaps even 1.2GHz to surpass it? I would definitely be satisfied with 1.2GHz, but I wouldn't mind having 1.5GHz if it was stable and didn't drain the battery. On to the next question, would an OC this high cause instability and/or would it drain my battery? I only overclocked an hour ago, so I haven't experienced any problems whatsoever... yet. On to the profiles... I'd like some suggestions for improving my triggers. Right now, it set everything up to the highest frequency, but looking at the help, it said to not touch the frequency, but experiment with thresholds. In the Help, it doesn't tell you what the thresholds are, and what they do, and more importantly, how they work. It just shows that the highest is the most battery saving. I would have thought the lower the better, but... Anyway, if you could tell me, I'd be highly appreciated it. Finally, the battery temperature... It has an option to enable a setting to change profiles if the battery gets a certain temperature, but I'd like to know what would be considered "Overheating". I get paranoid when the battery temperature gets a little warm at around 36 Celsius... but the profile it switches to is supposed to really slow down the CPU to preserve battery, so I'd really rather not use it unless it's necessary. So, would 45 - 50 Celsius do, or should I set it a bit lower? My battery is 4000+ mV, if that'd help at all. If you know any sources that you can direct me to that would answer my questions, it'd be highly appreciated.
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
prboy1969 said:
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
Click to expand...
Click to collapse
Thanks for the response. It's pretty late, so I've bookmarked the link to read tomorrow. Alright, so 45 degrees Celsius should the maximum then. I've been thinking of switching over to SetCPU, since there are more comprehensive guides than for CPU Tuner (In which no one seems to have heard about), and it doesn't seem that the settings it set will be ideal for the long run. Although, before I switch over to SetCPU, I want to at least give it a shot. I'll change my settings so that the frequency decreases depending on battery level. Also, I don't have much but the basic governors and configurations on CPU Tuner, so I've never heard of Smartass V2 (Prior to skimming through the link you posted). Also, the battery came with it, I knew it seemed a bit different from most other batteries (From what I've seen in searches, most of them had around 2000), but I didn't know it meant that much.
The Governor settings available will depend on the Kernel, not on the CPU Controller. I've always been partial to SetCPU, but that's just me. I would again suggest doing a bit of reading, and experimentation to find your best settings. But defiantly the closer to normal the Battery temperature is the better. When the Battery heats up to much it will in most cases also drain faster. If you can post a Pic of the Battery I would really like to see it. I've never come across a 400mAh Battery for the Shift.
When I first rooted my shift 2 years ago I was very concerned of over-heating. I constantly checked the temperature. After a while I realized it is quite hard to over heat and cause damage, especially with the newest kernels the devs have put out. Just experiment with different settings and see what works best for your phone
Sent from my PG06100 using xda app-developers app
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
k-semler said:
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
Click to expand...
Click to collapse
uhh well.... yea and no. there are a few things you need to understand about microprocessors. no two are alike. they are built on a scale of a few nanometers and any difference causes a significant difference. to keep production numbers up there is a line they have to draw between performance potential and stability. more chips will be stable at lower clocks so they pick an speed they can get a high production number out of. sometimes a whole line of chips is produced with exactly the same core. chips that pass the highest get boxed as the highest performing and priced. chips that dont pass will either have specific features turned off, cores turned off or be underclocked and sold as lower models. in addition to that the top performing models are actually over priced, and often many more pass the tests than they need so perfectly good processors are intentionally disabled to fill the market for lower speed processors, so yes the cpu may be "underclocked" in a sense. but i don't know if that really applies to the infuse because i don't know if there are any chips in the same family that have a higher rated clock speed, if there are they aren't used in phones.
in example, on my pc i have a 3 core processor, it's actually a 4 core and i can even turn the 4th core on in bios, but a certain percentage of that particular model of chip will be unstable with the 4th core active.
another thing to understand is how the clock speed is set. there is a buss and a table of multipliers and dividers. so as one part of the chip oscillates at one frequency the multipliers and dividers say how may times per oscillation the other components go. the cpu speed changes by changing these multiplier values. the problem is that there are only so many multipliers the cpu is designed to use. this is a hardware limitation and can't be overcome so at some point the only way to get more clock speed is to change the buss speed which affects the entire system and will cause instability in most cases. occasionally you can get around this if you change the multiplier values for other componants as well but it's probably not a good idea to mess with it. the hummingbird chip only has multipliers to go to 1600mhz regardless of stability unless you mess with the buss, one developer got the galaxy s to 1700 with buss overclocking but some things didn't really work at that speed and it took a lot of changes to other system clocks. snapdragon chips can go to higher clocks and process numbers better but the hummingbird is better for graphics and multimedia which is more important on a modern phone imho.
so yeah 1600 is it, as far as practicality goes anyway. there are a few infuses that can only go to 1400-1500 as well and galaxy s phones which have the same clock limitations but are only rates for 1000mhz rarely go to 1600, but a few do, my captivate was absolutely peaked out at 1300, believe me i tried to get it higher, i tried a lot of things with voltages to try to get it stable, but even 1300 took some doing. it took a long time before developers even produced a kernel for the sgs that used clocks over 1200 because many of the early builds of the sgs series were much like mine and were not stable at high speeds.
Beautiful. :thumbup:
Sent from my SGH-I997 using xda app-developers app