This is AT&T we're talking about.
Samsung has fixed it already - a few of their I9100 releases had issues with broadcast/ARP filtering, at least one (XWKK5) had the BT-AMP bug - but they fixed it fast. XWKL1 seems rock solid.
AT&T, however, insists on taking Samsung releases and mangling them to an epic degree, then delaying them forever.
And, if you haven't, consider JuiceDefender for its automated data regulation. It has helped so much with my battery in all my low signal areas where data usage sapped my battery levels!
I was wrong about XWKL1 and BT-AMP - XWKL1 suffers from the BT-AMP bug too.
There's a possibility I triggered this by mucking with power management settings for the wifi chip in my latest test kernel, so I'm sticking with XWKL1 for another week or so.
Edit: After two weeks I haven't seen it again. I'm chalking this one up to messing with stuff I shouldn't have in the kernel. XWKL1 seems to be (at least mostly) immune to the BT-AMP bug.
There's a possibility I triggered this by mucking with power management settings for the wifi chip in my latest test kernel, so I'm sticking with XWKL1 for another week or so.
Edit: After two weeks I haven't seen it again. I'm chalking this one up to messing with stuff I shouldn't have in the kernel. XWKL1 seems to be (at least mostly) immune to the BT-AMP bug.
Last edited:
I'm amazed there are still battery issues is 2.3.6. Samsung UK haven't got any further than 2.3.4 yet and since that update, my phone's battery life has been terrible. Never lasts more than a day, even with minimal usage. Android OS is always taking up 75-80% battery.
No idea what to do...was thinking about rooting the phone just so I had the latest clean version but if 2.3.6 has the same issue, what's the point?
No idea what to do...was thinking about rooting the phone just so I had the latest clean version but if 2.3.6 has the same issue, what's the point?
*sigh* Battery life has been so weird and inconsistent ever since 2.3.6.
Had my battery last for 2 days 3 hours and 26 minutes and it went down to 3 percent before I was able to get back and plug the phone into the charger.
Charged up 100% and then unplugged and left sitting for 7 hours while I was asleep.
Woke up this morning and the phone had dropped from 100% to 54%...6.5%/hr battery drainage on standby...
Checked CPU Spy and it NEVER went into deep sleep...88% at 200Mhz...something was keeping my phone awake.
Checked BBS and saw from Kernel Wakelock - Unplugged that my phone was being kept awake by 'wlan_rx_wake' <-- WiFi drain bug
I'm not at home so it's NOT my crappy uVerse router. (Out of town on business so I'm using the hotel's free wifi service.)
Like I said in other posts, this is an intermittent bug as it seems to come and go -- doesn't seem to matter what ROM and as Entropy's stated it seems to affect various GB modems. *sigh*
@Entropy, hopefully your genius can figure out the fix for this soon.
Had my battery last for 2 days 3 hours and 26 minutes and it went down to 3 percent before I was able to get back and plug the phone into the charger.
Charged up 100% and then unplugged and left sitting for 7 hours while I was asleep.
Woke up this morning and the phone had dropped from 100% to 54%...6.5%/hr battery drainage on standby...
Checked CPU Spy and it NEVER went into deep sleep...88% at 200Mhz...something was keeping my phone awake.
Checked BBS and saw from Kernel Wakelock - Unplugged that my phone was being kept awake by 'wlan_rx_wake' <-- WiFi drain bug
I'm not at home so it's NOT my crappy uVerse router. (Out of town on business so I'm using the hotel's free wifi service.)
Like I said in other posts, this is an intermittent bug as it seems to come and go -- doesn't seem to matter what ROM and as Entropy's stated it seems to affect various GB modems. *sigh*
@Entropy, hopefully your genius can figure out the fix for this soon.
Please PLEASE PLEASE refer to specific Samsung builds, not by base Android version! 2.3.4 vs. 2.3.6 doesn't mean jack **** - what's useful is specific build.
UCKH7 works great in terms of the problems described here, XXKI3 is pretty good but has minor flaws (esp. on "dirty" networks), UCKK6 (the subject of this thread) is a steaming pile of ****, XWKK5 seems to have some issues but not as bad as UCKK6, XWKL1 seems to be pretty good the majority of the time. (I've seen the BT-AMP bug on it once, but I think it was due to mucking around with stuff I shouldn't have been in the kernel wifi driver.)
Edit: Also, there are 219378971 different causes of high AOS - some are broken apps, some are wifi network problems and the ROM can affect how prone you are to those, only one is documented to be a firmware-specific issue with no known external contributors.
Last edited:
Hello Entropy,
I have an odd one for you. I did the update to 2.3.6 on my stock unrooted phone. My battery life immediately went in the ****ter. I tried to live with it for a couple weeks; but having my phone die 13 hours after it was taken off the charger was driving me crazy.
I followed the instructions to go back to 2.3.4. Battery life has been back to normal ever since. My Android version is 2.3.4. My Baseband version is I777UCKK6. Kernel version is 2.6.35.7. Build number is GINGERBREAD.UCKH7.
So is that correct? The Baseband version is UCKK6, not UCKH7. But the build number shows UCKH7.
So which modem am I running? I'm a bit of a noob with this stuff; but I am a tech head that loves to tinker and would love a little clarification.
Thanks!!
I have an odd one for you. I did the update to 2.3.6 on my stock unrooted phone. My battery life immediately went in the ****ter. I tried to live with it for a couple weeks; but having my phone die 13 hours after it was taken off the charger was driving me crazy.
I followed the instructions to go back to 2.3.4. Battery life has been back to normal ever since. My Android version is 2.3.4. My Baseband version is I777UCKK6. Kernel version is 2.6.35.7. Build number is GINGERBREAD.UCKH7.
So is that correct? The Baseband version is UCKK6, not UCKH7. But the build number shows UCKH7.
So which modem am I running? I'm a bit of a noob with this stuff; but I am a tech head that loves to tinker and would love a little clarification.
Thanks!!
G
garbagecanman
Guest
My girlfriends sgs2 is on 2.3.4 UCKH7 and s only getting like 2.5 hours screen on and 13 hours total bat life? Is that the norm or do I need to customize this bad boi? Stock kernal as well. She does have words with friends and told her that's prob eating it up...
Sent from my A500 ICS dream machine
Sent from my A500 ICS dream machine
I have seen people reporting much higher screen on time and battery performance with different ROM/Kernels and init.d scripts. I usually get 2-2.5 hours screen on time over say 24-30 hours period.
G
garbagecanman
Guest
If you read my post, I include the modem separately. If you want to do a warranty return - you want to revert the modem. If you want the best possible performance/battery life - Experiment. The UCKK6 system image sucks, but UCKK6 modem (baseband) isn't that bad and I think most people feel it's better. In fact, you reminded me I need to reflash the KK6 modem.
Words With Friends is on my "****list" of known battery drainers in my other thread on battery drainers.
I admit - I rarely have screen-on that high, but your life does seem a bit low. WWF is a notorious battery hog.
Well looks like I spoke too soon. I thought i was in the clear with not having any wakelock issues for the last 7 days or so. Then today and yesterday its cropping up again, same BT Amp issue.
PCAP here if interested:
http://dl.dropbox.com/u/7606677/shark_dump_1328668841.pcap
EDIT: WOw it's never been so bad. I've gone from 100 -> 15% in 7.5 hours! 6.45 hours were spent awake and screen was only on for 1 hour!
Last edited:
My kernel version is apparently XWKI4. According to the first few Google results, this is meant to be a good ROM in terms of battery life. :/
If there are so many causes of the problem, how can anyone ever fix it?
Is there no way of seeing exactly what apps are using all the battery rather than just "Android OS"? Ive tried Watchdog Lite but it only ever brings up "sleep/0" and "suspend", usually about 10 minutes after I turn the screen off.
Lost 11% in 1h25m so far this morning whilst it's been sitting on my desk doing nothing.
Last edited:
I've tested all modems on my GS2 and love uckk6. It's far faster for me them the rest.
Hmm, I turned off my WiFi and now I'm only losing 1% per hour! I don't get it because if an application constantly accessing the internet is the problem, surely it'd do it over both WiFi and 3G?Is there no way of seeing exactly what apps are using all the battery rather than just "Android OS"? Ive tried Watchdog Lite but it only ever brings up "sleep/0" and "suspend", usually about 10 minutes after I turn the screen off.
Lost 11% in 1h25m so far this morning whilst it's been sitting on my desk doing nothing.
See my "known battery drainers" thread in this forum section - Skip straight to the Wireshark section of the first post.My kernel version is apparently XWKI4. According to the first few Google results, this is meant to be a good ROM in terms of battery life. :/
If there are so many causes of the problem, how can anyone ever fix it?
Is there no way of seeing exactly what apps are using all the battery rather than just "Android OS"? Ive tried Watchdog Lite but it only ever brings up "sleep/0" and "suspend", usually about 10 minutes after I turn the screen off.
Lost 11% in 1h25m so far this morning whilst it's been sitting on my desk doing nothing.
Right now, my guess for XWKI4 is the same possible cause as XXKI3 - "dirty network" combined with a small bug with XXKI3 (haven't used XWKI4). A Shark for Root/Wireshark capture will confirm it.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3Well 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.3Just 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.2The 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.2Yovee 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.)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 II2
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.
