First time posting -- apologies in advance if I am inadvertently running afoul any rules by posting this here. I have read through the thread in order to understand why, since I was forced to update to .17 four or five days ago, my KT has been riddled with bugs and glitches, and as of last night is quite literally unusable.
Initially the problems I noticed were also experienced by others here. This, for example, is not an exhaustive list:
Quote:
Originally Posted by pdrewcock
When I launch tthe browser and go to favorites, the first favorite selection opens fine. The second time I try to open a favorite, the reader re-boots. Every time, no misses.
Customer service only managed to delete my favorites list, but it didn't fix the problem.
Any suggestions would be appreciated. Anyone else try this yet?
Oh yeah, and another thing:
Sudoku locks up constantly! Maddening!
I know both these apps are not officially supported, but they used to work well.
|
Quote:
Originally Posted by dioioib
Currently I experience:
Device resets during content processing.
|
Since .17, it would randomly re-boot itself probably three or four times during a reading session. But last night it randomly reset itself to its factory settings (!), and evidently froze in the process. So now I have the 'Restoring Device to Factory Settings...' screen
frozen onto the screen of the KT, and no combination of switch sliding, home button pressing, or paper-clip probing will cause it to respond. Nor does it recognize my laptop (or vice versa) when I plug it into the USB. It is dead as a doornail. I suppose the battery will run dry eventually, and presuming it is still functional at that point, it seems pointless to use it under the threat of random factory resetting.
The most galling thing is that I got the KT in Dec. 2011, and up until the firmware update it was absolutely perfect -- I had no technical problems, and no complaints. My father-in-law had some freezing issues with his KT and he complained to Kobo; he sent it back, they fixed it, and they sent it back to him. But my problems are not hardware-related; I have to conclude that they are 100% derived from .17, and the experiences of others here confirms that. It's baffling that they would botch this so spectacularly.