Touch When turning off and on sometimes the page of the book has moved backwards?

[topcat07]

hi all

hoping someone can help me with this please

So for example i turn off the device on page 150. Sometimes i will turn on the device a number of hours later and it will pick up from page 150 but other times it may have gone back to page 148 :S

what gives?

Thanks

[frankenhooker]

Same problem here using the latest firmware (3.3?).

[GeoffR]

Originally Posted by topcat07

So for example i turn off the device on page 150. Sometimes i will turn on the device a number of hours later and it will pick up from page 150 but other times it may have gone back to page 148 :S

Do you use a sleepcover?

If the sleepcover magnet is not positioned quite right or is disturbed, the device can wake briefly while the cover is still closed and the page turned by the cover touching the screen.

[topcat07]

Originally Posted by GeoffR

Do you use a sleepcover?

If the sleepcover magnet is not positioned quite right or is disturbed, the device can wake briefly while the cover is still closed and the page turned by the cover touching the screen.

Hello

i dont use a sleepcover , just a normal case

have been turning device fully off

if i put it into sleep mode would i get this problem ?

[davidfor]

Originally Posted by topcat07

have been turning device fully off

if i put it into sleep mode would i get this problem ?

It possibly would help. One of the reasons for seeing strange things like this is that the database on the device has become corrupt. In this case, the current reading position doesn't get stored correctly. As long as the device is running, everything seems OK. But, when you power off, the database isn't written to memory and when it turns on, old data is read. It sounds like the book is reopening to a spot near the last place you were reading. If that is the case, it suggests the database is OK, just that something is going wrong in calculating the position to open to.

So, some questions:

- Is this just one book, or all books?
- What format? epub, kepub, sideloaded kepup, PDF? For sideloaded kepubs, are they being sent from calibre via the KoboTouchExtended driver?
- Is the position always off by just a few pages? Does it get worse further along in the book? Does it reopen to the beginning of chapter correctly?
- If you use the table of contents or the navigation bar, does it go to the right place?
- What firmware version are you running?

There has been at least one firmware version that showed a problem like this. I think it was one of the 2.3.x versions. That had a problem that sounds like this one if the margin on the device was not set to the minimum. That has been fixed and I haven't heard of anything similar since.

[GeoffR]

Originally Posted by topcat07

i dont use a sleepcover , just a normal case

have been turning device fully off

if i put it into sleep mode would i get this problem ?

What sort of books are you reading, epub, synced kepub, sideloaded kepub? Faulty books can have navigation problems of various sorts. And the book is sideload as kepub just by changing the filename from .epub to .kepub.epub without using Calibre then a lot of things related to book location won't work.

There was a bug in firmware versions 3.0.x that caused settings to be lost for books on the external micro-SD card. But I think that was fixed in 3.1.x.

Beyond that I don't know. My Glo with firmware 3.5.0 always opens to the correct page whether turned fully off or after waking from sleep. I have tested with sideloaded epubs and synced kepubs in internal memory.

[MacEachaidh]

Originally Posted by topcat07

So for example i turn off the device on page 150. Sometimes i will turn on the device a number of hours later and it will pick up from page 150 but other times it may have gone back to page 148 :S

Hi topcat,
I've got a Touch and Aura HD. I've seen this behaviour on the Touch from the day I first got it, so I doubt it's a issue of database corruption. In any case, at least twice in its life I've done hard resets and reinstalled the firmware, and the behaviour has continued unchecked. It happens on my Aura HD as well, but far less frequently, and I think that's a clue.

What it seems to come down to, in my opinion, is that the Digital Editions logical page and the Kobo display page are often (usually?) different lengths. The difference is affected by font size, line spacing etc. If you switch on the ADE page numbers, you'll see they usually don't line up.

It seems that when the Kobo goes to sleep (or off) and then fires up again, if the display page you were on coincides with the top of an ADE logical page, then the Kobo opens up to the display page you were on. But if the start of the specific logical page you were on actually falls one or even two display pages back from where you were, then that's where the Kobo will open up.

That's how it seems to work for me, anyway. (And just to clarify, I'm only reading ePub books, not kepubs, which I believe use a different display enginge so may get different behaviour in this respect.)

[davidfor]

Originally Posted by MacEachaidh

Hi topcat,
I've got a Touch and Aura HD. I've seen this behaviour on the Touch from the day I first got it, so I doubt it's a issue of database corruption. In any case, at least twice in its life I've done hard resets and reinstalled the firmware, and the behaviour has continued unchecked. It happens on my Aura HD as well, but far less frequently, and I think that's a clue.

