Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.
Batter Usage shows the Android OS at 93%!!!
Not using my phone, it is dead in about 7 hours.
Kernel Version
2.6.35.7
Build Number
GINGERBREAD.UCKK6
I am not rooted and dont want to root.
HELP!
Ok, I installed 2.3.6 from AT&T and my bettery life has tanked.
Batter Usage shows the Android OS at 93%!!!
Not using my phone, it is dead in about 7 hours.
Kernel Version
2.6.35.7
Build Number
GINGERBREAD.UCKK6
I am not rooted and dont want to root.
HELP!
I do believe many are having this issue after upgrading to kk6 (with same apps installed). I had the issue as well.
For the purposes of attempting to fix the problem, I really would like some people to take some Shark for Root captures as described in my Known Battery Drainers thread.
With that data, the root cause of the problem might be identifiable.
So far I've only seen one capture, I really need more unless I can reproduce the problem myself.
I've searched a bunch but can't find that thread. Not at home to try it on my PC so if you'll link it here, I'll do what I can to get some captures for you.
Placebo effect - did nothing a plain old reboot would not have done.I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.
Worth a shot as it does not require anything more than charging your phone and pulling the battery.
Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.
That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.
Screen grab of my current battery use after trying this method this morning is attached.
Placebo effect - did nothing a plain old reboot would not have done.
I read a possible solution on another forum and tried it with my SGS2 today and am amazed at the difference today in my battery life.
Worth a shot as it does not require anything more than charging your phone and pulling the battery.
Charge your phone to 100% with the phone off (hold the power button for 3 seconds or so until the menu comes up and select power off). When you reach 100%, unplug the charger and remove your battery (some said keep the battery removed for 90 seconds while others said 3-5 minutes). I left my battery out for 5 minutes or so. Put the battery back in and power on.
That was it. My Android OS went back to normal and the battery life today has been great if not better then with 2.3.6 than before I updated.
Screen grab of my current battery use after trying this method this morning is attached.
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
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.