16e- same old problem

This message was edited 1 time. Last update was at 08/27/2010 18:06:53

For all the improvements that came with 16e, Ectaco jettisoned an important basic function- page memory (yet again). Once again I reflashed, then went back to 15D-B again.

If I am reading a book and I am on page 25, when I page down 4 times, I am still on page 25 because the reader uses what I would call sub-pages to duplicate the size of actual printed book pages. So at font #18, there are 4 screens or sub-pages per numerical page number- call them 25a, 25b, 25c, 25d-- THEN 26. Firmware version 15D-B always remembers the sub-page and brings you back to exactly where you left off. Version 16e brings you to the first sub page, 25a, even if you left off on 25d. If you are reading 4 or 5 books concurrently, this is, to ME at least, a major aggravation. When I encounter this, I flash back to the last known good version, and I don't care about ALL the other embellishments that came with the new version.

If I were improving cars and came out with a chip enhancement that made it go twic

ronouel wrote:For all the improvements that came with 16e, Ectaco jettisoned an important basic function- page memory (yet again). Once again I reflashed, then went back to 15D-B again.

If I am reading a book and I am on page 25, when I page down 4 times, I am still on page 25 because the reader uses what I would call sub-pages to duplicate the size of actual printed book pages. So at font #18, there are 4 screens or sub-pages per numerical page number- call them 25a, 25b, 25c, 25d-- THEN 26. Firmware version 15D-B always remembers the sub-page and brings you back to exactly where you left off. Version 16e brings you to the first sub page, 25a, even if you left off on 25d. If you are reading 4 or 5 books concurrently, this is, to ME at least, a major aggravation. When I encounter this, I flash back to the last known good version, and I don't care about ALL the other embellishments that came with the new version.

If I were improving cars and came out with a chip enhancement that

Sorry for the delay. The problem exists in plain old text files. I have not tested other formats. Page memory is acting like a BOOKMARK instead of simply remembering where you left off. The two functions are not the same. Recalling a bookmark has always been inexact, but the page memory on resuming power used to put you exactly where you left off.

This means that every time you shut off the JBL and turn it on again, you have to root around 3 or 4 screens to find your place again.

ronouel wrote:Sorry for the delay. The problem exists in plain old text files. I have not tested other formats. Page memory is acting like a BOOKMARK instead of simply remembering where you left off. The two functions are not the same. Recalling a bookmark has always been inexact, but the page memory on resuming power used to put you exactly where you left off.

This means that every time you shut off the JBL and turn it on again, you have to root around 3 or 4 screens to find your place again.

Hey,

Ok so on TXT files it would remember your page but not your sub-page. This happens when you leave and re-enter a book later on. Is this correct?

I can bring the issue up with the tech. Thanks for the feedback!