A small update:
The graphics problem is due to the SGX drivers not supporting RGBX_8888 and android assuming it works. With the honeycomb source this would be no problem to fix with some ifs and a recompile. So instead I'm patching the binaries by hand. The statusbar still isn't visible but at least other programs work now instead of showing a black screen.
Still haven't looked into why the sensors don't work. I assume the interface might have changed ... I can see the acceleration sensor working at /dev/input/event3
I have it running from an SD card. It also seems to hibernate/sleep without a problem now.
I'll upload all of this to github and upload a binary somewhere when it's a little bit more usable.
Patience is a virtue (= I have a social life too).
And yes, manual patching a binary is a bitch that can kill one's social life. Or any life, so take care, please.
I know I might sound extremely stupid but could it be that status bar not showing is because improper scaling and/or residual "phone's 800x480 max" screen definitions and/or pixel density is not good (even when correct 169 dpi) in build.prop.
Then, just for the sake of proof of the concept, so to speak, could the borrowing of 2.1 accelerator/orientation code help? Wish the same could apply to WiFi and sound (or a "borrowed" Media server; it might be just me, but in borrowing such thing I would love to have it with a volume boost hack of 2....3 db, please! NC in 1.0.0, 1.0.1, 1.1.0, and NookieFroyo just hardly whispers...)
In all fairness, I actually don't see any need of A3.0's possibly very buggy "improvements" in WiFi, accelerometer, and sound (except for volume boost.). Apart from visual candies, the most significant improvements that A3.0 may bring are in new, rewritten NEON, SGX/DSP support, new JIT/DVM.
Oh, and I keep forgetting: the new Fonts, LOL