Infuse 4G update to 2.3 Gingerbread?

[BMan17]

Not sure I'd this topic has been started but I wanted to get one going.

Yes the infuse has 2.2.1 and all seems to work well but why not put 2.3 on a phone as good as this is a shame.

And I'd hope 2.3 would have Bluetooth voice over dialing cause that's a glarring omission at this point.

Any news?

Thanks

Bman

[blindsight]

ZDNET seems to have the inside scoop...

http://www.zdnet.com/blog/gadgetreviews/gingerbread-coming-to-at-ts-2011-android-phones/26477?tag=nl...

[BMan17]

well that is some positive news. so fingers are crossed! i wonder though, the release says "Captivate 4G." didnt know there was a Cappy 4G? so my other phne the Cappy 3G is a lame duck and will be stuck with Froyo?

[Entropy512]

Rogers is releasing the Infuse with Gingerbread today and Samsung released kernel sources for the Gingerbread kernel for the Infuse yesterday, so expect Odin-flashable dumps to be available within a few days.

Also a good chance of CM7 within a few weeks now.

[steveru621]

The list includes Infuse and Captivate

http://www.prnewswire.com/news-releases/att-customers-to-enjoy-gingerbread-126113088.html

Sounds promising

[steveru621]

The list includes Infuse and Captivate

http://www.prnewswire.com/news-releases/att-customers-to-enjoy-gingerbread-126113088.html

[BMan17]

The biggest thing I want is the Bluetooth over voice dialing.

Especially nice that I will be able to pair to my BlueAnt Q2 headset.

And my wife's Cappy can be upgraded too!

Next we need to know what bugs are in 2.3, and if it's caused headaches for users!

[BMan17]

Oddly enough, I did a software check tonight justvtobsee if the gingerbread was pushed out to my infuse. And I should say I for this phone 5 weeks ago and never did a software check as it came with 2.2.1.

So update said I had a software update! So I was like cool, gingerbread is coming to my phone! The update was only 8MB, and thought that wasn't enough for a 2.3 update.

So it updated and my phone still says 2.2.1.

So nit sure what that update was for.....

[Ann154]

It was probably a maintenance update to fix a bug or two. I sure there is information out there about it. Maybe even on AT& T's support page for the phone.

[BMan17]

Yeah. I was going to check it out this morning.

Cause I figure the gingerbread update will be like a 100MB download?

[Entropy512]

That's a fairly old update - been around at least 1-2 months.  From Froyo UCKD5 to Froyo UCKE3.

Rogers Gingerbread is UCKG3.  AT&T Gingerbread doesn't exist yet.

[BMan17]

You got it. My phone is now UCKE3.

Well, maybe that makes sense since I got the on June 16th and I haven't even thought of doing a software update check till last night just to see if 2.3 came in, which I know wont happen for infuse for a while, but was giving it a shot!

Do you know what it fixed?

[21stNow]

What's stopping you from doing voice dialing via Bluetooth with Froyo?

[Entropy512]

UCKE3 has a radio firmware update, not sure what else.  The firmware binary plus the updater executable doesn't leave much else for an 8M update.

All of the attention on XDA is on the Rogers UCKG3 Gingerbread release now... 

[luskfamily]

Infuse user both wife and I.  I do pray, that AT&T checks GB good. Cause I have seen some posts on android central and a couple of other sites, that sprint customers are having issues with the GB upgrade. Yes, I know we are AT&T. But I was a Telecom mobile switch engineer and I know the cellular switch end of it can be an RF nightmare sometimes. I would rather have good testing and be a little patient than go through all that frustration.  I know I need to read more, I am new to Android, came from 3gs, and takes some getting used too but loving the freedom this awesome device provides. Amazing device speeds in reaction time... Thx...

[Entropy512]

The AT&T GB update will be garbage - bloated and laggy.  This is the definition of all factory AT&T firmwares unfortunately.  They always take forever to release updates in the name of "testing" but when the update comes out - it's always bloated and laggy compared to uncustomized "vanilla" firmware for similar hardware.  Really, if AT&T wants the best possible customer experience, then why are they continuing to allow Samsung to use RFS instead of ext4 as the filesystem on their phones - RFS is so notorious for poor performance that "Voodoo Lagfix" (automatic ext4 conversion) is a standard feature in all third-party firmwares for these phones and is #2 on the list of things third-party firmware developers for Samsung devices target (Clockworkmod Recovery being the #1 item...)

The Rogers Gingerbread firmware is awesome, other than the fact that it's missing HDMI/MHL support - this was an explicit conscious decision by Rogers not to have this feature.  Battery life with Gingerbread is FAR better than Froyo.

[aalmousa]

Is it possible to put Rogers ROM on ATT Phone?

[Entropy512]

---

aalmousa wrote:

Is it possible to put Rogers ROM on ATT Phone?

