Actually another thing I noticed since updating to 2.3.6 is that my phone gets warm now when I'm using it.

I guess whatever is causing the battery drain is to blame.


Sent from my SAMSUNG-SGH-I777 using XDA App

After barely using my phone today, my battery is at 70% and was unplugged from 100% at 8am this morning. I see that my Android OS usage is at 70% too. The display is at 10%. I'm hoping this goes down or we see another update soon.

I think looking at the WiFi as a possible cause is definately valid.

I started the day off at 7:30am with 100% battery, and with light use which is normal on a work day, and now it is 9:30 and I am at 60%. That is without turning on WiFi at all today.

If I had my WiFi on I would bet I would be down to 30% by now.

Before 2.3.6 I was able to go 2 or 3 days in between charges, but with 2.3.6 and using WiFi I have to charge it every day.

Also, I haven't seen Android OS usage above 13% all day with the WiFi off. With WiFi on I did notice the Android OS usage up very high.

Originally Posted by NascarFastcar

Im going back to 2.3.4 via this method.


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

Yea I ended up loading 2.3.4...that was short lived because it refused to turn on wifi or locate any wifi networks. Ended up moving over to 2.3.5 solved the battery problems, can get on wifi, introduced some other minor issues but not dealbreakers (gallery freezes and the task manager shortcut of holding down the home button no longer works). Overall I hope a fix can be found. With running 2.3.5 though I can definitely see that the battery usage of Android OS is now down in the single digits and near the bottom of the usage list

Originally Posted by Entropy512

only two people have provided the requested Wireshark captures to narrow down the problem so far.

after noticing the battery issue when I'm at home (on wifi) but no battery drain while outside my house (on 3g), I'm running wireshark now. I'll post the results as soon as I have them.

update: I ran shark for about 5 minutes and I'm still at 100% so I'm going to drain the battery a bit and try it later when I'm experiencing the wifi battery drain. It appears that the drain doesnt show its ugly head until the battery is below a certain percentage.

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

      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.)

Originally Posted by Entropy512

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

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.)

Glad to see that you were able to make anything out of that... and to pinpoint it down.

So if its not useful, lets rip it out.

Originally Posted by Red5

Glad to see that you were able to make anything out of that... and to pinpoint it down.

So if its not useful, lets rip it out.

Tried that on the Infuse by disabling it in the kernel. People are STILL reporting that the wifi chip is firing interrupts like crazy in some situations.

As I said:

****ING BROADCOM

Thanks again for taking a look at my log files, Entropy. Everyone else, please download "Shark for root" from the market and take log files while you're experiencing rapid battery drain, with the parameters "-vv -s -68". The log files are saved in the root directory of your internal SD card; send the logs to Entropy, or take a look at them yourself with the Shark Reader app.

Entropy, why is this only occurring with some of our phones and not everyone's? Do you suggest going back to 2.3.4?

Would disabling either bluetooth or wifi help the issue?

Originally Posted by Entropy512

Tried that on the Infuse by disabling it in the kernel. People are STILL reporting that the wifi chip is firing interrupts like crazy in some situations.

As I said:

****ING BROADCOM

You've got to be kidding. Disabling it STILL didnt work and it kept freaking out? Uh, ya, so whats the next step?