• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Horrible battery life after 2.3.6

Search This thread

Tymong

New member
Dec 24, 2011
1
0
Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.

Batter Usage shows the Android OS at 93%!!!

Not using my phone, it is dead in about 7 hours.

Kernel Version
2.6.35.7

Build Number
GINGERBREAD.UCKK6

I am not rooted and dont want to root.

HELP!
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,094
25,088
Owego, NY
Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.

Batter Usage shows the Android OS at 93%!!!

Not using my phone, it is dead in about 7 hours.

Kernel Version
2.6.35.7

Build Number
GINGERBREAD.UCKK6

I am not rooted and dont want to root.

HELP!

You have an app that is driving data to your phone, causing the wifi chip to wake the phone all the time. Apparently a system app - a lot of people have been having this issue with KK6.

Beyond this - sorry, but if you are not rooted you will have to live with it. Identifying what is triggering the wifi interrupts requires obtaining a Wireshark capture, this is not possible without root. Even if a common root cause is found for what's going on with KK6, it's most likely in /system itself so can't be fixed without a custom ROM or at least rooting.

If you're not willing to root, why are you on a firmware developer forum? Have AT&T help you instead if you're on 100% bone stock unrooted.
 

chocodough

Senior Member
Aug 28, 2003
427
40
Well if it's an APP causing it, then many many people must be running the same app cause all of the various forums out there are a lot of people with the battery drain after updating to 2.3.6. Even a lot of my customers have mentioned it also.

I doubt it is an APP doing it. I'd bet it is just some bad coding on Samsung's part. They are probably getting a lot of complaints and are most likely already looking into it.

As far as the why he is here if he doesn't root. Well I don't root as well and have no desire to being as stock works just great. (other than the battery drain)

This is a great place to hang out and keep up on other people using various phones. He posted in the General section, not the Developer's section for this phone. So I think his/her question was valid.

If he was asking the question in the Developers section I would understand your concern. But I don't feel you have to be into cooked ROMS to value this forum.

That's like saying to the people who like the "Fast and the Furious" moves to stop watching them because they have a Chevy and not a pimped up Civic. :)
 

envioustitan08

Senior Member
Jun 1, 2011
169
8
Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.

Batter Usage shows the Android OS at 93%!!!

Not using my phone, it is dead in about 7 hours.

Kernel Version
2.6.35.7

Build Number
GINGERBREAD.UCKK6

I am not rooted and dont want to root.

HELP!

I'm not rooted with wifi on all the time just got the phone 3 days ago and I'm getting 14-15hrs with no issue down to about 15-20% battery life left before I have to stick back on charger. Could be a bad battery or device, I'm coming over from Sprint after using rooted evo3d and rooted photon.

Sent from my SAMSUNG-SGH-I777 using xda premium
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,094
25,088
Owego, NY
The forum is called xda-DEVELOPERS.com

If you don't want to root, you're probably better off in the AT&T support forums, because honestly, it isn't worth our time to try and help someone who doesn't want to root fix a problem that is almost sure to require root access to fix, or in this case, even diagnose.
 
  • Like
Reactions: rankz787 and PdtS

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,094
25,088
Owego, NY
May be a system app, or something in /system causing an app to become unhappy.

Either way, it's not going to get fixed without Shark for Root captures from those encountering problems.

Sent from my GT-P7510 using Tapatalk
 

NascarFastcar

Senior Member
Dec 17, 2010
137
5
Having this issue as well. Phone is stock. Ive been here since the captivate but I hang around with the sgs2. Never needed to root this phone as it works perfectly for me. But I did the update this morning at 100% charge and 9 hours later with no use it's down to 9%. I could go all day with moderate use and be at 30-40% by the time I go to bed.
 

browncarpet

Member
Mar 23, 2011
21
2
I read on a rather long on a google forum that many had this issue after upgrading via ota but who knows. I found that wiping dalvik and flashing unnamed update again I have much better batter life. I did read in update that he reverted to an earlier kernel signature to fix the battery drain.
 

NascarFastcar

Senior Member
Dec 17, 2010
137
5
Im going back to 2.3.4 via this method.
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/

Losing 10% of my battery at idle /hour is ridiculous lol. Android os was at 87+% within 3 hours of restart.

Edit:
Okay so I did this method. Took about 5 mins after I got everything downloaded. I did not do the factory reset since it's not needed. Phones back to 2.3.4 and nothing was reset. Have all my sms's contacts, aps, wallpapers etc. Battery seems to be back to normal.
I recommend everyone who did that 2.3.6 update to revert back. To many problems with it.

I never entered download mode on this phone before. Just a tip: Keep holding all the buttons till the phone seems like it shuts off and keep holding them till you get into download mode. Do not let go or else it just powers off.
 
Last edited:

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,094
25,088
Owego, NY
For the purposes of attempting to fix the problem, I really would like some people to take some Shark for Root captures as described in my Known Battery Drainers thread.

With that data, the root cause of the problem might be identifiable.

