It's required a full source code of current EE's android with specific patches, full source code of device drivers, and some code of EE's and adobe software (library, journal and reader).
Probably now, when I know allmost all hardware used in EE, it's possible to compiile 2.2, but it will not contain any EE or adobe copyrighted software.
So there's two reason:
1. There's no many people who would use unofficial firmware, and there's much less people who will use unofficial firmware which didn't contain needed software.
2. It'll take a lot of time and money to develop.
So now, when my sick-leave certificate expired and I back to work, I don't have much time, and since there's no many people who interested in alternative firmware, there's no financial interest to develop it.

offtopic: I buy EE without reading reviews or watching video, the main buying points were the linux based OS, and good hardware specification, so I was very frustated when turned on EE for the first time. It was almost absolutly unusable for my needs. So I working developing firmware which allow me to use EE as I suppose it must be used. So at some point further development will depends on the mood of official EE's bosses (which is a bit sceptical) and customers. For example I do not need the support of changing the orientation of screens and a nice interface, but if the company would be interested in the product, then I'll work on those features.