Help My battery life is horrendous!

[Arcadia]

Wow, I'm not sure what it is but my battery life has been horrible for the past week or so. Very minimal usage has me at 20% in 5 hours. This is unacceptable. The most I do is browse the web or play the occasional game for a few minutes. Recently I installed launcher pro, is this program known to worsen battery life? I don't even have that many programs on this phone. I see peoples screen shots with 7 pages full of widgets, I have 3 pages and only two are "full" of widgets.

I'm rooted, on stock rom, bloatware removed, and overclocked @ 1.2Ghz. I'm aware that overclocking is harder on the cpu and can worsen battery life, but my phone isn't always running at full speed. I have all my profiles set on conservative. When the screen is off I have it set to clock at 600Mhz max, 100 minimum.

Does anyone know what might be causing the problem?

I heard that some custom roms improve battery life. What else can I do to improve battery life? If launchers can cause bad battery I'll just use touchwiz, doesn't bother me. I'd rather have good battery life over good looking screens.

Also, my screen is on the lowest brightness setting for most of the day. Today for example, I had my phone fully charged. Took it off the charger and texted my girlfriend for a bit. Browsed maybe 2 sites on the web. I took a 2 hour nap. Woke up and played Nova for 20 minutes. I check my charge and my.phone was at 30%! Unacceptable. It was off the charger for less than 5 hours!

 

[melll]

I dont understand how you can post this about battery life and saying that its terrible yet you continue to run your phone over clocked.

Stop complaining if you're going to continue running the phone over clocked.

Titles should have read: "Over clocked Vibrant battery life is horrendous"

 

[SamsungVibrant]

I dont understand how you can post this about battery life and saying that its terrible yet you continue to run your phone over clocked.

Stop complaining if you're going to continue running the phone over clocked.

Titles should have read: "Over clocked Vibrant battery life is horrendous"

If you bother to read in detail, you would notice the user also has the phone set underclocked when not needed. As the OP said, 100-600 mhz

 

[SamsungVibrant]

Wow, I'm not sure what it is but my battery life has been horrible for the past week or so. Very minimal usage has me at 20% in 5 hours. This is unacceptable. The most I do is browse the web or play the occasional game for a few minutes. Recently I installed launcher pro, is this program known to worsen battery life? I don't even have that many programs on this phone. I see peoples screen shots with 7 pages full of widgets, I have 3 pages and only two are "full" of widgets.

I'm rooted, on stock rom, bloatware removed, and overclocked @ 1.2Ghz. I'm aware that overclocking is harder on the cpu and can worsen battery life, but my phone isn't always running at full speed. I have all my profiles set on conservative. When the screen is off I have it set to clock at 600Mhz max, 100 minimum.

Does anyone know what might be causing the problem?

I heard that some custom roms improve battery life. What else can I do to improve battery life? If launchers can cause bad battery I'll just use touchwiz, doesn't bother me. I'd rather have good battery life over good looking screens.

Also, my screen is on the lowest brightness setting for most of the day. Today for example, I had my phone fully charged. Took it off the charger and texted my girlfriend for a bit. Browsed maybe 2 sites on the web. I took a 2 hour nap. Woke up and played Nova for 20 minutes. I check my charge and my.phone was at 30%! Unacceptable. It was off the charger for less than 5 hours!

Hey there, well I notice the same battery life on my phone. I must admit, considering the power of this phone, the cpu, the gpu, and the screen. I consider the battery life decent for the hardware stats.

You may want to try searching battery in this forum, and you can see a list of stuff to try. For example, running a pure black image as your background may help. Putting your phone into 2g mode only when 3g is not needed. Turning off wifi, random not required syncs, etc.

 

[BigCiX]

My captivate (same phone as vibrant). Fully charged at 7:25 am. Used it twice to check my fantasy football points. 34% at 3:00pm. Only thing i can think of draining the battery was live scores for the Rams game and my music application was running in running apps.

 

[Arcadia]

I dont understand how you can post this about battery life and saying that its terrible yet you continue to run your phone over clocked.

Stop complaining if you're going to continue running the phone over clocked.

Titles should have read: "Over clocked Vibrant battery life is horrendous"

Dumb ass learn to read before making assumptions. I clearly stated I am aware overclocking drains battery power. However, I am not running the phone at 1.2Ghz all the time. When my screen is off it clocks down to 600Mhz. When the battery gets below 60% the max speed is lowered to 1ghz. Below 30% and max speed is 800Mhz. Even when my phone is running at less than 1Ghz the battery still drains very fast.

I tried the black background thing and I didn't notice any huge improvements in battery life. Honestly I think some program I installed in constantly syncing or something because when I first overclocked my phone battery life was great. I would be in class at 95%, 2 hours later it would still be around 90%. Now it'll be at 60% despite the screen being off. Weird.

 

[melll]

If you bother to read in detail, you would notice the user also has the phone set underclocked when not needed. As the OP said, 100-600 mhz

I read that believe me. But if you're complaining about the battery when you run the phone overclocked when you use it then you should not be posting anything saying the battery is hurrendous.

Also the phone doent run at full clock speeds when it doesnt run anything and the phone is in sleep btw. You wouldnt have to underlock it for it to not run at 1000 mhz when in sleep.

 

[SamsungVibrant]

I read that believe me. But if you're complaining about the battery when you run the phone overclocked when you use it then you should not be posting anything saying the battery is hurrendous.

