Alleged 2.1 slowdown explained

[kellex]

Its interesting. At our site, we put everyone to the test and almost no one saw such a dramatic decrease as is represented in that video. In fact, almost everyone hovered around at least 40FPS. I know it's not 60 like the 2.0.1 Droid is showing, but not bad.

2.1 Update Slowing Down Droids? | Droid Life: A Motorola Droid Blog

 

[Martin030908]

* starred *

let Google/Moto know.

 

[tonydelite]

Does anyone want to try doing a full factory reset + cache partition clear and post before/after results? There are some people who say the droid feels much snappier afterwards.

EDIT: The instructions for a full rest + cache partition clear is right here http://www.droidforums.net/forum/dr...own-issues-2-1-update-factory-rest-fixes.html look under the "more involved way" section.

 

[tonydelite]

FYI my numbers are avg=36 min=10 max=124

off of a fresh reboot. v 2.1 OTA update

 

[k1ng617]

Thanks to all who posted their results from FPS2D. Did most of you see a bell curve, 1 middle peak, or did most see 2 peaks?

I feel this is most important because our minds don't recognize 30fps as either slow or choppy, in fact if I'm not mistaken, most TV is displayed at 30fps. Furthermore, I think most films & Blurays display at an even lower 24fps. I also averaged around 40fps but it jumps around so much my eyes interpret the difference as a lagginess/choppiness.

Does anyone want to try doing a full factory reset + cache partition clear and post before/after results? There are some people who say the droid feels much snappier afterwards.

I did a Privacy Menu reset and it definitely eased the Droid interface slowdowns, but the Emulator/2D game performance issues remain.

 

[tonydelite]

I saw 2 peaks.

 

[wernst]

I see two peaks, though the green is flatter and shorter than the red.

On my Bugless Beast .9 rooted droid overclocked to 1000 MHz , my speeds over a few passes are:

fps=25 avg=35 min=7 max=280
30, 31, 7, 280
32, 34, 13, 185
66, 32, 13, 282
29, 31, 13, 297
30, 32, 12, 289

Hmm. Some variability in there...

-Warr

 

[k1ng617]

A sad day to be a Droid owner...beaten by the ancient G1.

This was taken from the Google complaint. Issue 7520 - android - 2D frame rate cut in half after Motorola Droid 2.1 update - Project Hosting on Google Code

"OK, here are the results of FPS2D on some from my fleet of devices, in order of
decreasing age:

G1 (1.6): avg 58, normal bell w/ peak at 62
Ion (1.5): avg 58, normal bell w/ peak at 63
Hero (1.5): avg 53, flatter bell w/ peak at 63
CLIQ (1.5): avg 76, normal bell w/ peak at 80
DROID (2.1): avg 34, dual-peak bell w/ peak at 31"
Nexus One (2.1): avg 55, normal bell w/ peak at 62

 

[adrynalyne]

What exactly do you need above 30fps in 2D?

 

[k1ng617]

What exactly do you need above 30fps in 2D?

The issue is not the overall average, though that highlights the issue well, as much as the inconsistency of it as I expounded on before.

 

[adrynalyne]

That has to be the most words I've ever seen anyone use that says absolutely nothing.

Let me repeat what i said:

What exactly do you need above 30fps in 2D?

 

[cereal killer]

That has to be the most words I've ever seen anyone use that says absolutely nothing.

Let me repeat what i said:

What exactly do you need above 30fps in 2D?

nothing.

There is no use for more than 30-40 fps in 2D graphics.






Sent from my Droid using Tapatalk

 

[k1ng617]

yea and I said that wasn't the point

 

[k1ng617]

and if it averages 30-40 it dips much lower than that

 

[adrynalyne]

Oh is that what you were trying to say?

So what is the point? We should all be upset that we can no longer get 60 fps in 2D, when we wouldn't have noticed it in the first place?


I'm confused.