MobileRead Forums - View Single Post

Darnielle · 12-07-2011, 11:05 AM

My Vox had been relatively problem-free before today; it froze a handful of times and WiFi has been patchy, but other than that it worked smoothly.
This morning around 12PM I was given a prompt that an update was available for the Vox. "Great!", I thought, "This'll be Kobo fixing some problems."
I clicked to update and then the device locked up. I restarted it, and the touchscreen wouldn't accept input. I restarted it, and this time the screen worked fine. I checked the Firmware Update app and it says Firmware is up to date.

But now, problems with WiFi have skyrocketed, to the point that I have to toggle it five or six times to get it to work at all. The wake from sleep bug now happens two out of three times the device enters sleep, and typing seems less responsive. I'm not sure whether the lock-up during the update caused this or whether it's just bad timing, but I thought I'd better make a thread since the circumstances are unique.

Has anyone else experienced something like this? Can someone shed some light on the situation?

12-07-2011, 11:05 AM	#1
Darnielle Enthusiast Posts: 37 Karma: 136122 Join Date: Dec 2011 Device: Kobo Vox	Sudden increase in problems My Vox had been relatively problem-free before today; it froze a handful of times and WiFi has been patchy, but other than that it worked smoothly. This morning around 12PM I was given a prompt that an update was available for the Vox. "Great!", I thought, "This'll be Kobo fixing some problems." I clicked to update and then the device locked up. I restarted it, and the touchscreen wouldn't accept input. I restarted it, and this time the screen worked fine. I checked the Firmware Update app and it says Firmware is up to date. But now, problems with WiFi have skyrocketed, to the point that I have to toggle it five or six times to get it to work at all. The wake from sleep bug now happens two out of three times the device enters sleep, and typing seems less responsive. I'm not sure whether the lock-up during the update caused this or whether it's just bad timing, but I thought I'd better make a thread since the circumstances are unique. Has anyone else experienced something like this? Can someone shed some light on the situation?