[EVO 4G General] skydeaner:
And I don't know who keeps repeating this. Do you have any idea what the tolerance for the components inside the evo are? There is no fathomable way to have a kernel that performs better on one evo than another unless you are using a different rom. Yeah I said it.

Now from phone to phone you will get different QSD8650's that overclock to different levels, absolutely. Especially given the set voltages in all kernels.

I don't know where the misconception that one phone will like BFS or CFS or some other build version of the kernel came from. The phone WILL NOT MAKE THE DIFFERENCE. The person will. There is no logical backing to this theory.

It isn't that some phones don't like BFS and it works fine on others. More than likely it is a problem with the rom not cooperating with BFS scheduling, or that you personally don't like how the scheduling takes place.

Lets face it if you are trying to run 15 different programs at a time, or are converting movies with your phone lol, BFS scheduler probably isn't for you.

If you striving for single program performance like gaming or watching a movie, then BFS is going to offer half the latency of CFS and a much smoother experience.

One way to think about the differences between CFS and BFS is CFS is like a tree, and BFS is like a linear feed of requests.

The CFS tree can have the 20 percent of the cpu working on five different things at a time (this is really dumbed down, please don't anyone try to quote me on this or twist my **** around lol)

The BFS "line" has 5 different things being fed to the processor, when the first one is done, the second one goes in, and then the third and so on, each one getting 100 percent of the CPU's tender loving care.

Ok this is getting really long winded. Again, no one try to pick this apart, I am smarter than what I just typed lol.

But again, all evo's are more or less going to react identically to each kernel. Given the exact same environment, like I provided (a nand image with everything being identical and every test being performed identically) it is going to turn out the same on 100 different evo's if i had them sitting in front of me.

EDIT:

man I about fell asleep typing all that lol. Boring stuff. I feel like i am watching that guy from google talk about "making zippy android programs" by not calling to external servers for U/I commands and other completely ignorant things that cause latency.. Man that was a hoot. Everyone that has any common sense never would have done most of what that guy was talking about. Anyone watch that on youtube? It was some time middle of this year. Maybe I'm the only one that watches nerd stuff like that lol.

EDIT 2:

STARTING THE OOTB REVIEWS FOR MOST CURRENT ROMS - They will, like any reviews, be highly opinion based lol. But I will also be including testing along with my 2 cents lol.

EDIT 3

OMFG so excited here. I found this chick online that wrote a C program for linux that keeps the processor at a certain load percentage that you specify. So like say I want to test the difference in current draw between 600mhz at 100percent cpu usage and 1.1ghz at 50percent, i will soon be able to do that. And we can see if it is smarter to leave dynamic processor scaling enabled rather than limiting frequency when the battery goes down. When you set it to not go over 800mhz well more things are going to use a higher percentage of the processor, so maybe that will end up making your battery drop quicker? Time will tell. i can't wait for her to port it over for me. Also, if anyone here knows how to use the SDK and NDK on a C source program and get it to work in android please PM me ASAP.