The Froyo Code Drop | Hacker News Reader

The Froyo Code Drop

android-developers.blogspot.com

52 pointsmattyb16 comments

Check your build.. you'll have to go ERD79 to ERE27 to FRF50 and FRF72. FRF50 and 72 are Froyo but they are also NOT the final Froyo release for N1. These are test releases however they are signed by Google.. totally legit i.e. stock firmware and bootloader will gladly accept these. stay away if you're on an ATT N1 (or Rogers).

I have the Rogers/ATT N1, build number is EPE54B. So first step is to get ERD79, then ERE27, then FRF50 and FRF72?

The FRF50/FRF72 updates were built for the T-Mobile N1; they will not run on the Rogers/AT&T Nexus One

Why the sequence? And where can I get the final release? (And where check the build?)

The sequence is because Google uses binary diffs for their updates.

The latest release candidate (?) is FRF83. You can download an update.zip from http://android.clients.google.com/packages/passion/signed-pa... (requires updating to FRF50 first).

You can check the build in Settings -> About phone -> Build number.

OK, so I could also install FRF83 directly without going through the updates?

No, FRF83 has been published only as an update from FRF50 (using the link above) or from FRF72 using http://android.clients.google.com/packages/passion/signed-pa....

If you are running the stock Android 2.1 image, you'll receive an over-the-air update whenever Google deems it ready for general release. Or you can update your phone now to FRF50 or 72 and then to 83.

Thanks - so I guess since I have installed some Froyo image before, I will never get a push from Google for the final release anymore?

If you installed one of the Froyo updates direct from Google, then you will continue to receive future updates. If you unlocked your phone and installed a modified or custom image from another source, then that image probably has OTA updating disabled and you will need to apply updates yourself.

If you flash back to a stock image from Google, then I believe you will start receiving OTA updates again.

Now to wait for the Cyanogen Froyo ROM for my G1.

Those who have an HTC HD2 (aka HTC Leo) may want to keep an eye on http://forum.xda-developers.com/showthread.php?t=651632 (Development thread for Linux/Android on the HD2).

In short, there isn't (yet) Android on the HD2. Perhaps this code drop will help.

Does this mean I can grab it for my Nexus One and install it now? Or are they still pushing out things via the Over the Air updates?

I'd really like tethering...

Yes.

"We’ve also incorporated into the core platform all the configuration files necessary to build the source code of Android Open-Source Project on its own. You can now build and boot a fully open-source system image out of the box, for the emulator, as well as for Dream (ADP1), Sapphire (ADP2), and Passion (Nexus One)."

I wonder how good it will run on the Dream (ADP1) though. Open Eclair was not much fun.

Open Eclair on Dream always had issues, partially because they never finished reverse-engineering all the closed-source drivers. CM5 on Dream has been quite nice for me; it can get a bit laggy sometimes, but beyond that has worked well.

It'll be interesting to see how Froyo's JIT fairs on Dream, for sure.

If you have unlocked your Nexus One (using "fastboot oem unlock") then you can build Froyo from AOSP and install it yourself (or you can download and install a build by someone else if you trust them).

If you do not want to unlock your phone, then you will need to wait for a signed OTA update from Google.

The AOSP build does not include any of the Google apps or frameworks (GMail, Google Maps/Navigation, Market...). You either need an official Google build for that, or you need to use one of the methods to copy those apps from a image that has them.

If you have FRF50 try this http://www.androidpolice.com/2010/06/23/latest-nexus-one-fro...

edit: BobbyPhoenix (check link above) claims that if you have FRF72 you can flash back to FRF50 and then apply FRF83 and it will work.

Reply on news.ycombinator.com