Thanks for this blog post. I've been having the same issue on iOS and I'm glad to hear it's a behavior others have noticed and documented. I'll be building a workaround based on your NSTimer category.