Nexus One May Suffer from Same Framerate Issue as EVO


We reported recently that the EVO has been having some serious frame rate issues, namely that it is locked at 30 FPS in both 2d and 3d modes.  Now it seems that the Nexus One may be suffering from the same frame rate issue.

In a post over at, it is being reported that the XDA Forums are alive with posts saying that the N1 is having the same issues as the newer Sprint EVO.  This has been especially noticeable since people have been upgrading their N1’s to Froyo.

It seems that Google is not sure why this is happening, according to Android Framework Engineer Romain Guy, but that their target with Froyo is and always has been 60 FPS. A quote from the Dailytech article;

Android framework engineer “Romain Guy” isn’t quite sure where this problem is coming from.  He wrote a response, saying that for the record the “target was, is and will be 60fps.”  Strangely the Nexus One, which has official Froyo support already, also seems to be having the issue.  It at least starts out during the Froyo running load animation at 60 fps (which allows it to appear smooth), but its framerate subsequently drops to 30 fps upon reaching the home screen.

It seems that this might be related to something in the firmware that can be addressed with a patch. Let’s hope they can hunt down the cause quickly if two of the top Android phones have been afflicted.


  1. I ran some benchmarks on my N1 when the evo reported these issues. 60 fps here. Apparently someone wanted to stir up some more bad press.

  2. At Google I/O they showed a version of "Replica Island" with frame rates above 30 fps to show how much faster Android 2.2 is compared to 2.1. "Replica Island" ran on two Nexus One, one with Android 2.1 and one with Android 2.2. Even Android 2.1 had frame rates above 30 fps in the beginning of the demo.

  3. It's not bad press. This is actually a pretty serious issue. I've met it personally as a developer. On 2.2 an OpenGL game which runs smoothly on 2.1, runs like hell on 2.2. All we've managed to see at the moment is that this so called "pre-test froyo build" generates a LARGE amount of garbage collect actions(GC), which causes games to lag. I hope they fix this thing with the "official" build. And NO it's not inefficient or poor design in the game engine. It's simply 2.2 working in debug mode and generating too many logs and gcs. 2.0 and 2.1 run the game flawlessly.