Instructions for patching firmware 4.11.11982

[mountian]

Originally Posted by mbovenka

You can treat it as an Aura One, that works fine for me.

Many thanks for your answere. well, still a easy question... how to treat it as aura one, delete string for other device? thanks

[geek1011]

Originally Posted by mountian

Many thanks for your answere. well, still a easy question... how to treat it as aura one, delete string for other device? thanks

Just install it as-is.

[mountian]

Originally Posted by geek1011

Just install it as-is.

Thanks! it works well!

[DrChiper]

I tried the patches for FW 4.11.11982 on my KA2v1 and applied the rotation patch. It did worked to select landscape ... once
Thereafter, I could not select portrait mode, nor menus from the menu bar etc. anymore. The menus simply did not show and landscape remained
The only cure seemed a fresh, unpatched install of FW 4.11.11982

[geek1011]

I've released patches v30 with a new "Both page turn sides go next" patch by me

This patch makes both page turn sides (or top/bottom, depending on your selection in Reading Settings) go next in the reader. This patch was made at the request of anigrin and Mrs_Often.

This patch was quite tricky to track down, as there were quite a few ways I could have done this. The first way was to have changed out the dimensions of the calculated rectangles for page turning, but that ended up being too complicated due to the use of QHash's of QRects and pointers upon pointers to functions. I ended up wasting quite a bit of time trying to do it this way. The second way was to just swap out the next and previous page functions, but this had way too many side effects. The third way was to override the tap detection completely, and although this was relatively simple, it would have become a big hassle to update in future versions. The way I ended up doing this is by taking advantage of the right-to-left support (which swaps back and forward taps), and making it set back = forward and forward = forward instead of back = forward and forward = back.

[geek1011]

There is now a new kobopatch request thread, which consolidates all the requests for patches and major kobopatch features.

I have tried my best to collect all the requests from before scattered around the threads, and if I missed anything, please tell me.

[Mrs_Often]

Originally Posted by geek1011

I've released patches v30 with a new "Both page turn sides go next" patch by me



This patch makes both page turn sides (or top/bottom, depending on your selection in Reading Settings) go next in the reader. This patch was made at the request of anigrin and Mrs_Often.



This patch was quite tricky to track down, as there were quite a few ways I could have done this. The first way was to have changed out the dimensions of the calculated rectangles for page turning, but that ended up being too complicated due to the use of QHash's of QRects and pointers upon pointers to functions. I ended up wasting quite a bit of time trying to do it this way. The second way was to just swap out the next and previous page functions, but this had way too many side effects. The third way was to override the tap detection completely, and although this was relatively simple, it would have become a big hassle to update in future versions. The way I ended up doing this is by taking advantage of the right-to-left support (which swaps back and forward taps), and making it set back = forward and forward = forward instead of back = forward and forward = back.

Thank you. I wish there was something I could do in return.


EDIT: I haven’t downloaded V30 yet because I’m not near a computer at the moment, but: will it work for 4.9.11311, or will I have to give in and update to 4.11.11982?

[jackie_w]

Originally Posted by Mrs_Often

EDIT: ... will it work for 4.9.11311, or will I have to give in and update to 4.11.11982?

Assuming you mean the patch named 'Both page turn sides go next', the answer is - no, not as it stands.

Any patch which contains one or more absolute offsets, e.g.

- ReplaceBytes: {Offset: 0x9EA938, ...}

is always specific to a single firmware version.

[Mrs_Often]

Originally Posted by jackie_w

Assuming you mean the patch named 'Both page turn sides go next', the answer is - no, not as it stands.



Any patch which contains one or more absolute offsets, e.g.

- ReplaceBytes: {Offset: 0x9EA938, ...}

is always specific to a single firmware version.

Yes, that’s what I meant. Sorry, I was in a hurry and apparently didn’t make time to make sure my post made sense.

Thanks Jackie! Poo, I’ll have to put up with the long-tap for footer display information change. Oh well, tap anywhere for page forward is well worth it!

[geek1011]

Originally Posted by Mrs_Often

Yes, that’s what I meant. Sorry, I was in a hurry and apparently didn’t make time to make sure my post made sense.

Thanks Jackie! Poo, I’ll have to put up with the long-tap for footer display information change. Oh well, tap anywhere for page forward is well worth it!

I might be able to patch the long-tap if you want. I can also port the patch to the old version without much effort.

[codychan]

Originally Posted by geek1011

I've released patches v30 with a new "Both page turn sides go next" patch by me

This patch makes both page turn sides (or top/bottom, depending on your selection in Reading Settings) go next in the reader. This patch was made at the request of anigrin and Mrs_Often.

This patch was quite tricky to track down, as there were quite a few ways I could have done this. The first way was to have changed out the dimensions of the calculated rectangles for page turning, but that ended up being too complicated due to the use of QHash's of QRects and pointers upon pointers to functions. I ended up wasting quite a bit of time trying to do it this way. The second way was to just swap out the next and previous page functions, but this had way too many side effects. The third way was to override the tap detection completely, and although this was relatively simple, it would have become a big hassle to update in future versions. The way I ended up doing this is by taking advantage of the right-to-left support (which swaps back and forward taps), and making it set back = forward and forward = forward instead of back = forward and forward = back.

Thank you, geek1011, I think this patch solove my request at https://www.mobileread.com/forums/sh...0&postcount=57 with a different way.

[geek1011]

Originally Posted by codychan

Thank you, geek1011, I think this patch solove my request at https://www.mobileread.com/forums/sh...0&postcount=57 with a different way.

No problem! I'm glad it helped. Note that you have a typo in your link.

[anigrin]

Thanks for making the change and doing it so quickly. I really appreciate it.

I'm unsure about one thing. I have the Aura One, whose latest firmware version is: 4.10.11655. When I go the the v30 download page, there are multiple downloads available. If I choose the kobopatch_4.10.11655.zip, I notice that the "Both page turn sides go next" is not implemented. However, it is implemented in the kobopatch_4.11.11982.zip (which seems to be intended only from the Forma.)

So I'm not sure how to proceed. Should I copy the text snippet from the new version onto my version, or is it safe to install the 4.11.11982 onto my Aura One?

[geek1011]

Originally Posted by anigrin

Thanks for making the change and doing it so quickly. I really appreciate it.

I'm unsure about one thing. I have the Aura One, whose latest firmware version is: 4.10.11655. When I go the the v30 download page, there are multiple downloads available. If I choose the kobopatch_4.10.11655.zip, I notice that the "Both page turn sides go next" is not implemented. However, it is implemented in the kobopatch_4.11.11982.zip (which seems to be intended only from the Forma.)

So I'm not sure how to proceed. Should I copy the text snippet from the new version onto my version, or is it safe to install the 4.11.11982 onto my Aura One?

It is safe to install 4.11.11982 on your Aura ONE (and I recommend it, as I'm doing all new patch development on the latest version). If you want to stay with the old version, I can port the patch over.

The way the releases work is all the zips are generated from the currently available patches in the repository. Basically, the releases are a snapshot of the current state of the available patches. Not every release updates every zip (releases which do are added to the changelog in the second post of every patch thread). This makes it easy to add new patches, backport them to older firmware if needed (I always backport nickel patches, and sometimes libnickel ones), and make fixes and updates to old patch zips.

[anigrin]

Just upgraded to my Aura One to 4.11 and applied the patch. Everything works great! Thanks very much.