Update on this for anyone coming across this post: this issue only seemed to occur when the device was connected to the Mirror app and has been fixed in the 1.0.1 release.
