Quote:
Originally Posted by knc1
Go back a few pages, go forward and have part of one of those forward selected pages only show a partial page.
That sounds like the cache slots are organized in the order of a circular buffer, and the direction change causes an off-by-one error in the tracking of what cache slots have been filled.
Now if Amazon would release some program documentation . . . .
= = = = =
So, two slots per displayed page - the odd one is recorded as filled when it has been erased ....
If you go back far enough, so that you have rotated through all cache slots and then go forward, you should not see the blank half page.
"far enough" can probably be found by a binary search (go back 16, 8, 4 or 12, . . . .) |
FWIW, when I get the blank half page, going forward one page then back one page will cause the missing text to appear.
Also, when dumping the device logs, this error appears: "framework: 41m[PRE_RENDER] fillUpCache(533): ERROR: NO page cache list or current page is a special page that shouldn't use cache [0m"