The behavior of GAPI on the Q is as I would expect. Unfortunately, many/most GAPI Smartphone applications assume a 176x220 display in a specific format, and exposing any other format would break back-compat for existing apps. You can argue that GAPI and it's associated (existing) apps are poorly spec'd/designed (I wouldn't disagree), but the implementation on the Q is exactly as it should be given the back-compat situation.

As another poster mentioned, GAPI has been deprecated (for quite awhile now), so no one should be using GAPI for new applications. You shouldn't expect to see any new effort expended on GAPI beyond attempts to maintain some level of back-compat with existing well-behaved apps.

With respect to GETRAWFRAMEBUFFER, this is a call directly into the display driver. There's no guarantee that it will work on any specific device, nor is there a guarantee that it will return any specific resolution or format or that it will even continue to work in the future. I would recommend against using it if your goal includes cross-platform compatibility.

DirectDraw is the officially supported way of talking to the display, and will continue to get support/bug fixes/new features moving forward. If you find that DirectDraw doesn't work correctly/acceptably on the Q, I suspect Microsoft and Motorola would want to understand why (and please post your experiences/results for the rest of us as well).