Horrible battery life after 2.3.6

Search This thread
By:
Advanced…
W

wified

Senior Member
Nov 26, 2007
107
32
Los Angeles, CA
chocodough said:
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.
Click to expand...
Click to collapse

I really liked this phone as stock 2.3.4, but after the OTA to 2.3.6 and the horrible battery life, I wanted to force AT&T to deal with this. So, our two i777's are being replaced under warranty. But I did have to get through the above by convincing them that I already had extra batteries, and that this was not the problem.

I know I could have flashed back to 2.3.4 in 10 minutes, but I want to make AT&T deal with pushing through an update that hoses the battery like they did. I think that they pushed this update out quickly to reduce some of Samsung's liability with the bouncing end-of-scrolling which is now replaced by the blue flash.
 
F

flowbreak

Member
Dec 29, 2011
6
1
radeon962 said:
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.
Click to expand...
Click to collapse

This worked for me too. I was losing 10%/hr after the 2.3.6 update while locked. My battery life is much more like normal with a battery pull. I have a feeling 2.3.4 might still be better, but I just wanna get through the day. I was freaking out before I googled this though. I wiped the phone just to make sure the new update was comfortable. Doubt it did anything!
 
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
chocodough said:
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
Click to expand...
Click to collapse
Which forum?

It is a bunch of crap - it is really starting to appear like a wifi bug.

If you're getting bad battery life while on Wifi with UCKK6, read the first post of my Known Battery Drainers thread - skip straight to the instructions on getting a packet capture with Shark for Root.
 
C

chocodough

Senior Member
Aug 28, 2003
426
38
Entropy512 said:
Which forum?

It is a bunch of crap - it is really starting to appear like a wifi bug.

If you're getting bad battery life while on Wifi with UCKK6, read the first post of my Known Battery Drainers thread - skip straight to the instructions on getting a packet capture with Shark for Root.
Click to expand...
Click to collapse

Here is the thread on the other forum.

http://forums.androidcentral.com/t-galaxy-s-ii/143342-battery-drain-new-update-5.html

I think the battery being an issue is a load of crap personally.

I'm tempted to go back to 2.3.4 and wait it out.


Sent from my SAMSUNG-SGH-I777 using XDA App
 
DDuck4Life

DDuck4Life

Member
Dec 27, 2011
8
2
Lafayette, LA
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.
 
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
DDuck4Life said:
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.
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: gr8hairy1 and DDuck4Life
F

fe2o3y

New member
Nov 27, 2010
1
0
I was also having this battery issue. Roughly the same 10%/hr that everyone else seems to be experiencing, with the Android OS using most of the battery. (what was odd is that I think the phone was a lot better after a usb charge than compared from the outlet-charge?? which I had to use the usb a lot half-way thru my day ever since this update. anyone else notice this? I do have usb debug turned on, if that would make any difference here) Anyway, I had loaded the CPUSpy app, which reported that there was virtually no deep sleep or 200, bulk of the time was in 1200 and 800MHz. Then I saw the shutdown and pull-out-battery suggestion...

So, I did this, left the battery out for a couple of minutes, and then the phone has been fine for the past couple of days. I can go through my day on one charge again. Now CPUSpy is what I expect is more normal, most of the time is in deep sleep and 200, and a little bit of other. If the issue comes back, I am ready to do the wireshark and wakelock file tasks to see what might be going on...
 
Y

Yovee

Member
Nov 13, 2011
32
3
I'm also affected by this issue. Whereas before my phone, while not in use, would take < 1% battery per hour, it now takes 2-7% per hour because the wifi is keeping the phone from sleeping.

Entropy, I'll be sending you a shark log file within a few minutes. Thanks.
 
T

terefere

New member
Dec 19, 2009
1
0
You probably know that it is not only at&t sgsII 2.3.6 issue. :( I have the same problem with sgs (i9000) 2.3.6. On my billing I found out that my phone exchages data via gprs 2 times every second. It is not only battery drain but also internet pack drain. I had to shut apn down.
 
D

Demodave

Senior Member
Nov 7, 2011
56
21
Las Vegas
demodavepro.com
Demodave said:
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.
Click to expand...
Click to collapse

Reporting back...

Now that wifi is turned off, my battery is lasting a bit longer; although not as long as 2.3.4. I suspect that is because all data like email is now using the cell network instead of wifi.

I sure hope we can narrow down the exact cause and fix this issue.
 
C

chocodough

Senior Member
Aug 28, 2003
426
38
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
 
MattMJB0188

MattMJB0188

Senior Member
Apr 30, 2011
1,407
214
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.
 
C

chocodough

Senior Member
Aug 28, 2003
426
38
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.
 
W

werds

Member
Dec 29, 2011
20
0
Millsboro, DE
NascarFastcar said:
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.
Click to expand...
Click to collapse

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 :D
 
nyydynasty

nyydynasty

Senior Member
Sep 15, 2010
1,484
276
Entropy512 said:
only two people have provided the requested Wireshark captures to narrow down the problem so far.
Click to expand...
Click to collapse

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.
 
Last edited:
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
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.)
 
  • Like
Reactions: jasvncnt1 and Yovee
R

Red5

Guest
Entropy512 said:
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:

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.)
Click to expand...
Click to collapse
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. :D
 
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Red5 said:
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. :D
Click to expand...
Click to collapse

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
 
Y

Yovee

Member
Nov 13, 2011
32
3
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?
 
R

Red5

Guest
Entropy512 said:
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
Click to expand...
Click to collapse
You've got to be kidding. Disabling it STILL didnt work and it kept freaking out? Uh, ya, so whats the next step?
 
You must log in or register to reply here.

Similar threads

G
[ROM][2.3.6] UnNamed v2.2.1 - (2/23/2012) - Working download link - Final Release
Replies
5K
Views
754K
bleedingthru
bleedingthru
shoman94
[ROM][2.3.6]UCKK6 "SHOstock" [1.9.4][03/02][SuperHighOutput!] FINAL
Replies
3K
Views
389K
Poke01
Poke01
jivy26
  • Locked
  • Poll
[ROM]ICScrewD ‬‬‬‬‬♦‬♦♦FINAL♦♦♦[JkayMod][2.1]
Replies
4K
Views
439K
R
RatusNatus
E
[REF] Known identified battery drainers
Replies
845
Views
287K
M
mbonell
Pirateghost
[ROM][2.3.6][XLA4] - Binnacle Beta7 - [3-17-12] ||AROMA-Installer|| I Like Turtles |
Replies
1K
Views
123K
C
clay101eve

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    C
    chocodough
    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. :)
    View
    3
    J
    JustinW3
    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.
    View
    2
    E
    Entropy512
    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.
    View
    2
    E
    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://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.)
    View
    2
    E
    Entropy512
    DDuck4Life said:
    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.
    Click to expand...
    Click to collapse

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

New posts