Kindle firmware 5.8.5.0.2

[odamizu]

Originally Posted by jhowell

The all_systems_logs file is the one most likely to be useful. Try looking for errors somewhere within the last hundred or so lines of the end of the file.

Most messages are formatted as: date:time process[pid]: severity message
where severity is I (info), W (warning), E (error)

Thanks! Will do and will report back what I find. On quick glance, I see a lot of "I"s. Are these minor errors or simply information notifications?

Originally Posted by shalym

Hmmm...what if you download a book from the MobileRead Library and send it to your Kindle without making any changes to it? Do you still have the issue?

The changes I make are for readability because I have very poor eyesight. If the answer is to stop making changes that enable me to read comfortably, then I'd rather live with the missing-text bug.

What if you transfer the book using USB?

Then I lose WhisperSync. Another non-starter for me. But thanks for trying to help!

[shalym]

Originally Posted by odamizu

Thanks! Will do and will report back what I find. On quick glance, I see a lot of "I"s. Are these minor errors or simply information notifications?



The changes I make are for readability because I have very poor eyesight. If the answer is to stop making changes that enable me to read comfortably, then I'd rather live with the missing-text bug.



Then I lose WhisperSync. Another non-starter for me. But thanks for trying to help!

Sorry...I didn't mean to suggest that either of these were solutions, just troubleshooting steps. We can't figure out how to fix it if we can't figure out what causes the problem.

Shari

[jhowell]

Originally Posted by odamizu

On quick glance, I see a lot of "I"s. Are these minor errors or simply information notifications?

Just information about what is going on inside the Kindle.

[odamizu]

Originally Posted by jhowell

The all_systems_logs file is the one most likely to be useful. Try looking for errors somewhere within the last hundred or so lines of the end of the file.

I think we're looking at a caching problem.

This is the error that immediately precedes the missing-text bug:

framework: [41m[PRE_RENDER] fillUpCache(533): ERROR: NO page cache list or current page is a special page that shouldn't use cache[0m

However, the bug doesn't happen every time the error occurs, and once it starts happening, it recurs with shorter intervals in between.

Over the course of 30 minutes of reading:

- error occured 9 times before missing-text bug occurred
- then 3 times followed by missing-text bug
- then 2 times followed by missing-text bug

There's nothing special about the pages where the bug occurs — no illustrations or graphics or tables or anything else unsual. It's just plain old straight text. So I don't think the problem is "a special page that shouldn't use cache."

Therefore, it seems the problem is "No page cache list", though I don't understand what that means. Any ideas?

Another thought that occurred to me is that I need really big font size (resulting in 12 lines per screen with medium line-height). As a result, each screen doesn't have a lot of words, and each book has many more "screen-pages" than a person reading with a more normal font-size. I'm also probably turning pages faster than the average reader because I have fewer words per page.

Do other people experiencing this bug also use large font-sizes?

If this is indeed the problem, and changing font-size is not an option for me, any suggestions on how to ease pressure on the cache?

(This is particularly frustrating because this bug never occurred prior to 5.8.5.0.2 and it has persisted through 5.8.8.)

Thanks for any thoughts!

[HarryT]

Have you reported the problem to Amazon?

[Strether]

Originally Posted by odamizu

Do other people experiencing this bug also use large font-sizes?

I'm reading with the fourth largest size font and reading my latest book it happened three times, I think. But some books it doesn't happen at all.

Jim

[shalym]

Originally Posted by odamizu

I think we're looking at a caching problem.

This is the error that immediately precedes the missing-text bug:

framework: [41m[PRE_RENDER] fillUpCache(533): ERROR: NO page cache list or current page is a special page that shouldn't use cache[0m

However, the bug doesn't happen every time the error occurs, and once it starts happening, it recurs with shorter intervals in between.

Over the course of 30 minutes of reading:

- error occured 9 times before missing-text bug occurred
- then 3 times followed by missing-text bug
- then 2 times followed by missing-text bug

There's nothing special about the pages where the bug occurs — no illustrations or graphics or tables or anything else unsual. It's just plain old straight text. So I don't think the problem is "a special page that shouldn't use cache."

Therefore, it seems the problem is "No page cache list", though I don't understand what that means. Any ideas?

Another thought that occurred to me is that I need really big font size (resulting in 12 lines per screen with medium line-height). As a result, each screen doesn't have a lot of words, and each book has many more "screen-pages" than a person reading with a more normal font-size. I'm also probably turning pages faster than the average reader because I have fewer words per page.

Do other people experiencing this bug also use large font-sizes?

If this is indeed the problem, and changing font-size is not an option for me, any suggestions on how to ease pressure on the cache?

(This is particularly frustrating because this bug never occurred prior to 5.8.5.0.2 and it has persisted through 5.8.8.)

Thanks for any thoughts!

Sorry...I don't think it's large font size-related. There are many times that I have to use font sizes that large when my eyes are tired, and I've never seen the bug.

Shari

[odamizu]

Originally Posted by HarryT

Have you reported the problem to Amazon?

Yes. I keep hoping it will be fixed with each new update, but so far no luck.

Originally Posted by shalym

Sorry...I don't think it's large font size-related. There are many times that I have to use font sizes that large when my eyes are tired, and I've never seen the bug.

Actually that's good news! I was worried using a large font was the problem. Happy to rule that out!

[genoasalami]

Originally Posted by odamizu

Then I lose WhisperSync. Another non-starter for me. But thanks for trying to help!

I transfer exclusively by USB and can confirm that the problem is still there.

[Sirtel]

I've never had a problem with MOBI files, but I've had the same problem with AZW3 files. All my books are sent from Calibre via USB.

[HarryT]

Originally Posted by odamizu

Yes. I keep hoping it will be fixed with each new update, but so far no luck.

So it's not a problem that started with firmware 5.8.5?

[odamizu]

Originally Posted by HarryT

So it's not a problem that started with firmware 5.8.5?

The problem started for me with 5.8.5.0.2. I reported it to Amazon at the time.

Since then, there have been a few updates 5.8.7, 5.8.7.0.1, 5.8.8 and the problem continues with each (minor) update.

[genoasalami]

Originally Posted by odamizu

The problem started for me with 5.8.5.0.2. I reported it to Amazon at the time.

Since then, there have been a few updates 5.8.7, 5.8.7.0.1, 5.8.8 and the problem continues with each (minor) update.

I am really frustrated with myself for updating to the latest firmware instead of rolling back. I hope the jailbreakers figure out how to roll back soon

[odamizu]

Has anyone had the missing-text bug occur while reading a KFX book? (this would be a book with "Enhanced Typesetting" downloaded straight from Amazon)

I'm beginning to wonder if this bug only occurs with mobi and AZW3.

[Sirtel]

I've never had it happen with mobi (most of my books are mobi). Azw3, yes. No idea about kfx.