Thanks to the Forum members who have helped us find this bug. It looks like an easy fix for the next release. I would look for it to be fixed in November. Fortunately , you can avoid the problem by waking the device screen first and then powering off.