Yeah, I've been using Android devices since the Motorola CLIQ, and I can tell you from experience that benchmarks, while fun to run and compare, aren't very accurate. There are way too many variables, including different runs of the hardware manufacturing process. I has been discussed ad nauseum just about everywhere in the Android community. I've personally found that messing with CPU settings just to get higher scores can easily bork an install of a ROM, so I stopped a while back. Again, I go by usability and real-world speed over any benchmark score. And no one was trying to inflate egos or act superior. It's just kinda taken at fact these days
I appreciate your input but I think you are overlooking one important piece of information that I assumed was made clear from the beginning.
I realize that, because each device is different, benchmark scores cannot be compared between devices. But, when you take an average of a series of tests (say, 20 or so), replicating the same testing environment, with the same device, you can get a pretty decent baseline comparison to use against other roms tested on the same device with the same testing environment as it eliminates as many variables as possible.
Scores that are off by a couple hundred are no big deal and can be attributed to hardware issues....I get that. But when scores are off by a couple thousand, one could likely assume that it is no longer a hardware issue and should be looking elsewhere for the source of the problem.
That being said, had I known that my interest in such an anomaly would cause people to get so offended, I probably would have kept my original comments to myself. But I have very little patience for people who, knowing nothing about me, feel it necessary to address me as if I were some random 14 y/o who has very little working knowledge of a system.
There...I've said my peace and you'll hear nothing more from me.
Sent from my Kindle Fire using xda premium