It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
webmaster said:
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
Click to expand...
Click to collapse
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Chilled26 said:
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
It was my perception that the older single core phones had better battery life. Do you really think it would hurt the battery?
Dual core isn't properly utilized yet so it might not be a bad idea.
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Changing kernel and undervolting did the trick for me. Getting 20 hours moderate use.
Sent from my Sensation using xda premium
Chilled26 said:
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
What are your settings?
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Ace42 said:
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Click to expand...
Click to collapse
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
webmaster said:
What are your settings?
Click to expand...
Click to collapse
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Pretty snappy
su
chmod 644 /sys/devices/system/cpu/cpu1/online
echo "0" > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
Someone in faux kernel forum was talking about doing this. Gscript app makes it easy to run script. If you dont like it just reboot and 2nd core is back on.
Sent from my Sensation using XDA Premium App
Chilled26 said:
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
I tried Faux's and it was ok, I plan on trying Bricked tomorrow. However if disabling a core gives even better results then that might be the way to go.
webmaster said:
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
Click to expand...
Click to collapse
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
Click to expand...
Click to collapse
Is that permanent or does it need to be run each time you reboot?
webmaster said:
Is that permanent or does it need to be run each time you reboot?
Click to expand...
Click to collapse
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Ace42 said:
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Click to expand...
Click to collapse
How long have you been running like that?
I run Faux kernel, Joe's RCU, undervolted -50mV and underclocked to 1Ghz, I can now easily make it through the day and I'm a moderate to heavy user. I'm pretty sure disabling the second core isn't necessary, and frankly, if you check out how little it's used, it probably wouldn't benefit that much anyhow.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Click to expand...
Click to collapse
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
mrg02d said:
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
Click to expand...
Click to collapse
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
webmaster said:
How long have you been running like that?
Click to expand...
Click to collapse
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Ace42 said:
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Click to expand...
Click to collapse
I didnt say this. It is obvious what I said, so why would you even ask me? Just scroll up pal.
You didnt simply give an experience...You implied that your experience is LOGICAL. It may to you, but it is incorrect. Dont just throw things out there, please. It makes people with backgrounds in power and energy pissed off.
Also, my finding completely debuncts your theory. At night, while I sleep, I see 5mAH draw.
Matt
Related
Recently, I have seen the undervolted kernel for Nexus One which makes the battery spell longer.
Can anyone modify it for G1?
http://forum.xda-developers.com/showthread.php?t=634587
Look on the app market, dude. There are like 5 apps\widgets to do that EXACT same thing. Nothing has to be ported.
zimphishmonger said:
Look on the app market, dude. There are like 5 apps\widgets to do that EXACT same thing. Nothing has to be ported.
Click to expand...
Click to collapse
They actually don't do the exact same thing... My kernel is undervolted, not underclocked. Theres a difference. Undervolted uses less power at the same speeds, underclocked just drops the clockspeed.
interesting
This is interesting... I'd like to see this happen
EDIT: Forget it...
persiansown said:
They actually don't do the exact same thing... My kernel is undervolted, not underclocked. Theres a difference. Undervolted uses less power at the same speeds, underclocked just drops the clockspeed.
Click to expand...
Click to collapse
So you have one for cliq now or dream?
Ace42 said:
So you have one for cliq now or dream?
Click to expand...
Click to collapse
The one he linked for the Nexus is the one I made.
I don't think its possible for the G1/MT3g/CLIQ unfortunately.
persiansown said:
The one he linked for the Nexus is the one I made.
I don't think its possible for the G1/MT3g/CLIQ unfortunately.
Click to expand...
Click to collapse
In other words all 72XX lack this ability correct?
But the new Armv7 should be capable like the Droid,legend,devour,etc.
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
coolbho3000 said:
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
Click to expand...
Click to collapse
So we can lower it but not up it for the overclock?
Also, can we lower it at the lower speeds? (I have mine set up to underclock when the battery is low, when the screen is off, etc. so a lower VDD (if stable) would be great.
coolbho3000 said:
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
Click to expand...
Click to collapse
How feasible is it to underclock the phone even further than the 128 MHz?
personaly , i dont see a huge advantage to underclocking past what we got now, undervolting.... nah,
@ sleep mine atleast has virtualy no background processes.
and even on a heavy use day, cell standby shows up as my largest drain.
you want much better battery life, id say look into hacking the radio on it.
I am running Cognition 4.4.8, which will not allow OC/UC. I actually just want to UC. What recommendation would you have for a kernel compatible with Cognition 4.4.8 for Captivate that would allow me to UC?
Don't you mean oc/uv? I don't think you know what you are talking about.
Yeah its UV (undervolt). Find any kernel that allows it and is working with your ROM. Maybe ask in that thread as others could be using a custom kernel for that exact reason.
Sent from my SGH-I897 using XDA Premium App
UC is a real term, maybe he meant he wants to limit his clock speed to 800mhz. What's that called if not UC?
Although undervolting and underclocking to save battery is a waste of time. The cpu doesn't use that much battery in the first place, the screen and the modem use the most power, you want the charge to last switch to the lowest brighteness and 2g, that will give way more battery than uc/uv will.
studacris said:
UC is a real term, maybe he meant he wants to limit his clock speed to 800mhz. What's that called if not UC?
Although undervolting and underclocking to save battery is a waste of time. The cpu doesn't use that much battery in the first place, the screen and the modem use the most power, you want the charge to last switch to the lowest brighteness and 2g, that will give way more battery than uc/uv will.
Click to expand...
Click to collapse
+1 on the battery topic. Even at a high OC the battery drain is not that much worse... a little yeah but not too severe.
Also good point about UC.. wasn't thinking about that at all ..underclock what!?!?
some people falsely think that the phone runs at 1ghz all the time, when in fact it downclocks itself and ramps up clockspeed when it needs it....so unless you have an app thats using 100% CPU all the time, your phone is running around 200mhz at idle.
Pirateghost said:
some people falsely think that the phone runs at 1ghz all the time, when in fact it downclocks itself and ramps up clockspeed when it needs it....so unless you have an app thats using 100% CPU all the time, your phone is running around 200mhz at idle.
Click to expand...
Click to collapse
+1 again Although there are different governors that do different things most phone at stock will idle down to 200mhz. My phone for instance idles down to 800mhz, but thats just my prefrence
Yep, I meant OC/UV. I typed too fast for my own good!
Good points
Thanks for the message on how little battery undervolting saves. That was quite helpful. I did try the discussion board for Cognition, but no one seemed to be posting on using an alternate kernel, which is why I asked for recommendations here.
I believe Cog is KB1 based, so this kernel should work: http://forum.xda-developers.com/showthread.php?t=988805
Thanks I will certainly trie eXist's kernel.
Ernesto47 said:
Thanks I will certainly trie eXist's kernel.
Click to expand...
Click to collapse
If you want the best battery life, I suggest something other than cognition. In my experience, i9000 based custom roms get better battery life.
Sent from my CM7 powered captivate
@sixstringsg I notice that you are using Cyanogenmod. I keep looking at that, but since it was still not listed as stable, I was not sure whether to try it. How are you finding the stability?
What I am wondering and before you attack me I did research this and couldn't find anything specific to the Inspire. I want to know generally what is a good speed to underclock the inspire to achieve maximum batter and before you say every device is different I'm asking for a general idea not a specific one. Also do you think that overclocking has a big impact on batter I am overclocking right now at 1.3 ghz do you think that I'll notice a difference. And I know I have to test it myself but I just want others opinion on it.
I have the same question.
FWIW, I run the OnDemand Governor and underclock at 883200 (245000 min) and don't notice a slowdown in any apps I run except angry birds (I ramp it up to 1.2 to play that). I haven't run any benchmarks or anything to see how it might improve the battery, since I really don't need to worry about it. It goes on the charger every night and I've never seen it below 50% when I plug it in.
I've been running a relatively stock DesireHD Gingerbread ROM based on the Asian WWE GB (2.37.707.3) but as of yesterday, I've been running one based on the telus GB released a few days ago (2.43.661.1). My kernel is custom based on stock HTC source for the 2.6.35.10 with OC/UV support added as hacked from the LeeDroid kernel tree. My source is here:
https://github.com/hoxsiew/ace-2.6.35-gb-mr
King Askaba said:
I want to know generally what is a good speed to underclock the inspire to achieve maximum batter and before you say every device is different I'm asking for a general idea not a specific one. Also do you think that overclocking has a big impact on batter I am overclocking right now at 1.3 ghz do you think that I'll notice a difference. And I know I have to test it myself but I just want others opinion on it.
Click to expand...
Click to collapse
I'm running at my rom's default (1017mhz). Instead of underclocking, I use the conservative governor. Battery life is good, but I also haven't noticed a battery drain when overclocking (I've been up to 1228mhz). I didn't test/run it for an extended period of time (1 day), but I only noticed a slight bump in performance.
I've heard of people on my rom (GingerBeast), clocking down to 768mhz without noticeable slowdown. As you stated, it just depends on the rom.
I have my phone set at:
Max: 768000
Min: 230000
This works for me in literally all the situations.
diablo009 said:
I have my phone set at:
Max: 768000
Min: 230000
This works for me in literally all the situations.
Click to expand...
Click to collapse
just about default GingerBeast.
But what cpu scaling is best for balance of battery life and performance
Sent from my Inspire "4G" using XDA Premium App
King Askaba said:
But what cpu scaling is best for balance of battery life and performance
Sent from my Inspire "4G" using XDA Premium App
Click to expand...
Click to collapse
No one but you can figure that out.
Yea I know but id like to know what works best fire others
Sent from my Inspire "4G" using XDA Premium App
Pretty sad uve gotta worry bout people jumping down ur throat when u ask a question. I see it on here alot, thats why i dont ask.
sent from my inspire 4g on xda premium
Thank you its like they either yell at you to search or they give you all devices are different you have to try it. I'm not looking for a definitive answer I just wanted an idea of what has worked for them. Seriously this forum has some rude people exspecially that Scott guy hasn't helped me once just tells me to search I said I searched and he says its on google but when I bring up the page nothing. This forum would be 1000x better if people didn't have a stick up their asses everytime someone asked a question.
King Askaba said:
This forum would be 1000x better if people didn't have a stick up their asses everytime someone asked a question.
Click to expand...
Click to collapse
+1
Sent from the most interesting device in the world.
I hope my response wasn't considered rude, but the question really is too vague to answer. If there were some magic combination of OC/UV that worked for everyone, everyone would be using it.
They say that if you ask five New Yorkers their stance on an issue, you'll get six different opinions. Similarly, five smart phone users probably have six different opinions about the best setup for their device and none will be applicable to your situation.
Yea but I wasn't asking for the perfect combination out just wanted to know what others use to get an idea of what I should set it at but clearly you don't get that
even though I've said it three times
Sent from my Inspire "4G" using XDA Premium App
Does anyone know the dangers of running the inspire OC'd on a regular basis up in the 1500000 range?
I've personally never have run into any issues, besides maybe shorter battery life.
I keep a profile in SetCPU for the temp if it gets over a certain temp. Don't have my phone with me so I couldn't tell you. But it seems fine overall.
That is one of my concerns. With the DAEMON setup on TB Fusion and some other newer roms there is no provision for a temp profile. Simply 6 files to change the settings in as far as I know.
Not sure and I have not read about possible cpu damage running it at say 1.5 or 1.7 for long perios of time. Even though it will still throttle back so to say by means of the chosen governor.
A question for someone with more experience than I!
SNadler said:
That is one of my concerns. With the DAEMON setup on TB Fusion and some other newer roms there is no provision for a temp profile. Simply 6 files to change the settings in as far as I know.
Not sure and I have not read about possible cpu damage running it at say 1.5 or 1.7 for long perios of time. Even though it will still throttle back so to say by means of the chosen governor.
A question for someone with more experience than I!
Click to expand...
Click to collapse
If you are worried about that, the DAEMON setup gets disabled if you run setcpu or something else like that.
Sent from my Desire HD using Tapatalk
gmurphy0487 said:
If you are worried about that, the DAEMON setup gets disabled if you run setcpu or something else like that.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Understood, I do want the increased performance tough.
I mostly want to know if there is any data showing that OC will do permanant damage to the device if used in that manner for extended period of time.
i dont know about overclocking phones but i assume the answer would be similiar to overclocking computers...
the answer is it does shorten the lifespan of the chip, but we are talking about minor differences over time - for example: instead of your chip lasting for 25 years it may last for 20. HOWEVER are you really going to be using your phone for that long?
So the short answer is no. This is assuming you are overclocked to a stable setting. If it is unstable then the setting is way too high/hot - you wouldnt be able to use it long enough to damage it (assuming you dont keep trying)
I ran my Inspire at 1.5x ghz for a couple of days, but I got random complete lock ups (had to pull the battery) and fc's. Slowed it back to 1.26 ghz and the issues went away.
Also, the temp never got very high, so it was not an overheating issue IMO.
What do you guys use to control the CPU speed?
I've used setCPU in the past, it seems to work. SickSense ROM does come with one, and that also seems to work well. I'm curious what you guys use. Currently I'm using KingCobra ROM and he included the DualCore MOD which is supposed to make the second core work faster and thus improve performance.
I think I'm going to install setCPU and set it on On-Demand. Not entirely sure what the best settings are for speed and also for battery life. I am more concerned about battery life while at the same time my phone can't be sluggish. Also I've noticed a lot of battery savings tools do work, but they do so by taking away things I need. For an example, the awesome battery took that comes with SickSense works wonderfully but the default supersaver setting cuts off my data and bluetooth making the phone almost useless.
shgadwa said:
What do you guys use to control the CPU speed?
I've used setCPU in the past, it seems to work. SickSense ROM does come with one, and that also seems to work well. I'm curious what you guys use. Currently I'm using KingCobra ROM and he included the DualCore MOD which is supposed to make the second core work faster and thus improve performance.
I think I'm going to install setCPU and set it on On-Demand. Not entirely sure what the best settings are for speed and also for battery life. I am more concerned about battery life while at the same time my phone can't be sluggish. Also I've noticed a lot of battery savings tools do work, but they do so by taking away things I need. For an example, the awesome battery took that comes with SickSense works wonderfully but the default supersaver setting cuts off my data and bluetooth making the phone almost useless.
Click to expand...
Click to collapse
Weird I got cpueditor working great on my bastardized version of cobra1.0, battery saver just underclocks and turns cpu1 off.
Never affected data
Sent from my HTC One X using xda premium
ChongoDroid said:
Weird I got cpueditor working great on my bastardized version of cobra1.0, battery saver just underclocks and turns cpu1 off.
Never affected data
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I see. well maybe if I find the time I should bastardize kingcobra 1.2 so that it has CPU editor.
shgadwa said:
I see. well maybe if I find the time I should bastardize kingcobra 1.2 so that it has CPU editor.
Click to expand...
Click to collapse
Wasn't too hard, this is the zip I used.
http://db.tt/v0cNLQyU
As always make a nandroid first, I never tested it on anything besides 1.0
Sent from my HTC One X using xda premium
ChongoDroid said:
Wasn't too hard, this is the zip I used.
http://db.tt/v0cNLQyU
As always make a nandroid first, I never tested it on anything besides 1.0
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
And it works! thank you for the .zip, I didn't know where to look for it.
See the thread in my sig around sunday night there will be an updated version (hopefully - work permitting) It will have a few new things that should help out this device. Like on the fly setting changes so it will edit the cpu when it comes online. It will work like a daemon.