Related
Hi everyone,
I recently stumbled upon Hakeem's thread, which details the necessary configurations to extend the battery life of the HD2 running Android. One of the key configurations is to use SetCPU to underclock the device from 1GHz to around 600MHz.
I really want to try it out, but my bf told me it might be risky. He said that since the CPU is now running at a lower clockspeed, it might lead to HD2 overheating if I were to run multiple applications (compared to the default, 1 GHz config). I'm no techie, so I really don't know if what he's saying is true.
Are there any risks associated with underclocking the HD2 using SetCPU? Thanks a bunch!
Sarah
rikou_demon said:
Hi everyone,
I recently stumbled upon Hakeem's thread, which details the necessary configurations to extend the battery life of the HD2 running Android. One of the key configurations is to use SetCPU to underclock the device from 1GHz to around 600MHz.
I really want to try it out, but my bf told me it might be risky. He said that since the CPU is now running at a lower clockspeed, it might lead to HD2 overheating if I were to run multiple applications (compared to the default, 1 GHz config). I'm no techie, so I really don't know if what he's saying is true.
Are there any risks associated with underclocking the HD2 using SetCPU? Thanks a bunch!
Sarah
Click to expand...
Click to collapse
I have used SETCPU on my device for 1 whole month, there is nothing bad happens and it is safe.
In addition, you can install this app "current widget" or put a SETCPU on your homescreen to track your device temperature. This is the safest way.
Cheers,hope this help...
As opposed to overclocking, underclocking shouldn't pose any risks. You are basicly running your CPU at a lower frequency than designed, so your device will be cooler to start with. Even when maxing your CPU load, by running a lot of apps, your CPU is operating under its designed capacity. It will therefore never get hotter than a stock HD2 running full load at 1Ghz.
Furthermore there are built in safeguards to prevent catastrophic overheating. So basicly its safe and you should have no issues. Except, maybe, insufficient CPU capacity when running a lot or a heavy app.
Hope this helps!
Sent from my HTC HD2
christarius said:
Except, maybe, insufficient CPU capacity when running a lot or a heavy app.
Click to expand...
Click to collapse
I wonder if this is what my bf was talking about.
But anyways, I'll go ahead and give it a try. Thanks you guys!
Sarah
rikou_demon said:
I really want to try it out, but my bf told me it might be risky. He said that since the CPU is now running at a lower clockspeed, it might lead to HD2 overheating if I were to run multiple applications (compared to the default, 1 GHz config). I'm no techie, so I really don't know if what he's saying is true
Click to expand...
Click to collapse
He's an idiot. If you make it faster, its generating more heat, if you pump up the voltage it makes more heat. There is no possible way for lowering it to cause it to run hotter.
If you are that concerned, create a profile in set CPUto lower CPU and use conservative when temp reaches a certain point.
Sent from my HTC HD2 using XDA App
FROM WHAT I READ that if you underclock to the wrong level you can damage things that needs a desired amout of cpu ...if not it can stop working i wll find my source and post it later
weird thread. lol you cant damage your hd2 cpu by underclocking or undervolting
rossl said:
weird thread. lol you cant damage your hd2 cpu by underclocking or undervolting
Click to expand...
Click to collapse
Agreed, just turn it back up before playing memory intensive games & apps.
You're all wrong and I dont mind saying wrong section! stick to the topic of "Development"!
Regards
Flashmore
My HD2 is locked to 245mhz - 400mhz when on a black screen (so locked.) When in use it fluctuates between 245 - 998mhz depending on usage.
had it this way for months. No ill affects and makes the battery last that little bit longer.
I want to know of their is any way to stop my O1 to crash when I overclock it to 806mhz...
Sent from my LG-P500 using XDA App
LOL, stick it in the fridge... Or solder a bunch of heatpipes on it?
Seriously, if it is unstable, you do not need more cooling but primarily more voltage. And since that is just impossible to do, go and do some less overzealous overclocking -> problem solved.
doktornotor said:
LOL, stick it in the fridge... Or solder a bunch of heatpipes on it?
Seriously, if it is unstable, you do not need more cooling but primarily more voltage. And since that is just impossible to do, go and do some less overzealous overclocking -> problem solved.
Click to expand...
Click to collapse
Just curious as to why it's impossible to up the voltage on this chipset. I've searched and can't find any info.
On a side note the msm7227 in the galaxy ace runs at 800 and there are many p500's that can't handle that clock speed. Wonder if it is running at a higher voltage in that phone or if something else is different about it.
Something else is definitely different....
I run my phone at 806 with the Franco kernel although I think that it was unstable on other kernels. I would like to try higher I know it at least booted before at 825
vtmike said:
Just curious as to why it's impossible to up the voltage on this chipset. I've searched and can't find any info.
Click to expand...
Click to collapse
Voltage adjustment unsupported by chipset/CPU.
doktornotor said:
Voltage adjustment unsupported by chipset/CPU.
Click to expand...
Click to collapse
Thanks for the reply. I had read that there was no voltage scaling but wondered if the the overall voltage could be increased with the proper kernel. Aosp said he was going to be working on a kernel, had my hopes up that it might include a voltage increase. Sucks to hear its a hardware limitation.
Basically, i got this phone(GS2 i9100M) a week ago and found way too many problems that i cannot fix. So, why exactly does so many people like about this phone compared to other variant, e.g. GS2 T989 with snapdragon processor? I mean, my brother has the T989 and i also had it before too until i sold it to get this. It seems like i've been experiencing a lot of problem from this phone that does not really occur on the T989. The default music player is faulty which causes auto reboot, and the phone constantly heats up; even when viewing photos from the gallery! What attracted me to get this phone was people's opinion about the CPU and GPU also the gorilla glass, but i dont really notice a big differences in speed between the two phones. The T989 also doesn't heat up this much or this often. Feel free to share your experience people, and would appreciate if someone can offer me some advices on how to fix the heating up issues.
First, its better to talk n read at 9100 forum section but since im a 9100 user, ill share it here
Yes, on day one i got my 9100, it gets really warm even when not charging and got a lot worse when on charge. Its mostly the media scanning process which seems unstoppable on the earlier build when the SGS2 was released
I first noticed that its solved when using XXKG3 firmware and above. And also, undervolting to around 50mv reduces the heat too. A normal 9100 is capable of undervolting up to 175-200mv but it depends on phones are some silicones are made better and its not a constant result. What samsung made is setting the voltage at all the same safe level to avoid reboots. U have the option to undervolt it to reduce heat or even underclock to 1Ghz since 1.2ghz is quite overpowered and u want to conserve the battery and make it last longer.
Try Siyah kernel and learn to tweak using voltage controller and extweaks. There r guides given in SGS2 section here on XDA and it is well compiled.
Cheers
Sent from my GT-I9100 using xda premium
bershote Legiflature;
Thanks for your reply. I've posted in the wrong section by mistake. Someday I'd consider rooting the phone, but at the moment I don't want to take the risk because I'm still kind of new to smartphones and don't know much about it. What's your opinions on ICS? Do you think ICS OS release will solve most of these problems?
Hello I own the Samsung Vibrant for two years now and even though I was a bit reluctant to overclock the phone at first as new phones were coming out in the market and its (Vibrant's) performance deficit was becoming all the more significant (in comparison to newer phones) I "succumbed to the temptation". At first by a little margin (no more than 20% overclock) but eventually -as I was seeing my phone to be capable for it- for even greater ones. There was a time that I was using my phone at 50% over-the-stock clocks.... those were the days
Eventually -it seemed- as if it somehow starting becoming less and less capable holding the clocks so I started lowering my clock thresholds eventually killing the overclock altogether. Mind you the grand total of the time(s) that I had my phone overclocked (up until then) was not that great...
But then ICS came out with all its fancy tools and the "temptation" overcame me again and as if from a miracle I was able to maintain 50% overclocks like the good ole days (1512Mhz to be exact). To be sure -that time around- that that is a stable clock I devised a slew of different test from extensive software decoding, to 3D and CPU rendering. My phone was rock solid. To address the battery issue I bought an extended battery and all was well in "Vibrant-Ville"...
To my dismay though even though my phone seemed rock solid I seemingly starting losing my overclocking capacity (once again) as I migrated into Jelly Bean, so I said to myself "oh no, no, I'm not going through this again, I'd choose a moderate overclock and I'll leave at that". So I disabled Live-OC, custom voltages, hell even deleted NSTools and used the standard 1.2GHz setting, my battery was better, my phone was rock solid once again and thanks to jelly bean my phone was still fast enough...
Two days ago -though- the ghosts of the past reared their ugly head once again, out of the blue my phone lost its stability. Anytime I was trying to do anything remotely complex and it would reboot (BTW I'm using Helly-Bean right now, using the "Smooth" setting, Smartass governor @ 1.2ghz, pretty standard stuff).
I love this phone but I feel it's nearing its death-bed, what's your opinion guys?
I'll prolly remove the oc altogether but I fear it won't be enough, I fear that instability would start encroaching the 1ghz setting as well one of the days and then it would be game over. I want to avoid this fate at all costs, so anything you could recommend I would try, even changing my rom.
Also to those who used overclocks in the long term what was your own experience?
Thanks for your attention
No response(s)?
Sorry for the bump but I take it none of you guys ever have/had any of the problems I'm describing. Hmm, that means that I was unlucky with my piece of hardware it seems... pity :/
More than likely an aging chip is the case. Personally my phone runs smooth at 1GHz, so I don't see the need to unnecessarily overwork the CPU. After reading your original post, one line stuck out to me in particular. You mentioned that you ran the CPU at 150% for a time, and to me that sets off a red flag. Setting the CPU at 1.5GHz is risky and can cause some major wear on the CPU. Not to say I've never overclocked that high, but I usually only set it that high when playing a high graphics game. Even then, 1.5GHz is not recommended if you wish to use your device long-term. Even 1.4GHz is considerably pushing it. Although our devices can handle it, eventually, they're going to tire out. Now some phones may be able to last longer than others, it depends on the amount of iron in the sand used to make the silicon processors or other minuscule things could play a role. Essentially, it's random. No two chips will be exactly identical nor run exactly the same. So in your case, that may be the case. Perhaps your device really is nearing the its end. Considering that your phone was made to last only a few years at stock speeds, you should still be pleased with how long it's lasted. However, it is understandable if you're upset with this. The only thing I can suggest is to not overclock anymore and to try and keep its temperature low. Perhaps try undervolting? But if you want your phone to last, don't overclock (if your phone's processor is already starting to fail at 1.2GHz, when it used to run rock solid at 1.4 or 1.5GHz, then you definitely need to stop overclocking entirely). More than likely you won't hear other Vibrant users discuss similar problems because they've already moved on to new devices, before the long-term effects of high overclocking began to take its toll. But if you do a little research, you'll find other users on other devices having similar problems to what you are having.
Wish you the best in your efforts, and hopefully you'll get a year or two more out of the device... Hopefully someone will come forward with a better recommendation/solution to your problem. Since I pretty much stated what you probably already knew.
I'm not for overclocking, nor have i overclocked my vibrant.
With that being said, i have never had any performance issues, and I'm having difficulty recalling any issues with stability either..
I hope you treat your new phone with more respect..
I'm sure it will live you much longer for it.
Sent from my amazingly stable SGH-T959 using SlimICS
Hi, I own this phone and I do overclock the processor, if you can help me , tell me step by step how.
Thank you and excuse my English .
kppus said:
Hi, I own this phone and I do overclock the processor, if you can help me , tell me step by step how.
Thank you and excuse my English .
Click to expand...
Click to collapse
Your english is fine.
To overclock the CPU, you need a custom kernel that supports CPU overclocking. If you're using a stock rom, use a stock kernel, otherwise use an AOSP kernel.
I don't recommend overclocking this phone in particular. It has heat damage issues (can damage digitalizer at specific temperatures).
Overclocking in general is a good idea, but bad for phones. Remember that the temperature rises very quickly with slight voltage additions. Therefore, the CPU will be throttled instantly to a lower frequency (ie: 1497MHz) anyway to prevent damage. It also drains the battery that much quicker.
Quad core (armv8?) @ what? 2.5Ghz if I'm not mistaken. Dude that should already be plenty fast. Honestly most people overclock older devices to give them that last shining chance to go down. Your G2 isn't dated by any means and is still up with the crowd as far as hardware goes.
G2's cpu is still good enough for most tasks without compromising any performance issues.