sideloaded epubs page numbers wrong on home page

[deadmanDoul]

Hi guys,

Just got the Nook Touch. Loving it so far, but am getting a glitch.

Dumped a bunch of sideloaded epubs into the memory card. Many of them work just fine. On some though, the nook will report "Page 1 of 1" on the homescreen where it shows what you're currently reading. Doesn't matter how far into the book I am, and obviously the book has a lot more than one page.  If I tap the homescreen icon, it takes me back to the  cover page of that book.

if I tap the book cover on the library page, however, the nook takes me to the actual page I was reading last. So it actually has the proper page number stored somewhere.

Any ideas?

[jpcapili]

i had this problem too. Not sure what fixed mine. What I did was to remove digital editions directories stored in the memory. re-converted all my epubs. restarted the nook.

[keriflur]

---

deadmanDoul wrote:

if I tap the book cover on the library page, however, the nook takes me to the actual page I was reading last. So it actually has the proper page number stored somewhere.

Any ideas?

---

Have you tried tapping the book icon in the upper left corner of most pages (I think it's there whenever you're not actually in a book)?  This should take you to your actual last read page also.

[deadmanDoul]

Tried the upper left corner "Currently Reading" button. Doesn't work.

I'll try re-exporting the epubs and see how that goes.

[deadmanDoul]

Ok, its working again.

Neither removing the calibre metadata, nor re-exporting new epubs worked.

But I did do a hard factory reset of the device. Had to re-register and re-setup the device, so it was a bit of a pain.

That worked.

cheers,

[keriflur]

Glad you found a solution, and thanks for sharing it with us.

[Sun_Cat]

Based on my experience, this issue is apt to crop up again even after it's temporarily solved. If anyone finds this old thread and has a similar experience to share, please comment where I've posted this on the Issue Reporting board, including links to other threads that reported the same issue.