Android: applicationStateChanged events can occur out of order

If an Android application quickly receives onPause/onResume, etc... the slots connected to applicationStateChanged can be triggered out of order, where the parameter passed in does not match the value retrieved from applicationState().

In the attached example the Android activity was modified to call onPause/onResume back to back for ease of demonstration.