Sorry, I didn't realize someone had actually replied to this old thread. We determined it wasn't worth it and just used GStreamer directly (in C code, with the qmlglsink plugin). If I remember correctly, when I was trying the QtMultimedia route, after all my trouble, I was just barely able to get the basic example to work. As soon as I tried pulling in some other gstreamer elements to parse actual RTSP or other types, I had other library errors. Probably needed to link against more plugins or something. And it just wasn't worth the hassle to figure out the rest, especially considering I had to rebuild Qt from source every time I wanted to try. Not to mention the fact that even if I was successful, building Qt from source creates a serious challenge to our development workflow. We'd either have to host our custom built Qt somewhere, or just have every developer build from source themselves.
Plus since then we've encountered some requirements that required pipeline manipulation that I don't think would have been possible through the QtMultimedia interface anyway. We've had to do some dynamic pipeline stuff that you really need to be able to write C code for.
Tl;dr don't bother with QtMultimedia GStreamer on Android. Its either not possible or not worth the trouble.