Is the lack of speed and lag really that bad?

Having used a Motorola Droid and Nexus One and watching the video that was just posted about the Aria and benchmarking between the EVO, Moto Droid, N1 and Aria I can see where people think its sluggish.

http://www.androidcentral.com/htc-aria-benchmark-tests

In normal computing its fine. It was the fastest of the 3 phones (N1 has Froyo so doesn't count due to JIT) and in 3D they all spit out similar benchmark values. However the 30 FPS cap seems to affect its 2D rendering (most notable in the last benchmark of the video and in the screenshot of the 4 devices). 2D is what you use when interfacing with the phone aside from 3D games so this affects its performance the most.

In use, the Moto Droid and EVO seem to "hickup" while scrolling through applications and some games that are 2D while the N1 is smooth as butter. The new Droid X seems to be very smooth and I would love to see a similar 2D benchmark ran on it as well.
 
As others have said, the FPS cap is what causes the "lag". The droid doesnt suffer from this issue, so it would only seem faster from a visual standpoint.

Once someone figures out how to remove the cap, it should get a lot better. perhaps this is one of those things that will be fixed in 2.2?
 
The truth of it all is, YES, the incredible is Faster then the EVO. I own both, and I will tell you that the UI, navigating through the entire OS, Web sites, just about everything, is faster on the incredible. Now if you have never seen or used an incredible, you would not notice any speed dismay from the EVO, because its still a very fast device. However the incredible just has no lag, and really shines in that whole area.

Overall, the EVO is still an awesome phone. And it can become a Sprint/VZW debate real fast, which can most likely explain the faster web speed of the incredible. But moving away from data speed, and looking at the EVO from a whole, I would think Froyo fixes all this when it gets pushed out and hopefully ereases any slowdown or lag that is present.
 
As others have said, the FPS cap is what causes the "lag". The droid doesnt suffer from this issue, so it would only seem faster from a visual standpoint.

Once someone figures out how to remove the cap, it should get a lot better. perhaps this is one of those things that will be fixed in 2.2?

At first, I was really thinking that the 30 fps cap may be the culprit to these lag issues on the Evo. But now, i'm thinking it is the touch input lag or it's a mix of the fps cap AND touch input lag.

A member at xda actually showed a similar multi-touch test that android central did comparing the Evo and Nexus One. On both videos the multi-touch tool showed significant touch input lag.

Android Central's video: YouTube - Multitouch on the Sprint Evo 4G

User Mecha2142 on xda's video: YouTube - HTC Evo Touch Sensor Lag

XDA's thread: Significant touch input lag on the Evo - xda-developers
 
I think those reporting EVO lag are either all out GEEKS, haven't got the EVO yet or expecting waaaaay too much.

You will be hard pressed to find a perfect phone.....and you won't find a better gadget today, than this beast. Tomorrow? There will be better gadget yes, but today? It's the EVO. (read this again tomorrow)
 
Where in the hell did anyone hear that the Evo was slow and sluggish!? What complete bs.
 
I think those reporting EVO lag are either all out GEEKS, haven't got the EVO yet or expecting waaaaay too much.

You will be hard pressed to find a perfect phone.....and you won't find a better gadget today, than this beast. Tomorrow? There will be better gadget yes, but today? It's the EVO. (read this again tomorrow)

The fact is there are other phones out there that do a much better job with input than this. There were phones doing this better two years ago. Just because you don't care about it doesn't make it an invalid point for anyone else.
 

Trending Posts

Forum statistics

Threads
956,426
Messages
6,968,205
Members
3,163,542
Latest member
04ijordan