View Single Post
Old 02-20-2012, 02:22 PM   #3
saxondawg
Connoisseur
saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!saxondawg is faster than a rolling 'o,' stronger than silent 'e,' and leaps capital 'T' in a single bound!
 
Posts: 67
Karma: 50952
Join Date: Mar 2010
Device: kindle paperwhite
Quote:
Originally Posted by Blossom View Post
I've never had a crash with the Kindle app. Is it's happening in more then one book?

I do get the squashed covers and it's annoying! I don't have any other issues. If if it's happening with both amazon and sideloaded books there may be something wrong with your device. I would call Kindle Support.
As I said, I have called support and they sent me a new KF, which i appreciated--and found that the issues persist with different books. Not a great number of them, but not just one. I also repeat that I suspect now that the problem is not in the device but in something about the way I'm creating my books in Calibre. Otherwise more people would be reporting these crashes. I personally think it's a graphics issue. First books that had the problem had image files embedded. And whenever the Fire has crashed, it's been either on encountering an image or when I opened the book, and it encountered the cover. But this is just a guess.
saxondawg is offline   Reply With Quote