Thread: Kobo Bug thread
View Single Post
Old 09-29-2013, 07:43 AM   #264
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
@glos: This sounds like the device can't work out and store the reading position. Or if it stores it, it can't be reoponed to that point. The main times I have seen that problem is after replacing a version of the book without deleting it first. But, as the book didn't work after a factory reset, that isn't the case.

As it is one book that this is a problem for, then it probably is something about the book. And as you are sending it as a kepub via the extended driver, it might be something in how the kepub is created. I would recommend discussing this in the extended driver thread or raising a bug and supplying the original epub to the developer.
davidfor is offline   Reply With Quote