Instructions for patching firmware 3.17.0

[jackastor]

Originally Posted by DNSB

I took it as meaning to extract the files/directories inside the .zip file into the same patch_kobo_3170 directory as the original 3.17.0 patches.

Ahhh... that's why there is no .bat file, the current one handles the sickel patch.

Sounds good... it never hurts to clarify!

regards

Jack

[grucha44]

GeoffR, could you check "all download in browser" - if I turn patch on the script gives data mismatch error

[GeoffR]

Originally Posted by grucha44

GeoffR, could you check "all download in browser" - if I turn patch on the script gives data mismatch error

Sorry about that, I've fixed it and updated the attachment in post #1.

Here is the new `Allow download all in Browser` patch:

Spoiler:

<Patch>
patch_name = `Allow download all in Browser`
patch_enable = `no`
replace_bytes = 78B42C, 7C F4 8A EF, 01 20 01 20
</Patch>

[grucha44]

Forgot to say Thank You - for all patches from day 1

[GeoffR]

What it looks like to me is that sickle starts a 20-second timer when it is first run, and whenever it receives a ping it restarts the timer at 10 seconds. If sickle is suspended then after resuming it restarts the timer at 10 seconds. If the timer ever expires then sickle triggers a reboot.

If that is how it works then the patch I posted in post #13 should be completely safe, as it just increases those timer durations.

[frostschutz]

Not sure how you get 10 seconds. It still seems more like 5 to me.

If I force nickel to hang (-SIGSTOP) the device is dead after 7 seconds.

# pkill -SIGSTOP nickel ; while sleep 1 ; do echo -n . ; done;
.......Connection closed by foreign host.

(each dot represents 1 second - with a 10s timeout between pings there should be at least 10 dots?)

I will try it with your patch later.

Maybe it sends a ping every 10s but it does not wait 10s for reply? In that case sending a ping every 30s or even larger interval would not solve the issue entirely if nickel didn't happen to reply instantly when the ping was sent.

Yep, I don't really know how it works either. I just know that sickel is broken by design.

[fengcuo]

Dear GeoffR,

Could you check "Custom page refresh options"
there is a data mismatch error in line 349.

Thank you

[GeoffR]

Originally Posted by frostschutz

Not sure how you get 10 seconds. It still seems more like 5 to me.

I am just looking at the code, QTimer.start(10000) is called in two places and QTimer.start(20000) is called in one place.

If nickel is stopped 3 seconds after it sent its last ping then sickel's timer will expire 7 seconds later and it will reboot.

[GeoffR]

Originally Posted by fengcuo

Dear GeoffR,

Could you check "Custom page refresh options"
there is a data mismatch error in line 349.

Thank you

It is working okay for me, I use this patch myself.

If you are using the second alternative, check that you have only commented out the three lines from the first alternative. The first replace_bytes line in the patch should not be changed regardless of which alternative you are using.

[fengcuo]

1)IN THE POST 24

Originally Posted by GeoffR

It is working okay for me, I use this patch myself.

If you are using the second alternative, check that you have only commented out the three lines from the first alternative. The first replace_bytes line in the patch should not be changed regardless of which alternative you are using.

Thank you. it is working fine. It's my fault. I forgot to commente the lines from the first alternative.

2)IN THE POST 18

Originally Posted by GeoffR

Here is the new `Allow download all in Browser` patch:
<Patch>
patch_name = `Allow download all in Browser`
patch_enable = `no`
replace_bytes = 78B42C, 7C F4 8A E, 01 20 01 20
</Patch>

It seems that the `Allow download all in Browser` patch is still not working when i turn patch on. There is still a data mismatch error.

3)Is there any patch to custom(or reduce) the top margin (header) of the Kepubs.
The top margin (header) is too large in the kepubs.

Thank you~

[frostschutz]

Tried with your sickel patch, I get up to 29 dots = seconds until reboot. Sometimes it reboots after as little as 25 dots.

Also, things keep running if I wake nickel after 20 dots. So this patch seems to be working, for people who want longer timeouts than default.

Great work! I'll still leave it disabled entire for my system, though.

[GeoffR]

Originally Posted by fengcuo

It seems that the `Allow download all in Browser` patch is still not working when i turn patch on. There is still a data mismatch error.

Apologies once again, I am sure I have fixed it now, I've updated the attachment to post #1 and edited post #18

Is there any patch to custom(or reduce) the top margin (header) of the Kepubs.

I think the only options to affect the KePub header are:

1. Use the FullScreenReading=true feature setting to activate full-screen mode, which has no header or footer as such but the top and bottom margins adjust to match the side margins.

2. Use the showPageHeader=false reading setting to remove the title from the header. This still leaves a large gap at the top of the screen, but it is slightly smaller than with the title.

Here is a post about adding feature settings to the configuration file. Reading settings are the same but are added under the existing [Reading] section.

[judith009]

I forgot to upgrade my h2o to 3.17 first, before trying to apply the patches. So I tried to apply the patched 3.17 firmware to a 3.15 device. Now it's stuck in the upgrading loop, showing the progress bar/dots moving across the screen, with the led on the top blinking.

Is there any way to fix this?

Edit: BTW I've been using these patches successfully for over a year. I thank Geoff very much for the hard work. This was the only time I forgot to upgrade first.

Edit2: I ended up pressing the reset pin. It restarted, then I got a screen saying "critical error, do you want to restore factory settings?" I hit the "yes" checkmark, and now it says it's restoring. I guess I'll assume it'll be alright from here.

[DNSB]

Originally Posted by judith009

Edit2: I ended up pressing the reset pin. It restarted, then I got a screen saying "critical error, do you want to restore factory settings?" I hit the "yes" checkmark, and now it says it's restoring. I guess I'll assume it'll be alright from here.

This may have been triggered by the counter for the number of times the device restarted and nickel did not start successfully. After 5 failures, you get the critical error message. I've found it more reliable than tapping the screen corners to trigger a hardware factory reset on those Kobo devices without a hardware home/light button.

[sage79]

patch_name = `Enforce user line spacing and justification in ePubs`
It gives me a error.
THanks