Battery Life Suddenly Cut in Half!

[Psychokitty]

I suspect many of you are like me and monkey with your phones so damned much that sometimes it's hard to pinpoint what changes we've made to which changes we've noticed.
I've been running UD 9.0 ever since it came out. I've had great battery life with SetCPU profiles set from 250MHz to 1Ghz unless the battery goes below 30%, in which case it goes down to a max of 550MHz with a low still at 250MHz.
The only thing I've changed recently is downloads of app updates, (...including SetCPU, btw).
The other day my home WiFi crapped out, so I used a tether app and played around online with my laptop using my phone. I had never done it for so long before, but inside of about three hours, my battery was at 20%, when usually at that time of day, it's at hour 13 from last charge, and at about 40%.
Now my battery is not lasting a whole 14 hours, where it used to go from 5 AM to 10 PM before it gave me the "15% juice left" heads up. I don't know if it's because of a bad SetCPU update, or a wifi tether app problem, or what.

Just wondering if anyone else has had similar problems after similar updates, etc.

 

[Fadelight]

Umm, dude... have you read the threads about the OTA draining everyone's battery?

 

[RaFF_MyZZteR]

Oddly enough I had the same thing happen to me. I recalibrated my battery last night (drained all the way and full charged) and am hoping it gets better but I used wifi tether for about 2 hours (while it was connected to a power source) and don't worry I didn't do much...at the end it was only about 40 mb of download/upload total.

 

[nstallion]

Oddly enough I had the same thing happen to me. I recalibrated my battery last night (drained all the way and full charged) and am hoping it gets better but I used wifi tether for about 2 hours (while it was connected to a power source) and don't worry I didn't do much...at the end it was only about 40 mb of download/upload total.

I saw your other thread about this and honestly it seems like a coincidence. I can't see how those things could be related.

 

[Psychokitty]

Umm, dude... have you read the threads about the OTA draining everyone's battery?

So this just starts out of the blue? Like as of two days ago? Dude?

 

[nstallion]

So this just starts out of the blue? Like as of two days ago? Dude?

LOL. There are many things you could have said to counter his comment, but this is not one of them.

The OTA was sent out *gasp* 2 days ago. Refer to this thread: http://androidforums.com/all-things-root-droid/73245-new-ota-update.html

 

[Fadelight]

So this just starts out of the blue? Like as of two days ago? Dude?

Yeah... rumor has it there was a silent OTA pushed two days ago. The battery life drain comes from your phone blocking the OTA, so the OTA just keeps downloading over and over and over and over...


read this

http://androidforums.com/all-things-root-droid/73245-new-ota-update.html

 

[Fabolous]

Depends on which ROM you're running. If it's missing otacerts.zip, then yes, it will continue to redownload the OTA over and over.

 

[Fadelight]

Depends on which ROM you're running. If it's missing otacerts.zip, then yes, it will continue to redownload the OTA over and over.

Well, he said he was running UD 9.0. Who was BD ripping off during that release? That'd give you your answer on that one.

 

[Psychokitty]

OK, so what do I do? I just read a thread about the 2.1 update, but it's a month old.

 

[nstallion]

There are two identical links in this thread pointing you in the right direction.

 

[Psychokitty]

There are two identical links in this thread pointing you in the right direction.

Let's try not to be so friggin condescending, ok? That thread doesn't tell me shit, so are you saying nobody knows what to do?

 

[Fadelight]

Let's try not to be so friggin condescending, ok? That thread doesn't tell me shit, so are you saying nobody knows what to do?

Wow... nice way to treat other people.

I have suddenly lost the urge to help you. Good luck.

 

[tom108]

Let's try not to be so friggin condescending, ok? That thread doesn't tell me shit, so are you saying nobody knows what to do?

actually the thread suggests exactly what to do and provides the file to do it.

 

[Psychokitty]

He treats me like an idiot and you lose interest in helping me?
WTF?
I saw the links, I read the thread, and it's inconclusive. It wasn't like I was too lazy or stupid to read it, but that's certainly how he responded.

 

[tom108]

He treats me like an idiot and you lose interest in helping me?
WTF?
I saw the links, I read the thread, and it's inconclusive. It wasn't like I was too lazy or stupid to read it, but that's certainly how he responded.

truth of the matter is no one is sure who is targeted for the update but that it may be those whom have not updated the baseband. if the rom you are running does not include the otacert file your phone will try to download the update over and over again. you need the ota cert to accept the update and them block it from installing with sprecovery.

 

[DjOutlaw32]

He might have come out a bit harsh, but if you know the answer to help him at least give him the link to the thread or tell him the answer to issue straight up instead off just saying "well their are threads go find them," I mean I understand you can use the "search bar", but this is still a pretty new issue and will probably end up giving him non usable info. If you can't help don't post thats basically it. Not trying to defend him, just stating that this gets annoying from time to time on the forums.



Note: well this got posted later than it was supposed to.

 

[Psychokitty]

Thank you.
I don't know if I get the usual notification that comes with official downloads anymore (due to my ROM), and my wife's Droid hasn't been 'asking' her to accept one, either. Does this one just automatically load itself without notification on a stock phone, or is it just more likely that my ROM no longer shows the notification and that my wife hasn't been 'lucky' enough to get this update?

