Hmm, I can't see this bug on my test device, so looks like it is fixed. And I think it should be fixed even in PR1.2. Are you still on PR1.1?