Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 06-14-2015, 04:30 AM   #16
Nick_1964
Bookworm
Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.
 
Nick_1964's Avatar
 
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
Quote:
Originally Posted by GeoffR View Post
There is no patch to remove the kepub header. There is an option showPageHeader=false that you can add to the [Reading] section of the device's configuration file to remove the title from the kepub header, but it will still leave a much bigger space at the top of the screen than in epubs.
Thank you..so it seems I have a less responding epub reader,and a fast responding kepub reader with a non removable kepub header which can be taken away with the showPageHeader but then only the title is gone,it still consumes the same space,and it can't display PNG files properly anymore, with every update Kobo manage to introduce a new bug that cripple the reader more and more
And then we don't count the fact that without your patches it would be even a less device,because I will not even bother the update if you don't release the patches..
(did Kobo ever give an explanation/reason why it leaves such big gaps at the bottom of the reader while unpatched ?)
Sometimes I feel like i am involved at a hobby project,not a serious company that try to make a decent reader.

Last edited by Nick_1964; 06-14-2015 at 04:46 AM.
Nick_1964 is offline   Reply With Quote
Old 06-14-2015, 06:41 AM   #17
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
I've added the missing `Fix kepub side bearing font cut-off bug` patch to the attachment in post #1, and included it below so you can paste it into your current libnickel.so.1.0.0.patch file:

