MobileRead Forums - View Single Post

register512 · 10-13-2011, 06:58 PM

Well, so far 1.9.12 has turned out to be an absolute piece of crap for me. I've installed it twice, and had two completely separate sets of bad experiences with it.

The first time, I simply attached to Kobo Desktop, let it download the update, and added a few new books to my Touch. Then ejected, and let it do the upgrade. After that, I couldn't read more than about two pages in any book, because the Touch would suddenly show the "folded corner" in the upper right, and return to the home screen. Then I'd have to switch back to the book I was reading, and repeat the experience after one or two page turns. After 15 minutes of that, it was time for a factory reset and re-installation of 1.9.10.

The second time, I decided to break things into smaller steps, so I re-registered the Touch, re-installed 1.9.12, and then ejected and let updates happen. I then added a few books, and re-inserted my SD card. I started browsing my library, and everything seemed fine. However, if I put it aside for a few seconds, it completely locks up. It ignores all forms of tap or swipe, and presses of the home button. I have to slide the power switch, and let it sort itself out.

Therefore, I'm now back to 1.9.10, and everything is stable as it used to be.

I don't know if the problem is because of the SD card, although that didn't cause me any trouble in past releases. I keep the books I'm waiting to read on the main memory, and I store older books on the SD card. It's a 16GB card, so there's plenty of room to build my entire library onto it.

Under 1.9.10, I suffer from the "dead tap" problem, but I've gotten used to that. As well, my SD-based books don't always show up correctly on the home screen, but I have no problems accessing them from the Library list or the Shortlist, so I can take that as just a quirk of handling.

As a software developer, I have to say that it certainly doesn't seem like much QA was done on this release. I thought the new tunable-tap locations were a good thing, but they certainly seem to be a potential cause of the dead screen that I get.

10-13-2011, 06:58 PM	#24
register512 Kobo Touch User Posts: 20 Karma: 4608 Join Date: Jul 2011 Device: Kobo Touch	Well, so far 1.9.12 has turned out to be an absolute piece of crap for me. I've installed it twice, and had two completely separate sets of bad experiences with it. The first time, I simply attached to Kobo Desktop, let it download the update, and added a few new books to my Touch. Then ejected, and let it do the upgrade. After that, I couldn't read more than about two pages in any book, because the Touch would suddenly show the "folded corner" in the upper right, and return to the home screen. Then I'd have to switch back to the book I was reading, and repeat the experience after one or two page turns. After 15 minutes of that, it was time for a factory reset and re-installation of 1.9.10. The second time, I decided to break things into smaller steps, so I re-registered the Touch, re-installed 1.9.12, and then ejected and let updates happen. I then added a few books, and re-inserted my SD card. I started browsing my library, and everything seemed fine. However, if I put it aside for a few seconds, it completely locks up. It ignores all forms of tap or swipe, and presses of the home button. I have to slide the power switch, and let it sort itself out. Therefore, I'm now back to 1.9.10, and everything is stable as it used to be. I don't know if the problem is because of the SD card, although that didn't cause me any trouble in past releases. I keep the books I'm waiting to read on the main memory, and I store older books on the SD card. It's a 16GB card, so there's plenty of room to build my entire library onto it. Under 1.9.10, I suffer from the "dead tap" problem, but I've gotten used to that. As well, my SD-based books don't always show up correctly on the home screen, but I have no problems accessing them from the Library list or the Shortlist, so I can take that as just a quirk of handling. As a software developer, I have to say that it certainly doesn't seem like much QA was done on this release. I thought the new tunable-tap locations were a good thing, but they certainly seem to be a potential cause of the dead screen that I get.