If I'm missing the ota cert file or it has been renamed/altered, and I reinstall the file, how do I use SPRecovery to block the installation of the update? I'm confused about this part. I have ROM Manager, but I don't really know how to use most of it.
I back up my system with it every once in a while. If I screw this up and let this update install, will flashing to my latest back up erase the installation?
Also, is this update a fix for the baseband update that had a lot of people complianing about poor reception? If I understand correctly, it was the previous one that could supposedly reset rooted phones?

 

[nstallion]

Considering your reaction I'm not sure you deserve the help but in the spirit of this forum I'm going to give it anyway.

After being linked to this thread: http://androidforums.com/all-things-root-droid/73245-new-ota-update.html you came back talking about the 2.1 update that is 2 months old, which has nothing to do with that thread. Reading it will explain what people think the problem is and how to fix it.

No one is sure what phones are being targetted for the update but it is speculated to be one a few things:

1. Phones whose OS version is listed as something other than "2.1 update-1"
2. Phones which do not have the most current baseband file.
3. Some other unidentified reason.


In order to fix the problem (if it even is a problem) you have to dowload this file otafix.zip (provided by Fabolous) and install using Clockwork Recovery - Turn off phone and turn back on while holding X, select install zip from SD card, find the zip and apply.

You don't need SPRecovery unless your phone has already downloaded the file and is prompting you to install it.

 

[BigRedGonzo]

FWIW

I am stock. I used to be rooted, but became a flash addict and went on the wagon when the 2.1 update came out. Enough background...

My wife woke me up on either Monday or Tuesday night and told me to shut the stupid phone up. It usually behaves well with being quiet at night so I picked it up to see what was going on. The Red Eye animation was going, indicating a reboot, and it took forever for it to startup (a couple of minutes from the time I looked at it.) It started up finally with one last DDRROOIIDD, for which my wife elbowed me in the back, and then went back to its normal nighttime silent mode.

I DID NOT get asked to accept the update ( assuming that is what was going on ) and I have never had my phone reboot itself in the middle of the night. To repeat, my phone is currently ( and was at that time ) stock. I guess that sort of shoots down the idea of a Root User Witch Hunt, but I have noticed no difference in my phone.

I hope this is of some use to someone.

BigRedGonzo

 

[tom108]

FWIW

I am stock. I used to be rooted, but became a flash addict and went on the wagon when the 2.1 update came out. Enough background...

My wife woke me up on either Monday or Tuesday night and told me to shut the stupid phone up. It usually behaves well with being quiet at night so I picked it up to see what was going on. The Red Eye animation was going, indicating a reboot, and it took forever for it to startup (a couple of minutes from the time I looked at it.) It started up finally with one last DDRROOIIDD, for which my wife elbowed me in the back, and then went back to its normal nighttime silent mode.

I DID NOT get asked to accept the update ( assuming that is what was going on ) and I have never had my phone reboot itself in the middle of the night. To repeat, my phone is currently ( and was at that time ) stock. I guess that sort of shoots down the idea of a Root User Witch Hunt, but I have noticed no difference in my phone.

I hope this is of some use to someone.

BigRedGonzo

it is possible you got an update. however bot unrooted and rooted i have experienced random reboots.

 

[BigRedGonzo]

it is possible you got an update. however bot unrooted and rooted i have experienced random reboots.

I just found that it was odd that this reboot coincided with the timing of what was going on here. On stock, my droid has never rebooted itself. In fact, the only time that I ever had random reboots was on Bugless Beast. I have used SholesMod, Bugless Beast, DroidMod and Simply Stunning, all in various incarnations and the only random reboot that I have ever experienced, with the exception of the one that we are discussing, was on the Bugless Beast. I had all sorts of issues with BB and I am certain that it had to do with the flash - I AM DEFINITELY NOT BASHING BB. It certainly could have been a random reboot, but if it was, it's timing was certainly coincidental.

 

[BigRedGonzo]

Sorry, they were having a sale on the word "certainly" and I obviously bought a bunch!!

 

[DjOutlaw32]

Considering your reaction I'm not sure you deserve the help but in the spirit of this forum I'm going to give it anyway.

After being linked to this thread: http://androidforums.com/all-things-root-droid/73245-new-ota-update.html you came back talking about the 2.1 update that is 2 months old, which has nothing to do with that thread. Reading it will explain what people think the problem is and how to fix it.

No one is sure what phones are being targetted for the update but it is speculated to be one a few things:

1. Phones whose OS version is listed as something other than "2.1 update-1"
2. Phones which do not have the most current baseband file.
3. Some other unidentified reason.


In order to fix the problem (if it even is a problem) you have to dowload this file otafix.zip (provided by Fabolous) and install using Clockwork Recovery - Turn off phone and turn back on while holding X, select install zip from SD card, find the zip and apply.

You don't need SPRecovery unless your phone has already downloaded the file and is prompting you to install it.

You were very helpful nStallion, Mods should maybe consider this post as a temporary sticky since i'm sure more will come and ask for the solution to this problem, or at least until rom devs institute the fix. But this was a very helpful post Thank you.

 

[Psychokitty]

Thanks everyone, this seems to have fixed my problem.