(Posts: 14255; Member since: 19 Dec 2008)
if it was google that forced the hold, u cant be mad at sammy. Besides, it still one of the first to get 2.3.3 anyways. It would have been "the first" had moto not snuck out the droidX update.
Now if the rest of us galaxyS users are still waiting for it after everyone else gets it, then its time to be annoyed. But i dont think thats going to happen again. (I hope) sammy learned their lesson with 2.2.
Fascinate users yell at VZW for holding 2.2 back, not Sammy.
(Posts: 7296; Member since: 05 Dec 2009)
"It would have been "the first" had moto not snuck out the droidX update."
*snickers* Tee hee hee. :D
I'm happy to see Gingerbread rolling out to more manufacturers. If it works anything like it does on the X, it's extremely fantastic.
(Posts: 1227; Member since: 05 Nov 2010)
Gingerbread update for Galaxy S would be only for the European version (most likely). I don't really care if the Galaxy S gets Gingerbread any more; all I really care about is if and when the Desire Z/Evo Shift is going to get Gingerbread.
I don't know if I'm "one of the lucky ones" or one the unfortunate ones for downloading it the very moment it came online here in the Nordic region.
First of all it screwed up my whole phone. The lockscreen lacked the bottom part (the time was shown sliced into half), the status bar went completely missing and the phone constantly told me it had been force closed. After a factory reset everything seems to be working and quite snappy. Merely some visual changes have been made and minor speed increases, otherwise I don't get what's the big deal about Gingerbread. No new highlights like with 2.2 offering Adobe Flash support and SD-card use for apps. Pretty lame of Gingerbread just to offer a general speed boost and a batterylife improvement (or so they say). My unit seems to lose batterylife more quickly now, I dare say. After I loaded it up to a 100% it immediately after unplugging changed to 92%. It has never done this before, so where's the improvement? Furthermore normally I've still had like 80% juice left after a working day, but now it's down to a little over 60% with NO MORE USE than before.
Care to explain Samsung and Google, HMMM? :/
First of all, you were suppose to do a factory reset. Second, if you only get 92% when unplugging, are you sure it was fully loaded when flashed? Third, you won't be able to know for sure if the battery life is better or not before you have charged it fully and completely drained it three times. 'cause that will optimize the performance of the battery.
One thought on why it might have been held up... There has been complaints and reports that an xml-file that controls the multitouch is missing... Making the phone react to only one touch at a time... =(
Don't know for sure, haven't upgraded myself.
I can confirm that with my unit running 2.3.3 there is absolutely no problems with multitouch. Tested it with both the browser and images. I don't understand what you mean by "flashing". I only know Adobe Flash and Flash memory, but not a verb "to flash something". But thanks for the info. My unit was fully recharged when I upgraded it, yes.
I didn't know that optimization thingy. Thanks for the tip! I know that happens when you first buy the phone, but didn't know upgrading would require that again. I mean recharging multiple times.
Is this 2.3 available for the US GalaxyS lines as well?
I was one of the (un)lucky ones.
Flashed my phone, never manged to re-start it. It will go blank screen imediatelly after the S logo and will vibrate randomelly (menu and back buttons lid).
After few more attempts, I had to wipe it out and reset to factory settings (nothing else worked).
After reset it was back to Froyo. I tried again but KIES said I'm on last version ( I guess this is when it was pulled out).
One very important note (saying at the end just to make sure you'll read the rest :)). I had a lag fix installed and did not uninstall it prior to upgrade attempt.
any custom patches(like lagfix in this case) will not work when installing a standard update, that can be the reason why your phone did not manage to start...u can try again after uninstalling the lagfix..that should work
(Posts: 2892; Member since: 19 Jun 2010)
So, a Samsung Android phone, and a delayed OS update? This is news all of a sudden?
who know's when that rollout will hit the states, bah...I'm on MIUI 2.3.3 gingerbread for over a month now, except for the bad battery life on MIUI I love Gingy! wonder if we'll get honeycomb on Galaxy S....
Expected! Seriously man. We all know whats up
Running Gingerbread 2.3.3, custom rom. Simply marvellous.
Go ahead and update, you know you want to!
Le me guess maybe this time samsung did it right then google pull it off because it is too fully featured as i was reading the 19000BUJV4 changelog. google must be like "hey those special feautures is only for nexus (google phone), Take off the gingerbread keypad, Its exclusive only to nexuses,
I'm so happy with 2.2.1 on my Galaxy S that I'm more than willing to wait for the Gingerbread goodness. I just hope the browser in Gingerbread is as smooth as it is in 2.2.1 (by far the smoothest and most responsive Android experience out there).
I'm wondering if pulling the Gingerbread update has anything to do with Apple suing Samsung for "copying the iPhone"...