The OFFICIAL 2.3 Gingerbread Discussion Thread!

[miscrap]

I JUST COULDN'T TAKE THE FREEZES AND REBOOTS ANYMORE!!!!
Made multiple backups, finally decided it was now or never.  I pulled out the SIM and SD cards, hit the magic keys, and... nothing.  Just sat there.  I was using GOdialer, so I thought I would try it again using the stock dialer.  The red message came up!  Said factory reset at the top.  Then said...  "After a few seconds.   Reboot!  Do not touch any button!"  Rebooted.  When it came back up it went through a minitutorial, eventually leading to the stock, basic home screen I saw when the phone was new.  But brace yourself...  When I went to Menu>Settings>About phone...  Firmware version is 2.3.5, Build number is GINGERBREAD.UCKK4 !!!!!   I'M STILL ON GINGERBREAD!!!  My hope now is that by installing my apps over a clean OS I won't run into all the glitches I had, or that I find that I had apps installed that were not compatible, and leaving them off takes care of my problems.  But, to repeat, doing a GSM reset on a phone updated to Gingerbread will not reset it to a prior flavor of the operating system.  Updates to come as I reinstall my phone.
Update:  The first thing I installed was MyBackupPro.  Went to Restore... and it said no backups existed.  I installed File Expert.  Viewed the card, did not see any files on it.  (It was uninstalled when I did the reset, so it's not like it was reformatted.  It seems almost like when you lose the MBR on a hard drive - the files are there but the HD doesn't know it.)  Anyway, the next thing I installed was Dropbox.  I had copied the backup files to there, and when I looked, there it was!  I unzipped it and copied the result to the mnt/sdcard/external_sd folder.  Reran MyUpdatePro, and it still said the backup wasn't there.  I rebooted the phone and tried again, and it saw the backup!  Told it to go ahead and Restore, it said it was deleting the current contacts (I guess from the SIM, that's all that was there), then nothing.  Stayed on that screen for several minutes.  Then suddenly started saying that it copied 1 contact, 2, 3, etc.  When it finished it said to reboot.  That just finished.  It looks like the contacts are there, although it will need a bit of cleaning up - there are some dupes and things I don't want there.  I'm displaying only the phone contacts (not Sim or Google) but still seeing 2 and 3 of some.  I have a  sync message that says Too many Contacts deletes.  Delete limit exceeded.  The phone is looking ugly right now, with blue bubbles on the home screen.  Think I'll pretty it up a bit and call it a night. 
Oh, and so far, no freezes and no reboots!

[DesElms]

AT&T Device Support Centers, nationally...

http://www.att.com/esupport/article.jsp?sid=KB91429
(scroll down to item 3)

...have recently had their Samsung re-flashing software (and a hardware item or two) upgraded by Samsung (most centers have been visited by their Samsung reps to install and train on it within the past month).  The new flashing hardware and software is capable of returning the phone to 2.2 Froyo exactly as it came from the factory...

