MobileRead Forums - View Single Post - Hacks Savory - a native ebook conversion package for the Kindle 2

mrlitsta · 07-12-2009, 10:53 AM

I just got a new kindle with firmware v2.0.3 installed. I installed Savory on it, got into an infinite reboot loop (hold 'r' when the screen flashes and it will let you boot a recovery kernel to let you exit the install and retry). Once I fixed that, at first I didn't think Savory worked on the new firmware.

Anyway, I CAN CONFIRM that Savory works as expected (I think) with firmware 2.0.3. It did take about 2 days for my 3 initial PDFs to show up in the menu (I thought it didn't work at first, as other posters have intimated). After that, though, I tried another PDF, and it showed up just fine.

I do still have an issue, can anyone comment? When I load a pdf (images), the screen won't refresh until I hit the menu button twice (to get in and out of the menu). Same thing when I scroll in the images. It is quite annoying. Is the refresh behavior different in earlier firmware revisions, or is this a "known" limitation?

07-12-2009, 10:53 AM	#70
mrlitsta Junior Member Posts: 1 Karma: 10 Join Date: Jul 2009 Device: K2 v2.03	Savory and 2.0.3 I just got a new kindle with firmware v2.0.3 installed. I installed Savory on it, got into an infinite reboot loop (hold 'r' when the screen flashes and it will let you boot a recovery kernel to let you exit the install and retry). Once I fixed that, at first I didn't think Savory worked on the new firmware. Anyway, I CAN CONFIRM that Savory works as expected (I think) with firmware 2.0.3. It did take about 2 days for my 3 initial PDFs to show up in the menu (I thought it didn't work at first, as other posters have intimated). After that, though, I tried another PDF, and it showed up just fine. I do still have an issue, can anyone comment? When I load a pdf (images), the screen won't refresh until I hit the menu button twice (to get in and out of the menu). Same thing when I scroll in the images. It is quite annoying. Is the refresh behavior different in earlier firmware revisions, or is this a "known" limitation? Last edited by mrlitsta; 07-15-2009 at 09:33 AM.