---

Yes.  Infused v2 on XDA was based on the Rogers ROM.  Some small kernel source tweaks were needed to get the Rogers kernel to play with the AT&T bootloaders - yay open source!

Unfortunately for a variety of reasons, the guy that released Infused v2 temporarily pulled his ROMs.  Some aspects of the Rogers firmware base don't get along with AT&T users:

1)  Rogers firmware is completely missing HDMI support

2)  The Rogers modem and RIL have data speed issues in some AT&T areas.

That said, I used a Rogers-derived firmware on my phone for two weeks and loved it.  I'm running an unofficial CM7.1 development/test release now.

The nice thing about Samsung phones is that they are REALLY difficult to hardbrick.  In fact it's nearly impossible to hardbrick an Infuse.  (Only one person has ever done it, and they volunteered to run an exceptionally dangerous experiment.)

[BMan17]

---

Entropy512 wrote:

The nice thing about Samsung phones is that they are REALLY difficult to hardbrick.  In fact it's nearly impossible to hardbrick an Infuse.  (Only one person has ever done it, and they volunteered to run an exceptionally dangerous experiment.)

---

I would love to hear about the "exceptionally dangerous experiment!" Sounds like you tried to nuclear fission or something! hehe.

Well, I am HOPING GB isn't fat and bloated cause since my "maintenance update" on 2.2 my phone is now routinely locking up on the data service. Before the update, never did a hard reboot. After update, pulling the battery 1 or twice a day.

[Entropy512]

---

BMan17 wrote:

---

Entropy512 wrote:

The nice thing about Samsung phones is that they are REALLY difficult to hardbrick.  In fact it's nearly impossible to hardbrick an Infuse.  (Only one person has ever done it, and they volunteered to run an exceptionally dangerous experiment.)

---

I would love to hear about the "exceptionally dangerous experiment!" Sounds like you tried to nuclear fission or something! hehe.

Well, I am HOPING GB isn't fat and bloated cause since my "maintenance update" on 2.2 my phone is now routinely locking up on the data service. Before the update, never did a hard reboot. After update, pulling the battery 1 or twice a day.

---

Well, a common theme on Samsung Galaxy S and similar devices is that running Gingerbread kernels with Froyo bootloaders causes weird "rainbow" artifacts in some cases.

So multiple attempts were made to flash a Rogers bootloader to an AT&T device.  In general the device refused to flash - it seems to be set up well to protect against hardbricking.  So after multiple go arounds, one of the devs figured out a way to flash the BML5 partition, and when that got flashed - brick.

So odin/heimdall seem to be unable to accidentally flash bootloaders, and if you can't damage the bootloader, you can't hardbrick the device into an unrecoverable state.  It's ALWAYS recoverable unless your USB port encounters a hardware failure.

[LilyDi]

gingerbread isn't even out yet, you sound rediculous..how do you know what its gonna be like?

[jdmchugh]

Well we didn't seem to make the August deadline for the 2.3 update! Seems we are the poor stepchild, since some of the others got theirs. If there is anyone from ATT monitoring this thread, please give us an idea of when we might expect the update so we don't have to deal with hearsay and unrequited expectations.

Thanks

[Ann154]

Samsung has gotten a reputation in the USA of being slow with the phone updates especially when the phone is question is tied to a carrier and their bloatware.

[BMan17]

Yeah. I tried it yesterday and nothing. We're left out in the cold. And now the new Galaxy SII coming out it looks extremely similar to the Infuse. And will have 2.3.4!!

[swoosh76]

Once again ATT delivers on their promise.........

[Entropy512]

---

LilyDi wrote:

gingerbread isn't even out yet, you sound rediculous..how do you know what its gonna be like?

---

Gingerbread has been out for months on other devices, so we know what general features can be expected.

Also, Gingerbread has been out for the Infuse since late July in Canada - Rogers released the infuse on their network with Gingerbread (2.3.3 to be specific) - many people are running Rogers-derived firmware on our phones, with the main limitations being that the Rogers RIL doesn't do HSPA+ and Rogers didn't release their device with MHL/HDMI support so it's completely missing from the firmware.

So we know what Gingerbread is going to be like - it's going to be like the Rogers release, plus AT&T bloat, plus proper HSPA+ and HDMI support.

[tovisual]

Still waiting........ :-(

[aann]

is there a way to push ATT to do it? just curious

[davidusr]

Not really. They'll get around to it when they're ready.

[BMan17]

I tried my daily software update hoping that 2.3 will finally come through.

But no, I did get an update, but looks like just a maintenance update for 2.2.1

Build and kernal are now i997UCKH1  & 2.6.32.9

Is the Infuse the last of the phones to get the 2.3 update from the late July press release?

[ghirsh]

I just got the same update.  It's about 14.2mb. Not sure what it provided.