Related
I have a Thunderbolt running Das BAMF Remix 1.6.3 and Imo's 2.7.0 kernel (I have tried going between Batt Saver/Normal, and now I am on Extreme). I adjusted my brightness of my display to about 20% (instead of automatic), and when I am home I try to be on my Wi-Fi. For some reason, I am not getting a full day's charge out of my Thunderbolt (when I first got the extended battery, I was getting at least 32 hours). I read about people's batteries and I feel people with the stock battery are getting more/equal amount as I am with an extended battery. I tried running Normal setting on Imo's kernel at one point and I did not even last 12 hours, and I was on 3G doing only minimal texting. I tried Batt Saver, and the first day I used it, it was really good (about 10 hours and I was down to 75%, but until I got to 18% or so and then within 3 minutes it was dead, which was weird). But the following day it was not as good as it was, and it died again less than a day. I even tried the Das BAMF kernels and they have similar results. I am also trying to switch between InteractiveX/SmartAss/OndemandX, but I am not seeing too much of a difference (unless someone can give hints on which is supposed to lend to a longer lasting battery). Any advice would be appreciated! (And if you need more specs on my phone, let me know... I generally only text, I do not play games or do very intensive internet things).
I have found the best battery life on bamf stripped v1.1, I get better battery life on that than any other Rom I've tried including stripped v1.7 and all the other bamf versions. I'm running the 4.4.6 kernel, I haven't tried the batt saver kernel from Imoseyon yet. I get 2-3x's the battery life as stock and almost twice the battery life as any other bamf Rom
There are lots of things to consider about your battery life. If you look at your batter use on your phone does it show anything that might be suspiciously draining battery more than normal? If you're using Imo's kernel you can type "12" into the terminal when you are changing governors to see the stats of how long your phone is staying at different frequencies, does it show a high amount of time spent at the higher frequencies? How long does your phones display stay on for?
There are so many things that can drain the battery its ridiculous and randomly I will have severe drains at times that are only solved by a reboot.
eraursls1984, do you have an extended battery? How much battery life are you getting?
Beastclaw, battery use seems normal - nothing out of the ordinary or suspicious is really eating at my battery. As I said before, I am currently running InteractiveX and at Extreme mode, and these are my states at different frequencies:
245760: 2102206
368640: 409810
768000: 58113
1024000: 263351
1222400: 12737
1408000: 72575
1593600: 0
1766400: 0
1920000: 0
Seems that nothing is really running too much on high frequencies, mainly on the lower end. My phone display is supposed to stay on for, I believe, 2 minutes, but whenever I am doing using it, I always lock it.
I heard Autostarts was a good app that could help with battery life and performance (and I was warned to not change any system settings), but I am trying to see if maybe there is anything else I can do to figure out why my battery seems to not last as long as other batteries.
You can try using an app from the market called "CurrentWidget" It allows you to log how much power your phone is using at different intervals of time. My phone generally runs at 40-60mA when the screen is off and its not doing anything and between 400-600mA when the screen is on and I am running tasks. You can use the log to check to make sure your phone isnt drawing too much power in the down state. It even shows you the stats in a nifty little graph form
Aup808 said:
eraursls1984, do you have an extended battery? How much battery life are you getting?.
Click to expand...
Click to collapse
I have a stock battery and with normal use I get 12-14 hours compared to about 4 when I was completely stock. When I use my phone heavily, constant browsing, I get about 4 hours compared to less than 2 stock. I always have my brightness all the way up except for when I'm in bed because this screen is not bright at all compared to my old phones. Unless you just have to have sense (which to me makes no sense, lol) then I would recommend trying bamf stripped v1.1. I am also not overclocked, I noticed a little increase in performance but not enough to justify the loss of some battery life., however I was going to experiment with it again since I haven't tested the performance and battery life of stripped v1.1 overclocked.
I mean, I have BAMF Remix 1.6.3, which I guess has Sense elements since I do not have BAMF Stripped? I mean, I do not think I use any Sense features or anything like that, so I have no reason not to get BAMF Stripped if it helps increase performance/battery life. Yeah, on Remix 1.6.3 and Imo's kernel at Normal, I had 12 hours on my extended battery... Haha.
Bump - does anyone have Autostarts? Or any other program/app that will help with the battery life, or any other suggestions? I will test the CurrentWidget app tomorrow when I am actually up and using my phone and see if I get similar results or if I find another program is using up my memory... I also recently installed Advanced Task Killer today to help with this battery problem, but I heard mixed things about using it and how it can actually negatively impact the phone instead of helping.
Aup808 said:
Bump - does anyone have Autostarts? Or any other program/app that will help with the battery life, or any other suggestions? I will test the CurrentWidget app tomorrow when I am actually up and using my phone and see if I get similar results or if I find another program is using up my memory... I also recently installed Advanced Task Killer today to help with this battery problem, but I heard mixed things about using it and how it can actually negatively impact the phone instead of helping.
Click to expand...
Click to collapse
Before 2.2 they were useful on some phones if used right, but its not needed nor does it work on the thunderbolt. If its set to autokill then it will drain the battery faster by running and killing apps, then the phone using juice to reopen the apps that were killed. If you root you can use autokiller (not a task killer) to set parameters for ram memory but I haven't found it to be necessary on the t-bolt, it was needed on my old droid X to keep it from lagging. I would suggest uninstalling the task killer.
Took your advice and uninstalled the task killer - thanks! Anyone else have any other suggestions or advice about my battery problem?
Autostarts is definitely worth $1. If you are familiar with Windows, it's kinda like msconfig for android. It prevents nonessential apps from starting in the background and wasting battery & network bandwidth. If you want to do everything you possibly can to minimize resource hogging, you should get Autostarts.
I downloaded Autostarts - I hate to be asking this sort of question but I am sort of cautious when changing these sorts of settings (because I heard a person who had to boot into recovery because he shut off system applications by accident), which programs should/shouldn't I turn off? I am a little confused how to use this program - did it automatically shut off some programs, because as I look through I see some programs are crossed off in a green line... Any help would be appreciated! Thanks!
Bump - can anyone help me with Autostarts? Any help would be appreciated! Thanks!
Sent from my ADR6400L using XDA App
Sigh, Autostarts isn't a "task killer"
I stay away from any proccess that's needed to run in the background. Things in yellow, leave alone. IMO pandora has no business running in the background at start up. If there's no valid reason, I kill it.
Tossed from my Tunabowl
I realize Autostarts isn't a task killer (it cannot kill a task if it never opens up, hehe). Thanks for your advice though! The more I was looking at it last night, the more I was understanding, but you just reassured what I was assuming. Hopefully this helps my battery a bit... Or I figure what else makes my extended battery drain faster than others.
Even with Autostarts, my battery life has not improved that much... I have been experimenting a bit with different governors and settings, but now I am back with the extreme Imo kernel and on InteractiveX. Does anyone have any other suggestions? Any help would be appreciated!
I was having trouble with my battery also. I've been lucky with Gingeritis but still the battery was killing me. This may not be an option but the extended battery is amazing. I got the case to go with it and I'm not disapointed. This OS with heavy use also and display at 50% and all animations enabled. Also running 4g all day!
Sent from my ADR6400L using XDA Premium App
The problem is, I DO have the extended battery and now seeing some of the battery life that others are getting (a lot say 30+ hours, I am barely pushing my phone and I am getting less than 20 at a time).
BAMF 3 RC2, imo 3.3.4, 245/1593, LTE Only mode, auto brightness, twitter sync every 15 minutes, facebook every hour, gmail push, weather every hour, 4 hours of music streaming, another couple of playing, a lot of twitter and facebook, and doing a bunch of other things with the phone, and I rebooted about 3 times. I think I could hit 50+ hours if i didn't OC or reboot.
Oh yeah, I have the extended battery
g00s3y, which governor are you using?
i'm on the same kernel, but using gingerremix w/ a std battery. the phone drains 40% overnight with it being on wifi. (that's with just gmail pushing and gtalk on).
Hey! this is my first android phone, and upon playing with it the first day I was kind of bummed on the battery life, which I knew wouldn't be great compared to my dumb phone, but I never thought it'd run out before the end of the day.
I started reading about it and found a lot of people saying to just manually turn off all these options, but I also found JuiceDefender Ultimate which does so automatically... only when I set it to. So far it has helped me improve the battery life by at least 5 hours per day just by tweaking screen brightness and data usage.
I see that there's more options to control CPU speed, network mode, background data and some other stuff by using AOSP helper and having a supporting kernel. Has anyone used these on this device? is it safe to mess with those settings? Does it help improve battery more?
I'm currently running FreeGS3 0.4 if that makes much of a difference.
What are your SetCPU settings on the Amaze? What do you consider optimal/suggest?
I pretty much need everyone's input before underclocking to preserve battery, cuz whenever I set it up, it lags my phone like crazy and my battery takes long to charge and still goes down pretty much the same speed. Using SpeedROM 6.5.
Instead of underclocking, you can simply undervolt instead, maintaining your current performance while reducing battery use.
sent from a galaxy you'll never see.
I think use 1.2Ghz is ok for me.It's also fast, but for me, I seldom play games
Mystery? said:
What are your SetCPU settings on the Amaze? What do you consider optimal/suggest?
I pretty much need everyone's input before underclocking to preserve battery, cuz whenever I set it up, it lags my phone like crazy and my battery takes long to charge and still goes down pretty much the same speed. Using SpeedROM 6.5.
Click to expand...
Click to collapse
3rd party cpu apps aren't even needed, you can control more just by changing a few things in a few system files. I gave pretty good details here http://forum.xda-developers.com/showpost.php?p=30298629&postcount=4
You CAN undervolt, but if you have any issues, it could be undervolt related.. system tuner is better for undervolt, I actually don't like setcpu anymore at all.
If you ARE determined to use setcpu, don't use the profiles part- like cpu speed on screen off, etc.. it hurts more than it helps.
But not using a cpu app means you don't have yet ANOTHER app running on the phone constantly, eating ram, slowing things down.. my 2 cents.
hey, so i have ran pretty much every "jelly bean" rom out there for this phone for about 2-2.5 months. maybe less. note sure..
anyway, the battery has been horrible! on every rom.. I have a 2700 mAMP battery, and a regular Samsung battery. I have to use both once a day for this phone.. now I have no idea what is making the phone loose percentage after percentage of battery as fast as it has for me, but everytime i post i get about 0 luck from people that either have the same issue, or just people saying they have heard it a million times. i probably should have put this in the "Q&A" thread, but maybe i forgot. can someone, preferably more than one, help me out here?? i don't get how other people say they have 8 or more hours of screen on time with half the battery left. it just doesn't make since. I am loving the android system. but this could be anything! the apps in the background. the kernel, maybe I didn't clean my cache or something. i can't raise my brightness up to far or it'll drain my battery, jamie in the paranoid thread said he had his batter on 100 percent and had excellent battery. so I'm far from confused here. do I need to get another phone, or what. very much apprentice the help from as many people as possible. I love my phone, but I hate that i have to focus on using two battery a day with this phone.
Same here battery draining pretty quick on all jb ROMs.
Sent from the TermiNOTEr!
Battery usage is highly subjective..
It's nearly impossible to determine a baseline Usage expectancy, simply due to the untold number of variables that drain the battery.
We know the obvious power users ....the display, wifi, data ..
But it gets far more difficult to track the Usage after that.
We know that JB is not optimized for our device, but it's getting better, and until we see a true JB kernel with the rom matched to it, the battery is going to suffer.
Then of course we have the many services that users run, along with countless apps ...
Long story short ....maybe a more stable choice would work better? ?
Like ICS, At least until JB calms down a bit ...
I'm actually running Saurom as I type this ...and my battery life is excellent.
JB just isn't quite there yet ...IMHO ....g
to get better battery turn brightness to lowest usable setting, turn off sync for any non essential apps, turn off soft key lights, flash a kernel that lets you under volt and under clock, try different govonors and io schedulers, turn off gps, put in airplane mode when not using. these should help. keep in mind cell signal strength will also impact battery and 4g will kill it faster then 3g. i am on cm9 stable under clocked to 1.18 undervolt all by 25mv( not much change but i like to be safe) ondemand and sio and get amazing battery life.
What's your screen-on time? 4 hours is the close to the limit on ANY rom for our Notes. You have to make sure it's not some sort of confirmation bias going on here.
gregsarg said:
Battery usage is highly subjective..
It's nearly impossible to determine a baseline Usage expectancy, simply due to the untold number of variables that drain the battery.
We know the obvious power users ....the display, wifi, data ..
But it gets far more difficult to track the Usage after that.
We know that JB is not optimized for our device, but it's getting better, and until we see a true JB kernel with the rom matched to it, the battery is going to suffer.
Then of course we have the many services that users run, along with countless apps ...
Long story short ....maybe a more stable choice would work better? ?
Like ICS, At least until JB calms down a bit ...
I'm actually running Saurom as I type this ...and my battery life is excellent.
JB just isn't quite there yet ...IMHO ....g
Click to expand...
Click to collapse
thank you so much man! i actually went to at&t and they mentioned that too. they said the kernel im using isn't fully optimized for the phone yet. other words. the phone wont support it. he said basic stock ics is the best thing to do now. he also said. these forums are for phones from Europe as well. not just for AT&T in the us. again, the ROMS these devs are making are not supported for the phone, and is kinda like a mimic of something its not. he said jelly bean was out, but i don't know where to get it. can someone tell me how to install ICS, because when I download it, and use KIES, it installs the system, but never fully completes the process.
trancemusic+1 said:
thank you so much man! i actually went to at&t and they mentioned that too. they said the kernel im using isn't fully optimized for the phone yet. other words. the phone wont support it. he said basic stock ics is the best thing to do now. he also said. these forums are for phones from Europe as well. not just for AT&T in the us. again, the ROMS these devs are making are not supported for the phone, and is kinda like a mimic of something its not. he said jelly bean was out, but i don't know where to get it. can someone tell me how to install ICS, because when I download it, and use KIES, it installs the system, but never fully completes the process.
Click to expand...
Click to collapse
Sure...
At the top of the general note section, you will find the "note super everything thread"....
Scroll down to find the ICS info you need...
There are many great ICS roms, and you will find that your phone is "MUCH" better running on the software that was intended for it..
Do the homework in the superthread, and read, read, read......then if you have more questions....just PM me, and we'll get ya up and running....g
gregsarg said:
Sure...
At the top of the general note section, you will find the "note super everything thread"....
Scroll down to find the ICS info you need...
There are many great ICS roms, and you will find that your phone is "MUCH" better running on the software that was intended for it..
Do the homework in the superthread, and read, read, read......then if you have more questions....just PM me, and we'll get ya up and running....g
Click to expand...
Click to collapse
thank you so much! I will get right to this
I never got more then 2 hours screen on time on any ROM, just figured that was normal.
Ugh.
That is low scout ....
I pull 3 hours average ...
Must be the internut ..on XDA ....LOL ......g
gregsarg said:
Ugh.
That is low scout ....
I pull 3 hours average ...
Must be the internut ..on XDA ....LOL ......g
Click to expand...
Click to collapse
I'm in the same boat as manel, never gotten anywhere above 2h on screen time. Maybe additional 10m or so. Figured it was normal lol
Sent from my SAMSUNG-SGH-I717 using xda premium
Battery life is purely subjective. No two people will have the same experience.
Have you used an app like CPU spy to make sure the phone is going into deep sleep? Rogue apps keeping the phone in a wake lock can seriously affect battery life, but its hard to say if anybody's apps are doing that, because we all use different apps and there's no list of apps that keep a wake lock, so you need to use something like CPU spy to see if you are going to deep sleep when your screen is off.
Related to apps as well, don't use any task killers or constantly kill apps when you exit them. A lot of people think killing apps is necessary when it completely is not. Android, since donut or eclair, manages its RAM very well, so that when a properly written app (ie. It's not keeping a wake lock) is in RAM, it's just in a frozen state not using any CPU cycles. Constantly killing well written apps hurts battery life, because restarting the app fresh is much more processor intensive than pulling a frozen app out of RAM. Plus you don't have to deal with annoying loading/splash screens.
Also, like others have said, using the lowest brightness possible, and turning off sync for any unnecessary apps will help battery life. GPS doesn't matter so long as you don't keep something running that uses it. If an app isn't using GPS, then GPS isn't using battery. I always leave my GPS on and do not notice a difference compared to turning it off. If you're paranoid about GPS leave it off, but it's annoying to have to turn it on every time you want to use an app that requires it. You can also disable location access in most apps like Facebook, twitter, etc where you don't need GPS really, and that will make leaving it on even better. If you don't use GPS much anyways, leave it off.
Like somebody said, your cell signal can greatly affect your performance, so use WiFi whenever possible, and even put a data toggle in your pulldown so you can disable cell data when you don't really need it. WiFi in general uses less battery than cellular data, so I use it whenever possible.
I've also noticed that how you use your screen on time also has a great effect on battery life. When I have extended lengths of constant screen on time where the phone starts heating up and whatnot, I see much less battery life than if I just use my phone here and there intermittently. Long stretches of screen on time stress the processor and battery heating them up and making them less efficient, where as short stretches allow the processor time to stay at a cooler, more efficient temperature. If you game at all on your phone, you've definitely experienced this, as you know that your phone heats up due to the extended lengths of screen on time and heavy processor usage. Gaming is a no-no if you're striving for better battery life.
With following those guidelines, my Note sees about 3.5 screen on time with JB on Gubment Cheeze. I would get around that on ICS as well, and I don't remember what it was on GB. Fellow testers and teammates for Gubment Cheeze have seen up to 4 hours and a little more even on JB, so it's definitely possible to have decent battery life on JB.
It really comes down to your own personal usage.
Sent from my Galaxy Nexus using Tapatalk 2
(quoted)(Related to apps as well, don't use any task killers or constantly kill apps when you exit them. A lot of people think killing apps is necessary when it completely is not. Android, since donut or eclair, manages its RAM very well, so that when a properly written app (ie. It's not keeping a wake lock) is in RAM, it's just in a frozen state not using any CPU cycles. Constantly killing well written apps hurts battery life, because restarting the app fresh is much more processor intensive than pulling a frozen app out of RAM. Plus you don't have to deal with annoying loading/splash screens. )quoted)
I was not aware of this info....many thanks for the heads up...I always supposed that since the ram was consumed with applications, that those apps were pulling CPU usage from the device...
that is clearly not the case......g
Yep, no problem. If you go back to a touchwiz based ROM and go into the stock task manager, it shows you what's taking up RAM, as well as the CPU usage of each thing in the list. If the apps are working properly, pretty much everything will show very little to 0% CPU usage, and ones that are using it heavily will even be highlighted in yellow or red depending on their CPU usage %age. Unfortunately aosp based ROMs don't have that task manager, one of the things I miss from touchwiz.
Every time a non-techy friend buys a new android, it seems the overly aggressive sales rep that sold the phone to them 'helped' them get to know the phone and installed a task killer, specifically advanced task killer. I always just uninstall it without telling them and see how long it takes them to notice lol.
It's still useful in certain instances, for example if you have an app that doesn't run well but you still like/need to use, but in general practice android does a much better job of managing itself. Besides, if you have an app that you know runs poorly and hogs your processor in the background, but you still need to use it, with most aosp based ROMs you can set your phone so that long pressing the back button kills the current app, essentially making task killers useless.
Sent from my Galaxy Nexus using Tapatalk 2
welchertc said:
Battery life is purely subjective. No two people will have the same experience.
Have you used an app like CPU spy to make sure the phone is going into deep sleep? Rogue apps keeping the phone in a wake lock can seriously affect battery life, but its hard to say if anybody's apps are doing that, because we all use different apps and there's no list of apps that keep a wake lock, so you need to use something like CPU spy to see if you are going to deep sleep when your screen is off.
Related to apps as well, don't use any task killers or constantly kill apps when you exit them. A lot of people think killing apps is necessary when it completely is not. Android, since donut or eclair, manages its RAM very well, so that when a properly written app (ie. It's not keeping a wake lock) is in RAM, it's just in a frozen state not using any CPU cycles. Constantly killing well written apps hurts battery life, because restarting the app fresh is much more processor intensive than pulling a frozen app out of RAM. Plus you don't have to deal with annoying loading/splash screens.
Also, like others have said, using the lowest brightness possible, and turning off sync for any unnecessary apps will help battery life. GPS doesn't matter so long as you don't keep something running that uses it. If an app isn't using GPS, then GPS isn't using battery. I always leave my GPS on and do not notice a difference compared to turning it off. If you're paranoid about GPS leave it off, but it's annoying to have to turn it on every time you want to use an app that requires it. You can also disable location access in most apps like Facebook, twitter, etc where you don't need GPS really, and that will make leaving it on even better. If you don't use GPS much anyways, leave it off.
Like somebody said, your cell signal can greatly affect your performance, so use WiFi whenever possible, and even put a data toggle in your pulldown so you can disable cell data when you don't really need it. WiFi in general uses less battery than cellular data, so I use it whenever possible.
I've also noticed that how you use your screen on time also has a great effect on battery life. When I have extended lengths of constant screen on time where the phone starts heating up and whatnot, I see much less battery life than if I just use my phone here and there intermittently. Long stretches of screen on time stress the processor and battery heating them up and making them less efficient, where as short stretches allow the processor time to stay at a cooler, more efficient temperature. If you game at all on your phone, you've definitely experienced this, as you know that your phone heats up due to the extended lengths of screen on time and heavy processor usage. Gaming is a no-no if you're striving for better battery life.
With following those guidelines, my Note sees about 3.5 screen on time with JB on Gubment Cheeze. I would get around that on ICS as well, and I don't remember what it was on GB. Fellow testers and teammates for Gubment Cheeze have seen up to 4 hours and a little more even on JB, so it's definitely possible to have decent battery life on JB.
It really comes down to your own personal usage.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's a very big heads up. Thanks. But thing is when I have wifi on. Don't I need to be connected to wifi network first before it actually can help me??
Sent from my SAMSUNG-SGH-I717 using xda premium
trancemusic+1 said:
That's a very big heads up. Thanks. But thing is when I have wifi on. Don't I need to be connected to wifi network first before it actually can help me??
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
This is true. What kind of signal strength do you get where you are at? Does your phone bounce back and forth to lte. I have noticed when i go from a strong signal to weaker signals or band switching a lot, my battery drains rapidly.
Use cpuspy, as mentioned, to verify you do see deep sleep. Also, i find if rooted, that seting the min speed to 192 helps quite a bit.
So I'm looking to try to get my phone running more efficiently. In respect to both battery life and overall running smooth. Honestly my phone just runs like crap... lots of lag (not horrible most times), and battery life lasts me to 5pm every day.
I have a feeling my biggest culprit is the constant running background apps. How the hell do I stop an app from always running? Things like facebook, scoremobile, wechat... and many more. All of these, I turned updates, refresh, notifications, everything possible off. I just want to be able to use the app when I open it. Yet even with turning everything off, they're still using up a ton of RAM and in the running apps list!
So I imagine things like this are my main culprit of poor battery life and performance.
Anything else I can do? Underclock?
Running CM10.1 unofficial P10 about to go p11.
Thanks!
buump?
Try a different kernel perhaps? Either that or play around with governors. Hopefully these can optimise CPU usage.
It might take a while to figure out how to balance CPU power with maximum battery life. It really is just about trial and error.
Biggest battery hog for me is the massive screen, so you could turn down brightness too. Google ways to save battery life on Android and see what the rest of the Internet suggests
Also try the app Wakelock Detector. (I think that's what it's called haha) see what is keeping your processor running and find out ways to stop processes eating your battery when it shouldn't.
Hopefully this helped some
Sent from my SAMSUNG-SGH-I717 using xda app-developers app