Mobi Files Crashing in Kindle Fire

[Blossom]

Originally Posted by ElizabethN

I'm on windows 7 64bit. How do you take screenshots?

Use your print screen button on your keyboard then paste into a graphics program.

Here are the settings for my Calibre. Other then using a different profile all other settings are default.

[Sasssysweeet]

Elizabeth, the crashing of mobi files that could be seen was my original problem which got fixed but then all of the sudden after the most recent update of calibre new files just didn't show up at all. You would not believe how frustrating this all has been.

[Sasssysweeet]

Okay, I converted a file using Blossom's format and it seems to be working. Let's hope it continues. LOL. If not I will be back over here again. You all have been sooooooooo helpful and I totally appreciate it. I'll post an update if this fix continues to work out. Thanks again for everything.

[Blossom]

Originally Posted by Sasssysweeet

Elizabeth, the crashing of mobi files that could be seen was my original problem which got fixed but then all of the sudden after the most recent update of calibre new files just didn't show up at all. You would not believe how frustrating this all has been.

Sounds to me there is a setting that is causing this and those using that setting is having this issue. Now if only we could narrow down which setting it is.

[ElizabethN]

With the Harmer John book, I've narrowed it down to structure detection. Just a few more permutations and I'll post more.

[ElizabethN]

Using Harmer John epub - converting epub to mobi,

the crashing problem arises from settings in structure detection, specifically "insert metadata at start of book."

Variations with it checked, never opened on the fire without crashing. Variations with it not checked, worked with no problem.

for those that like AZW3, checked or not resulted in the book opening with no problems.

Does this apply to all calibre created mobi files? Probably not, as I have several that have metadata inserted at the beginning and that work just fine on the fire. But, if I have problem with a file, I would try re-doing the conversion without insert metadata. I'd also try to avoid additional variables by removing the problem file from the device and deleting the mobi file from calibre. Then convert, and send the new mobi to the fire.

Hope this helps Sasssysweeet and others with problems.

[Blossom]

Originally Posted by ElizabethN

Using Harmer John epub - converting epub to mobi,

the crashing problem arises from settings in structure detection, specifically "insert metadata at start of book."

Variations with it checked, never opened on the fire without crashing. Variations with it not checked, worked with no problem.

for those that like AZW3, checked or not resulted in the book opening with no problems.

Does this apply to all calibre created mobi files? Probably not, as I have several that have metadata inserted at the beginning and that work just fine on the fire. But, if I have problem with a file, I would try re-doing the conversion without insert metadata. I'd also try to avoid additional variables by removing the problem file from the device and deleting the mobi file from calibre. Then convert, and send the new mobi to the fire.

Hope this helps Sasssysweeet and others with problems.

Good work! The other person who had crashing had metadata inserted too. Looks like a bug ticket needs to be submitted so that Kovid can take a look at it.

[Sasssysweeet]

Out of curiosity I used all of Blossom's settings but went ahead and checked the insert metadata and the file still appeared. I haven't tried the drag and drop method to see if it works yet.

[ElizabethN]

bug report filed, probably low priority as this is not happening with every conversion and work-arounds exist

[saxondawg]

I'm another show-metadata guy who is having the crashing problem. Just found this thread. Interestingly, when I converted to azw3 instead of mobi, the files seem to work (though I don't like them because they justify the right margin against my preferences). I do hope Kovid will find a workaround for this bug that doesn't involve some of the drawbacks the earlier workaround did. These file crashes have been annoying. My observation is that the Fire can't approach how sturdy a reader the K3 (keyboard) is. I never had any of these problems with it, and I have collections and so many other features they've never bothered to add to the Fire.

[Sasssysweeet]

I also never had any probs with my K3G. I am currently able to convert without crashing problems but I haven't used any of the updates for Calibre recently because I'm afraid something will go wrong again.

[saxondawg]

Just as a note here, what is currently working for me is to reconvert the file from its source to .rtf (rich text file). Then I convert from there to a .mobi, and the file doesn't crash. it's not an ideal solution. I lose some hyperlinks, for example. But it's a workaround until we a new version of Calibre addresses this bug.

[saxondawg]

Well, it looks to me like Kovid has already addressed this problem with Calibre 8.5.5. The fact that I'm not surprised indicates just how my opinion is of this program and the perfectionist approach to it of its creator. I couldn't be any more appreciative.

[saxondawg]

Oops. I spoke too soon. Getting lots of crashes in the Fire now. For the record, i see the problem as a Kindle Fire one, not a Calibre one. I never heard about crashes on previous generations of Kindles. I don't really understand why the Fire is so unstable in its reader program--why it still lacks features like collections, universal search, page numbers. I hate to say it (being a big Amazon supporter) but my K3 eInk looks better and better all the time. The Fire has given me lots of headaches.

[Sasssysweeet]

Try following all the settings that Blossom posted. It worked on mine and I haven't updated because I don't want to mess anything up.