Horrible battery life after 2.3.6

Search This thread

fiffan86

Senior Member
Dec 2, 2010
734
201
Las Vegas, NV
a moderator should close the thread to kill this zombie thread!!!!!!!!!!!! My conspiracy theory is that it is members of the umbrella corp is keeping this zombie thread alive
 

gastonw

Senior Member
Dec 19, 2012
5,266
1,758
I'ma add a little Q to this bumpef thead that everyone is whinning about.

Those who recently updated to stock jb are having media scanner issues?

Done, i'm off to the jb threads now.

Sent from the little guy
 

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://xdaforums.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.