[Q] Talon-dev4.1 battery life - Captivate Q&A, Help & Troubleshooting

Wanted to post in the talon dev thread but didnt have enough posts.
so heres my setup
I'm running serendipity VII build 2 rom
Talon dev 4.1 1440 oc 340mb kernel
and JVQ modem (tried jv6, and jvo)
also i have the bluedipity theme installed
My voltage control settings
sched = vr (tried sio, and noop. didnt notice much difference)
Conservative (powersave is unresponsive [on 100mhz constantly, takes forever to get back into VC], ondemand sits between 1000 and 1440mhz constantly [lowest ive seen it go is 800, but not for long])
UV to -75 across the board (was on 125 on talon 1200 oc, but too many issues on 1440)
my battery life was ok on talon 3.1 oc 1200 340mb
but now i hardly make it through the day with minimal use
i unplugged around 8:30am by the time i get home from work at 5:30 battery is at only around 28%
by minimal use i mean i only made 2 phone calls, send/receive a few texts, check email, facebook, xda, and a couple sites once on lunch and thats it
any suggestions on improving my battery life? id be happy with 1200 oc if i could have decent battery life

I got decent battery life with Talon 0.4.1 1200 OC. I use Dlev-3.8.1 rom, with TUBJV6 modem. Bettery lasted 2 days after full charge with normal use, including several short calls, a couple hours wifi internet and Angry birds, and some other usage I couldn't recall.

Something isn't right. You should be using the ondemand scheduler, and it shouldn't be stuck between the high clocks. It should go down to 100MHz when nothing is being done, and jump up to 1000MHz+ when there is activity. Either something went wrong during flashing, or there's something running in the background that's keeping the phone active.
I haven't tried any of the later Talon builds, but considering I get up to 2 days with more than moderate use on one of the older ones (no undervolting, 1200MHz OC), such a decrease in battery performance seems off.

That's what I thought. Ill go back to 1200 oc and see how it is
Sent from my captivate using XDA App

Related

HOT battery~!

OK...so MUCH THANKS to Mr. Carlisle for gettin me all squared away with rooting my Hero and upgrading to Froyo 2.2. All back ups complete, apps downloaded and only major bug thus far is the camera...SO....why is my battery running at 105 degrees on average? What should the normal range be? I turn it on @ 6 am after charging to 100% and wiping battery stats and ten hours later recharge it to 100% (Currently @ 50%) and all day the temp has been between 103 and 105. whycome? HELP!
Pauper7 said:
OK...so MUCH THANKS to Mr. Carlisle for gettin me all squared away with rooting my Hero and upgrading to Froyo 2.2. All back ups complete, apps downloaded and only major bug thus far is the camera...SO....why is my battery running at 105 degrees on average? What should the normal range be? I turn it on @ 6 am after charging to 100% and wiping battery stats and ten hours later recharge it to 100% (Currently @ 50%) and all day the temp has been between 103 and 105. whycome? HELP!
Click to expand...
Click to collapse
Because on FRF91 on Cyanogen mod (which i assume you are using) is overclocked to 710 mhz, where the hero's processor runs at 528 normally. My suggestion is to download an app called overclock widget from the market, (Obviously, it's a widget and you'll have to add it to your homescreen) and set the minimum and maximum clock (processor) speed to 240mhz(min) and 518mhz [or 534, if you want to, but it won't make much difference] (max).
You can set the max (or minimum) clock speed to be more or less. Lower clock(processor) speed=More lag but better battery life, and potential to freeze your hero because the processor can't operate the system fast enough. Higher clock(processor) speed= Faster and less lag but less battery life and can damage your touch screen (It's happened to me). if you leave it at too high a clock speed for too long, and can also freeze your phone because your processor can't operate at that speed and crashes your phone.
It's up to you if you want to overclock or not, but you should keep it resonable, and if you have heavy phone usage, don't go much further than 613 mhz for your max. There is also another program called set cpu that is avalible for free for xda members, but is a paid app on the market. Using that, you can set your frequencies to the default hero processor, or of other phones. But overclocking over 710mhz could do some harm to your phone, so be careful.
If you say, "I wonder if this will damage my phone," then don't take the chance without asking around first.
If you have any more questions about overclock, pm me, and I can help you out.
That temperature range, ~40C is completely normal when charging and using at the same time (with me, anyway). I'm OC'ed to 710 and using undervolt, too. The highest I've ever seen mine go is 43C, or about 109F. I don't really know where the "danger zone" is, but if I had to guess it would be around 48C or higher.
Edit: I reread your post, and do you mean it's at 40C always, even when it's sitting doing nothing? If that's the case then follow Ryoma Echizen's advice and fine-tune your CPU speed.

