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.
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
Undervolting and profiles.
I have tried a crap ton of different undervolting setting, but none work
Also the profiles in set cpu don't seem to work for me. I have a few of them set and it always sits on the top one I need some guidence with both please!
Another thing my xda premium app isn't pushing my notafications yes its set
Sent from my MB860 using xda premium
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
jack_slapped said:
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
Click to expand...
Click to collapse
When I was on alien rom, I tried 25 on all and it restarted after like a minute. What worked for me was 25 25,50,50,75,75,100 fromm bottom to top. I tried it with cm7 and total no go lol
Lemme tryi 25 on all and see what I get and I didn't know that. They all werent working, so I set them all to 100 lmao, I understand that now
Sent from my MB860 using xda premium
Aparently its been running 125,125,50,75,75,75,75bottom to top cm7 with 1.3 kernel.
It did restart a couple min ago randomly. Will keep posted
Sent from my MB860 using xda premium
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
jack_slapped said:
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
Click to expand...
Click to collapse
25,50,50,50,50,75,75
Still getting a reboot:'(
Only good thing about the reboot is it turns on instantly
PROFILES CONFIRMED WORKING trying to indwrvolt this thing
I think I'm gonna order another battery too bc this one isn't getting the 16 hours it was, I cant say much bc I'm screwing with the settings hardcore xD I will show.all settings in a sec
Sent from my MB860 using xda premium
Sent from my MB860 using xda premium
Blahhh
Put blah there so it would post lol. Also going to download a stress test or quadrent thing to test the stress and find maximum uv
Sent from my MB860 using xda premium
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Smittyzz said:
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
well my battery was draining mad quick so I am not overclocking It anymore unless I want to show off or play games lol, lost 20% in one hour. Now its stable and undervolted
Sent from my MB860 using xda premium
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Phalanx7621 said:
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Click to expand...
Click to collapse
I understand the 100 thing and I got the undervolting and profiles done. I hope he gets both cores supported soon and thank you dmfor the reply
Sent from my MB860 using xda premium
Yea Im skeptical about not setcpu not having support for dual cores... Did some searching on the net and couldnt find anything to support that. As far as not the tegra 2 not being able to do over 100mv jumps. That's not true. My lowest frequency is 600mv (-150) and my next frequency is at 750mv. That's a 150mv difference right there... And I'm completely stable. Its entirely dependent on your processor. They are all different and respond differently to undervolting. You just have to find what works for you. Generally though the lesser the jumps in voltage will give you more stability.
a good kernal helps too im useing faux123 v2.0 0C1.3 its undervolts quite well
us/alienv4UL/OC1.3{webtop2sd{fixed}
So I'm interested in undervolting using the stock CPU freq's, and I'm going to be using setCPU (obvi).
So, first question: Even if I want to use the stock frequencies, do I have to be using the OC kernel (0.2.1/1.45ghz at the time)? And then adjust the max to 1000mhz?
Second, I started up SetCPU and whenever I go to the voltage tab it forcecloses. This happens with both the stock enhanced & OC kernel, and I've tried fixing permissions to no avail.
All I really understand so far is that the end result is a table of CPU frequencies and linked voltages. I've OCed the hell out of desktops, but I'm lost here.
I'd just like to know how to get from starting up setcpu to ultimately popping out that new voltage/freq table.
I do apologize if this seems kinda stupid, I'm just trying to exercise caution lest I demolish my phone's innards. I've done it with many an intel.
If you just want stock frequencies, then there's no need for a custom kernel. I guess in that case, you could just use SetCPU for undervolting & profiles.
However, if you want overclock, you'll need a custom kernel.
If you're going to be using a overclocked kernel (i.e. the new Faux 1.45 GHz), then you will need to set the max to 1.45 GHz, and make sure SetCPU is set to start on boot; other wise it will stay at the stock clock speed of 1 GHz... So i guess if you only wanted the OC at certain times, you could set the max speed manually, only when you want to, and not select to start on boot.
I haven't really had any success with undervolting yet... always crashes on me & reboots. The best thing to do is make sure "set to boot" is not selected, when testing your undervolting, other wise you could get stuck in a loop, with the phone crashing every time it boots and tries to apply you undervolting values. I'd start at -25 for each and work from there... stress testing each choice with a benchmark app to make sure you wont reboot... if it reboots, then you know your undervolt was to much. Also remember that you can not undervolt more than -100 between each frequency, otherwise the undervolting will not make any difference.
I really like the profile options in SetCPU... you can set the screen off frequencies to the lowest two, that way for whatever reason your phone isn't running at full strength while your not using it. Also, you can set frequency speeds at custom defined battery levels.
Hope this helps somewhat.
It's unclear to me why it force closes. This may be a rom incompatibility or a SuperUser issue? I assume you've tried uninstalling it and reinstalling it? Updating your SU app? Try flashing to the latest Aura rom?
A few quick words about SetCPU:
1. When you first get started, do not set to "Set on Boot" in case you've undervolted too much and it crashes when applied. You can always check it later once you know the voltages are stable.
2. Between each frequency step there is a maximum of 100mV step off. Anything greater than that it defaults to native voltage. I think this is a Tegra2 issue.
With that said, undervolting is simple: simply slide the little slider on SetCPU to negative values. How much you can under-volt largely depends on your particular hardware and it is inconsistent across all Atrix's. My voltage table is as belows:
1000mhz: -50
912: -50
750: -50
608: -75
456: -75
312: -100
216: -100
I, however, did not test the limits of my phone. Many people will slowly increment the voltage lower until they start to get resets, and then they'll move it back to find the lowest stable point.
It has, however, been well established that minor undervolting improves battery life and diminishes heat generation. Excessive undervolting may actually hurt battery life. You can look around on this forum regarding the data. However, reasonable undervolting will improve battery life.
Thanks fellas, this helps A LOT.
I was so afraid I'd get 17 responses of "You're such a noob. Stop cluttering the forums" etc etc
At this point, I think that the problem is, for whatever reason, the FC when I tap the voltages tab.
I'm on the newest Aura (1.2.2.1) newest enhanced stock kernel from Faux123 (0.2.1) and the newest SetCPU (2.4). I'll try updating my SU (though I believe I did that right after I flashed.
I'll reintall SetCPU and report back.
Until then, THANKS BUCKETS fellas. I really appreciate the info and advice.
UPDATE: May have found the problem. When it first boots up it prompts to autodetect freq's or choose them manually (or something like that). I was afraid this would actually alter my CPU clocks right then and there and so I hit manual detect, saw something that said Tegra2 etc and clicked it. I just now hit 'menu' and set it to autodetect, tried the voltages tab, and no FC, so I think that's solved.
Thanks again for all the info guys! I'll start experimenting and let you know HOW LOW I CAN GO (ha).
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
AdiNova said:
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
Click to expand...
Click to collapse
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
xyrovice said:
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
Click to expand...
Click to collapse
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Swiftks said:
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
xyrovice said:
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
Click to expand...
Click to collapse
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
ghost_og said:
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
Click to expand...
Click to collapse
That makes perfect sense- limiting the max during the stress test. Thanks for the tip bro I really appreciate it.
I installed the webtop over hdmi mod on my Atrix and while testing it out, it got very warm in my hand. I opened the setcpu app and noticed that while overclocked to 1.3GHz, the CPU was running at 75C! I lowered it back down to the stock 1GHz and the temp slowly went down and settled at 63C.
It seems that while in webtop mode, the CPU is taxed at 100% all the time so I'm wondering if it's safe to stay overclocked when using webtop.
Everyone has different opinions of what is too hot around here.
IMO the cooler the better. IMI No Atrix should have a temp above 60c and I'm not even comfortable with above 50c either...
Sent from my MB860 using xda premium
I have experienced the same problem and worried that something may fry.... I have had mine overclocked at 1.45 using debian linux and all of a suddent he phone freezes and restarts.... Since it did it to me the second time I have kept my phone at 1Ghz... I am new at this so please don't beat me up too bad for being a noob... Just want to see if maybe undervolting it a little might help or hurt it?
Thanks in advance
Here are some tips I can offer
1.Try re-flashing your custom kernel and see if that fixes the web-top thing and over heating
Whenever the phone is plugged to the web-top it will naturally overheat so it's kinda expected remember now it's gotta work harder since its displaying on lap-dock or TV,but if you can cook an egg on it it might be too hot...lol
2.Set profile for temperature on setcpu so this way once you reach for example 100F your phone will clock down a little and so it might help the heat issue.You can set even more than one temp profile so this way when it reaches 96 it goes down a little then when it reaches 100 it will clock down a little more and such.
3.If that doesn't help,which in my situation it did.Flash a different kernel mayb it's just the one you're using that is causing funny stuff to happen.
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
I tried reflashing the kernel but it didn't change anything. I'm using Faux's 1.3GHz overclock kernel for Gingerbread (2.6.32.9). Is there something else I should be using?
sk8trix said:
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
Click to expand...
Click to collapse
Do what sktrix said in rest of his post.
I use the stopgap 1.0GHz kernel, and UV does lower temperatures. I would definitely try UV'ing a wee bit. You don't need to go crazy. I am using the following with great results for both temp and battery life:
-50
-50
-75
-75
-75
-100
-100
My setcpu profile clocks it back if I reach 60C, (I idle in the low to mid 30's). Under heavy load I reach around 52C max which is quite acceptable.
Now, granted I am not using Webtop, but the end result for UV should be the same. Lower temps and better battery life. You may also want to try just using 1.0GHz when on Webtop. The phone has more than enough power at this clock speed.
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
I know I'm straying from my correct forums here, however I have an LG Optimus 2X which like the Atrix, is a Tegra 2 CPU.
Our phones get VERY hot, I have had my CPU up to 86C before I decided to back off the stress test. CPUs are very good at handling high temperatures, and IMO you will see no ill effects from doing so, I am unsure of whether or not the Tegra 2 has thermal throttling/shut down, but in my experience they should be fine to around 80C.
The only issue I can forsee is the battery, batteries HATE high temperatures and it is awful for their life span, this is why your laptop batteries turn to crap after 1-2 years, even if low charge cycles, because they are always hot.
I would not be concerned about anything in the 70C realm, at all.
Alcapone263 said:
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
g2tegg said:
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
Click to expand...
Click to collapse
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
ericemir said:
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
Click to expand...
Click to collapse
It will still hang at 1.3ghz, though it's a known bug. I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick. Right now, the software that's out there is optimized to run on existing hardware w/o overclocks. I've run Shadowgun at 1.45ghz and didn't see any difference over the 1.0 enhanced.
Now, if we were trying to run games that were coded specifically or faster-paced chipsets then we'd need overclocking to catch up much like you would in the PC arena. That, however, is not happening in the cell phone market just yet.
treehumper said:
I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick.
Click to expand...
Click to collapse
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
cjrhoades said:
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
Bump.
Anyone?
cjrhoades said:
Bump.
Anyone?
Click to expand...
Click to collapse
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
CaelanT said:
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
Click to expand...
Click to collapse
I see... guess that explains why the phone doesn't really feel any faster when it's overclocked. I'll flash the 1GHz kernel then.
Thanks for the info.
Not sure if this is the same with phones but normally a CPU should stay at 40C idle and 50C load. Maximum would be 60C while benching or something.
If it goes above that I would definitely underclock/undervolt.
cjrhoades said:
what's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
also has other fixes besides overclocking you can go read them in the kernel threads