Post Reply

Horrible battery life after 2.3.6

4th February 2012, 07:12 PM   |  #141  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,413
 
13,300 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by torchedlh

I've been on CF Root now for 4 days or so and i havent had any issues with huge wake times. Seems like it's solved my problem. Now just need to find a BLN-enabled kernel that can do the same.

Hmm... Interesting...
5th February 2012, 04:51 AM   |  #142  
Member
Thanks Meter: 3
 
32 posts
Join Date:Joined: Nov 2011
Samsung/AT&T should really get their act together and fix this issue already.
5th February 2012, 06:15 AM   |  #143  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,413
 
13,300 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by Yovee

Samsung/AT&T should really get their act together and fix this issue already.

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.
6th February 2012, 07:16 AM   |  #144  
Member
Thanks Meter: 1
 
54 posts
Join Date:Joined: Jan 2012
More
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!
6th February 2012, 01:41 PM   |  #145  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,413
 
13,300 posts
Join Date:Joined: Aug 2007
Donate to Me
More
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.
Attached Files
File Type: zip btamp_wireshark_1.zip - [Click for QR Code] (2.7 KB, 13 views)
Last edited by Entropy512; 21st February 2012 at 03:11 PM.
The Following 2 Users Say Thank You to Entropy512 For This Useful Post: [ View ]
7th February 2012, 01:36 AM   |  #146  
blaex's Avatar
Senior Member
Flag Berlin
Thanks Meter: 29
 
214 posts
Join Date:Joined: Nov 2009
More
thank you for providing the information about the BT-AMP-bug, looking forward on your insights
7th February 2012, 02:54 PM   |  #147  
Junior Member
Thanks Meter: 2
 
21 posts
Join Date:Joined: Oct 2011
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?
7th February 2012, 03:21 PM   |  #148  
Senior Member
Thanks Meter: 39
 
324 posts
Join Date:Joined: Jun 2009
More
*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.
7th February 2012, 11:45 PM   |  #149  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,413
 
13,300 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by DragonQ

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?

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 by Entropy512; 8th February 2012 at 12:08 AM.
8th February 2012, 01:18 AM   |  #150  
Member
Flag Las Vegas
Thanks Meter: 17
 
43 posts
Join Date:Joined: Nov 2011
More
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!!

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes