JBPatch

[diba]

Originally Posted by ixtab

All of the cover-view stuff is originally coded by Amazon, but simply deactivated. I merely patched three methods in the Home Booklet to allow setting and retrieving the view mode value, and two controller classes to return true instead of false when asked if they support cover view. You'll see that the code of the patch is pretty trivial: https://bitbucket.org/ixtab/jbpatche...ViewPatch.java

OK, tried to understand, but no chance ..., my question, do you think, by modifying the one or other file "manually" on a K4, coverview could be activated there as well? Where do I have to look for to give you an idea, if this could work?

[ixtab]

I repeat: I don't own a K4, so I have no idea

The first thing would be to port the JBPatch core to the K4.

Then you could decompile the Home Booklet and check whether it looks anything like the one of the K5 (in particular, if you find the strings "LIST_VIEW_MODE" and/or "COVER_VIEW_MODE") in there, it's probably possible. But it still wouldn't be a piece of cake, because you'd have to do all the reverse engineering work again (well, if you're lucky, you might be able to benefit from some of the stuff I did for the K5).

Remembering from back when I got a K4 image for testing, the K5 and K4 jars are radically different (probably an entirely different code base), so the chances to actually find substantial (code) similarities between these framework is minimal.

[techiemonkey]

Does anyone know why amazon book covers look bigger than calibre generated book covers?

[Titano]

Originally Posted by techiemonkey

Does anyone know why amazon book covers look bigger than calibre generated book covers?

Just an idea but maybe your computer has a higher resolution then 600x800. Just messing with you . But your computer most likely does have a higher resolution and because of that (depending on your monitor size) the images will look smaller. Right?

[techiemonkey]

i dont think i undestood you completely but i am saying they look bigger on my kindle.

[geekmaster]

Originally Posted by techiemonkey

Does anyone know why amazon book covers look bigger than calibre generated book covers?

The cover image is stored inside the ebook file. Calibre has some rules that it follows when adding a cover image to a converted ebook, as documented here:
http://manual.calibre-ebook.com/conversion.html

Amazon may use different rules when converting ebooks, giving a different cover image size.

[Abradoks]

Originally Posted by ixtab

More info about the Kindlet jailbreak (including source code) here: https://www.mobileread.com/forums/sho....php?p=1905690

I tried to derive from SuicidalKindlet, then call "jailbreak.getContext().requestPermission(new AllPermission())". It returns "true", but exec doesn't work.

[ixtab]

Originally Posted by Abradoks

I tried to derive from SuicidalKindlet, then call "jailbreak.getContext().requestPermission(new AllPermission())". It returns "true", but exec doesn't work.

Give it a little time after loading, like I do in my Kindlets with the splash screens. Alternatively, try to do it in the onStart() method instead of onCreate() (untested).

I don't know why that is, but immediately trying it in onCreate() seems to fail most of the time. And of course, be sure to follow the syslog and /mnt/us/developer/AppName/work/crash.log.

[techiemonkey]

@so is there a way to change the calibre-generated covers so that they are equal in size to that of amazon book covers?

[Abradoks]

Originally Posted by ixtab

Give it a little time after loading, like I do in my Kindlets with the splash screens. Alternatively, try to do it in the onStart() method instead of onCreate() (untested).

I don't know why that is, but immediately trying it in onCreate() seems to fail most of the time. And of course, be sure to follow the syslog and /mnt/us/developer/AppName/work/crash.log.

Well, I call it from onStart() (as in CollectionManagerKindlet.java, so I guess it is tested ). Adding "Thread.sleep(1000);" around it changes nothing. It doesn't crash, and I'm not sure what to look for in messages. They are pretty verbose with ;debugOn.
Is it too much to ask for sample app, that works for you?

[geekmaster]

Originally Posted by techiemonkey

@so is there a way to change the calibre-generated covers so that they are equal in size to that of amazon book covers?

If you had read the calibre page at the link that I provided in my previous post, you would have known that the answer to your question is "yes" and you would not have needed to ask it here.

Go back and read the calibre web page at the link provided in my previous post. Pay attention to the fact that calibre can insert an cover image of your choice into the ebook. You can resize an image before giving it to calibre.

[techiemonkey]

i read your link.i should resize the cover to 600*800 right

[ixtab]

Originally Posted by Abradoks

Well, I call it from onStart() (as in CollectionManagerKindlet.java, so I guess it is tested ). Adding "Thread.sleep(1000);" around it changes nothing. It doesn't crash, and I'm not sure what to look for in messages. They are pretty verbose with ;debugOn.
Is it too much to ask for sample app, that works for you?

https://www.mobileread.com/forums/sho...&postcount=293
That's a pretty minimal application with only two classes.

[veezh]

After upgrading from a Kindle Keyboard to a Kindle Touch in March, I have to admit there's one feature I do miss -- the progress bar at the bottom of the screen showing where you are at all times in a book.

If the TOC was formatted correctly, the chapters would also appear on the bar as nodes, which I found useful, too.

The Touch does show a progress bar, but only for periodicals, as far as I know.

IMHO, it would be great to be able to have this old functionality back, at least for those who miss it.

I'm a complete and utter noob when it comes to Java (but am planning to have a look at your tutorial, ixtab! ). Anyway, just thought I'd put the idea out there.

[NiLuJe]

@veezh/ixtab: FWIW, there was a reader setting to enable/disable the progress bar in FW 3/[4?]. I don't remember if it was properly hooked to anything, but it existed .