[HTC Amaze 4G] Yank555:
I'm more than willing to help out, but since I don't have an Amaze, I can't give tips as to what works best on that device. I can explain each of the settings, though ;)

CPU Frequencies

I suppose min. max. CPU is pretty obvious, it allows to set the frequency range you will allow your device to use,

The "Screen-off max frequency" is just limiting the max. CPU frequency when the sceen is off. Don't set this too low, or you might not be able to wake your device, or it might reboot when waking. To know the limit, you'll have to cross it once, so start high, go lower until it won't wake or reboot and go one step higher again.

Intellidemand governor Frequencies

Inactive max frq. is a specific of faux's Intellidemand governor, which will limit CPU max. frq. if your GPU is not busy, meaning if you're like reading text on you screen, so your GPU has nothing to do, no need to allow CPU peaks, you're not asking anything from your device at that moment. This saves battery. When GPU activity reaches a certain level, full CPU max. frq. is restored again.

Two phase is just a midstep keeping the CPU from racing to the max. freq. too fast, so in essence it's also a battery saving thing.

CPU Undervolting

Pretty obvious as well, this lowers the voltage on your CPU. It will allow for battery savings, really tiny little difference, keep the CPU cooler (the only real plus if any if you ask me) at the risk of rendering your device unstable.

Each device is different, so has a different UV capacity. Here the same technique applies as for the screen off frq. start at 0, go lower until your device gets unstable, reboots randomly, or even bootloops and go one level back.

GPU 3D OC

Just as for CPU, here you can overclock the 3D GPU, allowing it to run faster, thus drawing slightly more battery, and potentially producing more heat (300MHz should be fine, 330MHz started heating up my Sensation, even if for some others it was fine). Only 300MHz is now possible, the gain in speed was not worth the hassle, really not !

I/O settings

This allows you to choose how much data a read request would read

more

than asked for to keep the next few Kb ready hoping they will get asked for. Makes sense having it high when reading video files, music files etc. since you will generally always want to "read" that file from the beginning to the end. But on database requests (like your navigation app reading its map database), will read randomly, so set it too high, and you'll have your device read much data to through it away, thus slow it down. The keyword here is balance ! Since you all use your devices differently, there's only experimenting to find the one that fit your needs.

You can also choose the I/O scheduler you would like to use, have a look here to understand what they do and makes them different (the thread is generic, not all are available !).

Android Low Memory Killer settings

Well ... my favorite ;) Best it to no touch it, it's a bit like Pandora's box ;) Here's what I had to say about it in my S3 kernel thread :

The Mods

USB forced fast charge will allow to use AC charging levels on a USB charger. Be aware, you can't pull more than comes out of a USB socket, so it's not because you're asking for 1A that you'll get it. Also, a poor USB port, which doesn't fully comply with the standards, might overheat and get damaged. You've been warned !

Virtual Memory (Hardswap and Zram)

Allow another quote from my S3 kernel :

Vsync

This is one special brother ;) OK, vertical sync means, no GPU operation is allowed to change the screen content until the full screen frame is drawn, to keep the image consistent.

You can however, on the Sensation at least, disable this. This means GPU operations can go on faster, but also that what you see on the screen might just be half the picture (and this I mean litterally ;)).

Try it, if you don't see anything strange, keep it, it's faster. If you see hicups, just revert back to enable it.

---------------------------

I guess that more or less summs it up ;)

JP.