Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

Master

Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

The original GS2 just got 2.3.6 OTA update. It is a 20MB download. Have fun.

Message 1 of 132 (34,928 Views)
Contributor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

Oh, I should mention that I did not let it charge during that half hour. I left it completely dead (I didn't have a charger on me at the time). After I plugged it in to charge, I turned it on immediately and haven't seen the issue since.

Message 76 of 132 (6,384 Views)
Tutor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

How come you guys don't just root your phone and remove all the ATT bloatware/rogue apps?

Message 77 of 132 (6,377 Views)
Teacher

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live


kyrax13 wrote:

How come you guys don't just root your phone and remove all the ATT bloatware/rogue apps?



Why should we do that as a work around when it's an ATT issue?

 

Some of us don't care to root.

 

Bottom line... att issue, they need to find the problem and fix it for their customers.

Message 78 of 132 (6,363 Views)

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

Yes, either AT&T didn't adequately test this update or they knew about the outstanding issues and released it anyway. In either case, they will not admit responsibility (and, of course, liability) and are content to let us complain here where we can cause the least amount of PR damage.

I'm sure a fix will be released in the weeks ahead, but there will be no acknowledgement of what they did -- and certainly no apologies.
Message 79 of 132 (6,356 Views)
Teacher

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

Saw this on another site and said what the heck.. ez to try... well... I don't know the reasoning but so far...

Pulled battery and pulled SD card. Charge overnight.. So far.. my android OS is back down to 9-11% where it has been running at 57-87% or so. ON battery for 5hrs and at 81%.

Will monitor this more to see if anything changes in the next few days.
Message 80 of 132 (6,353 Views)
Contributor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

I'm having battery issuses as well. But what I did notice was when I turn on WiFi, my battery drains a lot quicker. I think it's a WiFi issue....

Message 81 of 132 (7,056 Views)
Highlighted
Mentor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live


ironj221 wrote:

I just wanted to restate the instructions Beef posted.

 

How to Downgrade 2.3.6 to 2.3.4

Follow the instructions here: http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/

Don't follow step 8 and beyond unless you have to.  All your settings will be completely saved and you will be back on your old phone like before without the bad battery life.  Your phone does NOT have to be rooted to follow these instructions.


I did this - ended up having to follow step 8, as my wifi wouldn't turn on. Now everything works like a champ and the battery seems to be much better! Thank you everyone who posted about this. Smiley Happy

Message 82 of 132 (7,025 Views)

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

It's a problem with how the Broadcom BCM4330 (which does Wifi and Bluetooth) is managed.

 

It is also affecting recent leaks for the Samsung Infuse.

 

Basically, a "feature" of this chip is Broadcom's Bluetooth Alternate MAC and PHY (BT-AMP) which apparently is supposed to allow Bluetooth to be routed over Wifi for increased speed with BT chipsets that support it.

 

The problem is that I've never seen BT-AMP do anything other than go nuts and fire wakeup interrupts at 1 Hz.  This is the cause of at least one of the 2.3.6 battery drain situations.

 

All of the tricks people have described involving weirdo charging regimens are NOT fixes.

 

The problem is intermittent, so rebooting usually fixes it for a while, but it will come back.  Over in the Infuse forums, sometimes it seemed to be caused by having wifi active and then leaving the wifi network (but not always):

 

http://forum.xda-developers.com/showthread.php?t=1408433

 

If you want to confirm that your root cause is BT-AMP, when you are experiencing drain, follow the Wireshark capture instructions here:

http://forum.xda-developers.com/showthread.php?t=1308030

 

Look for stuff like this:

      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

 around once a second.

Message 83 of 132 (6,972 Views)

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

As I posted above, when I turn WiFi off I am getting great battery life with 2.3.6.  I have also been rebooting for the last two mornings when I take the S2 off the charger.  Entropy512 your post is the first one that makes sense to me.

Message 84 of 132 (6,958 Views)
Mentor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

It sounds like it might be a problem with noise suppression. Try the settings menu in a call to temporarily turn it off or on.

 

There is also a setting in Settings, Call, Additional Settings, Noise Suppression that I think is the default.

 

Let us know if that helps or not...

Message 85 of 132 (6,939 Views)
Mentor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

One of the things included in 2.3.6 is a very important update to a security bug. Before, if you have a lock screen pattern, there was NO SECURITY.

 

With 2.3.4, when I power up the phone from sleep, I see the lock screen. I log in, check email, whatever, turn off. Then when I hit the power again, I see the lock screen. Sounds good, but wait. I just let that lock screen time-out, the phone goes dark, then hit the power again...presto, you are in the unlocked phone without knowing the lock pattern.

 

This is lethal if you leave your phone at a coffee shop, and someone picks it up and starts snooping.

 

2.3.6 patches this bug.

Message 86 of 132 (6,938 Views)
Contributor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

[ Edited ]

so i downloaded the update, but i'v been reading these issues so i postponed it for 3 hours i think. is there any way I can delete the update or delete the reminder all together. I really dont want the phone to force update itself after 3 hours.

 

 

Message 87 of 132 (6,930 Views)
Tutor

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

I don't understand your logic.

 

Why should you have to wait on your carrier to fix the problem when a simple root can fix most of the problem?

 

Why in the world woul someone get an Android phone without even spending a bit of time with their phone. Also for implying rooting is hard.... SMH

Message 88 of 132 (6,915 Views)
Teacher

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live

[ Edited ]

Thanks for your detailed explanation, Entropy.

 

To update everyone on my attempt to have AT&T replace my two phones, I received the two "refurbished" phones today. They are both BRAND NEW, and they are both 2.3.4.

 

If everyone will push this issue until you get sent a replacement phone, this will force AT&T to deal with this more quickly. Don't let them just send you a battery to get rid of you.

Message 89 of 132 (6,886 Views)

Re: Samsung Galaxy S2 SGH-i777 2.3.6 OTA update now live


3GJockey wrote:

One of the things included in 2.3.6 is a very important update to a security bug. Before, if you have a lock screen pattern, there was NO SECURITY.

 

With 2.3.4, when I power up the phone from sleep, I see the lock screen. I log in, check email, whatever, turn off. Then when I hit the power again, I see the lock screen. Sounds good, but wait. I just let that lock screen time-out, the phone goes dark, then hit the power again...presto, you are in the unlocked phone without knowing the lock pattern.

 

This is lethal if you leave your phone at a coffee shop, and someone picks it up and starts snooping.

 

2.3.6 patches this bug.


This bug did have an identified workaround in UCKH7 that worked fine.  It involved setting the security timeout to "immediate" or something like that.

Message 90 of 132 (6,879 Views)
Share this topic
Announcements

Welcome to the AT&T Community Forums!!! Stop by the Community How-To section for tips on how to get started.