09
Jun
image_thumb1681

A few weeks ago, Froyo started to find its way onto the phones of a few lucky journalists and random twitter users, and then eventually into the hands of the hackers over at XDA-Developers.

At the time, speculation abounded as to whether or not this was the official OTA. It wasn’t until a few days later when we received word that this was actually a release candidate, intended for a small group of testers and not consumption by the general public.

Since that revelation, users have been anxiously awaiting an announcement from Google regarding the official, final OTA. When we quoted our inside source at Google who revealed to us that the leaked build was indeed a release candidate, they made sure to emphasize that a release candidate is usually close to the final version and that unless bugs are found, it may very well end up being the final release.

Information has been sparse since then, but our own Ian Douglas found the following quote from Google employee ‘ben1010’ on the Android support forums:

Hi everyone,

I feel your anxiety, and though I'd love to give you all a definitive date, that's not possible, because there is no date. What I mean is, it's not that there's a Froyo release ready to go, and we're holding it back, or waiting for the right time to release it. That's not how it works. Software development is an iterative process, and each release candidate goes through extensive testing.

Sometimes, the testing exposes issues introduced in the new version, and the release gets delayed as a result. And so, although we know that we are pretty close to having a final build, we won't be sure of the release date until it arrives, and at that point the release goes out to the public without any further delay.

It's a bit like a baby -- the delivery date is a best guess, but if the baby has other ideas, we all have to wait ...

Ben

After reading that, I had an initial feeling of disappointment (I want my Froyo now!), that quickly gave way to that of hope. Why? Well, like many, I chose to flash Froyo onto my phone, and while it did run well, it still had its fair share of small kinks – enough that I chose to scrap Froyo for the time being and go back to the latest Cyanogen mod.

The fact that the Froyo is being delayed for further development means that they’re taking the time to properly iron out these kinks so that by the time Froyo hits your handset, it should be a smooth and delicious experience, rather than melted and sticky mess. I know we all want Froyo, but let’s give Google some time to throw a cherry on top.

Source: Android Support Forums

Chris Dehghanpoor
Chris is an Android devotee based out of Houston, TX. He enjoys indie rock, general geekery and long walks on the beach. If you can't find him online, he's probably playing Plants VS Zombies.
  • http://www.typhonrt.org/ Mike Leahy

    Well.. bugs are being found by us game devs for sure using the RC version. One big one regarding OpenGL 2.x quite likely would have gotten into the final build if us game devs didn't try the RC. Major credit for almost a crippling bug went to this fellow though:
    http://apistudios.com/hosted/marzec/badlogic/wordpress/?p=688

    Honestly I strongly believe Google should start an official RC process to give developers early releases, so that we can inform them in advance of issues that they may not be testing for or have yet in the compatibility test suite which supposedly has 20k tests.

    If the above issue I mention does indeed ship with 2.2 / FroYo it will cripple official OpenGL 2.x support for months and months if not more than a year given how only some devices receive new OS updates and often not long after it's released.

  • Josh

    Say if we are running froyo now, will we still be able to receive the official update and use it?

  • http://www.typhonrt.org/ Mike Leahy

    @Josh: This is my understanding of the situation that if you are running the FroYo RC that was posted for a short time after I/O you will still receive the full OTA when it is available.