Battery drain with new update

[Lawrence of a Labia]

AFAIK, the bootloader isn't locked.

[Entropy512]

Originally Posted by MakaiOokami

How do I unlock the bootloader? I've been searching around the forums. My phone is already rooted since I had to get rid of Tethering Manager 2. I'm not going to pay them money to allow me to burn through my data plan quickly. I pay for 2 GB if I want to let a co-worker put his iPod Touch on the web through my phone, or connect a device to wifi that I can't use WPA2 on, then they can bite me. Not paying 40 dollars a month for a feature I use 5 times a year. >_> If I use more than 2 GB they'll get THAT money and nothing more data related.

So... ya sorry for the rant. How do I unlock the boot loader. Searching isnt' helping me much.

You can't unlock something that was never locked to begin with.

The closest thing to bootloader locking we have is that if you flash a custom kernel with Odin, it puts up a big yellow triangle warning screen when you boot. If you flash a custom system image (including a prerooted one) it doesn't trigger the warning, same for if you flash a custom kernel using Mobile Odin or a similar approach on a rooted device.

To the person considering getting a GS2 - It depends. Out of the box, there are SEVERE flaws with both AT&T firmware releases. The AP Mobile widget eats data in the original UCKH7 firmware, and there are major issues with wifi in the UCKK6 update, some of which cause major battery drain issues.

If you're willing to root, you can nuke the AP Mobile widget and the OTA updater from the UCKH7 base to get a pretty good base, and if you're willing to go for more aggressive customization, there's a tool over on the XDA forums called Hellraiser that allows you to run I9100 Gingerbread firmwares. (You MUST use Hellraiser or a similar approach, and it only works for Gingerbread) My personal recommendation right now is the international XWKL1 base - it's very solid and has none of the problems UCKK6 had.

[johnf440]

I'm relatively new to this, having my phone for a week and all... but I found another fix that has worked for me for battery life issues. Somewhere else on the net, I found an explanation for 2.3.6 battery drain that involves wireless advanced settings and wifi sleep policy. When set to screen off, apparently, the phone continues to search for off and on states to the point that it drains the battery down. I simply set that to sleep never and downloaded a free app, Battery Defender, to shut wifi and data off when the screen is off.

I've gone from barely 7 hours of battery life to going on 32 hours and still the phone is at 16% battery. Previously, my biggest battery user was Android OS, at usually 70% or higher and now it is where it should be for my usage patterns at around 18%.

I don't claim to be a genius on this one, but that is what has worked for me and I have no complaints now, off the charger yesterday morning and it's 3:00 pm today and it's still going.

[Strawdawg]

Strange, I had Juice Defender on my phone and when I upgraded to 2.3.6, I saw virtually no difference in battery performance. Then it got worse. After reading your post last night, I went to check JD and discovered that it was missing. I don't know what happened, but, I reinstalled and changed the phone setting for wifi on at all times so that it was under the control of JD instead.

Seems to be working well so far...thanks for the tip

[Docjeep]

Originally Posted by Entropy512

My personal recommendation right now is the international XWKL1 base - it's very solid and has none of the problems UCKK6 had.

Entropy,

Been wanting to ask this question (reading up on xda also, and lots I still don't follow) and hoping you can help. I'm considering rooting and going to another ROM. I don't like the 2.3.6 (UCKK6? as you say a steaming pile) and would like to go with something else (stock 2.3.4, can't remember the samsung version number sorry, or something similar). Seems like from reading that unamed 1.3.x is a possibility, or I might consider XWKL1 as you recommend. But I will say I like the Touchwhiz interface (yea, I'm wierd) and was wondering if any of the ROMs retain that or do they get rid of it?

Thanks

[Entropy512]

Originally Posted by Docjeep

Entropy,

Been wanting to ask this question (reading up on xda also, and lots I still don't follow) and hoping you can help. I'm considering rooting and going to another ROM. I don't like the 2.3.6 (UCKK6? as you say a steaming pile) and would like to go with something else (stock 2.3.4, can't remember the samsung version number sorry, or something similar). Seems like from reading that unamed 1.3.x is a possibility, or I might consider XWKL1 as you recommend. But I will say I like the Touchwhiz interface (yea, I'm wierd) and was wondering if any of the ROMs retain that or do they get rid of it?

Thanks

Everything but AOSP-based firmwares (primarily Cyanogenmod 7) retain Touchwiz.

[Trip64]

this is BS. so how long has it been since it was clear that the .6 update has a wifi code problem that kills battery life?

8 hrs of limited use and i was at 17% when i was getting 17hrs of moderate to heavy use and still plugging in at night with +30% left.

this is my first android/samsung phone so based on the time that .6 came out does anyone have a feeling on when att will have a fix?

[Entropy512]

Originally Posted by Trip64

this is BS. so how long has it been since it was clear that the .6 update has a wifi code problem that kills battery life?

8 hrs of limited use and i was at 17% when i was getting 17hrs of moderate to heavy use and still plugging in at night with +30% left.

this is my first android/samsung phone so based on the time that .6 came out does anyone have a feeling on when att will have a fix?

No one has a clue - this is AT&T we're talking about. Without a doubt, blame AT&T - Samsung had already fixed these problems in international builds for the GT-I9100 (such as XWKL1) by the time AT&T started pushing UCKK6 out to users. AT&T is notorious for doing an awful job with updates. For example, Gingerbread for the Captivate didn't get released until 9 months after it was released for the I9000, even though the devices are nearly identical and people on XDA had Gingerbread firmwares ported within weeks, if not days. Similarly, I wouldn't expect to see ICS on the I777 officially until early 2013, even though I'll likely have it working unofficially within hours of the I9100 release (which is probably later this month).

(Since you're new - the I9100 is the I777's international sibling. They're almost identical, to the point where only minor changes are needed to run I9100 firmware on the I777.)

[JChapa13]

I've been using Battery Defender and I went from a 70% battery drain overnight to about 7-8%. I highly recommend using it until they fix the issue. Push notifications from chat apps, sports widegets and emails may be delayed, but at least your battery is usable after sleeping.

[Trip64]

Originally Posted by Entropy512

No one has a clue - this is AT&T we're talking about. Without a doubt, blame AT&T - Samsung had already fixed these problems in international builds for the GT-I9100 (such as XWKL1) by the time AT&T started pushing UCKK6 out to users. AT&T is notorious for doing an awful job with updates. For example, Gingerbread for the Captivate didn't get released until 9 months after it was released for the I9000, even though the devices are nearly identical and people on XDA had Gingerbread firmwares ported within weeks, if not days. Similarly, I wouldn't expect to see ICS on the I777 officially until early 2013, even though I'll likely have it working unofficially within hours of the I9100 release (which is probably later this month).

(Since you're new - the I9100 is the I777's international sibling. They're almost identical, to the point where only minor changes are needed to run I9100 firmware on the I777.)

i agree that it is att. im new android but did start fallowing the gs2 3 months before release and got mine 5 mins after the store opened on the first day. so im debating if i can live with this for xx days or just root.