So T-Mobile, When You Said Froyo Was “Coming Soon” for the Galaxy Last Dec. 2nd Did You Mean in Dog Years or Human Years?

Update: Apparently there is an actual update at this point, but you can only update doing a manual Kies update on your phone and only with a PC. I’m not sure why T-Mobile won’t push this out as an OTA upgrade or at least let us use a Mac. Trying to get the update software installed on a work PC as I don’t own a personal Windows machine anymore and our household has gone 100% Mac.

There is a comment in the comments section blaming Samsung for trying to charge T-Mobile for the upgrade, but Michael Gartenberg sent me a tweet over on twitter saying that this has been debunked by Samsung a while ago and that they don’t charge carriers for upgrades. This still leaves me scratching my head wondering who is to blame for such crappy customer service, Samsung or TMobile.

Update #2: I’m now running Froyo on my Samsung Galaxy Vibrant. It was a royal PITA. I made the mistake of following the link above which had me download Kies 2. Turns out Kies 2 won’t recognize this phone. So instead I had to download Kies Mini (which did recognize my phone). I had to do this all on a PC as there is no Mac version. Kies mini after three tries finally recognized my device and I was able to update it. An awful lot of trouble and work, but I am actually running Froyo now.

Loading Facebook Comments ...
11 comments on “So T-Mobile, When You Said Froyo Was “Coming Soon” for the Galaxy Last Dec. 2nd Did You Mean in Dog Years or Human Years?
  1. robk says:

    This is long, but sums up your situation.

    From XDA Forums:

    Hello,

    I’m going to step across the NDAs and explain the issues behind the Android Froyo update to Samsung Galaxy S phones in the United States. I think most of you have come to this realization yourself now: the withholding of the Froyo update is a largely political one, not a technological one: Froyo runs quite well on Galaxy S phones, as those of you that have run leaked updates may have noticed.

    To explain the political situation, first, a primer on how phone firmware upgrades work for carriers. When a carrier decides to sell a phone, a contract is usually written between the phone manufacturer and the carrier. In this contract, the cost of updates (to the carrier) is usually outlined. Updates are usually broken into several types: critical updates, maintenance updates, and feature updates. Critical updates are those that resolve a critical bug in the phone, such as the phone overheating. Maintenance updates involve routine updates to resolve bugs and other issues reported by the carrier. Finally, feature updates add some new feature in software that wasn’t present before. Critical updates are usually free, maintenance updates have some maintenance fee associated with them, and feature updates are usually costly.
    In the past, most phone updates would mainly consist of critical and maintenance updates. Carriers almost never want to incur the cost of a feature update because it is of little benefit to them, adds little to the device, and involves a lot of testing on the carrier end. Android has changed the playing field, however – since the Android Open Source Project is constantly being updated, and that information being made widely available to the public, there is pressure for the phone to be constantly updated with the latest version of Android. With most manufacturers, such as HTC, Motorola, etc. This is fine and considered a maintenance upgrade. Samsung, however, considers it a feature update, and requires carriers to pay a per device update fee for each incremental Android update.

    Now, here’s where the politics come in: most U.S. carriers aren’t very happy with Samsung’s decision to charge for Android updates as feature updates, especially since they are essentially charging for the Android Open Source Project’s efforts, and the effort on Samsung’s end is rather minimal. As a result of perhaps, corporate collusion, all U.S. carriers have decided to refuse to pay for the Android 2.2 update, in hopes that the devaluation of the Galaxy S line will cause Samsung to drop their fees and give the update to the carriers. The situation has panned out differently in other parts of the world, but this is the situation in the United States.

    Some of you might have noticed Verion’s Fascinate updated, but without 2.2 : This is a result of a maintenance agreement Samsung must honor combined with Verizon’s unwillingness to pay the update fees.
    In short, Android 2.2 is on hold for Galaxy S phones until the U.S. carriers and Samsung reach a consensus.

  2. CDS says:

    2.2 on Tmobile works if you just use the KIES on a 32 bit WIN machine. I like the added features and I have called in to tech support and they are still willing to help, like making your phone be a WAP. Nice feature and it works too, even though they say you are to call in and activate it for $15 more a month. Great for tethering the ipad or laptop off of for small searches or lengthy e-mails while on the ferry.

  3. JD says:

    I got a Samsung Galaxy I9000 in December and it came with Android 2.2. I’m on a local Alaskan carrier (GCI) but … I’m thinking 2.3 now – what is that – Gingerbread? Might have to grab an image off one of the root sites for that though as I doubt Samsung will roll it out for the “old” phone. Could be wrong though.

  4. JeffPHenderson says:

    Shoulda stuck with the iPhone after all then huh?

  5. lee says:

    its the same over here in the UK. This is definitely something Android needs to get figured out. I had to install XP on my mac down grade to an earlier update, then get the latest update! as you put it a PITA!!