That might be it, but playing around with it a bit by rotating the device and then back again after a second or so, the call for rotation has already been triggered and the screen will rotate to landscape even tho I've already turned it back to portrait.
This doesn't happen all the time but often enough for me to believe the standard rotation method is just slow, and the times it doesn't trigger using the method above is simply because another call to rotate the screen back has been triggered and canceled out the original call.
This is all conjecture of course since I haven't seen the code, but it seems odd to me to do this deliberately to prevent accidental rotation knowing it will adversely affect perceived performance. I mean accidental rotation isn't that big of a problem.
Of course to others this might not be an issue at all
But showing a colleague a youtube video the other day and rotating the phone to go into full screen, I literally had time to say "Any second now...", which was a bit embarrassing
Edit: Good example of where it becomes a real issue is in the market, viewing landscape screenshots (e.g. games). The screen will rotate to landscape, but if you back out, you will experience that delay in rotation before anything happens at all. The whole system freezes up waiting for the screen to rotate back
Edited by Celeborn81, 27 November 2011 - 10:46 PM.