Also the phone doent run at full clock speeds when it doesnt run anything and the phone is in sleep btw. You wouldnt have to underlock it for it to not run at 1000 mhz when in sleep.

Your own logic is going against you.

The OP complained about battery life when the phone was not in use. Then you made some comment about being over clocked. Again you are not reading in detail and you proved yourself wrong. If the OP is getting horrible battery life, even when the phone is not in use, then overclocking is not the cause. By your own confession, the phone underclocks when not in use. Also the OP has stated the phone is underclocked manually when not in use. So your comment about overclocking was uncalled for. THE OP IS HAVING BAD BATTERY LIFE EVEN WHEN IN PHONE IS NOT IN USE, MEANING THE PHONE IS UNDERCLOCKED WHEN NOT IN USE.

 

[howetechnical]

Whatever widgets you do have, if they update with a server, check the update interval time set. Also, you may not know this, but an OC'd proc, even if in use for a short time, will drain the battery considerably faster than a non-OC'd proc. I don't know the inns and outs of the OC app doing the software OC, but it may be constantly sending a signal to underclock at your specific setting while the phone is sleeping, which would also drain battery faster if that's the case.

Do this as a test, it won't hurt anything and it will get you closer to a resolution: take the OC off, and see if your battery life is more acceptable. Also check the update intervals of your widgets, as mentioned.

 

[melll]

Your own logic is going against you.

The OP complained about battery life when the phone was not in use. Then you made some comment about being over clocked. Again you are not reading in detail and you proved yourself wrong. If the OP is getting horrible battery life, even when the phone is not in use, then overclocking is not the cause. By your own confession, the phone underclocks when not in use. Also the OP has stated the phone is underclocked manually when not in use. So your comment about overclocking was uncalled for. THE OP IS HAVING BAD BATTERY LIFE EVEN WHEN IN PHONE IS NOT IN USE, MEANING THE PHONE IS UNDERCLOCKED WHEN NOT IN USE.

What is all this crazyness lol...

Overcloking, its whats killing his battery when its in use!

EOT lol

 

[SamsungVibrant]

what is all this crazyness lol...

Overcloking, its whats killing his battery when its in use!

Eot lol

ohh goodness

 

[Arcadia]

What is all this crazyness lol...

Overcloking, its whats killing his battery when its in use!

EOT lol

If you would READ you would know I haven't always had bad battery with this phone when it's been overclocked. For a while I was getting better battery life because of the SetCPU app. When the screen is off the phone is underclocked to 600Mhz. Once I had went into class at 95% and left at 90%.

Now the battery will drain 30% in two hours. Overclocking is not the reason why my battery is draining so much.

 

[howetechnical]

What is all this crazyness lol...

Overcloking, its whats killing his battery when its in use!

EOT lol

Hey man, as much as you may be sure of this, unless you know for certain exactly how the OC app uses resources when the phone is in use as well as sleeping, you may want to let this one settle. That's why I gave a suggestion, and my best shot-in-the-dark reasoning as to why it may be happening, but admitted that I don't know the backend of the app. At times, if you're not 100% sure, it's best to not instigate a fire (and this isn't an insult, but some of your other posts around the forums lead me to believe that you may not have the Android related knowledge currently to make the statements you did above with full certainty).

Just trying to help the situation out. I applaud your eagerness on the forums, and look forward to eventually seeing that eagerness intensity matched that with the advanced knowledge that other members can learn from.

 

[howetechnical]

If you would READ you would know I haven't always had bad battery with this phone when it's been overclocked. For a while I was getting better battery life because of the SetCPU app. When the screen is off the phone is underclocked to 600Mhz. Once I had went into class at 95% and left at 90%.

Now the battery will drain 30% in two hours. Overclocking is not the reason why my battery is draining so much.

If you're sure it's not the OC, and you're not willing to turn it off for a day to once more be absolutely certain (something I would strongly recommend, as OC'ing a proc sometimes has unpredictable results over time), then it's time to look at everything else you have constantly running: widgets. Since the time that your battery life was great while the OC was turned on, have you added any widgets? If so, do those widgets have update intervals? Facebook, Twitter, etc are all known to by default update every 15 minutes. That will kill the battery. Also, is WiFi and/or GPS constantly on? You need to look at -everything- that may be causing your battery to evacuate its charge quicker than you'd like.

Again, I strongly recommend just humoring the situation and turning the OC off for a day. You know how, when you call in to PC tech support companies, they ask you to restart your computer? As much as it sounds stupid and you really don't want to do it, it's exactly what will fix the problem 5 times out of 10. So even if there's a 10% chance that the OC is not the problem, I would just do it to be completely certain.

 

[HadouGhost]

try turning off any and all overclocks and underclocks. run it stock for a few days. see how the battery lasts. Until then dont qq about bad battery life.

Rembmer its still technically a program running these over and underclocks.

 

[howetechnical]

try turning off any and all overclocks and underclocks. run it stock for a few days. see how the battery lasts. Until then dont qq about bad battery life.

Rembmer its still technically a program running these over and underclocks.

Do I hear an echo in here?

 

[Arcadia]

Sorry, I read your comment earlier howetechnical but forgot to reply to it.

I will try turning off the overclock for a day and see what happens. I'll turn it off when I go to bed tonight and keep it off the entire day tomorrow.

 

[HadouGhost]

Do I hear an echo in here?

lol i didnt even read your post i just scrolled down to the reply button. im sorry