March 24th, 2012, 03:58 AM
Join Date: Dec 2010
Device(s): HTC Evo 4G & Design 4G, Wildfire S (x3), One V, Galaxy Nexus, Nexus 7 (2012), HP Touchpad, etc.
Carrier: Not Provided
Thanked 45 Times in 26 Posts
I wouldn't hold my breath on help.
Here is the low-down skinny in developer world.
Sense is often copied, hacked, modded, ported, etc.
Cyanogenmod is built. A port or anything less is at best unofficial and a possible blight on a great team's work.
So building what must one do? One must build a device tree defining the hardware in their device and at least achieve basic bring-up... Then build and grow that tree until all the modules work, then further perfect the tree so that all runs efficiently, correctly, etc.
I suppose getting a cm port booting is an ok thing, but coders want the hardware list first or maybe an upload of all modules [from stock RUU] to a github. That is every bit as good or better info for one to start building with. Unfortunately there are very few marvelc devs. I know the team I'm on is focused on getting a gb tree working before we would look at or consider cm9. But perhaps there are those who want the latest and greatest... At this point, there are no known aosp [working] builds though for marvelc. Makes sense to try 7.2 first as their is more documentation [or help] for the developer[s] attempting.