MobileRead Forums - View Single Post

KoboJW · 11-03-2011, 01:34 PM

Thanks, everyone, this kind of detail is great and very helpful as we investigate.

Some more detail that might help - right now we know of an issue when waking a Vox from sleep right around the 1 minute mark. Basically, when wifi is on and the screen is turned off (manually or via timer), we wait 1 minute before powering down wifi radios. This is so that should you try to immediately turn it back on, wifi is still available and the device is instantly ready to go. However, when the wifi starts to power down, there is a period of a 10s or after that minute mark where the screen will take a few seconds to respond to being turned on. It is responding, it just isn't showing anything. So if you try and press the button again during that delay, you effectively turn off the screen again! If you wait after the first press, the screen pops on after a few seconds. This leads to a lot of confusion, obviously, and we're working to fix that.

I just want to make sure that we are able to differentiate between this issue and one where the screen is not just delaying response at this 1 minute mark, but not responding at all.

Thanks again, everyone.
James

11-03-2011, 01:34 PM	#13
KoboJW UX Lead, Kobo Vox Posts: 113 Karma: 199002 Join Date: Oct 2011 Device: Boxes of Voxes	Thanks, everyone, this kind of detail is great and very helpful as we investigate. Some more detail that might help - right now we know of an issue when waking a Vox from sleep right around the 1 minute mark. Basically, when wifi is on and the screen is turned off (manually or via timer), we wait 1 minute before powering down wifi radios. This is so that should you try to immediately turn it back on, wifi is still available and the device is instantly ready to go. However, when the wifi starts to power down, there is a period of a 10s or after that minute mark where the screen will take a few seconds to respond to being turned on. It is responding, it just isn't showing anything. So if you try and press the button again during that delay, you effectively turn off the screen again! If you wait after the first press, the screen pops on after a few seconds. This leads to a lot of confusion, obviously, and we're working to fix that. I just want to make sure that we are able to differentiate between this issue and one where the screen is not just delaying response at this 1 minute mark, but not responding at all. Thanks again, everyone. James