[HTC Amaze 4G] ericdjobs:
If you want to build a flashable zip you're more than welcome :) Just been busy with work and trying to get this damn CM 10.1 kernel to compile.. being a real bear actually. Much (Much!) harder than I anticipated...No wonder there's not many kernel devs! And there's so many juicy juicy commits to merge from sensation kernels!

Those files are from CM10.1, actually. I have a feeling that JB ones would be required, as the change from ICS to JB was quite substantial.

Positive note though I did get the upgraded Adreno drivers working (The April 4th ones for JB 4.2)... Read DRIVERS, I can't (nobody can, really) seem to get the libs working.. just the leia_*.fw DRIVERS. Not sure what's up with the libs, but I know they aren't working and completely destroy any display from coming up.

I'm really hoping to master compiling from code, because I feel that will give us a lot more options ROM wise... instead of depending on ports from the Ville (Besides sensation, probably the easiest device to port from)...

Funny thing to note: Our port of Carbon ROM from the Ville actually seems to work better and have more functionality than the Ville's ROM itself.. hah?

Definitely some bugs in hardware composer though.. I can't get any other composition type besides GPU to work without having to turn hardware overlays disabled ON... otherwise I get massive logcat spam of like thousands/second.. that means no MDP 4.0 or c2d2... which is a shame because they do provide some pretty substantial benefit to battery life over strictly GPU composition. And disabling HW Overlays simply isn't that viable of an option, as it kind of defeats the purpose. I'd like to see three truly working framebuffers with full overlay support for our amaze (The true "butter" in JB's butter implementation) but not sure if that's ever going to happen. At least we're on kernel version 3+ which allows us to take advantage of a lot of these features... I feel really bad for the devices still stuck with a 2.6+ kernel because they've had to implement really clunky "hacks" to get jellybean working, and completely bypass a lot of these graphical system overhauls. I

Also narrowed down the soft reboots (at least for this ROM... and probably CM 10.1 as a whole ) is almost 100% caused by PMEM allocation. I found a commit to a sensation kernel that fixed it in board_pyramid.h but unfortunately we don't ahve the same structure and I can't get the damn thing to compile anyways... but maybe someone with more experience can. I have tried every toolchain (From gnueabi 4.4.3-4.4.4, linaro 4.6, google's GCC 4.7.. hell even 4.8) and I can't get the git clone of CM10.1 kernel to compile even using a config straight from device (/proc/config.gz)... which means either people are using specialized toolchains to build, some kind of weird optimizations or flags, or I have my environment set up wrong... could potentially be any of those...

Basically I need help on the kernel side of things.. because I'd really like to get a functional 10.1 kernel with lots of changes... Like SIO i/o sched, USB fast charge sysfs interface, overclocking interface for CPU up to 1.8ghz, as well as user configurable voltages and user configurable GPU OC.

But if I can't get the base kernel to compile without any cherry-picks being pushed, bah.