[Tilt, TyTN II, MDA Vario III General] jgermuga:
Are you saying software/firmware has nothing to do with it? If this were true, every benchmark test would come back the same regardless of the ROM, registry settings, installed software, etc. You are contradicting yourself.

I never claimed to be an expert. This is an extremely basic concept, almost common sense really. It's about the scientific method which my 6th grader is learning about right now. The more variations within the sample, the less likely the results will correlate.

For instance, her sciense project was to see if a sports drink made a difference in how fast someone could run a quarter mile. As it happens, one of the boys tested ran faster every time than one of the girls tested, with or without the sports drink. Does this prove the sports drink helped him run faster?

Since we're doing research as you say, I'll even throw in a citing from wikipedia

"the dependence of confidence is high if the noise is low and/or the sample size is large and/or the effect size (signal) is large. The confidence of a result (and its associated confidence interval) is not dependent on effect size alone. If the sample size is large and the noise is low a small effect size can be measured with great confidence. "

I think what you may be trying to say is the noise is low. How can you say the noise is low when the ROMS, registry settings, installed programs, etc, etc are all over the map. This means high noise which means you need a very high sample size or a very large difference in results to reduce the bias of noise. The large difference in result would also need to be in the same way per one or more of the 5 tests being run, not the composite score, and in the same direction I might add.

If we could eliminate all noise, as I have already proposed, the best sample would be two devices only, one with the drivers and stock ROM, one without driver and a stock ROM.

And let's keep in mind that the tests you are running do not even test the capability we are talking about.

What is more likely is since the drivers are not present, the normal CPU needs to take over the tasks for graphics rendering, which runs the risk that outside processes will have a greater impact on the devices ability to process graphics capabilities. So if it has to take time out to play sound, or to respond to a screen tap, there goes the video performance. If the device had the proper drivers, these tasks would be isolated and prioritized such that audio or a screen touch interrupt would have no impact on the video rendering. In this case, the test may be of some limited value. But as far as a potential lawsuit goes, this is probably still too much noise in the sample to prove the hypothesis I have just made.

I bet you could, by the way, run the same test while receiving a call and while not receiving a call and see no difference in the numbers because the radio is cordoned off to a sperate process. This is to make sure your phone call doesn't get squashed by the video you are trying to play.

Pardon me for trying to keep a thread on topic, which is not about the search for a solution, it's about how to get the word out that this is an issue and how to support a case if we decided to go that route. And at least I was polite about it, which you have failed to do.

At any rate, I agree not to come to your new gruesome thread and start asking incessently when the lawsuit is going to start, if you stop trying to argue these benchmarks have something to do with raising awareness or that they would be useful in any court of law.