[Q] Best Governor for Setcpu?

Hey guys. Just wondering which governor works the best for you guys. Want to find the perfect compromise between battery life and no lag while scrolling.
i find that snartassv2 works best for me
Sent from my GT-N7000 using xda premium
Lagfree using Abyss 2.6 does what it says, very smooth desktop scrolling in ADW EX, even at stock 1.4GHz.
Battery life seems ok, and heat is about the same as On Demand.
For SetCPU
- Use Ondemand, that will give performance when CPU need it
and In profile add power saver (200 min 500 max), when screen off. if compromise any SW then max 800
What is the necessity to set this profile if the phone goes into deep sleep? Many times we don't need apps working in the background...
For instance I disabled all the background activities of apps requesting data (autosync...) and I am always in deep sleep with screen off...
My 2 cents.
Cheers.
I see guys. Been bouncing back and forth between intellidemand, smartass v2 and lagfree. Lagfree seems to consume more batteries though
abyssPlug
Sorry to bring this thread back to life but I was wondering what everyone thought the optimal settings for CPU speeds would be.
Galaxy Note GT-7000
CheckROM
Abyss Kernel
On Demand governer
I have them set right now for min 200 and max 1500. I had the set at min 50 and max 1600 but the min 50 made the phone a little laggy.
Another question, what should I set the temp profile to temp wise?
Thanks in advance
right now im running ondemand....min 200 max 1664
abyss kerenl... stock rom....
seems fine to me....

[Q] Optimal CPU settings

Hello, I tried searching but didn't find a thread about this. Sorry if there is one that I didn't find. I'm playing around with SetCPU and trying to figure out optimal settings. I know its a matter of preference but I wanted to see what everyones opinion is and what they have theirs set as. I have:
CheckROM Revo noteHD v5
Abyss Kernel
On Demand governor set
Max 1500MHz
Min 200MHz
I want a happy medium between battery life and performance.
I set a profile for screen off to min 200 and max 500.
I've been reading mixed reviews as to whether or not lower speeds actually increase battery life. I originally had the min at 50 but increased it to 200.
Another question is what would be a good temperature to set the temp profile to? Not sure when the phone begins to get too hot.
Thanks in advance
I used FM kernel with ondemand with min of 500Mhz and max of 1400Mhz with 2nd core always enabled, didnt notice that much of a battery loss.
go for rocket rom v22 with abbys note 4.2 kernel
set cpu min 50 max 800
on demand (if u want both cores active)
abbysnote (if u want single core running and 2nd to be used only if required otherwise 2nd would be off)
i got normal usage batt backup of 3 days least

Get more battery life (CM 10.1)

Hi all guys, I have got stock rom with a custom kernel for a lot of time. But with Cm 10.1 I can't get the same battery life and I don't understand why. All people here say the have more than 3 hours of screen-on time. But I can't say the same and I don't understand why.
I have optimous prime kernel and cm10.1 and I set every time these CPU frequency:
Min 102 MHz
Max 1.2 GHz
Interactive Scheduler
I don't have any strange app that cause drop of battery. I was wondering if Facebook app can drop it, but I have setted Facebook to don't synchronize.
LoKKeR said:
Hi all guys, I have got stock rom with a custom kernel for a lot of time. But with Cm 10.1 I can't get the same battery life and I don't understand why. All people here say the have more than 3 hours of screen-on time. But I can't say the same and I don't understand why.
I have optimous prime kernel and cm10.1 and I set every time these CPU frequency:
Min 102 MHz
Max 1.2 GHz
Interactive Scheduler
I don't have any strange app that cause drop of battery. I was wondering if Facebook app can drop it, but I have setted Facebook to don't synchronize.
Click to expand...
Click to collapse
Install better battery Stats or any other app that measures the sleep time of your phone, and see what's keeping your battery drain and / or keeping it from going into deep sleep
he is right. some app must drain your battery otherwise the battery is dying. also i can say that 1.2 is really low. mine is 1.7 and is running like a lion for around 3 hours too.

