Thanks, I'll check it out!See my "known battery drainers" thread in this forum section - Skip straight to the Wireshark section of the first post.
Thanks, I'll check it out!See my "known battery drainers" thread in this forum section - Skip straight to the Wireshark section of the first post.
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.)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 am more than a little irritated that Samsung has not fixed this issue yet.
Samsung if you are listening: "If you want to be like Apple then you need to be like Apple." Admit the issue and fix it!
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.
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).
Do you have to install superuser &/or busybox after rooting with that method?
Do you have to install superuser &/or busybox after rooting with that method?
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.
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
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.