I was referring to the OP's home screen swiping issue, not giving a broad generalisation of all animations/frame rate - neither was I saying that the Nexus One has a better framerate than the iPhone.
I own a Nexus One and an iPhone 3GS - I'd definitely counter that my Nexus One is competitive to my iPhone on performance (though the iPhone out-performs it by a smidgen). What I do notice though, is when I launch certain apps or home screen widgets, the background tasks can sometimes interfere with the foreground activity. Even the home screen. This has been particularly noticeable for Twitter/Email/News apps, some of which start pulling data across the network and processing it regardless of the current resource usage (for instance, whilst I'm in the middle of a game). My iPhone on the other hand does not experience this kind of problem. The other thing to watch out for is the Live wallpaper feature. I haven't noticed much difference in performance personally, but I wouldn't be surprised if certain live wallpapers become very resource intensive, sometimes enough to start interfering with the home screen swiping animation. On Sun, Feb 7, 2010 at 1:01 PM, Ralf Schneider <[email protected]> wrote: > 2010/2/7 Sean Hodges <[email protected]> >> >> I don't see any choppiness on my Nexus One. I suggest you take a look at >> the appwidgets you are using, perhaps one is updating too frequently... > > Really? My wife has an IPhone and I own a Nexus One. There is a huge > difference in smoothnes of all animations, even with no appwidgets. > On the IPhone all animations seems to run with constant 60 FPS, whereas on > the Nexus One the frame rate is never constant. If a garbage collection > kicks in things get really slugish. > > My guess is: > Because the IPhone has known hardware specs it is possible to design a GUI > and animation framework which runs with a constant high frame rate. The > kernel is probably tuned to treat screen updates and animations with > soft-real-time constraints. It doesn't hurt that apps are written in a > compiled language which is suitable for this kind of device. > > On the other hand: Devices running Android have a wide range of capabilities > (cpu speed, graphics hardware acceleration, screen resolution, ...) . Apps > are interpreted. There is no concurrent garbage collection. Parts of the > hole frame work seems to be really slow. Simply touching the screen triggers > a process which burns an enormouse amount of CPU cycles. > > And most important: It seems Android was not designed to have smooth > animations. Smooth animations requires a software stack which is designed > under this constraint. It can not be an after thought. IMO with the current > software stack even a device with a dual core 2 GHZ CPU will not run as > smooth as the first IPhone. > > But I prefer Android, anyway. Except of the slugish animations and the > android market I really prefer the Nexus One over the IPhone. > > Regards, > Ralf > > -- > You received this message because you are subscribed to the Google Groups > "Android Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/android-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
