Well I'll be damned! Thanks, Kimmo, I can confirm it has really been fixed! Yaay!
So what happened in 2.1.1 that triggered it? Because I first experienced it on an upgrade to that OS version (and have been plagued with it ever since).