What it seems to come down to, in my opinion, is that the Digital Editions logical page and the Kobo display page are often (usually?) different lengths. The difference is affected by font size, line spacing etc. If you switch on the ADE page numbers, you'll see they usually don't line up.

It seems that when the Kobo goes to sleep (or off) and then fires up again, if the display page you were on coincides with the top of an ADE logical page, then the Kobo opens up to the display page you were on. But if the start of the specific logical page you were on actually falls one or even two display pages back from where you were, then that's where the Kobo will open up.

That's how it seems to work for me, anyway. (And just to clarify, I'm only reading ePub books, not kepubs, which I believe use a different display enginge so may get different behaviour in this respect.)

Firstly, the bottom of the screen page number is the page number for the first character on the screen. That means the in-margin page number is usually one higher than at the bottom of the screen. And if you use a small font, there can be two or three page numbers in the margin. I don't usually show the in-margin page numbers, but I have never seen the two number not following these rules.

For the reading position, the device does not store the page number. It stores a reference to the current file within the epub, and a pointer to first character on the screen. An example of this is:

OEBPS/Text/Section0001.html#point(/1/4/6/2/1:126)

The set of numbers in the "point" are a count of the number of tags at each level of nesting within the file. The last number is the count within the tag of the character that is first on the screen.The position above is in the middle of bold text within the third paragraph in the chapter.

Note: The tag counts are always even and seem to counting opening and closing tags. I'm not sure what happens with "<br/>" or "<hr/>".

When the book is reopened, it should be reopened to display that character. If nothing has changed in the reading settings, this same character should be the first on the screen. If the reading settings have changed, then it could be elsewhere on the screen. And if that happened, the page number displayed could be one or two less than when the book was closed.

I don't think this is what topcat07 is seeing. But, I could see the rendering getting slightly different results when paging through a book vs opening to a position. And the further into a chapter, the more likely this would be.

[topcat07]

Originally Posted by davidfor

It possibly would help. One of the reasons for seeing strange things like this is that the database on the device has become corrupt. In this case, the current reading position doesn't get stored correctly. As long as the device is running, everything seems OK. But, when you power off, the database isn't written to memory and when it turns on, old data is read. It sounds like the book is reopening to a spot near the last place you were reading. If that is the case, it suggests the database is OK, just that something is going wrong in calculating the position to open to.

So, some questions:

- Is this just one book, or all books?
- What format? epub, kepub, sideloaded kepup, PDF? For sideloaded kepubs, are they being sent from calibre via the KoboTouchExtended driver?
- Is the position always off by just a few pages? Does it get worse further along in the book? Does it reopen to the beginning of chapter correctly?
- If you use the table of contents or the navigation bar, does it go to the right place?
- What firmware version are you running?

There has been at least one firmware version that showed a problem like this. I think it was one of the 2.3.x versions. That had a problem that sounds like this one if the margin on the device was not set to the minimum. That has been fixed and I haven't heard of anything similar since.

>all books
>epub via calibre
>not sure on this one havent finished a book yet
>i just open the book without a table of contents of navigation bar
>Firmware 3.3

Thanks for your help

[the.Mtn.Man]

Originally Posted by MacEachaidh

I've got a Touch and Aura HD. I've seen this behaviour on the Touch from the day I first got it, so I doubt it's a issue of database corruption. In any case, at least twice in its life I've done hard resets and reinstalled the firmware, and the behaviour has continued unchecked. It happens on my Aura HD as well, but far less frequently, and I think that's a clue.

Just to add some murkiness to this issue, I have never experienced this on my Kobo Touch which I used for several years, nor does my recently purchased Kobo Aura exhibit this behavior. The only time I got random page turns on my Touch is when I closed the cover before flicking the switch to put it in sleep mode, in which case the cover was breaking the infrared beam and causing a page or two turn. Once I got in the habit of putting it to sleep before closing the cover, it never happened again.

[topcat07]

is this the answer? ref: https://www.mobileread.com/forums/sho...d.php?t=146967

this is actually been mentioned a couple of times; when in sleep mode , the last page you are on stays in the systems ram, which requires power to maintain, and this is why it's much faster to get back into your book from a sleep state. When the device is off, ram is cleared so no power is required to maintain it. There is however, I believe, constant power drain regardless of the power state for the system clock, but this should be negligible.