Thread: Touch Last stable firmware?
View Single Post
Old 04-15-2013, 02:26 AM   #21
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by MacEachaidh View Post
OK, thanks for the comments.

Let me ask, please, before I go through a factory reset and upgrade to 2.4, and then maybe have to do it again, are others seeing these happen under 2.4?

1) About half the ePubs I have loaded (all of them sideloaded ePubs) will now open at the first screen of the ToC, and if I tap the screen to move to the next page, the book is closed and marked as completed. None of these had any problem under the previous f/w (2.3.2, I believe).

2) Display settings (font size, margin width etc) no longer update in real time. I have to make the changes, then close and reopen the book, to see their impact. This makes changing settings quite laborious.

Any of this familiar to anyone?
That is probably a corrupt database on the device. The logout suggested earlier should have fixed this. But, as you had a problem logging in again, do a factory reset and let it reinstall the firmware.

As to the best firmware to use, I think it is 2.4.0. I haven't found any of them to be unstable. I have seen problems like you describe for reading epubs. They have always been because of database. Either the database was corrupt, or I had restructured the epub and replaced the copy on the device without first deleting it. The device stores the TOC in the database and if this is out of sync with the book, you will have problems.
davidfor is offline   Reply With Quote