Reading progress

[jhowell]

Originally Posted by HarryT

Every one of the books on my Kindles is sideloaded, so I don't think that can be the problem.

Actually, I am wondering. Do you sideload manually or do you use calibre?

I know calibre does some extra things when sideloading book and I'm wondering if that could be a factor.

[HarryT]

Originally Posted by jhowell

Actually, I am wondering. Do you sideload manually or do you use calibre?

I know calibre does some extra things when sideloading book and I'm wondering if that could be a factor.

I use Calibre.

[NullNix]

Originally Posted by shamanNS

I had exactly the same experience with both PW1 and PW3. Having to do / type reset thing (IIRC none of those "switches" beginning with ; go into search history?) multiple times per book was annoying so I'm not using. Reading Time feature anymore. Number of pages (Calibre generated, number of characters based) is much more reliable.

They do go into the search history, thank goodness. Only ;chkup doesn't (not sure why not: possibly related to the fact that it doesn't try to actually run a search, unlike ;ReadingTimeReset).

[jhowell]

Originally Posted by HarryT

I use Calibre.

Thanks.

Well, I am out of ideas.

[jbjb]

Originally Posted by NullNix

What's oddest is that it happens completely without warning. I could understand it, a bit, if it went mad only after I'd paged frantically back in the book or something, but I can be sitting there reading a page and *not even changing pages*, 200 pages into a 500-page book, and suddenly flick! 3m to finish this book. I don't think so.

I get exactly the same behaviour.

[dordale]

Very interesting--I see the same behavior as NullNix on my Voyage. Reading time will work fine for quite awhile and then suddenly the reading time will be half of what it actually is--or only a few minutes to finish a long novel. I too ;ReadingTimeReset pretty much permanently in my search bar.

The really interesting thing is that I also have a PW2 that I don't recall ever having this problem on.

[shamanNS]

Originally Posted by NullNix

They do go into the search history, thank goodness. Only ;chkup doesn't (not sure why not: possibly related to the fact that it doesn't try to actually run a search, unlike ;ReadingTimeReset).

Maybe it was different on older firmware? I haven't been using ;ReadingTimeReset since early days of PW1. I often use ";un" for toggling between USBNetwork and "mass storage" USB modes and that 100% doesn't show in search history. Reading time reset switch does go into history now on firmware 5.6.5 (my PW3 is still on that firmware and it will remain forever... don't like the UI redesign on the fw 5.7.x +)

[dordale]

Originally Posted by shamanNS

Maybe it was different on older firmware? I haven't been using ;ReadingTimeReset since early days of PW1. I often use ";un" for toggling between USBNetwork and "mass storage" USB modes and that 100% doesn't show in search history. Reading time reset switch does go into history now on firmware 5.6.5 (my PW3 is still on that firmware and it will remain forever... don't like the UI redesign on the fw 5.7.x +)

This doesn't seem to be the case for me. I'm currently running 5.7.4 on my Voyage and have seen this behavior with earlier firmware. Although, admittedly, the problem could be fixed in 5.8.x.

But--on my PW2 which is also currently running 5.7.4 I don't recall ever seeing this issue. Doesn't mean it hasn't happened and I just forgot about it. But it certainly doesn't happen anywhere near as often as I see it on my Voyage.

It's very perplexing.

[NullNix]

Originally Posted by dordale

This doesn't seem to be the case for me. I'm currently running 5.7.4 on my Voyage and have seen this behavior with earlier firmware. Although, admittedly, the problem could be fixed in 5.8.x.

It's still broken for me on my Oasis running 5.8.5.0.2.

[Barty]

There are lies, damn lies, and "1m remaining in chapter", which could mean anything from 1 to 10 minutes to something is broken and it's always going to be 1m for the entire book. I just ignore it and read.

[ny10522]

Yes, I am having the same problem with my new Oasis purchased middle of March 2017. Random switching of page progress from page number to time remaining in chapter. Frustrating!

[Cinisajoy]

Originally Posted by ny10522

Yes, I am having the same problem with my new Oasis purchased middle of March 2017. Random switching of page progress from page number to time remaining in chapter. Frustrating!

Where are you tapping on the screen?
Try moving your page turn finger up a bit.

[patrickt]

Originally Posted by Oldgeeza

I have a Kindle Oasis and the reading progress is set on page number out of the blue it will change to time left in chapter of it's own accord. Can go for weeks between it happening and never the same point in the chapter.

Mine changes to location. It doesn't do it out of the blue, though. It does it when the particular book being read doesn't have page numbers.

[HarryT]

Originally Posted by patrickt

Mine changes to location. It doesn't do it out of the blue, though. It does it when the particular book being read doesn't have page numbers.

And that's exactly the behaviour you'd expect. Naturally it can't display page numbers if there are no page numbers to be displayed . As you say, in that situation it switches from page number to location.