They Said it Couldn’t Be Done: Froyo on the G1 (Video)


It wasn’t long ago that Cyanogen and his team got Android 2.1 working on the G1 (video) — a feat that many said couldn’t be done.

Now they’ve gone and proven everyone wrong again: Froyo (Android 2.2) can run on the G1 — and run well.

Of course, getting this up and running isn’t for the faint of heart, and it’s not yet “fully cooked” — it’s still a release candidate (more stable than alpha and beta ROMs, but still with some rough-edges).

Come take a look at the first Android phone running the latest Android OS!

First off, if you decide to put Froyo on your G1 you are assuming the risks — and hopefully have backed up already. When flashing custom ROMs, doing it wrong can brick your phone. Doing it right could turn you into the envy of all your friends.

Next, you’ll need to have rooted your phone, updated the radio, installed a custom recovery image, and successfully flashed the DangerSPL. (Be careful with that last one, doing something out of order or not having the right prerequisites could brick your phone.) For how to do that, follow these instructions.

Once that’s all out of the way you boot into recovery (hold the home button while powering up) and wipe. This will erase everything on your phone. After wiping, flash the Froyo ROM, then flash the Google app pack (both can be found here).

My upgrade didn’t go smoothly at all. Immediately after booting up the phone rebooted while I was in the “touch the Android to begin” screen. And kept rebooting.

After some searching I came across this thread which reports that boot loops are not uncommon with this release candidate. Generally speaking, boot loops of this sort are generally caused by a corrupt ROM, or a corrupt or incorrect Google app pack having been installed. In my case it was file corruption.

I backed up the data on my sdcard, ran some diagnostics in Windows, and was able to determine the sdcard was sick. (Which explains some of the problems we’d been having with apps on previous ROMs.) After some repairing I repartitioned and reformatted the card to fat32, then repartitioned and upgraded my ext partitions using RA-Recovery on the G1. After downloading both the ROM and the Google apps pack to the sdcard again, I rewiped and reflashed both packages. After that is was smooth sailing!

So far I am VERY impressed with the overall stability and performance of Froyo on the G1. Some things to note are that the stock Froyo launcher is just too heavy for the little G1, but that’s okay, this ROM comes pre-packaged with ADW.Launcher (which I replaced with LauncherPro right away). The 3D Gallery for your pictures is present, and functions quite well. The JIT compiler is disabled by default. If you’re using a 32A you have more RAM than the 32B, and JIT should work and give you a performance boost — but if you’re on a 32B, you may want to stick with the default. If you want to experiment, backup first, then toggle JIT in the Cyanogen settings, you’ll need to reboot for the changes to be applied.

All that having been said, this is only a release candidate. It’s purpose is to find bugs so they can be corrected in the final release.

Share This Post
What's your reaction?
Love It
Like It
Want It
Had It
Hated It
About The Author
Joe Levi
Joe graduated from Weber State University with two degrees in Information Systems and Technologies. He has carried mobile devices with him for more than a decade, including Apple's Newton, Microsoft's Handheld and Palm Sized PCs, and is Pocketnow's "Android Guy". By day you'll find Joe coding web pages, tweaking for SEO, and leveraging social media to spread the word. By night you'll probably find him writing technology and "prepping" articles, as well as shooting video. Read more about Joe Levi here.