...I'm just saying if you end-up needing that, that is.  The center nearest me got upgraded this very week, and I only learned about it yesterday.   So the GSM Reset, I was told, is no longer what the Device Support Center staff would do for something like your situation.  Rather, they'd re-flash the phone from the hardware/software that just got upgraded by Samsung.  I'm told that that's extremely thorough and effective.  (Wish I'd known about it earlier in this thread.)

As for the backup, remember that you were supposed to have copied the entire Internal SD to your local desktop/laptop computer's hard drive for safe-keeping before GSM Reset, because GSM Reset reformats all media; then do the GSM Reset; then copy at least the backup from the desktop/laptop back to the Internal SD, and then restore from there.  

However, as I earlier wrote, though I do backups, the truth is that I mostly just restore contacts from the SIM card; and most users don't really need SMS restored since usually it's contacts about which most phone users worry.  And then I re-install all apps from the Android Market... at least with something like an OS upgrade.  I do this, in part, because as I hit each app's page to re-install it, I'm told, right then and there, if the app's still compatible with the phone... which, after a 2.3 Gingerbread upgrade, one would want to know; and having the app's Android Market page indicate, in the right area of the app's page, if the app's still compatible with whatever's on the phone (assuming the phone has logged-in to the Android Market via the Android Market app, so that the Android Market account can "see" that the phone now has 2.3 Gingerbread on it) is invaluable.

Restoring everything from a backup is more useful (and safe) and faster when the OS after the backup is the same as before the backup.  At least then you know that all apps are still compatible with the OS because nothing about the OS has really changed.   That said, you can certainly re-install from all the backed-up .APK files, and except for the apps which are no longer compatible (because they're for 2.2 Froyo and lower only), they should install fine.

Having a phone which no longer crashes and reboots and does whatever else it was doing is at least good.  If you can tweak the phone back to where you need it to be from there, then you're golden, it would seem to me.

OS upgrades are never fun or easy.  There's always something.  It sounds like, though, you may be on your way to finally getting things back to where they need to be; and on a higher-level OS, to boot! (no pun intended)


______________________________________
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com

[miscrap]

That's pretty much what I did.  I basically only used MyBackupPro to reinstall my contacts, which I had also backed up to my SIM, AT&T Backup, and another program, SuperBackup.  Belt & suspenders.  Reinstalled fine from MyBackupPro, except some of the street addresses are messed up - the street, city and state are there, but not the house number.  Not a problem, I can fix easy enough.  I then reinstalled the apps from the Market, but did it from the Android Market web site via my laptop.  It was  just easier to use a full size keyboard then a touch screen.  Still told me if something was compatible.  The apps were automatically sent and installed.  
So far, no freezes, but the phone has spontaneously rebooted a couple times.  Not nearly as bad as before, but still annoying.  The phone will be sitting untouched and I'll hear the "Start" sound.  I'll keep at it and see if I can come up with the cause and how to fix it.
Thanks again for all your help.
Oh yeah, and no more tethering error messages.

[jec145]

Anybody having issues with dialing into phones systems (i.e. conference centers, voice mail systems, etc.)?  After the update I'm having issues after calling into conference centers and dialing meeting codes, or accessing voice mails systems for messages. 

The systems register more than the numbers i press or not at all.

I only have this issue, and the tethering error(seems like I'm luckier than most so far)

My thinking is this:  If have I have to reset my phone or have it re-flashed back to froyo to fix anything, I'm going custom and trying out ICS.  It can't be any more buggy at this point.

1 last thing, after the update my ring tone changed to something else, no big deal, except i can't FIND that tone listed anywhere.  Weird.

[DesElms]

...but the phone has spontaneously rebooted a couple times.  Not nearly as bad as before, but still annoying.  The phone will be sitting untouched and I'll hear the "Start" sound.  I'll keep at it and see if I can come up with the cause and how to fix it. [...] Oh yeah, and no more tethering error messages.

Again, sounds like a 300% improvement, but the auto-reboot is still unacceptable.  I can't help but wonder if you went to your nearest AT&T Wireless support center and asked them to just flash the phone to 2.2 Froyo, and then went straight home and did the 2.3 Gingerbread upgrade, if all symptoms would be gone...

...at which point re-installing everything won't have been the waste of time that I fear your just having done it will end-up being.

I'm still rootin' (no pun intended) for ya', though! [grin]


__________________________________
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com

[DesElms]

Anybody having issues with dialing into phones systems (i.e. conference centers, voice mail systems, etc.)?  After the update I'm having issues after calling into conference centers and dialing meeting codes, or accessing voice mails systems for messages.  

The systems register more than the numbers i press or not at all.

I only have this issue, and the tethering error(seems like I'm luckier than most so far)

My thinking is this:  If have I have to reset my phone or have it re-flashed back to froyo to fix anything, I'm going custom and trying out ICS.  It can't be any more buggy at this point.

1 last thing, after the update my ring tone changed to something else, no big deal, except i can't FIND that tone listed anywhere.  Weird.

Sounds like 2.3 Gingerbread doesn't include a ringtone which was included in 2.2 Froyo.  That happens.  Heck, ringtones vary just from the Captivate to the Infuse (which, the latter, some joke, is just a Captivate with 200GHz faster processor and an 11% larger screen... which is kinda' true); and those Captivate owners who haven't upgraded to 2.3 Gingerbread have the exact same OS version as Infuse owners.

If I had to bet, I'd also say that you need to get back to 2.2 Froyo, exactly as from the factory; and then immediately (before the phone becomes "used" again, and gets goofed-up in a manner which could adversely affect) upgrade(ing) to 2.3 Gingerbread.  All your symptoms, I'll bet, will go away at that point.

As for rooting, it's, of course, your call; but I usually counsel against it (making me in the minority around here, I realize) unless there's actually something you're being blocked from doing by not rooting; and unless whatever that is is pretty darned important.  My argument against rooting is based, simply, on my belief that most Captivate users just want to use their phones, and not have to babysit and worry about it all the time; and have to learn to be something of a techno-geek just to maintain it...

...and if there's one that rooting one's phone (and especially installing another ROM) does, it's force the user to become something of a techno-geek just to maintain the phone... and keep an eye on it, and worry about how apps installed on it, or updates to its OS, might cause a whole new symptom with which the user would prefer not to have to deal.  It's not brain surgery or rocket science, I realize; but rooting a phone and installing a new ROM takes the user into a whole new world of unforeseen godonlyknowswhat, and for most end-users who just want their phone to be a reliable phone, and the apps installed on it to do what they claim they'll do, it's all just not worth it.  Life's just too short.

You wrote, "it can't be any more buggy at this point," to which I respond, resoundingly:  Oh, yes it can!  Trust me.

And then there's the whole business of the possibly nefarious intentions of whomever wrote the rooting software and ROM, and how that could impact the privacy and security of your data on the phone... again, just not worth it.  The Internet is rife with postings from people who describe inexplicable adware, and data streams (phoning home) to servers in China, and all kinds of other crap!  Who knows what of one's private information is being reported to Beijing and godonlyknows where else with such rooted phones.  Yes, of course, it's possible to figure it all out and put a stop to it... but that just brings us back to the simple question:  Why?  Why even bother?  Why even put oneself through it.

I'm a techno-geek, and I've rooted phones; but I haven't the slightest interest in doing it to either my Infuse or my wife's Captivate.  Not the slightest!  And that's, in largest measure, because my life already has all the challenges it needs without my phone adding to the mix.  It's a commodity... a tool... like a blender or a fax machine.  I just need it to work; and I'm old enough that I get no kick, anymore, out of conquering the technological challenges.

There's an old, old Steve Martin comedy routine where he talks about how getting older tends to help one learn to slam doors on things in life.  He then illustrates by quoting some unknown young person as saying, "Hey, everyone... let's go try this new thing!," after which he pauses, and then makes the sound, with his mouth, into the mic, of a door slamming shut.

But, hey... that's just me.  Root away, if you insist.  And may you encounter neither hitch or glitch along the way!  (And the wind be at your back, and blah, blah, blah... you get the picture.) [grin]

Hope that helps!


________________________________
Gregg DesElms
Napa, California USA
gregg at greggdeselms dot com

[jec145]

Anybody having issues with dialing into phones systems (i.e. conference centers, voice mail systems, etc.)?  After the update I'm having issues after calling into conference centers and dialing meeting codes, or accessing voice mails systems for messages.  

The systems register more than the numbers i press or not at all.

I only have this issue, and the tethering error(seems like I'm luckier than most so far)

My thinking is this:  If have I have to reset my phone or have it re-flashed back to froyo to fix anything, I'm going custom and trying out ICS.  It can't be any more buggy at this point.

1 last thing, after the update my ring tone changed to something else, no big deal, except i can't FIND that tone listed anywhere.  Weird

Sounds like 2.3 Gingerbread doesn't include a ringtone which was included in 2.2 Froyo.  That happens.  Heck, ringtones vary just from the Captivate to the Infuse (which, the latter, some joke, is just a Captivate with 200GHz faster processor and an 11% larger screen... which is kinda' true); and those Captivate owners who haven't upgraded to 2.3 Gingerbread have the exact same OS version as Infuse owners.

If I had to bet, I'd also say that you need to get back to 2.2 Froyo, exactly as from the etc........

OK so you're in IT, I get it.  I and alot of people around here are as well.
First, you make vaild point, if a little long winded(sorry, I hate reading a lot of text on the screen)

1.  New ring tone.  Yeah phone get new ring tones when they get updated.  Wierd part is, I can't find the new ring tone listed on the phone, anywhere.  Shame really, it was kinda cool, but i switched back to the Torchwood mp3.  I take so few calls, without the tone being recongnized I don't bother looking for the thing.

2.  The phone systems I can't seem to take conferences calls on so far are all manufactured by ATT competitors.  (I have a Siemens Hipath4000 sitting here near me.  I ran some experiments, as well as made some calls to the meeting center and the bank.  ATT builds work, other system no go so far.

3.  Tethering error has been "fixed"(at least on mine, everyone elses so far seems to have reverted back.  see post on main section for carrier updates)

4. Rooting and Custom ROMS.  Vaild it could be worse, for most.  I only found out I had a new ring tone a week after upgrading.  Same with the voicemail/conference call's.
I have alot of meetings, but most i take fro my desk.  Ocassionally I get scheduled one after I leave work.  Come to think of it, I found both things out at the same time.  i couldn't dial into a meeting, so they called me.  Needless to say, the Phone part i don't use much, or email.  Actually I play angry birds, browse the internet, watch netflix, etc. 

Hell, I only really have a phone so the wife can call for milk on my way home!!!!(btw she was supper pissed when i bought this originaly, but the GPS(yes the GPS) saved our buts more then once on vaction.

But needless to say, this thing is just a toy for me.  So rooting, Custom roms, tweaking settings, its all good.  If I want a phone hat "just worked" I'd get an iPhone, but then again, I'm no Rockeffeller(1%er, Gates, guy who invented Facebook) either. 

[upinhere65]

Um wow... that's a lot of information overload.  You guys got some mighty fine techincal skills!!!

Please break it down for us who are just flat out having issue with the upgrade. My sammy was working great for a while now I'm getting force closed errors like crazy and major Lagg.

Whatever the upgrade did... it jacked up Echange mail big time.  I open an email and it takes 3 min  ( I may exag) for the text to download and sometime it justs hangs there an then freezes and I have to shut it down. If you rotate the phone the send-attach-discard buttons disappear and you have to rotate the phone to the upright positon to get them to reappear. Don't have my little arrow do-hicky to slide over words and correct errors. I'm basically touching the sport at the words in hope of the line going to the right spot to correct the spelling.
It's a mess I tell ya.. a mess!!!

Does anybody use exchange server for their mail and are you experiencing this problem?

Now.. are you all saying that the best way to fix these issses is to take cappy to an ATT service center and have them wipe it back to stock since the GSM doesn't do the job?
Once this is done is they will re-install the new ginge up grade and this will make everthing better?

Because I'm at the point to where i'm bout to call Sammy and ATT and give them some choice words that my mom or Tebow won't approve of.

[markls]

I just got off the phone with Samsung with my issue unsolved...well, actually, totally destroyed. Having endured the torture of waiting for the continually delayed Froyo upgrade and patiently holding off for the official release last year, I saw Gingerbread being teased with the same pattern, so last summer I flashed (no root) 2.3.3 successfully then did the October 2.3.5 build just a week before the recent official release.

My problem is I can't Kies Mini to this upgrade because I'm not on Froyo then found out Samsung withdrew Froyo from the links I had from last year. So I apparently can't get back to Froyo...which was a dilemma not hinted to in all the forums that gave me the courage to flash to 2.3.3! Samsung just told me I can't get back and to send in the phone for a complete reflash.  Wonderful. Anyone have any ideas of how to get to a point to do the Kies Mini upgrade?

[jec145]

I just got off the phone with Samsung with my issue unsolved...well, actually, totally destroyed. Having endured the torture of waiting for the continually delayed Froyo upgrade and patiently holding off for the official release last year, I saw Gingerbread being teased with the same pattern, so last summer I flashed (no root) 2.3.3 successfully then did the October 2.3.5 build just a week before the recent official release.

My problem is I can't Kies Mini to this upgrade because I'm not on Froyo then found out Samsung withdrew Froyo from the links I had from last year. So I apparently can't get back to Froyo...which was a dilemma not hinted to in all the forums that gave me the courage to flash to 2.3.3! Samsung just told me I can't get back and to send in the phone for a complete reflash.  Wonderful. Anyone have any ideas of how to get to a point to do the Kies Mini upgrade?

There is a site that they dump all the Samsung roms to, official and beta(sorry, can't remember it off hand.)  You should be able to find it on XDA pretty easily, if you search for GB releases, the froyo stock rom is there.  You can then use ODIN to flash it back to the phone.  Again, see XDA for instructions.

Wish i could be a little more detailed, but my kids are streaking through the house right this second, and I need to go though them in the tub.

[DesElms]

...Whatever the upgrade did... it jacked up Echange mail big time.  I open an email and...
[...]
...to the right spot to correct the spelling.  It's a mess I tell ya.. a mess!!!

I'm sorry to learn of the problems you're having with the Captivate and an Exchange server.  I've long heard/read about such problems, even on 2.2 Froyo and earlier versions; without the complication of an OS upgrade.  

Some users report flawless Exchange interaction, others never quite get it to work right; and, of course, neither Microsoft nor Google have even the slightest interest in making it work properly.  That said, I've made it work beautifully, even on phones which exhibited problems, but it can be tricky.  

Fortunately, for many, many users, making a Captivate work with Exchange goes pretty smoothly; and so they have no idea what people are even talking about when they suggest that the Captivate and an Exchange server sometimes don't play nicely together.  

Trying to apply an OS upgrade to a Captivate which is communicating -- either successfully, or otherwise -- can definitely cause the sort of thing it seems you're now experiencing...

...which brings us, as a possible solution, to...

Now.. are you all saying that the best way to fix these issses is to take cappy to an ATT service center and have them wipe it back to stock since the GSM doesn't do the job?

Once this is done is they will re-install the new ginge up grade and this will make everthing better?

Because I'm at the point to where i'm bout to call Sammy and ATT and give them some choice words that my mom or Tebow won't approve of.

Ha!  Funny. [grin]

Well, at first I counseled to reverse the 2.3 Gingerbread upgrade by doing a GSM reset.  And I counseled that because when I finally tried replicating everyone else's troubles by applying the 2.3 Gingerbread upgrade to one of the Captivates we had (which had both been exhibiting the infamous auto-shutoff symptom) which had been in use awhile (and as also shipped from the factory) as a 2.2 Froyo phone, I was able to restore the phone to 2.2 Froyo after a failed 2.3 Gingerbread upgrade; so I mistakenly thought that a GSM reset would restore the phone to 2.2 Froyo after a successful (even if glitchy) 2.3 Gingerbread upgrade.  But I now realize that my being able to restore to 2.2 Froyo was only because the 2.3 Gingerbread upgrade actually failed... never properly completed.  Turns out that if the 2.3 Gingerbread upgrade succeeds (even if it results, after reboot, in a glitchy and error-prone phone), then any GSM Reset (or any other kind of reset, for that matter) performed thereafter simply resets the phone to 2.3 Gingerbread... as "miscrap" first advised us in this thread (and which advising is what made me re-test and learn that he's right... my bad... sorry).


So my triple-net, bottom line (at least at this point), revised advice is now as follows:


(1)  Don't upgrade to 2.3 Gingerbread... either:

(1)(a)  For a little while longer (until AT&T and Samsung have perfected it and have released an update); or,

(1)(b)  ever (because 2.3 Gingerbread's benefits are actually, all things considered, quite negligible for 2.2 Froyo Captivate users whose phones are working well).

RECOMMENDED ACTION, if you agree with either or both of the above...

(1)(c)  If you've not yet tried to apply the 2.3 Gingerbread upgrade to your phone, then do nothing; or, on the other hand,

(1)(d)  if you've already tried to apply the 2.3 Gingerbread upgrade to your 2.2 Froyo phone (and if a GSM Reset does not return said phone to a pristine, as-if-from-the-factory 2.2 Froyo phone), then take said phone to the nearest AT&T Wireless Device Support Center...

http://www.att.com/esupport/article.jsp?sid=KB91429
(scroll down to item 3)

...and have them flash the phone back to 2.2 Froyo, then just continue using the phone like that either until there's an update to the 2.3 Gingerbread upgrade, or forever, depending on with which of the two items (1)(a) or (1)(b) you agree.  But before you decide with which one (or both) you agree...

COMMENT REGARDING ITEM (1)(a):  Many here (and in other forums) will tell you that this recent 2.3 Gingerbread upgrade will be it for the Captivate; that nothing further will ever follow -- especially because the Captivate will soon (if it hasn't happened already) no longer be in production -- and so waiting will have no benefit.  Just FYI:  The corporate buyer for a dealer I know told me, during the first week of January 2012, that his Samsung rep told him in December 2011, that there will be no more new Captivates manufactured in 2012; that what's in the supply channels, and/or in dealers' and/or AT&T's inventory, is it; that there will be no more.  Period.  Mind you, I've not done one single bit of research to verify, but I'm just sayin' that that's what someone whom you'd think would know told me a couple weeks ago... for whatever that's worth.

COMMENT REGARDING ITEM (1)(b):  Many here (and in other forums) will argue that the benefits of 2.3 Gingerbread are, in fact, not negligible; and even those who might agree that they're negligible will, nevertheless, counsel that one should always run the most current possible OS version on one's device, no matter what, just as a matter of good(best) practice(s).


If you don't agree with any of the above, then...


(2)  Upgrade to 2.3 Gingerbread, but only by one of the following two means...

(2)(a)  If no attempt to uprade from 2.2 Froyo to 2.3 Gingerbread has yet been applied to the phone, then do a GSM Reset on the phone (after backing-up everything, of course) to restore it to the way it shipped from the factory; and then, immediately -- before the phone is used for anything, while the 2.2 Froyo restoration is still pristine -- apply the 2.3 Gingerbread upgrade using Kies Mini.

(2)(b)  If a 2.3 Gingerbread upgrade has already been applied to the 2.2 Froyo phone, and if said phone is now exhibiting glitches, symptoms and problems under the 2.3 Gingerbread OS such as others have herein described (and, in my opinion, even if it isn't), then take the phone to the nearest AT&T Wireless Device Support Center...

http://www.att.com/esupport/article.jsp?sid=KB91429
(scroll down to item 3)

...and have them flash the phone back to 2.2 Froyo; and then, immediately -- before the phone is used for anything, while the 2.2 Froyo restoration is still pristine -- apply the 2.3 Gingerbread upgrade using Kies Mini.

COMMENT:  If you're one of the lucky ones who applied the 2.3 Gingerbread upgrade to a 2.2 Froyo phone didn't have to do either (2)(a) or (2)(b) immediately above; and so if your 2.3 Gingerbread upgrade to said phone -- even if it's long been in use -- went smoothly, and said phone is now exhibiting no problems, then I suppose you could just not look a gift-horse in the mouth, and move forward, not looking back, and not worrying about it anymore.  Most here would, I"ll bet, so advise.  However, being the anal retentive that I can be, I can't help but wonder if so doing will cause unforeseen problems to rear their ugly heads later... and if that's a valid concern, then then it seems to me that even those who think their 2.3 Gingerbread upgrade went okay, and that their phone's now okay, should nevertheless do item (2)(b), above, just to play it super-safe... but that's just me.


Hope that helps!


_________________________________
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com

[DesElms]

I just got off the phone with Samsung with my issue unsolved...well, actually, totally destroyed.

No surprise, there.  I've found Samsung to be helpful only -- and I mean ONLY -- for pure hardware issues.  For OS-related -- and especially for carrier-installed stock apps related -- issues, only AT&T (if one's in the US; or Rogers, if one's in Canada) tends to seem helpful.

Having endured the torture of waiting for the continually delayed Froyo upgrade and patiently holding off for the official release last year, I saw Gingerbread being teased with the same pattern, so last summer I flashed (no root) 2.3.3 successfully then did the October 2.3.5 build just a week before the recent official release.

Wait a minute... ho da' fone...

...how does one flash a 2.2 Froyo Captivate to 2.3 Gingerbread -- other than via an official update/upgrade from the carrier (AT&T, for those in the US; or Rogers, for those in Canada) -- without rooting?  It's a rhetorical question, actually, since I'm unaware of any way of doing it.  So, then, you did root... no?  Or maybe you're a Canadian Rogers customer, where 2.3 Gingerbread was available before it was for US AT&T users?  In any case, if the phone was rooted, then the response given here by "jec145" is, indeed, useful; but if the phone wasn't rooted, then it could not possibly be.

Additionally, assuming that one's a US AT&T Captivate user, how could one have possibly recognized a "teasing" pattern by only last summer (or have possibly had sufficient time to reasonably become frustrated thereby) when the official announcement (at least by AT&T, for its US customers) that Captivates would be upgraded to 2.3 Gingerbread was but days or weeks earlier?  (Yet another rhetorical question.)

My problem is I can't Kies Mini to this upgrade because I'm not on Froyo then found out Samsung withdrew Froyo from the links I had from last year.  So I apparently can't get back to Froyo...which was a dilemma not hinted to in all the forums that gave me the courage to flash to 2.3.3!  Samsung just told me I can't get back and to send in the phone for a complete reflash.  Wonderful. Anyone have any ideas of how to get to a point to do the Kies Mini upgrade?

Again, it's not Samsung with which you should be consulting.  The OS upgrade is a decidedly carrier-centric (AT&T for US users, and Rogers for Canadian users) sort of thing.  Samsung, indeed, does the work; and it is nearly always Samsung, and not the carrier, which is responsible when an OS upgrade is delayed (as was definitely the case with the 2.3 Gingerbread upgrade for Captivate users), but once the work is done and both Samsung and the Carrier agree that it's the way the carrier wants to release it, it's the carrier, and not Samsung, which primarily supports it.

If you're in Canada, and you're a Rogers customer, then well-illustrated by all this is the value of each user, here, making sure to specify his/her geographic location in his/her profile, here.  And so, if what I'm about to write doesn't apply to you because you're not an AT&T subscriber (because you're a Rogers subscriber), then your not having specified, in your profile, here, that you're in Canada is the reason.

At any rate...

...if you're an AT&T Samsung Captivate user, then you can take your phone to your nearest  AT&T Wireless Device Support Center...

http://www.att.com/esupport/article.jsp?sid=KB91429
(scroll down to item 3)

...and have them flash the phone back to 2.2 Froyo... the absolutely latest, in fact, version of 2.2 Froyo for the Captivate as of this writing, to wit:

Firmware version 2.2
Baseband version I898UCKB1
Kernel version 2.6.32.9
Build number FROYO.UCKB1

NOTE:  As I was typing the immediately-above, I thought to myself, "Wait a minute... I thought UCKB2 was the most current baseband version," and I then even consulted my notes regarding both the Captivates which my wife and I purchased at the end of October 2011 (both of which were manufactured in September 2011).  Sure enough, both phones were shipped from the factory with baseband version UCKB2, not the UCKB1 version to which AT&T Wireless Device Support Centers -- at least the one nearest me -- are currently flashing.  

So, then, maybe AT&T Wireless Device Support Centers are not, after all (either that, or at least the one nearest me isn't), flashing to the absolutely latest 2.2 Froyo version.  The version that the center nearest me is flashing is still kernel 2.6.32.9, but it's just not baseband UCKB2.  Instead, it's UCKB1...

...which, when it comes to getting the phone to a state which best predisposes it to a successful 2.3 Gingerbread upgrade (and trouble-free post-upgrade general usage) may be good enough.  I suspect it is, but I'm now sure gonna' call the guy I now know at the AT&T Wireless Device Support Center nearest me and chat with him about it.  This is actually quite irritating, come to think of it.

It's even further frustrating, in my case, because when I spoke with the AT&T Wireless Device Support Center guy on the phone last (as of this writing) week, he said that the Samsung rep had been in his center that very week, and had upgraded both the flashing software, and the ROMs, to the allegedly absolutely latest and greatest possible available versions.  He made a big point of telling me that.

[sigh]  Oy.  Every time I turn around, this all just gets more and more unnecessarily complicated. [sigh... yet again]

Anyway, that having been lamented, if all that really matters to the recently-released 2.3 Gingerbread upgrade (in order for said upgrade to be successful, and for post-upgrade phone behavior to be trouble-free, as both the AT&T and Samsung engineers experienced when testing the recent 2.3 Gingerbread upgrade) is that the phone being upgraded is, prior to said upgrade being applied, simply running 2.2 Froyo, kernel 2.6.32.9, regardless of baseband version (as I suspect is the case), then no harm, no foul, I suppose.  But, still... I'm just sayin'. [shakes head in disbelief]

UPDATE Thu 26 Jan 2012:  I called my contact at the AT&T Wireless Device Support Center and asked about the UCKB1 vs. UCKB2 thing.  He said the Samsung rep actually made a point of talking about that when he upgraded the center's software; and he apologized for not covering it with me when I was there last Saturday.  He said the Samsung rep said that UCKB2 ended-up not being as stable as Samsung had hoped it would be; that UCKB1 is actually more stable, and that a corporate decision was made to only ever flash Captivates to the more stable UCKB1 at AT&T Wireless Device Support Centers.  I asked him if UCKB1 or UCKB2 better predisposed the phone to the 2.3 Gingerbread upgrade, and he said it mattered not.  He added that, in fact, it was during testing of the 2.3 Gingerbread upgrade that some of UCKB2's instabilities were discovered; and that it's actually better (though, admittedly, only marginally so) to perform the 2.3 Gingerbread upgrade on a UCKB1 phone; that statistically more upgrade successes were experienced during testing on that particular build.  But he said that the differences between UCKB1 and UCKB2 were so insignificant that it didnt really matter much to which build the 2.3 Gingerbread upgrade is applied, as long as it's being applied to 2.2 Froyo.  He closed by assuring me that even though my phone came with UCKB2 from its September 2011 manufacture date, it's actually a better phone with UCKB1 on it; and that even if I insited on UCKB2, he was not equipped to do it... that the Samsung rep didn't include UCKB2 in the update.  I'm still trying to decide how much of it to believe, but that, at least, is what he said.


Regarding Kies Mini...

...it's available for use (on Windows machines, via a USB connection between said Windows machine and the phone) with all US versions of the AT&T SGH-I897 (Captivate); Kies Mini version 11011.4, updated September 27, 2010; 41MB in size; compatible with Windows XP, Windows Vista, and 32-bit Windows 7 (fully; and 64-bit Windows 7 only partially) directly from the Samsung web site.

Begin here...

http://www.samsung.com/us/support/downloads

...then specify "Cell phones" under "Category"...

...then specify AT&T as your carrier under "Sub-Category"...

...then specify "SHG-i897" under "Model Name"...

...and then it matters not what you specify (in other words, just pick one) under "Model Code" because they all result (as of this writing) in the exact same downloadable version of Kies Mini (version 11011.4, updated 9/27/2010) that I just specified, above...

...then click on the "Find it" button...

...then once you arrive on the "Manuals" page, simply click on the word "Software" (to the right of the word "Manuals"); and then click on the little "EXE" icon for the Kies version dated September 27, 2010 (the lowermost of the two versions shown there) to begin the download.

Either that, or just go straight here...

http://www.samsung.com/us/support/downloads/at-t/SEG-I897ZKAATT

...then click on the "Software" item (to the right of "Manuals")...

...then click on the little "EXE" icon for the Kies version data September 27, 2010 (the lowermost of the two versions shown there) to begin the download.  

In either case, before you actually install and use Kies Mini...

...remember that the Windows machine on which you're running it may (most likely will, especially if you've never before connected a Samsung smartphone to it) require that you first download and install the official Samsung Captivate USB drivers...

...which, curiously, no longer (as of this writing) seem to be available on any of the above-referenced Samsung software download web pages for the US (AT&T) SGH-i897.  While this would normally make me wonder if they're now built-right-in to the 41MB Kies Mini installer download, I happen to remember downloading that very installer in the first week of November 2011, and at that time the Captivate USB drivers were required (and were also downloadable from the very same Samsung web site SGH-i897 software download page).  

Hmm.  Interesting. [and, again, sigh]

Well, while that's certainly vexing, it doesn't really matter much because, according to the official CAPFAQ web site, you can also get them here...

* Captivate USB drivers for 32-bit Windows machines
* Captivate USB drivers for 64-bit Windows machines

...both of which, I assure you, are fine (safe, virus-free, etc.).  If Kies (any version, but specifically Kies Mini for US AT&T Captivate users) doesn't work right, then uninstall Kies Mini; then install the appropriate USB drivers; then re-install Kies Mini. NOTE:  Personally, in my case, I didn't even test Kies Mini until after I had installed the appropriate USB drivers... in other words, I just installed them, whether or not I thought my machine actually needed them; and then Kies Mini, once subsequently installed, worked perfectly.  I, therefore, recommend that everyone else do the same... but, hey... that's just me.


For those not in the US, get Kies Mini here...

http://www.samsung.com/us/support/downloads/global

...which, yes, is still being downloaded from the US Samsung web site (go figure); and the use of which also may or may not be successful unless the aforementioned USB drivers are first installed (and were I you, I'd just go ahead and install the drivers first, regardless).


There is also a full (as opposed to the "mini") version of Kies available from numerous non-US Samsung web sites (and also here, from Softpedia), but unrooted US Captivate users generally report that it won't -- even with the USB drivers installed, and no matter how the Captivate's...

Menu > Setup > Applications > Development

...settings are set -- properly communicate with the Captivate; nor will it allow any OS upgrades.  So, therefore, it's really only "Kies Mini" that will work, via a USB connection between the computer and the phone, for purposes of applying the 2.3 Gingerbread upgrade to a 2.2 Froyo Captivate for US AT&T users...

...or at least that's how it's all supposed to work; other users' actual mileage may vary.


Hope that helps!


_____________________________
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com

[bigKb0y]

First off I have to say that I love reading all of these posts on different from 1 or 2 months ago by people saying that AT&T will not release a Gingerbread update and they are switching carriers blah blah blah. It's silly that people are so determined to get an update that they are willing to switch carriers or even to an iPhone. It's also silly that people think that complaining on forums is going to make them release one sooner. They think that they know why AT&T has not released one but they have no idea. I could have cared less if they released a Gingerbread update or not, my Captivate has been working fine with me. Of course it has bugs but they always will. I'm sure they have their reasons, whether it was taking their time "loading the OS with junk" or holding off as a strategy to get people to go ahead and get a newer phone. Whatever it is people need to just stop flooding the forums with their stupid opinions and misinformed rants and accept the fact that AT&T will do what they do. Anyways 

I installed the Gingerbread 2.3.5 update (Kernal version 2.6.35.7-I897UCKK4-CL614489 Build number GINGERBREAD.UCKK4) on my non-rooted Captivate, which I bought in October and came with Froyo, through Kies Mini last Saturday. I went ahead and backed everything up and the whole upgrade process took about 5 minutes before my phone booted back up into the OS. I'm not missing anything that I used before and have had no problems with any of the apps that I normally use yet. It seems to be a great update with noticeable improvements. I have noticed a lot less lag and lock ups. I have only had my phone physically lock up once or twice before and one of the times my daughter was using it and doing all kinds of stuff so it was understandable. I haven't experienced any hard lockups yet but of course I have only been using it for 5 days.

Improvements:

They weren't joking about the improved battery life! I could usually get my phone to last me around 24 hours unless my daughter played her apps and then it would end up being 12 - 14 hours. I seem to be getting an extra 4 - 5 hours now!

The phone seems to shut down and boot up significantly faster now. When I would power off the phone before it would play the tone, screen goes black and then 20 - 25 sec later the phone would vibrate. Now it takes maybe 10 sec before the phone vibrates. When I would power on the phone before it would get to the idle screen, saying scanning SD card at the top status bar, but I couldn't unlock the phone with my pattern for probably 30 seconds because it would be running so slow that it wouldn't register most of my finger motions. Even after finally unlocking the phone it would run very slow for another 20 seconds. Now I can give it 10 seconds after the idle screen and I can unlock it and it runs fairly fast!

The new icons and status bar look is great. The ability to scroll from your last desktop page to the first is nice. You all already know about this stuff.

Bugs/Quirks:

Sometimes after my screen times out and goes black I will press the unlock button but nothing happens. I have to press it a 2nd time for the screen to come back on. It's another minor bug that I can deal with and get used to but I haven't seen it mentioned on here so I am curious if anybody else is experiencing this.

The default browser now has a feature where you can do a finger motion to bring up the open tabs. I have experimented with it and the only way that I can replicate it every time is to imagine an imaginary line dividing the screen down the middle and then taping a finger in between the left side of the screen and the line and another finger between the right side of the screen and the line at the same time and sliding them in towards the line. Kind of like the finger motion to zoom the page in. If I press my fingers down on the screen, hold, and do the motion it zooms but if I tap them on the screen, quickly give them a little slide inward and release it brings up the tabs every time. I do this accidentally all the time when trying to zoom in on websites and it is pretty frustrating. Is anybody else experiencing this problem?

The dreaded tethering error. I usually get it when I plug my phone in to charge, whether it is in the wall charger or in my computer, it gives me the error any time I unlock my screen while it is charging. I tried turning my wi-fi off and I got the error. I turned the wi-fi back on and got the error again. I never disable my wi-fi so I never really see this error unless I use my phone while it is charging or just 1 time after my phone gets done charging.

[DesElms]

First off I have to say that I love reading...
[...]
...while it is charging or just 1 time after my phone gets done charging.

Interesting!  Thank you!

I, personally, would not be willing to live with those glitches (despite the obvious improvements).  I don't have the patience... but, hey... that's just me.

That's the primary reason, though, that I prescribe backing-up everything, then doing the Factory (actually, the GSM) Reset to restore to pristine 2.2 Froyo exactly as it shipped from the factory, then immediately (before the 2.2 Froyo has a chance to become un-pristine... <rhetoricalquestion>wait... is that even a word?</rhetoricalquestion>) applying the 2.3 Gingerbread upgrade...

...but, again, that's just me.

I'm also beginning to consider the possibility that when it comes to these phones, maybe (and I stress that word, 'cause I'm still pondering it), just philosophically, we should all consider the OS version to be as much a part of the phone as any of its hardware components; and that for statistically optimum performance, we should just stick with whatever OS came with the phone and look forward to an OS upgrade only with whatever phone to which we eventually upgrade.  Hmm.  Dunno... just wondering.

Anyway, thanks!


_________________________________
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com

[blowfish]

Hey guys, we've had some good discussions on here and I've read them all, but I am still unclear what issues might pop up if I do a GSM/Factory reset BEFORE upgrading to 2.3.  The issues people have reported, I'm not sure if they did this beforehand or not.  Anyone want to chime in with results from doing a full reset beforehand?  Currently, I'm running 2.2 with practically no issues and don't want to deal with freezing or weird reboots, etc.  Although, I would like the 2.3 features, so I'm still on the fence.
Thanks.