Paul made it pretty clear that there's no chance of this happening in the near future. At least until v2 is all done and debugged.
After that point Rick and Paul may be contacting my rep at Chartboost and integrating it. It's really not hard to switch it out once you get a handle on android java and the alimighty runnable class.
I also plan to update the FB SDK too. That's next on our list. I'd be focusing on login, posting (with proper permissions). Then later friends lists and images (FB now uses their own UI for this which is nice because then we don't have to design a scrolling ui for it).
Basically it seams that AppGameKit will not update any of the SDKs unless broken. Unfortunately, this means to me that AGK's SDK implementations will be archaic by the end of the year. So I hope to provide a way for devs to be able to compare the AppGameKit java setup and make their own decisions on SDK integration/update. Hopefully, I'll also be able to restructure some of AGK's java so that it is much easier to swap out the SDKs too.
EDIT: Back on topic - @east
I do think that scissors and virtual resolution have unintended consequences on the ads. When I was using AdMob I had a percentage-base coordinate system and all of the positioning was perfect. This is the third time in the past few months that I've heard of complaints with ad size and positioning. Each time has been with the virtual resolution system.