[Atrix 4G Android Development] :
Yeah the 1.6Ghz is pure hell working with, as well as anything above. Since they by default cause so much heat. It's crazy. One other thing is never touch the voltages. That's one thing I learned the hard way. Just stick to the kernel in my sig. It's amazing. I have issues with faux much more than the one in my sig. People say faux is fine but if you don't ever want to have a problem with your phone stick to my configuration settings and the kernel in my sig all my suggestions for the pinnacle of performance/ stability.

On the stock setup I always got tons of stutters in some games and little to ton in others. I also would get eventually get lag out's and the phone would just freeze up on a black screen on ocassion. After make all those changes. There are about 10 or so. I get no lag at all in games or on anything else. Have 500MB of free ram just ***** slaps the games. No lag at all. It also has an overall light system feel like it's under no load so there's a ton of power to output for apps or whatever your doing. The 384m vmheap kills the games. It comes in to play either on a heavy ass application load, or with time it helps. It acts like a Windows computers pagefile. Say your computer has 1024MB of ram on windows 7. As we all know Windows 7 loves ram, the more the better. It's because it cache's it all just like the android system does. Which is a really good thing. Disable it and all hell breaks lose. So on a windows pc setting the initial and maximum to 4095 provides more performance and makes that performance last a much longer time. When all the ram is cached or actively being used by the operating system being linux(android)/ or windows per say. The OS and the applications at hand will either suffer or the OS will say hell we got a lot more "virtural ram" here to use. So a rather small vmheap say 128m/256m or pagefile of only 1024 or 2048 it's not utilizing the cluster size efficiently. Even on nand memory cluster size matters. The bigger the better. So on a 64KB cluster size hard drive, the pagefile should be big like 4095 so it can have a TON of over head. Overhead is what we want. As for the vmheap it's the same thing. Overhead is always what you want. You don't want a smaller virtural memory capacity since it will have minimal overhead. It may not show in benchmarks but it will in the Long term. When it's comes to stability and having the same performance over and over again for months. The big ass vmheap or pagefile makes a world of difference. On my core i7 desktop I have the pagefile on a seperate RAID0 array with a 64k cluster size and a minimum of 6144MB and a maximum of 6144MB. One thing that would be great for our phones is to go beyond 384m. If your willing to test it out on these newer android builds. Try pushing past 384m. I say do it in 16 multiples only. Make sure to my a Nandroid backup since from my experience 384m was the max bootable amount in android in the past. Honestly you won't notice a difference on 16 multiples so honestly 64m multiples at the minimum since that's more realistic. 448m or 512m should be extremely awesome and amazing. If anyone had any disputes on other factors and environments I can dial in some more real world extremely realistic situations. I hope I helped anyone out!

Yep happens when your running a faux kernel. Get the kernel in my sig and you'll be fine for the rest of eternity.

cya

Later Broski's! :p