Haven't had a time to read that stuff yet (will do so this afternoon) but interestingly, I turned on the WiFi at home last night and the battery was fine. Dropped ~2% per hour with ocassional use, as opposed to the ~10% per hour with no use at all I was getting at work. I'm now at work with the WiFi off and it's only dropped 3% in 4 hours with negligible use (2 texts).
Maybe it's some weird compatibility issue with the WiFi I connect to at work? In fact, I'm sure I still get the drain with the WiFi on at work but not actually connecting to any access point...
Maybe it's some weird compatibility issue with the WiFi I connect to at work? In fact, I'm sure I still get the drain with the WiFi on at work but not actually connecting to any access point...
Drain without connection sounds weird, unless you are getting hit with the BT-AMP bug which is mentioned throughout this thread.
Drain with connection - Some networks are "dirty" with lots of various broadcast traffic (a work network would very likely be in this category). You'll see a few reports in this thread (and I now have it as an item in "known battery drainers" of misbehaving routers that send out ARP spam for example - There's a small bug in XXKI3 (and probably in XWKI4) that disables the wifi chip's packet filters that SHOULD be enabled when the screen is off. As a result, even though it's not prone to the BT-AMP bug, XXKI3 is prone to drain on a "dirty" network.
Drain with connection - Some networks are "dirty" with lots of various broadcast traffic (a work network would very likely be in this category). You'll see a few reports in this thread (and I now have it as an item in "known battery drainers" of misbehaving routers that send out ARP spam for example - There's a small bug in XXKI3 (and probably in XWKI4) that disables the wifi chip's packet filters that SHOULD be enabled when the screen is off. As a result, even though it's not prone to the BT-AMP bug, XXKI3 is prone to drain on a "dirty" network.
I have been going crazy with this battery life problem. I started with stock 2.3.4 and everything was great. Then AT&T upgraded me to 2.3.6 and things were really bad. Android OS showed upwards to 80% consumption and I was getting over 6% per hour idle consumption. And my saga began:
- I downgraded to 2.3.4 and I thought everything was great, but no, it was not. Somehow it started going south again.
- So I went with SHOStock 1.9.1 and 1.9.2 and same thing
- I read all of (well, most of) Entropy's writings and ran wiresharks, BBS, CPUSpy etc and nothing really looked that off
- I went to UnNamed 1.3.2/DD 1208 as everybody said that was the one. Nope
- Went with the Hellraised European ROMs (several). Nope
- Tried about every Kernel out there. Nope
- Went back to try all those ROMs without any apps added to ensure it wasn't one of my apps. Nope, they were all horrible battery life still.
Finally I decided that the only thing that was constant in my phone was the HW. So most likley there was something physically wrong with my phone. Before going to the store to return it, I decided to Format my SDCARD. So I did and guess what... <1% drain per hour. I added all my apps from TiBu and still <1% per hour today. It has only been a few hours and last time when I reverted to 2.3.4 it worked for a while and then went back to bad, so I cannot claim that this is a fix. However, formatting my SDCARD storage definitely made a difference.
I am sharing to see if somebody can make any comments on if it makes sense. I will post again in a couple of days to let you know if the good battery life has continued or the drained returned.
- I downgraded to 2.3.4 and I thought everything was great, but no, it was not. Somehow it started going south again.
- So I went with SHOStock 1.9.1 and 1.9.2 and same thing
- I read all of (well, most of) Entropy's writings and ran wiresharks, BBS, CPUSpy etc and nothing really looked that off
- I went to UnNamed 1.3.2/DD 1208 as everybody said that was the one. Nope
- Went with the Hellraised European ROMs (several). Nope
- Tried about every Kernel out there. Nope
- Went back to try all those ROMs without any apps added to ensure it wasn't one of my apps. Nope, they were all horrible battery life still.
Finally I decided that the only thing that was constant in my phone was the HW. So most likley there was something physically wrong with my phone. Before going to the store to return it, I decided to Format my SDCARD. So I did and guess what... <1% drain per hour. I added all my apps from TiBu and still <1% per hour today. It has only been a few hours and last time when I reverted to 2.3.4 it worked for a while and then went back to bad, so I cannot claim that this is a fix. However, formatting my SDCARD storage definitely made a difference.
I am sharing to see if somebody can make any comments on if it makes sense. I will post again in a couple of days to let you know if the good battery life has continued or the drained returned.
Corrupt SD cards can cause mediascanner to go nuts - usually there's evidence of this in BBS and such though. (I'm not sure as it's never happened to me.)
They have - AT&T is just not releasing the fix. XWKL1 has no BT-AMP bug and the wifi packet filters work correctly, it seems like XWLA4 is also working properly.
Any idea why they aren't releasing it? I'm getting very frustrated with this and haven't worked up the nerve to root since I'm still on warranty. Right now I'm in the process of doing a discharge of my battery relevant to this thread.... I have a screenshot that of my battery draining overnight. 9h 17m 10s on battery. Down low enough for bar to be under 20%. Usage list: Android OS 98%, nothing else on the list.
sec-battery-monitor
I keep looking at this problem and have noticed that my top three wakelocks are SVNET, WLAN_RX_WAKE, and sec-battery-monitor.
So the first two tell me, from what I have read here, that I have an app that is asking for data quite a bit. I am freezing things trying to figure out which one is my rogue app. I am currently on UnNamed 1.3.2 (XXKH7).
The one I am puzzled about and have spent a bit of time researching is the sec-battery-monitor. From what I read that is the Android built in battery monitor. Why in the world would that thing have that high of a wakelock count? Is that a bug? I have tried several ROMs at KH7 and KK6 and both bases show the sec-battery-monitor high wakelock. Maybe when I fix my data problem this one will go away, but after reading for hours trying to see if anybody knows why this wakelock is there, I have not read a root cause explanation that makes sense (most people conclude an OS bug).
I keep looking at this problem and have noticed that my top three wakelocks are SVNET, WLAN_RX_WAKE, and sec-battery-monitor.
So the first two tell me, from what I have read here, that I have an app that is asking for data quite a bit. I am freezing things trying to figure out which one is my rogue app. I am currently on UnNamed 1.3.2 (XXKH7).
The one I am puzzled about and have spent a bit of time researching is the sec-battery-monitor. From what I read that is the Android built in battery monitor. Why in the world would that thing have that high of a wakelock count? Is that a bug? I have tried several ROMs at KH7 and KK6 and both bases show the sec-battery-monitor high wakelock. Maybe when I fix my data problem this one will go away, but after reading for hours trying to see if anybody knows why this wakelock is there, I have not read a root cause explanation that makes sense (most people conclude an OS bug).
Ok, so like I said I was doing some discharging and such relevant to this thread, I didn't get any diag. stats for your Entropy but I just wanted to show this is it's most exaggerated and plain to see form. There are 3 pics here...
Pic 1, this was an overnight drain with the phone not being touched *AT ALL* Not even to check the time.
Pic 2, this was a drain using the fabled "pull out your battery because it's magic!" method.
Pic 3, this pic is showing the DRASTIC difference in battery life since using Entropy's root method (2c in creepycrawly's sticky) this is showing the battery after I had just done a data wipe (to fix WiFi problem after root) and yes the battery drained from ~50% to ~20% in just over an hour and a half, but the screen was on 97% of that time, and I was downloading/resetting all my apps and widgets and such. Also, since I'm now rooted, I have the thrill of using TiBu to freeze TetheringManager and DRM Content.
Take note of how Android OS is at 4% battery life as opposed to 70-95%.
Edit: I was also playing music the entire time I was restoring app settings and redownloading/installing them.
I am charging my phone right now and going to do a normal discharge of it to see change in battery life just to be 100% sure that it's back to normal (I'm currently 99% sure because when I stopped using the phone, I reset the clocks on CPUSpy and checked back after about 45minutes, the 200MHz bar was very small, Deep Sleep was almost full).
I will throw that pic up on this post after I have the results.
Pic 1, this was an overnight drain with the phone not being touched *AT ALL* Not even to check the time.
Pic 2, this was a drain using the fabled "pull out your battery because it's magic!" method.
Pic 3, this pic is showing the DRASTIC difference in battery life since using Entropy's root method (2c in creepycrawly's sticky) this is showing the battery after I had just done a data wipe (to fix WiFi problem after root) and yes the battery drained from ~50% to ~20% in just over an hour and a half, but the screen was on 97% of that time, and I was downloading/resetting all my apps and widgets and such. Also, since I'm now rooted, I have the thrill of using TiBu to freeze TetheringManager and DRM Content.
Take note of how Android OS is at 4% battery life as opposed to 70-95%.
Edit: I was also playing music the entire time I was restoring app settings and redownloading/installing them.
I am charging my phone right now and going to do a normal discharge of it to see change in battery life just to be 100% sure that it's back to normal (I'm currently 99% sure because when I stopped using the phone, I reset the clocks on CPUSpy and checked back after about 45minutes, the 200MHz bar was very small, Deep Sleep was almost full).
I will throw that pic up on this post after I have the results.
Last edited:
It polls periodically doing work - it seems to sometimes wake the device but not always (considering the polling interval is 10 seconds), but will usually go and do its thing if something else wakes up the device. I've never seen it consider an unreasonable amount of time either.
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.
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.
I dont think you need to install either after rooting.
Last edited:
SuperUser is automatically installed when you root using most methods, if not all. This method automatically installs it.
Update. Currently at 18h 8m 49s on battery. 68% battery remaining. Exactly how my phone SHOULD be when I'm not using it.
Update 2. Got to 1d 3h 51m and had 14% battery life left, I actually played some games and such, had around 2.5-3 hours of screen on time. I just plugged it in because I don't feel like having a near-dead battery all day tomorrow :lol:
Update 3. (For those wondering, I'm updating the same post over and over to avoid bumping this and making it appear on people's list again... It is mostly for people looking for info who come upon this thread after the fact).
Well it's been about 2-3 days since I rooted, charging my battery is basically optional every night. I'm consistently getting well over 20 hours with my normal usage. For me normal use would be maybe 10-30 minutes of browsing via Dolphin browser, maybe 100-150 texts using Handcent, 200-500 texts via Heywire, maybe 10-30 minutes of games, a couple hours of listening to music with PowerAmp, 2 email accounts, 1 updating every hour, the other updating every 4 hours. A weather widget that updates every hour, WiFi always on, even when not in use. Facebook notifications refresh interval 1 hour. Screen on auto-adjust brightness with 30 second screen timeout.
If there are any other new users out there or anybody else that would like to ask me a question or point something out to me, I will gladly give/take any advice available.
Last edited:
I have read this whole thread. Phew. I had an I777 that I put CM7 on. Went all the way to nightly 22 or something. I think at this point, I was trying different modems from this thread. I moved up to UKK6. Then I got tired of the volume adjustment issues and wanted to try the Car Dock and Home Dock and MHL adapters. So I had to move off of CM7. I moved to UnNamed 2.2.1. I flashed that back in December or something, without ever changing the baseband. I have had pretty awful battery for months and never really cared to find out why. In my opinion, this stuff should just work. Now, I'm starting to change my tune. I need to make it work. Anyway, my question is, Entropy keeps talking about XWKL1 baseband. Is that only available on the I9100 (which would make it useless for I777 correct?)?
I never said anything about XWKL1 baseband... I9100 basebands will never work on I777. I777 system firmware bases will with porting efforts.
Baseband is the modem to handle cellular traffic. I think that most everybody will tell you that this is not what is causing significant battery issues.
What Entropy is talking about is the Gingerbread base. i9100 phones have the base for the ROM XWKL1 (among others). Using the Hellraised process allows us to use these ROMs on i777 phones. You might want to try UnNamed 1.3.2 first or just make sure you try a XWKL1 based ROM that has been Hellraised.
That is my fault. I didn't realize you were referring to the ROM only and not the modem firmware.
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.
