08-13-2015, 02:27 PM | #16 | |
Wizard
Posts: 1,847
Karma: 3212428
Join Date: Jun 2011
Device: iphone stanza, kobo touch,ASUS TF300,KOBO GLO, Kobo Aura HD, Kobo Mini
|
Quote:
regards Jack |
|
08-13-2015, 03:20 PM | #17 |
Member
Posts: 21
Karma: 194
Join Date: Nov 2008
Device: Cybook Gen 3
|
GeoffR, could you check "all download in browser" - if I turn patch on the script gives data mismatch error
|
Advert | |
|
08-13-2015, 03:31 PM | #18 | |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
Here is the new `Allow download all in Browser` patch: Spoiler:
Last edited by GeoffR; 08-14-2015 at 08:29 AM. Reason: Fixed the patch again! |
|
08-13-2015, 03:46 PM | #19 |
Member
Posts: 21
Karma: 194
Join Date: Nov 2008
Device: Cybook Gen 3
|
Forgot to say Thank You - for all patches from day 1
|
08-14-2015, 06:01 AM | #20 |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
How does sickle work?
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. |
Advert | |
|
08-14-2015, 07:13 AM | #21 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
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. Code:
# pkill -SIGSTOP nickel ; while sleep 1 ; do echo -n . ; done; .......Connection closed by foreign host. 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. Last edited by frostschutz; 08-14-2015 at 07:16 AM. |
08-14-2015, 07:24 AM | #22 |
Junior Member
Posts: 9
Karma: 13128
Join Date: Jun 2015
Device: Kobo Aura HD & Glo
|
Dear GeoffR,
Could you check "Custom page refresh options" there is a data mismatch error in line 349. Thank you |
08-14-2015, 07:31 AM | #23 | |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
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. |
|
08-14-2015, 07:35 AM | #24 | |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
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. |
|
08-14-2015, 07:52 AM | #25 | ||
Junior Member
Posts: 9
Karma: 13128
Join Date: Jun 2015
Device: Kobo Aura HD & Glo
|
1)IN THE POST 24
Quote:
2)IN THE POST 18 Quote:
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~ Last edited by fengcuo; 08-14-2015 at 08:06 AM. |
||
08-14-2015, 07:53 AM | #26 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
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. |
08-14-2015, 08:46 AM | #27 | ||
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
Quote:
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. |
||
08-14-2015, 08:59 PM | #28 |
Groupie
Posts: 151
Karma: 2000
Join Date: Aug 2010
Device: Kindle 3, Voyage
|
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. Last edited by judith009; 08-14-2015 at 11:04 PM. |
08-15-2015, 01:06 AM | #29 |
Bibliophagist
Posts: 38,016
Karma: 150500002
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
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.
|
08-15-2015, 03:10 AM | #30 |
Enthusiast
Posts: 46
Karma: 66500
Join Date: Jan 2011
Device: kobo glo
|
patch_name = `Enforce user line spacing and justification in ePubs`
It gives me a error. THanks |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Instructions for patching firmware 3.16.10 | GeoffR | Kobo Developer's Corner | 12 | 08-14-2015 03:40 AM |
Instructions for patching firmware 3.11.0 | GeoffR | Kobo Developer's Corner | 226 | 06-01-2015 05:32 AM |
Instructions for patching firmware 3.12.1 | GeoffR | Kobo Developer's Corner | 56 | 03-20-2015 05:14 AM |
Instructions for patching firmware 3.12.0 | GeoffR | Kobo Developer's Corner | 165 | 02-07-2015 09:22 AM |
Instructions for patching firmware 3.2.0 | DNSB | Kobo Developer's Corner | 66 | 12-05-2014 07:28 AM |