I don't think 256 colours would suit Robotica's project.. maybe the 32,768 would be fine. Frame Rate / Memory / Performance doesn't really seem to be an issue for him anyway.. if it were there's a lot of other things he could do first (optimize texture size (LOADS could be done there), turn off fine detection on most objects etc.)
I'm sure the animation issue would be an easy fix, it is annoying that there are differences between the Android / Windows runtimes, but all you can do is thoroughly test on both platforms throughout development so any differences you encounter you can work around right away.
There are definitely some quirks with sounds that have appeared with the Android run times sound handling that never used to exist... I was going to do some tests this past weekend but never got around to it.. if someone can isolate sound bugs it will be easier for Fernando to fix.
The transitions "zoom, zoom2, fade, and scrolling" can all be replicated with events like the example I sent you, you might just have to dig deep and work them into each frame.