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.
my sgs2 kept getting a little hot and i also felt that the batterylife wasn't bad, but could be better.
so i decided to underclock it to 500mhz and see what happens.
after all, it's a dualcore and 500mhz shouldn't feel like...500mhz right?
but it did feel like 500mhz with everything choppy and so on..
perhaps i just have the wrong concept of how dualcores are supposed to work....or perhaps gingerbread/apps/filesystem isnt yet fully optimized for dualcore? i don't know.
i decided to look for some sort of system monitoring app that'd show individual core usage...like "Tablet cpu usage monitor". but found none
StabilityTest 1.5 sometimes only shows 1 core. probably just the app's problem....
thoughts anyone?
edit: i just realised one thing...though havent tried it enough times to say it's something meaningful. from a fresh reboot, if i don't open SetCPU, StabilityTest v1.5 detects just the 1 core. then if i close Stability Test, open SetCPU, let it have its permission then back out, StabilityTest would then show 2 cores.
I use OS monitor. I found that Wifi Sharing was killing my battery, by takin up 20-30% of CPU time and causing the CPU to clovk itself to 1000 MHz! So using OS monitor, I killed the process and the battery drain goes away (until wifi sharing starts itself up again!)
yer i use osmonitor too but it doesn't display individual cores D:
and yes i probably check my cpu usage about twice a day specifically to make sure wifisharing isnt on and eating up my batt. im surprised samsung didnt fix this with their updates..
im very interested in this too, especially underclock + lower voltage for CPU - could drastically increase battery life.
Try disabling a whole bunch of default apps that come with the phone if you havernt already, details here:
http://forum.xda-developers.com/showthread.php?t=1069924&page=2
And report back your findings ???
plenty of battery threads lets not make another, we know there is a battery problem they say its 2.3.3 related to the dual cores.
As for wifi it might have something to do with your router the dlink dir 655 router was having problems with this phone, i imagine maybe other dlink routers have the same issue.
Get a app called juice defender it shuts of any wifi that is not in use ( when phone is in sleep mode ). it also works with 3g data.
Hope that helped
i suppose im more interested in the dualcore aspects here...rather than the batterylife. sorry i didnt really make it clear
i did search up on "dualcore optimization" here in the forum but there really isnt much about it
for example..what is the state of gingerbread's dualcore optimization? what about apps etc
i think i'll also do some googling myself
I don't think Gingerbread is dual core optimized but the underlying Linux kernel should take advantage of the dual core for multitasking. Every app using multiple threads will use the dual core too.
now that boot is flashable i think our devs can start developing custom kernels,
this means also that for all the people like me with problems of cpu can have finally a solution
if any dev can help, all who messed up with tenfar's recovery needs a new kernel, overclocked and without the thermal throttling ( god knows what partitions have been formatted) as our phone thinks is always in the temp range to cut 50% of frequency
i found this kernel in lg optimus, it's a tegra device so should be so different...
http://forum.xda-developers.com/showthread.php?t=1029799
all the features are interesting...maybe finally we can have a phone fully working again
I'm on the same boat as Kermit, unfortunately
Hopefully this will be resolved soon with the help of a dev.
I'm willing to make a sizable donation if somebody shows interest in this problem...
i see that there is even a tutorial to create custom kernels, seems "easy" but not for me at all...
our custom kernel, (i'm still on froyo for the moment) should have the ability to bypass the 50% cpu freq policy of the cpu thermal throttling.
so the possible solution are:
we raise the cpufreq to overclock it till 2000mhz (so we can run our 50% at normal 1000mhz)
or
we remove/change the policy to limit to 50% the cpu in case of high temp leaving the 115C shutdown only
i have 35C cpu temp, while the 50% policy should run above 90C cpu temp...i assure phone is cold...
if perflock is disabled we can adjust cpu setting with setcpu and create our temp policies
anyone could help us?
I have made a lot of searches and read a lot about battery calibration... and of course i know what the hell is kernel panic, its definition and its symptoms.
However I still have some confusions and I hope some of you may be able to solve them
Maybe some of them are noobie questions but I honestly sorry for that also this may help others who has these confusions too
My situation:
The system stats are shown in my signature.
on 5/9 I have flashed franco.Kernel v19.4 bfs and then started a lot of OC tests,
finally I was stable on stress test (SetCPU) 729mhz for 2 hours non-stop,
and also I used the phone stably for over 24 hours without reboot.
However I faced a problem which is related to Darktremor scripts.
I used 2 weeks to solve it and finally it is gone now.
I started battery calibration which is the final process before I use my phone normally in my daily lives.
But in these two days, my kernel panics after ~4 hours of usage of 729mhz max CPU frequency.
without the need of advice, surely i have downclocked to 710mhz max and its all good. but however i am super curious about why 729 becomes from stable to unstable before and after.
1) Does battery stats related to kernel panics in ANY extent? if yes, how?
Ignore all questions under 1 if the answer is No.
1.1) Does wiping battery stats before flashing a kernel helps you OC higher?
1.2) Does wiping battery stats before flashing a ROM helps you OC higher?
1.3) Does wiping battery stats (for calibration purposes) has possibilities to produce kernel panics?
2) Why is there a sudden drop of battery level (~4-5%) after kernel panics?
3) Is there any other possible causes of kernel panics BESIDES overclocking too high?
3.1) *2sd scripts?
3.2) ext4 barrier = 0?
3.3) inputting EXT4 data writeback?
(tune2fs -o journal_data_writeback /dev/block/mmcblk0p2)
4) Is SetCPU the problem?
Some says "dont use SetCPU when you can overclock using CM7 settings."
Is that true?
5) BESIDES the max speed, does it also depends on Governors?
Ignore powersave governor or others which forces the clock to the minimum frequencies.
So, is there any difference between setting the same maximum speed, different governors?
(for example) Would smartass gives a panic at 729mhz but ondemand doesnt?
6) Does the "change of frequencies" gives easier kernel panics?
Situation A: 729min, 729 max
Situation B: 480min, 729max
In situation B, the system makes the frequencies change due to load, means it may switch from 480 -> 600 -> 729 -> 710 -> 691 -> 480 etc.
so does this "change of frequencies" makes the kernel loads more and finally gets it to panic?
Thanks for your time reading and answering my questions!
Please just quote one of them if you would just like to answer one of the above
Thank you very much!
1) no.
2) It happens when u remove the battery and put it back.
3) There are some strange reports of kernel panic at 600Mhz which are weird. Sometimes Roms/kernel play a part(unknown).
4) it is because you can overclock in Cm7 settings menu, so no need to install another app such as SetCpu
5) Maybe, a governor who stays more on the highest frequencies i think are easy to panic because hardware can't handle it.
6) for me, i would say situation A would be easier to kernel panic, as it is constantly on the highest frequency and stressing your cpu too much that it can't handle it.
Since you get stable at 729mhz for 2h and panicked when 4h of use, that means the cpu can't handle 729mhz for above 4h.
@terratrix
thanks for your reply!! at least im not using my stupidity to wipe battery stats and trying to avoid kernel panics, lol.
@info update and conclusion after 1 more day of testing
And there, after some readings on the forum and the experiences myself, i think i have found the critical point already - QUESTION NO.5
Conclusion : kernel panics are related to governors, at least, our new amazing profiled one - SmartassV2!!
On the thread of Franco's .35 v1 kernel, there are some users reporting the panic issues faced with ONLY SmartassV2.
And me myself, has joined the party as well
Smartass(v1) has been my best bud all the time at 729mhz or even higher for more than 6 months. And when I left it and went to choose his next generation, my phone got a generation gap with Mr.V2, lol.
On my phone: (Franco.kernel 19.4bfs and no any reflash or stuffs between testings)
SmartassV2 ---
very unstable panics AND random shutdowns at random times
729mhz - sometimes 2 hours, sometimes 4 hours
710mhz - yeah I justnow kernel paniced with this also, you know how long after boot? 30minutes!!!
Why 30minutes? I suspect that it.is related to franco's network speed hack. I'm on EDGE data plan and because of Franco, I can enable HSDPA with 4x more speed.
On 710mhz, my phone was stable for over 8 hours with EDGE on (I intended to save battery), but after a reboot (manual one for some other purposes) I started to use (the hacked) HSDPA. After 30 minutes, panic. I remembered when I was at 729 on smartassv2 I panicked after 3 hours and at that time I was using HSDPA too.
Smartass (v1) ---
Well now I'm on smartass v1 at 729mhz stably typing this message. Funny huh...?
Results:
Franco's network speed hack
OR
3G network/HSDPA network
OR
Even just because of specific phone hardwares
IS NOT COMPATIBLE WITH THE ALMIGHTY SMARTASS-V2 GOVERNOR AND WOULD RESULT IN KERNEL PANICS AT THE FREQUENCIES WHERE THE PHONE CAN BE STABLE WITH OTHER COMMON GOVERNORS.
If I am wrong or you can confirm this by testing yourself, please let me know!!! thanks and hope I have provided some useful information
Goodnight and I'm going to continue working with my old friend smartass-v1 despite v2 has better profiling tweaks, lol
Sent from my LG-P500 using XDA Premium App
Dude, as i had mentioned earlier in franco's thread, that it had to do with the governors... cause i usually try and find out the cause of the issue myself before posting a bug..
SO all i tried were playing around with the performance settings... and i start off with changing the governors... the best targeted experimental ones are MINMAX (my personal fav), SMARTASS, SMOOTHASS (now removed but one AWESOME governor), and INTERACTIVE-X (rewritten by franco i guess).... About the frequencies... from what i have observed so far apart from reading stuffs is that, at 729 Mhz our optimus DOES pretty much stay stable even in the ****TIEST devices.. LOL i can say that cause we indians get the crappiest hardware of all... the point is... if you got a kernel panic at 729, it is most likely that you would get it again at 600 Mhz too cause its not overclock related..!!!
Bottom-line: Avoid SmartassV2 unless your phone is made of the finest hardware i.e. you can easily overclock it to 806 Mhz (ive seen some users using it at this frequency without any issues at all .. :O ) Use Smartass older or Minmax instead...!! And avoid overclocking above 729..!!!
P.s.: mine works fine even at 768 BTW....
We have to wait for Franco's next release for more smartass2 updates
Sent from my LG-P500
SmartassV2 is kind of strange, at least in my phone. I notice my battery draining faster while I use it, and it's probably because it stays in the max frequency longer for some reason, despite screen off. I use NoFrills for my CPU setting and it has the ability to view stats, and when I'm using V2 it stays longer at the max than at the min (65 vs 35%). The opposite is true for Smartass v1, which to me makes more sense because my phone stays at standby more often than being used.
As comparison data, my phone with smartass v1 can typically be OCed up to 787 MHz. 748 MHz on v2 is stable, but I haven't extensively tested higher freqs.
I have a Indian phone , smartass v2 oc to 768 stable xD
Sent from my LG-P500
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Haven't used powersave mode at all yet, It's possible that profile has bugs on this phone.
I have my screen off profile set to 800 mhz and conservative and have had 0 issues so far.
as far as I'm aware powersave doesn't let it out of the minimum frequency (could be wrong). Use the conservative governor instead.
Don't use power save. I have done a lot of testing with this.
Here is the lowest that you can go.
Range: 200-500mhz
Mode: ondemand or conservative
If you go less than 500mhz or put it on powersaver, then it won't wake up from locking the phone.
Thanks
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
geauxlsu83 said:
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
Click to expand...
Click to collapse
I noticed that setting it to 200-500mhz increased my battery life by about 15-20%, but I did notice a significant performance drop. 200-800mhz is much less noticeable performance wise, but I didn't check to see what kind of battery life I got on that setting.
As for widgets...I'm not sure on that one either.
geauxlsu83 said:
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Click to expand...
Click to collapse
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
thanks
yeah im actually flashing your kernel as we speak i looked under a battery thread and they said your kernel is good for battery conservation thanks for your help
actually i flashed it from heimdall and it says it is kernel version is 2.6.35.7 is this yours?
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Entropy512 said:
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Click to expand...
Click to collapse
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Well said.
Entropy512 said:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
Click to expand...
Click to collapse
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
vladm7 said:
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
Click to expand...
Click to collapse
This is why I also have my screen-off limited to 500. Once in a while, the phone needs to do a little extra work, and it's better to ramp to 500, get stuff done, then go back to deepsleep. As I said min=max=200 SHOULD be OK, but personally, I wouldn't recommend it.
I would love if SetCPU allowed for different governor tuning depending on profile. e.g. make up/down threshold more battery-biased with screen-off than screen-on. (Slower polling rate, higher up/down thresholds.)
SetCPU root access problem
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
IshouldntbeHere said:
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Click to expand...
Click to collapse
Pretty sure it's your phone cause mine OC's to 1.6 with no problem.
BigBopper said:
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
Click to expand...
Click to collapse
Have you tried updating the su binary in Superuser? (Even if you have the app updated, the app itself needs to update the binary.)
Beyond that I have no ideas.
Entropy512 said:
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
Click to expand...
Click to collapse
Ahh, that was my problem. I was using powersave. Do you (or anyone else) see there being a benefit to having a screen off profile?
In theory, a screen-off profile shouldn't help - in reality, it's a line of defense for cases where something goes nuts in the background.