This issue does seem to occur with some devices and not others. We have reproduced the problem internally and we're looking into it further. Thanks for the reports guys!