Spoiler:
Code:
<Patch>
patch_name = `Fix kepub side bearing font cut-off bug`
patch_enable = `no`
# Multi-version patch: 3.16.0 - 3.16.0+
#
# In kepubs, characters with large side bearing values (such as italic f, J) can
# be cut off if they appear at the very end of a line. The problem occurs in
# normal reading mode when the margin adjustment slider is set to minimum and
# in full-screen mode at any margin slider setting. To fix it this patch adds
# one of the following lines to the built-in kepub stylesheet, depending on
# patch options chosen (first line is the default if no options are changed):
#
#  body>div{padding-left:.2em!important;padding-right: .2em!important}
#  body>div{padding-top: .2em!important;padding-bottom:.2em!important}
#  body>div{padding:     .2em                          .2em!important}
#  body>*  {padding-left:.2em!important;padding-right: .2em!important}
#  body>*  {padding-top: .2em!important;padding-bottom:.2em!important}
#  body>*  {padding:     .2em                          .2em!important}
#
# There are two main types of kepub, each affected differently by this patch:
#
# Type 1: kepubs created by Kobo from epub2 books, or created by Calibre with
#         a recent version of the KoboTouchExtended driver.
#
# Type 2: kepubs created by Kobo from epub3 books, or created by Calibre with
#         an old version of the KoboTouchExtended driver.
#
# Type 1 kepubs work best with this patch, the only side effects should be
# slightly larger screen margins. Some Type 2 kepubs might suffer additional
# side effects such as extra horizontal or vertical space between elements.
# There is an option below (marked **1**) where you can choose whether to
# fix the bug only for Type 1 kepubs (default) or for both types.
#
# There are also options below (marked **2**) to make the patch suit kepubs
# with horizontal or vertical text directions, or both. The side effects for
# Type 2 kepubs will likely be worse if the option for both horizontal and
# vertical is chosen.
#
find_base_address = `.\0K\0B\0H\0i\0g\0h\0l\0i\0g\0h\0t\0i\0n\0g\0,\0 \0.\0K\0B\0S\0e\0a\0r\0c\0h\0R\0e\0s\0u\0l\0t\0 \0{\0 \0b\0a\0c\0k\0g\0r\0o\0u\0n\0d\0-\0c\0o\0l\0o\0r\0:\0 \0#\0C\06\0C\06\0C\06\0`
#
replace_string = 0000, `.\0K\0B\0H\0i\0g\0h\0l\0i\0g\0h\0t\0i\0n\0g\0,\0 \0.\0K\0B\0S\0e\0a\0r\0c\0h\0R\0e\0s\0u\0l\0t\0 \0{\0 \0b\0a\0c\0k\0g\0r\0o\0u\0n\0d\0-\0c\0o\0l\0o\0r\0:\0 \0#\0C\06\0C\06\0C\06\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0\t\0`, `.\0K\0B\0H\0i\0g\0h\0l\0i\0g\0h\0t\0i\0n\0g\0,\0.\0K\0B\0S\0e\0a\0r\0c\0h\0R\0e\0s\0u\0l\0t\0{\0b\0a\0c\0k\0g\0r\0o\0u\0n\0d\0-\0c\0o\0l\0o\0r\0:\0#\0C\06\0C\06\0C\06\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0.\0K\0B\0S\0t\0a\0c\0k\0K\0`
#
replace_string = 0098, `.\0K\0B\0S\0t\0a\0c\0k\0K\0e\0y\0w\0o\0r\0d\0,\0 \0.\0K\0B\0S\0e\0a\0r\0c\0h\0R\0e\0s\0u\0l\0t\0,\0 \0.\0K\0B\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0,\0 \0.\0K\0B\0H\0i\0g\0h\0l\0i\0g\0h\0t\0i\0n\0g\0 \0,\0 \0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0{\0 \0f\0o\0n\0t\0-\0s\0i\0z\0e\0:\0 \01\00\00\0%\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0-\0w\0e\0b\0k\0i\0t\0-\0t\0e\0x\0t\0-\0c\0o\0m\0b\0i\0n\0e\0:\0 \0i\0n\0h\0e\0r\0i\0t\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0\t\0`, `e\0y\0w\0o\0r\0d\0,\0.\0K\0B\0S\0e\0a\0r\0c\0h\0R\0e\0s\0u\0l\0t\0,\0.\0K\0B\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0,\0.\0K\0B\0H\0i\0g\0h\0l\0i\0g\0h\0t\0i\0n\0g\0,\0 \0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0{\0f\0o\0n\0t\0-\0s\0i\0z\0e\0:\01\00\00\0%\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0-\0w\0e\0b\0k\0i\0t\0-\0t\0e\0x\0t\0-\0c\0o\0m\0b\0i\0n\0e\0:\0i\0n\0h\0e\0r\0i\0t\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0.\0K\0B\0S\0t\0a\0c\0k\0K\0e\0y\0w\0o\0r\0d\0 \0a\0{\0c\0o\0l\0o\0r\0`
#
replace_string = 1D8, `.\0K\0B\0S\0t\0a\0c\0k\0K\0e\0y\0w\0o\0r\0d\0 \0a\0 \0{\0 \0c\0o\0l\0o\0r\0:\0 \0b\0l\0a\0c\0k\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0\t\0`, `:\0b\0l\0a\0c\0k\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0,\0.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0`
#
replace_string = 0238, `.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0,\0 \0.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0C\0o\0n\0t\0i\0n\0u\0e\0d\0 \0{\0 \0b\0a\0c\0k\0g\0r\0o\0u\0n\0d\0-\0c\0o\0l\0o\0r\0:\0 \0t\0r\0a\0n\0s\0p\0a\0r\0e\0n\0t\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0t\0e\0x\0t\0-\0d\0e\0c\0o\0r\0a\0t\0i\0o\0n\0:\0 \0n\0o\0n\0e\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0\t\0`, `n\0o\0t\0a\0t\0i\0o\0n\0C\0o\0n\0t\0i\0n\0u\0e\0d\0{\0b\0a\0c\0k\0g\0r\0o\0u\0n\0d\0-\0c\0o\0l\0o\0r\0:\0t\0r\0a\0n\0s\0p\0a\0r\0e\0n\0t\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0t\0e\0x\0t\0-\0d\0e\0c\0o\0r\0a\0t\0i\0o\0n\0:\0n\0o\0n\0e\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0.\0K\0B\0S\0t\0a\0c\0k\0K\0e\0y\0w\0o\0r\0d\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0`
#
replace_string = 033E, `.\0K\0B\0S\0t\0a\0c\0k\0K\0e\0y\0w\0o\0r\0d\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0 \0a\0 \0{\0 \0b\0o\0r\0d\0e\0r\0-\0b\0o\0t\0t\0o\0m\0:\0 \01\0p\0x\0 \0s\0o\0l\0i\0d\0 \0b\0l\0a\0c\0k\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0\t\0`, `]\0 \0a\0{\0b\0o\0r\0d\0e\0r\0-\0b\0o\0t\0t\0o\0m\0:\01\0p\0x\0 \0s\0o\0l\0i\0d\0 \0b\0l\0a\0c\0k\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0,\0.\0K\0`
#
replace_string = 03FC, `.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0,\0 \0.\0K\0B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0C\0o\0n\0t\0i\0n\0u\0e\0d\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0 \0{\0 \0b\0o\0r\0d\0e\0r\0-\0b\0o\0t\0t\0o\0m\0:\0 \02\0p\0x\0 \0d\0o\0t\0t\0e\0d\0 \0b\0l\0a\0c\0k\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0\t\0`, `B\0A\0u\0t\0h\0o\0r\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0C\0o\0n\0t\0i\0n\0u\0e\0d\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0{\0b\0o\0r\0d\0e\0r\0-\0b\0o\0t\0t\0o\0m\0:\02\0p\0x\0 \0d\0o\0t\0t\0e\0d\0 \0b\0l\0a\0c\0k\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0.\0K\0B\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0,\0.\0K\0B\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0C\0o\0n\0t\0`
#
replace_string = 0536, `.\0K\0B\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0,\0 \0.\0K\0B\0A\0n\0n\0o\0t\0a\0t\0i\0o\0n\0C\0o\0n\0t\0i\0n\0u\0e\0d\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0 \0{\0 \0b\0o\0r\0d\0e\0r\0-\0b\0o\0t\0t\0o\0m\0:\0 \02\0p\0x\0 \0s\0o\0l\0i\0d\0 \0b\0l\0a\0c\0k\0 \0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0 \0}\0 \0`, `i\0n\0u\0e\0d\0[\0w\0r\0i\0t\0i\0n\0g\0M\0o\0d\0e\0=\0"\0h\0o\0r\0i\0z\0o\0n\0t\0a\0l\0-\0t\0b\0"\0]\0{\0b\0o\0r\0d\0e\0r\0-\0b\0o\0t\0t\0o\0m\0:\02\0p\0x\0 \0s\0o\0l\0i\0d\0 \0b\0l\0a\0c\0k\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0b\0o\0d\0y\0>\0d\0i\0v\0{\0p\0a\0d\0d\0i\0n\0g\0-\0l\0e\0f\0t\0:\0.\02\0e\0m\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0p\0a\0d\0d\0i\0n\0g\0-\0r\0i\0g\0h\0t\0:\0 \0.\02\0e\0m\0!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0}\0 \0`
#
# Fix typo in annotations styles: KBAuthorAnnotation --> .KBAuthorAnnotation
replace_string = 0102, `\x20`, `.`
#
# Choose padding size: 1 = 0.1em, 2 = 0.2em, etc.
replace_string = 05FA, `2`, `2`
replace_string = 0636, `2`, `2`
#
#
# **1** Choose to fix bug for Type1 kepubs only, or both Type1 and Type2 kepubs.
# Default fixes the bug for Type 1 kepubs and has no effect on type 2 kepubs.
#
# Uncomment the following replace_string line to fix the bug for both types,
# but beware there can be undesirable side effects for some Type 2 kepubs:
#replace_string = 05CC, `b\0o\0d\0y\0>\0d\0i\0v\0`, `b\0o\0d\0y\0>\0*\0 \0 \0`
#
#
# **2** Choose padding location to suit text direction of your kepubs.
# Default is left/right padding (suits horizontal text directions only.)
#
# Either uncomment the following two replace_string lines for top/bottom
# padding (suits vertical text directions only) ...
#replace_string = 05EE, `l\0e\0f\0t\0:\0`, `t\0o\0p\0:\0 \0`
#replace_string = 0626, `r\0i\0g\0h\0t\0:\0 \0`, `b\0o\0t\0t\0o\0m\0:\0`
#
# ... or else uncomment the following two replace_string lines for top/bottom
# and left/right padding (suits both horizontal and vertical text directions,
# but may have some undesirable side effects on the layout of Type 2 kepubs,
# such as extra space between paragraphs.)
#replace_string = 05EC, `-\0l\0e\0f\0t\0:\0`, `:\0 \0 \0 \0 \0 \0`
#replace_string = 0600, `!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0;\0p\0a\0d\0d\0i\0n\0g\0-\0r\0i\0g\0h\0t\0:\0`, `\x20\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0`
#
</Patch>