[Q&A] [KERNEL] FusterCluck Kernel (39a) CM/AOSP/Stock

Q&A for [KERNEL] FusterCluck Kernel (39a) CM/AOSP/Stock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL] FusterCluck Kernel (39a) CM/AOSP/Stock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery life update on 3.1 for stock
On default settings this kernel (r3b3) used more juice than the stock one.
I flashed 3.1, tweaked some things and now I have 3h 40min SOT with 50% battery left, which is pretty awesome imo and gets the job done for me. No heavy gaming, but I use camera and image editing apps and had no problems whatsoever. Today I was mostly browsing the web.
Settings I am using are :
cpu governor - ondemand with max frequency set to 1497 (but it keeps coming back to 1900, dunno what's up with that)
Cpu hotplug - inteliplug on conservative profile. Minimum cpu's online set to 4 (no difference in speed imo but very battery friendly combined with underclocking)
I/O scheduler - sio
Undervolted everything - 50mV
I had one reboot when I walked outside and tried to set brightness to the max (really weird and random). Didn't catch the log tho. The problem didn't reoccur, so I don't think it's a big of a deal. The phone acts nice and it's cool, no drops in signal, radios, gps and wifi work like a charm. BT works on my speakers and headphones.
Screen uses ~ 40% of battery, kernel ~ 28%, android system ~ 8%.
Using extreme 1.1 rom btw.
Great job on stock 3.1 @Yoinx I will update the status when I get to test it a bit more.
MilanStojkovic said:
On default settings this kernel (r3b3) used more juice than the stock one.
I flashed 3.1, tweaked some things and now I have 3h 40min SOT with 50% battery left, which is pretty awesome imo and gets the job done for me. No heavy gaming, but I use camera and image editing apps and had no problems whatsoever. Today I was mostly browsing the web.
Settings I am using are :
cpu governor - ondemand with max frequency set to 1497 (but it keeps coming back to 1900, dunno what's up with that)
Cpu hotplug - inteliplug on conservative profile. Minimum cpu's online set to 4 (no difference in speed imo but very battery friendly combined with underclocking)
I/O scheduler - sio
Undervolted everything - 50mV
I had one reboot when I walked outside and tried to set brightness to the max (really weird and random). Didn't catch the log tho. The problem didn't reoccur, so I don't think it's a big of a deal. The phone acts nice and it's cool, no drops in signal, radios, gps and wifi work like a charm. BT works on my speakers and headphones.
Screen uses ~ 40% of battery, kernel ~ 28%, android system ~ 8%.
Using extreme 1.1 rom btw.
Great job on stock 3.1 @Yoinx I will update the status when I get to test it a bit more.
Click to expand...
Click to collapse
Could be a bug with on-demand. Set the max cpu freq in the msm limiter... Should stop that.
3.1
Had a few random reboots yesterday under pretty mild usage. I am positive undervolting or underclocking was the cause since the 1400 wouldn't stick. I tried both trickster and adiutor. Not sure what was the problem but flashing bouchigo's int.d support zip and installing ukm and setting frequencies in synapse msm limiter solved the problem. It seems to be sticking now. Still undervolted, but working good for now. Thanks for the suggestion! I will keep monitoring the frequencies to see if that was a permanent fix.
Also noticed that underclocking the gpu while using msm-tz-adreno won't stick, not even in synapse. Same with msm_cpufreq. Choosing simple_ondemand is causing an instant system crash on extreme 1.1
That's all for now
UPDATE
Yup, freq sticking at 1574, undervolted - 45mV global, stable and smooth
3h20min SoT with 55% battery remaining. Sweet!
Where is the apk to change settings
richielasalsa said:
Where is the apk to change settings
Click to expand...
Click to collapse
look it up on Playstore. Synapse worked best for me, just make sure you have init.d set up if you are on extreme 1.1. There are other options too. Trickster, kernel auditor etc.

Categories

Resources