So far I've only seen one capture, I really need more unless I can reproduce the problem myself.
 

n7slc

Senior Member
Jul 21, 2010
321
31
Salt Lake City
For the purposes of attempting to fix the problem, I really would like some people to take some Shark for Root captures as described in my Known Battery Drainers thread.

With that data, the root cause of the problem might be identifiable.

So far I've only seen one capture, I really need more unless I can reproduce the problem myself.

I'm also having battery issues but would like to try to fix it before giving up.

I've searched a bunch but can't find that thread. Not at home to try it on my PC so if you'll link it here, I'll do what I can to get some captures for you.

Sent from my SAMSUNG-SGH-I777 using Tapatalk
 

radeon962

Senior Member
Dec 15, 2011
252
44
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.

Worth a shot as it does not require anything more than charging your phone and pulling the battery.

Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.

That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.

Screen grab of my current battery use after trying this method this morning is attached.
 

Attachments

  • SC20111226-214122.jpg
    SC20111226-214122.jpg
    31 KB · Views: 1,009
Last edited:
  • Like
Reactions: Twisted Z

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,094
25,088
Owego, NY
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.

Worth a shot as it does not require anything more than charging your phone and pulling the battery.

Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.

That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.

Screen grab of my current battery use after trying this method this morning is attached.
Placebo effect - did nothing a plain old reboot would not have done.
 

radeon962

Senior Member
Dec 15, 2011
252
44
Placebo effect - did nothing a plain old reboot would not have done.


Quite possible, but still running on the same charge from this morning and am at 28% battery after 14+ hours of normal use which is all I expect (calls, texts and light web browsing during the day over data) and then couple hours of web use at night over Wi-Fi when at home.

The last few days I was charging the phone when I got home from the office if I wanted to use it at night. Android OS was way up in the 60+ range after I first updated OTA and today it has been under 20% and more near 15%, so I'll take it.

---------- Post added at 11:09 PM ---------- Previous post was at 10:59 PM ----------

Come to think, I probably did not do a reboot after the update and could have been all that was needed.
 

Demodave

Senior Member
Nov 7, 2011
56
21
Las Vegas
demodavepro.com
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.

Worth a shot as it does not require anything more than charging your phone and pulling the battery.

Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.

That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.

Screen grab of my current battery use after trying this method this morning is attached.

I did this and saw absolutely no change. 2.3.6 is draining my battery far faster than 2.3.4 ever did. The culprit is the Android OS running at 90%.

I read that it might be an issue with the wifi so I have turned that off and will report back if that seems to fix it.
 

chocodough

Senior Member
Aug 28, 2003
427
40
I read on another forum that att and Samsung are trying to blame it on bad batteries and shipping out new batteries.

What a bunch of crap. People everywhere wouldn't suddenly all have bad batteries at the same time. Sounds like usual BS.

I personally think its just some bad coding that Samsung needs to figure out.

On a different note, I played with the Verizon Droid Razr yesterday. Man that is a really nice phone. I'm tempted to get it, but I work for att and get free cell service, so it wouldn't make sense to pay for Verizon service, even though I think their network is better.


Sent from my SAMSUNG-SGH-I777 using XDA App
 

Patsfan123

Senior Member
May 23, 2010
145
28
Quincy, MA
I read on another forum that att and Samsung are trying to blame it on bad batteries and shipping out new batteries.

What a bunch of crap. People everywhere wouldn't suddenly all have bad batteries at the same time. Sounds like usual BS.

I personally think its just some bad coding that Samsung needs to figure out.

On a different note, I played with the Verizon Droid Razr yesterday. Man that is a really nice phone. I'm tempted to get it, but I work for att and get free cell service, so it wouldn't make sense to pay for Verizon service, even though I think their network is better.


Sent from my SAMSUNG-SGH-I777 using XDA App


Android OS is definately eating up the battery now. I think it does have to do with wifi, because it seems to be much improved with it off. I'll take a free battery as long as I don't need to exchange the old one.
 
  • Like
