MobileRead Forums - View Single Post

MidwestJen · 10-08-2014, 12:16 PM

I've recently noticed an issue on my Kindle Fire - that I'm almost positive is 'newish', but not 100%. I can't imagine not noticing this before the last few weeks, but I won't rule it out completely (even if I really am sure I used to be able to open a file and have it pop to the most recent page read).

When I open a book in CC, it always opens to the first readable page (ie not the cover, but the summary title page/ToC/Chapter 1). For a new book, this is perfect - but for a book I've been reading and had exited, it's very annoying.

I realize that the Go To --> Furthest Page Read will work to move me back to where I was - assuming of course that I haven't finished the book previously. I usually use my Fire at bedtime, which means I'm frequently starting and stopping books and may not remember that I had already read part of it. My memory is pretty good, but as of this writing my Calibre library tells me it has over 9k books.

A few things to hopefully trace down either what's changed or what I'm doing wrong.

These are all downloaded fanfiction stories - some source files are html/zip, others are epub, but all have been converted into mobi using calibre's conversion tools. I have also tried a few in azw3 just to see if it makes a difference.
Both mobi and azw3 act the same way on the Kindle Fire.
My Kindle Paperwhite and the Calibre e-Reader on my PC both keep track of last page read without any issues. Amazon e-books on the Fire go to last page read (using native Kindle reader).
Testing has been done on various configurations for conversion settings and formats to see if it's a setting issue. Typical testing is to delete a book from CC on Fire, use Calibre on PC to convert file (one change at a time), connect Fire to Calibre and redownload book (typically using content server), disconnect from Calibre and use CC to open book, page to some random page, exit book, re-enter book (and get frustrated that it's the same first page). Going to furthest page read, exiting the book and re-entering also takes you back to that first page, not the furthest.
Plugins - I am using FanFictionDownLoader (v2.0.6), Find Duplicates (v1.6.2), Generate Cover (v1.5.15), Kindle Collections (v1.7.15, only with ebooks, so not relevant) and Reading List (v1.6.5).
Versions - CC is version 3.3.5, Kindle Fire system version is 8.4.9, Calibre version is 2.5.0.
I will admit to recently reorganizing some parts of my library and configurations for various things (both plugins and calibre itself) - but I have tried to ameliorate that by testing old settings (see 4).

Since I don't use CC on any other device (I sideload onto the PaperWhite), I can't say for sure that this is a CC issue, but since I can't find anything on this using google (which rarely fails me!), I'm hoping someone can help. I did find lots on how to synch with multiple devices - but it wasn't relevant to what I am trying to fix.

Thanks in advance for any suggestions or explanations! =)

10-08-2014, 12:16 PM	#1
MidwestJen Enthusiast Posts: 25 Karma: 10 Join Date: Oct 2014 Device: Kindle Fire HD, Kindle Paperwhite, K1 (ret), K2 (ret)	CC, Kindle Fire, and last read position I've recently noticed an issue on my Kindle Fire - that I'm almost positive is 'newish', but not 100%. I can't imagine not noticing this before the last few weeks, but I won't rule it out completely (even if I really am sure I used to be able to open a file and have it pop to the most recent page read). When I open a book in CC, it always opens to the first readable page (ie not the cover, but the summary title page/ToC/Chapter 1). For a new book, this is perfect - but for a book I've been reading and had exited, it's very annoying. I realize that the Go To --> Furthest Page Read will work to move me back to where I was - assuming of course that I haven't finished the book previously. I usually use my Fire at bedtime, which means I'm frequently starting and stopping books and may not remember that I had already read part of it. My memory is pretty good, but as of this writing my Calibre library tells me it has over 9k books. A few things to hopefully trace down either what's changed or what I'm doing wrong. These are all downloaded fanfiction stories - some source files are html/zip, others are epub, but all have been converted into mobi using calibre's conversion tools. I have also tried a few in azw3 just to see if it makes a difference. Both mobi and azw3 act the same way on the Kindle Fire. My Kindle Paperwhite and the Calibre e-Reader on my PC both keep track of last page read without any issues. Amazon e-books on the Fire go to last page read (using native Kindle reader). Testing has been done on various configurations for conversion settings and formats to see if it's a setting issue. Typical testing is to delete a book from CC on Fire, use Calibre on PC to convert file (one change at a time), connect Fire to Calibre and redownload book (typically using content server), disconnect from Calibre and use CC to open book, page to some random page, exit book, re-enter book (and get frustrated that it's the same first page). Going to furthest page read, exiting the book and re-entering also takes you back to that first page, not the furthest. Plugins - I am using FanFictionDownLoader (v2.0.6), Find Duplicates (v1.6.2), Generate Cover (v1.5.15), Kindle Collections (v1.7.15, only with ebooks, so not relevant) and Reading List (v1.6.5). Versions - CC is version 3.3.5, Kindle Fire system version is 8.4.9, Calibre version is 2.5.0. I will admit to recently reorganizing some parts of my library and configurations for various things (both plugins and calibre itself) - but I have tried to ameliorate that by testing old settings (see 4). Since I don't use CC on any other device (I sideload onto the PaperWhite), I can't say for sure that this is a CC issue, but since I can't find anything on this using google (which rarely fails me!), I'm hoping someone can help. I did find lots on how to synch with multiple devices - but it wasn't relevant to what I am trying to fix. Thanks in advance for any suggestions or explanations! =)