Qt code should be using QEventLoop when it has to force synchronous behaviour in naturally asynchronous cases. But QtMobility is using CActiveSchedulerWait instead. This causes active objects to run outside of Qt's round robin active scheduler and events to be processed without Qt's event loop being kicked as often as normal. For example, see QTTH-1494 and
QTBUG-21928 for problems caused by this.
Here's a list of places in QtMobility that use CActiveSchedulerWait.
It is generally bad practice to force synchronous behaviour by nesting the active scheduler or event loop anyway. Much of this code should be re-written to handle the events asynchronously. This nested event loop style of code causes many defects all over the code base, by introducing unexpected re-entrancy conditions. It may be easy for you to write, but it's a huge pain in the arse for everyone who uses your code.