The patch has changed a little but I think it will work just as well. (The new patch employs the body>div selector instead of the div#book-columns selector to save some space.)
GeoffR is offline   Reply With Quote
Advert
Old 06-14-2015, 07:58 AM   #18
outlandos
Connoisseur
outlandos doesn't litteroutlandos doesn't litter
 
outlandos's Avatar
 
Posts: 68
Karma: 152
Join Date: Jun 2015
Device: Kobo Glo HD
Quote:
Before starting:

1. Make sure your Kobo ereader is already running firmware version 3.16.0 (f56b42a2e1).

2. Check that your battery is well charged.

3. Note that in Windows 8 the instructions below might require the batch file to be run in admistrator mode.
I think you mean 3.15.0, or am I wrong?

Anyhow, I followed all the steps carefully and when I unplugged my Glo HD it started updating, but now I see 5 blocks getting black and white in the middle of the screen for as long as 10 straight minutes, does updating always takes this long or should I get worried?

Edit; oh shit, I actually think you did not make a typo there, and this topic is for patching 3.16.0...... I am stupid. Did i brick my device permantly now?

Last edited by outlandos; 06-14-2015 at 08:02 AM.
outlandos is offline   Reply With Quote
Old 06-14-2015, 08:02 AM   #19
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Quote:
Originally Posted by outlandos View Post
I think you mean 3.15.0, or am I wrong?

Anyhow, I followed all the steps carefully and when I unplugged my Glo HD it started updating, but now I see 5 blocks getting black and white in the middle of the screen for as long as 10 straight minutes, does updating always takes this long or should I get worried?
The instructions and patches in this thread are for firmware 3.16.0 only. If you have applied them to a device that is running firmware 3.15.0 then you might have to do a factory reset.

Edit: There is a procedure for doing a manual factory reset for the Glo HD here. There might be other methods too.

Last edited by GeoffR; 06-14-2015 at 08:20 AM. Reason: link to Kobo manual factory reset procedure
GeoffR is offline   Reply With Quote
Old 06-14-2015, 08:08 AM   #20
Nick_1964
Bookworm
Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.
 
Nick_1964's Avatar
 
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
Is the search in library by default still possible ? (not meaning to rush you Geoffr ? )
Nick_1964 is offline   Reply With Quote
Advert
Old 06-14-2015, 09:06 AM   #21
outlandos
Connoisseur
outlandos doesn't litteroutlandos doesn't litter
 
outlandos's Avatar
 
Posts: 68
Karma: 152
Join Date: Jun 2015
Device: Kobo Glo HD
Quote:
Originally Posted by GeoffR View Post
The instructions and patches in this thread are for firmware 3.16.0 only. If you have applied them to a device that is running firmware 3.15.0 then you might have to do a factory reset.

Edit: There is a procedure for doing a manual factory reset for the Glo HD here. There might be other methods too.
Thank you, factory reset worked.

Now I have 3.16.0 installed, it was way easier than i thought!
outlandos is offline   Reply With Quote
Old 06-15-2015, 06:00 AM   #22
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
`Search in library by default`

I've updated the attachment in post #1 to include the missing `Search in library by default` patch, and include it here for those who want to paste it into their current libnickel.so.1.0.0.patch file:
Spoiler:
Code:
<Patch>
patch_name = `Search in Library by default`
patch_enable = `yes`
# SearchEditBox.setSearchType(0) --> SearchEditBox.setSearchType(1)
replace_bytes = 9025D4, 41 46, 01 21
</Patch>


There are now 5 search location options available when you tap the search bar: Bookstore, Library, Current Read, Annotations, and Dictionary. Which one comes up by default depends on where you were when you invoked search.

The patch should cause Library to be the default whenever Bookstore would have been the default without the patch, but have no effect if another location is the default. I.e. if you invoke search from within a book it should still default to Current Read.

Last edited by GeoffR; 06-15-2015 at 06:04 AM. Reason: spelling
GeoffR is offline   Reply With Quote
Old 06-15-2015, 07:19 AM   #23
Nick_1964
Bookworm
Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.
 
Nick_1964's Avatar
 
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
Quote:
Originally Posted by GeoffR View Post
I've updated the attachment in post #1 to include the missing `Search in library by default` patch, and include it here for those who want to paste it into their current libnickel.so.1.0.0.patch file:
Spoiler:
Code:
<Patch>
patch_name = `Search in Library by default`
patch_enable = `yes`
# SearchEditBox.setSearchType(0) --> SearchEditBox.setSearchType(1)
replace_bytes = 9025D4, 41 46, 01 21
</Patch>


There are now 5 search location options available when you tap the search bar: Bookstore, Library, Current Read, Annotations, and Dictionary. Which one comes up by default depends on where you were when you invoked search.

The patch should cause Library to be the default whenever Bookstore would have been the default without the patch, but have no effect if another location is the default. I.e. if you invoke search from within a book it should still default to Current Read.
Thank you very much !
Nick_1964 is offline   Reply With Quote
Old 06-15-2015, 07:53 AM   #24
cramoisi
Librarian
cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.
 
Posts: 346
Karma: 72225
Join Date: Apr 2015
Location: Liège - Belgium
Device: kobo gloHD - KA1
Quote:
Originally Posted by GeoffR View Post
I've updated the attachment in post #1 to include the missing `Search in library by default` patch, and include it here for those who want to paste it into their current libnickel.so.1.0.0.patch file:
Spoiler:
Code:
<Patch>
patch_name = `Search in Library by default`
patch_enable = `yes`
# SearchEditBox.setSearchType(0) --> SearchEditBox.setSearchType(1)
replace_bytes = 9025D4, 41 46, 01 21
</Patch>


There are now 5 search location options available when you tap the search bar: Bookstore, Library, Current Read, Annotations, and Dictionary. Which one comes up by default depends on where you were when you invoked search.

The patch should cause Library to be the default whenever Bookstore would have been the default without the patch, but have no effect if another location is the default. I.e. if you invoke search from within a book it should still default to Current Read.
I was waiting for this ! thanks a lot
cramoisi is offline   Reply With Quote
Old 06-15-2015, 08:08 AM   #25
Ripplinger
350 Hoarder
Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.Ripplinger ought to be getting tired of karma fortunes by now.
 
Ripplinger's Avatar
 
Posts: 3,574
Karma: 8281267
Join Date: Dec 2010
Location: Midwest USA
Device: Sony PRS-350, Kobo Glo & Glo HD, PW2
One I was watching for daily as well, thank you very much!
Ripplinger is offline   Reply With Quote
Old 06-16-2015, 08:10 AM   #26
Gabriel.Voyager
Connoisseur
Gabriel.Voyager began at the beginning.
 
Gabriel.Voyager's Avatar
 
Posts: 50
Karma: 10
Join Date: Jun 2015
Location: Turin, Italy
Device: Kindle Oasis 2, Kindle Voyage 3G, Kobo Aura H2O, iPad Mini Retina
The last version of the patch on my Kobo Glo HD, with the `Search in Library by default` and `Fix kepub side bearing font cut-off bug` activated is perfect.
Thank you!
Gabriel.Voyager is offline   Reply With Quote
Old 06-16-2015, 08:12 AM   #27
Gabriel.Voyager
Connoisseur
Gabriel.Voyager began at the beginning.
 
Gabriel.Voyager's Avatar
 
Posts: 50
Karma: 10
Join Date: Jun 2015
Location: Turin, Italy
Device: Kindle Oasis 2, Kindle Voyage 3G, Kobo Aura H2O, iPad Mini Retina
Quote:
Originally Posted by cramoisi View Post
I was waiting for this ! thanks a lot
Do you have installed the 3.16 on your Aura H2O?
If yes, which Mark? The Mark 6?

Thank you!
Gabriel.Voyager is offline   Reply With Quote
Old 06-16-2015, 08:20 AM   #28
cramoisi
Librarian
cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.cramoisi did not drink the Kool Aid.
 
Posts: 346
Karma: 72225
Join Date: Apr 2015
Location: Liège - Belgium
Device: kobo gloHD - KA1
Quote:
Originally Posted by Gabriel.Voyager View Post
Do you have installed the 3.16 on your Aura H2O?
If yes, which Mark? The Mark 6?

Thank you!
I did it on my H2O with mark4 KoboRoot only, following the advice of davidfor here. No problem till now.
cramoisi is offline   Reply With Quote
Old 06-16-2015, 09:57 AM   #29
mbovenka
Wizard
mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.
 
Posts: 2,018
Karma: 13471689
Join Date: Oct 2007
Location: Almere, The Netherlands
Device: Kobo Sage
Quote:
Originally Posted by cramoisi View Post
I did it on my H2O with mark4 KoboRoot only, following the advice of davidfor here. No problem till now.
Same here: Mark 4 KoboRoot.tgz + patches. Works like a charm.
mbovenka is offline   Reply With Quote
Old 06-16-2015, 07:16 PM   #30
forster01
Groupie
forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.forster01 can do the Funky Gibbon.
 
Posts: 195
Karma: 82624
Join Date: May 2013
Device: Kobo Forma, Kobo Aura One, Kobo Aura HD, Kindle, Amazon Fire HD
Kobo aura HD, Mark 4 KoboRoot.tgz + patches. Works like a charm, here also.
But i cant make on change that i would like to: I cant chande inital font size from 12 to 18. I could really use some help:

Code:
# Start with this font size: (GloHD, Others)
replace_int = 87B38E, 14, 14
replace_int = 87B392, 12, 18
Is this the line that should look like this? or i'm doing something wrong?
forster01 is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Instructions for patching firmware 3.13.1 GeoffR Kobo Developer's Corner 56 07-01-2016 09:59 AM
Instructions for patching firmware 3.15.0 GeoffR Kobo Developer's Corner 146 05-24-2016 06:10 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


All times are GMT -4. The time now is 05:18 PM.


MobileRead.com is a privately owned, operated and funded community.