Reactions: selw0nk

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Well if it's an APP causing it, then many many people must be running the same app cause all of the various forums out there are a lot of people with the battery drain after updating to 2.3.6. Even a lot of my customers have mentioned it also.

    I doubt it is an APP doing it. I'd bet it is just some bad coding on Samsung's part. They are probably getting a lot of complaints and are most likely already looking into it.

    As far as the why he is here if he doesn't root. Well I don't root as well and have no desire to being as stock works just great. (other than the battery drain)

    This is a great place to hang out and keep up on other people using various phones. He posted in the General section, not the Developer's section for this phone. So I think his/her question was valid.

    If he was asking the question in the Developers section I would understand your concern. But I don't feel you have to be into cooked ROMS to value this forum.

    That's like saying to the people who like the "Fast and the Furious" moves to stop watching them because they have a Chevy and not a pimped up Civic. :)
    3
    Just an update about my last thread, I'm currently at 6 hours off battery so far, battery still at 91%, so that's about 1.5% drain per hour. I have used it a tiny bit also, and yes WiFi and the cell radio have been on the whole time. Right now Android OS is sitting at 46% battery life which is reasonable on the current usage, I know that it's not running away with my battery anymore because Android System is right behind it at 24% and then Cell standby at 12% after that. CPU spy timers are 15 min in 200MHz, 5 hours 39 min in deep sleep, and that's out of 6:09:21 total.

    If somebody would like me to post the screencap I have of it, just let me know, otherwise I'm going to just be lazy and not upload it.


    The reason I am posting all of this info is for the other people out there lurking (I know there are some) who are trying to decide whether or not to make the jump into rooting for the sake of getting their battery life back. It seems scary if you've never done it before, but now that I have, I'm not sure why it ever was. Anyway, very simple steps here.

    1. Go to this thread: here.

    2. If you're on 2.3.6 (which I'm assuming you are if you received the OTA update that murdered batt. life) Use method 2c (titled: 2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader)

    Before doing step 3 I advise that you download Titanium Backup, go into the Backup/restore tab, hit menu button on your phone, click Batch, and select Backup all user apps + system data.


    Note: You will have to redo all your widgets and such manually using this method. So I'd suggest taking a few screen shots of what each of your homescreens look like.

    3. After you are rooted (all steps on how to use that method are included in that thread) you will most likely not be able to activate your WiFi. Simple solution, go to Settings>Privacy>Factory data reset. You do ****NOT**** need to format USB storage for this to work. So leave that checkbox UNchecked.

    4. Boot your phone up and do all the intro steps to get back to your freshly wiped device. Confirm that your WiFi is working. Is it working? Yes? Good. Now go back into the market and redownload Titanium Backup.

    !!!!!!!!!!!Do NOT do a full batch restore with TiBu as it will rebreak your WiFi!!!!!!!!!!!


    5. Go to the Backup/restore tab in TiBu, go find all the apps that you actually want back, and click "Restore" and it will ask you if you want to restore the app, the data, or both. Do this until you have all your apps back.

    Hopefully this will give a few of you that are still on the fence the courage to join the wonderful world of rooting. My next step will be finding out more info on the topic of Kernels and ROMs.
    2
    The forum is called xda-DEVELOPERS.com

    If you don't want to root, you're probably better off in the AT&T support forums, because honestly, it isn't worth our time to try and help someone who doesn't want to root fix a problem that is almost sure to require root access to fix, or in this case, even diagnose.
    2
    Yovee got me two good caps that seem to have the smoking gun.

    As to how to FIX it, I'm not sure.

    But I do have to say: ****ING BROADCOM.

    It's the exact same issue the Infuse community has had for a while:
    http://forum.xda-developers.com/showthread.php?t=1408433

    Confirmation from other people would be useful (there may be multiple sources, such as one person seemed to be getting drain due to Windows Client Backup broadcasts) - but if you see stuff like this in your Wireshark captures:
    Code:
          1 0.000000    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
          2 1.230671    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
          3 2.457567    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
          4 3.688167    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
          5 4.915498    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
          8 6.145554    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         10 7.374758    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         11 8.603045    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         12 9.832158    9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         15 11.061042   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         16 12.289468   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         19 13.518508   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         20 14.746922   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         22 15.976068   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         25 17.204985   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         26 18.433658   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         27 19.662156   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         28 20.890973   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         29 22.120120   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         30 23.144282   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         31 24.168026   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         32 25.396524   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         33 26.625761   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         35 27.854481   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         36 29.083182   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         37 30.310235   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         38 32.367309   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         39 32.747929   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
         40 34.402309   9a:0c:82:63:72:56     SamsungE_63:72:56     0x886c   74     Ethernet II
    It's Broadcom's BT-AMP function flaking out. This is some wacky proprietary Bluetooth-over-wifi **** that apparently never does anything except kill battery. (I've never seen this function actually be USEFUL.)
    2
    Is this affecting everyone that has updated to 2.3.6 or is it only a small percentage? Should I wait until this is fixed before updating?

    I'm still new to android so not sure if this is just an issue every time there is an update, a small percentage of users will experience problems or if it's this particular update. Just trying to decide if I should take my chances and go ahead and update.

    Right now, my suspicion (but I need more data to confirm) is that a few IPv6 multicast addresses got added to the wifi chip's MAC filter in UCKK6. So IPv6 multicast data (like Windows Client Backup traffic) will cause the wifi chip to fire lots of wakeup interrupts. The problem is that out of 10-20 complaints about wifi battery life in KK6, only two people have provided the requested Wireshark captures to narrow down the problem so far.

    A lot of people are doing fine with KK6, but the general known problems are:
    1) Bluetooth HID (keyboards/mice) is 100% broken
    2) Lots of wifi compatibility problems - if you have a Belkin router, don't update. Actually, a better solution is to throw the router in the trash. Belkin sucks.
    3) This wifi battery drain issue - doesn't affect too many people, but it clearly affects people not affected on UCKH7.