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 01-11-2017, 03:24 PM   #121
kido.resuri
Groupie
kido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura about
 
Posts: 172
Karma: 4282
Join Date: Dec 2016
Location: Hungary
Device: Kobo Aura H2O
Quote:
Originally Posted by GeoffR View Post
There is a lot you can do without a disassembler though, most of the current patches just modify the data, mainly strings, and dont need to know anything about the code that uses it.
Nice, I will play with it a bit later, I have some other projects now to finish (Kobo translation).

Last edited by kido.resuri; 01-11-2017 at 05:38 PM. Reason: Removed obsolate questions
kido.resuri is offline   Reply With Quote
Old 01-13-2017, 10:27 AM   #122
giddie
Member
giddie began at the beginning.
 
giddie's Avatar
 
Posts: 19
Karma: 10
Join Date: Jan 2017
Location: Birmingham, UK
Device: Kobo Aura H2O
Quick question: I've patched my libnickel.so to fix the text-align rule on p and divs. But I haven't been able to find anything that might be responsible for forcing all links to be underlined and blue (well, grey, but I assume blue). I can't get "a" elements to respond to text-decoration or color css properties, even with !important. But it doesn't look like anyone's figured out a patch for it yet either?
giddie is offline   Reply With Quote
Old 01-13-2017, 01:20 PM   #123
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 giddie View Post
Quick question: I've patched my libnickel.so to fix the text-align rule on p and divs. But I haven't been able to find anything that might be responsible for forcing all links to be underlined and blue (well, grey, but I assume blue). I can't get "a" elements to respond to text-decoration or color css properties, even with !important. But it doesn't look like anyone's figured out a patch for it yet either?
Is this for ePub or KePub?

In general,if you have some CSS that does what you want when it is added to the book's stylesheet by Calibre, say by using the kobo_extra.css feature of the KoboTouch driver, then you can create a patch that will add the same CSS to the device's built-in stylesheet. But if You can't do it with Calibre then it is unlikely you will be able to do it with a patch. (Edit: The exception is that a patch can change something that is being forced by the built-in stylesheet.)

Edit: There is this string in libnickel.so.1.0.0:
Code:
a:link, a:visited, a:hover, a:active { border-bottom: 1px dotted black !important; color: #696969 !important; }
I'm not sure in what context it is used, probably somewhere in the KePub stylesheet. Maybe it is the culprit?

Edit: Here is a patch to remove !important from the above CSS in libnickel.so.1.0.0, if you want to test it:
Spoiler:
Code:
<Patch>
patch_name = `test`
patch_enable = `yes`
#
# Removes !important from the following CSS:
#
#  a:link, a:visited, a:hover, a:active { border-bottom: 1px dotted black !important; color: #696969 !important; }
#
find_base_address = `a\0:\0l\0i\0n\0k\0,\0 \0a\0:\0v\0i\0s\0i\0t\0e\0d\0,\0`
replace_string = 008E, `!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0`, ` \0 \0 \0 \0 \0 \0 \0 \0 \0 \0`
replace_string = 00C4, `!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0`, ` \0 \0 \0 \0 \0 \0 \0 \0 \0 \0`
#
</Patch>

Last edited by GeoffR; 01-13-2017 at 01:56 PM. Reason: Here is a patch ...
GeoffR is offline   Reply With Quote
Old 01-15-2017, 02:20 AM   #124
ams
Enthusiast
ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.ams is not intimidated by interfenestral monkeys.
 
Posts: 29
Karma: 26326
Join Date: Jul 2013
Device: Kobo: Mini, Libra 2
Yes this is used in the kepub stylesheet. Tried the patch on my mini: now the formatting of links is as specified in the book's css, except that the dotted border-bottom is added. How can I change the patch to completely remove 'border-bottom: 1px dotted black !important; ' not just '!important' ?

Last edited by ams; 01-15-2017 at 02:21 AM. Reason: typo
ams is offline   Reply With Quote
Old 01-15-2017, 04:25 AM   #125
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 ams View Post
Yes this is used in the kepub stylesheet. Tried the patch on my mini: now the formatting of links is as specified in the book's css, except that the dotted border-bottom is added. How can I change the patch to completely remove 'border-bottom: 1px dotted black !important; ' not just '!important' ?
This patch should do that. You can comment out the last replace_string line if you want to leave the color style intact:

`Un-force link decoration in KePubs` (libnickel.so.1.0.0.patch)
Spoiler:
Code:
<Patch>
patch_name = `Un-force link decoration in KePubs`
patch_enable = `yes`
#
# The built-in KePub stylesheet contains the following link decoration CSS:
#
#  a:link, a:visited, a:hover, a:active {
#    border-bottom: 1px dotted black !important; color: #696969 !important;
#  }
#
find_base_address = `a\0:\0l\0i\0n\0k\0,\0 \0a\0:\0v\0i\0s\0i\0t\0e\0d\0,\0`
#
# These two lines remove !important from the border-bottom and color styles:
replace_string = 008E, `!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0`, ` \0 \0 \0 \0 \0 \0 \0 \0 \0 \0`
replace_string = 00C4, `!\0i\0m\0p\0o\0r\0t\0a\0n\0t\0`, ` \0 \0 \0 \0 \0 \0 \0 \0 \0 \0`
#
# These two lines remove the border-bottom and color styles:
replace_string = 004E, `b`, `_`
replace_string = 00A6, `c`, `_`
#
</Patch>
GeoffR is offline   Reply With Quote
Old 01-24-2017, 08:04 AM   #126
giddie
Member
giddie began at the beginning.
 
giddie's Avatar
 
Posts: 19
Karma: 10
Join Date: Jan 2017
Location: Birmingham, UK
Device: Kobo Aura H2O
Thanks GeoffR. I'd really like to be able to customise the info shown in the footer on kepubs (e.g. book percentage as well as time left in chapter). I've only had a quick look, but I'm guessing the various footer display options are switched in code, with separate data strings for each. I can see strings for e.g. "Page %1 / %2", but presumably there's no known way to introduce additional data into the footer at this time?
giddie is offline   Reply With Quote
Old 01-25-2017, 12:04 AM   #127
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 giddie View Post
Thanks GeoffR. I'd really like to be able to customise the info shown in the footer on kepubs (e.g. book percentage as well as time left in chapter). I've only had a quick look, but I'm guessing the various footer display options are switched in code, with separate data strings for each. I can see strings for e.g. "Page %1 / %2", but presumably there's no known way to introduce additional data into the footer at this time?
It might be possible to create a patch to do that, but it would probably be quite difficult. With the source code it would be trivial, but adding something extra with a patch usually requires extensive re-writing of the surrounding code to make enough room to fit in the extra thing.

Edit: There is already a quick way to switch between percentage and page number (and time remaining in KePubs) by long-pressing the footer.

Edit2: An extra complication with such a patch is that the "Page %1 of %2" string is used in other parts of the UI such as in the library lists, where a percentage is not used.

Last edited by GeoffR; 01-25-2017 at 04:09 AM.
GeoffR is offline   Reply With Quote
Old 01-25-2017, 03:50 AM   #128
Iñigo
Guru
Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.Iñigo did not drink the Kool Aid.
 
Posts: 730
Karma: 72743
Join Date: Feb 2008
Location: Here or there
Device: iRex iLiad, iRex DR800S. K4NT. Kobo Aura, Aura One, Libra 2.
Quote:
Originally Posted by GeoffR View Post
Edit: There is already a quick way to switch between percentage and page number (and time remaining in KePubs) by long-pressing the footer.
Hey! I didn't know about this. Thanks a lot for the tip!
Iñigo is offline   Reply With Quote
Old 01-25-2017, 04:06 PM   #129
kido.resuri
Groupie
kido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura aboutkido.resuri has a spectacular aura about
 
Posts: 172
Karma: 4282
Join Date: Dec 2016
Location: Hungary
Device: Kobo Aura H2O
Quote:
Originally Posted by GeoffR View Post
Edit: There is already a quick way to switch between percentage and page number (and time remaining in KePubs) by long-pressing the footer.
Nice, I didn't know that, thanks!

Is there any way to show page number instead of % read on the main page and in the library?
kido.resuri is offline   Reply With Quote
Old 01-27-2017, 09:20 PM   #130
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 kido.resuri View Post
Is there any way to show page number instead of % read on the main page and in the library?
No. A patch for that would be very difficult if it was possible at all because the percentage for KePub and ePub books are calculated differently, and I think the KePub percentage is based on the word count rather than the page count. I don't think the page numbers are stored in the database anywhere.
GeoffR is offline   Reply With Quote
Old 02-14-2017, 04:05 PM   #131
boriar
Evangelist
boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.
 
boriar's Avatar
 
Posts: 407
Karma: 314204
Join Date: Jan 2015
Device: bq Avant XL, Kobo Aura H2O, Onyx Boox M96C Plus
@GeoffR

Can you help me, please?
I have problems with this two patch but they are supposed to be correct for that FW:

Spoiler:
<Patch>
patch_name = `Increasing the view details container`
patch_enable = `yes`
find_base_address = `qproperty-topMargin: 0;\n\tqproperty-leftMargin: 20;`
#<<Bottom margin top container >>
# Touch
#replace_string = 0050, `qproperty-bottomMargin: 10;`, `qproperty-bottomMargin: 05;`
# Glo\Aura
#replace_string = 00ED, `qproperty-bottomMargin:15;`, `qproperty-bottomMargin:10;`
# Aura HD\H2O & Glo HD
replace_string = 0188, `qproperty-bottomMargin: 25;`, `qproperty-bottomMargin: 15;`
#<<reducing the book Info>>
# Touch
replace_string = 01D9, `min-height: 300px;`, `min-height: 200px;`
replace_string = 01ED, `max-height: 300px;`, `max-height: 200px;`
#Glo\Aura
replace_string = 0233, `min-height: 390px;`, `min-height: 230px;`
replace_string = 0247, `max-height: 390px;`, `max-height: 230px;`
# Aura HD\H2O & Glo HD
replace_string = 028C, `min-height: 550px;`, `min-height: 400px;`
replace_string = 02A0, `max-height: 550px;`, `max-height: 400px;`
#
find_base_address = `#details[qApp_deviceIsTrilogy="true"]`
#<<Increasing the details (text) Container>>
# Touch
replace_string = 0029, `min-height: 292px;`, `min-height: 390px;`
replace_string = 003D, `max-height: 292px;`, `max-height: 390px;`
# Glo\Aura
replace_string = 007C, `min-height: 365px;`, `min-height: 515px;`
replace_string = 0090, `max-height: 365px;`, `max-height: 515px;`
# Aura HD\H2O & Glo HD
replace_string = 00CE, `min-height: 560px;`, `min-height: 710px;`
replace_string = 00E2, `max-height: 560px;`, `max-height: 710px;`
</Patch>


<Patch>
patch_name = `Custom Header menubar - reduce height by 33%`
patch_enable = `yes`
# N.B. *** fw 3.19.5761 only (all models) ***
#
replace_bytes = 4A1AA8, 9C 9D 95 4B 4F 02 31 14, 9C 9D 95 5D 4F C2 30 18
replace_bytes = 4A1AB0, 85 F7 FC 8A 09 6C 25 81, 85 EF F7 2B 16 76 2B 09
replace_bytes = 4A1AB8, E1 39 10 17 A8 0B 59 90, 0C 36 BE E2 05 EA 85 5C
replace_bytes = 4A1AC0, 68 34 B2 30 C6 94 E9 B5, 90 68 34 72 61 8C 29 EB
replace_bytes = 4A1AC8, 34 0E 6D E9 14 81 18 FE, EB D6 B8 B5 A3 EB 04 62
replace_bytes = 4A1AD0, BB 2D 33 8C 99 57 19 D8, F8 EF EE DB EC AB 0C 2E
replace_bytes = 4A1AD8, 9E 3B 3D DF E9 E9 25 34, 39 6F 7B 9E D3 D3 92 69
replace_bytes = 4A1AE0, 5E 14 52 9B F0 0E C9 37, 2F 02 89 30 B8 43 FC 8D
replace_bytes = 4A1AE8, 0A DB F7 F5 44 88 4F 0C, C0 FE 7D B7 F4 FD 4F 0C
replace_bytes = 4A1AF0, 3F D4 87 69 F8 2A 69 C0, 3F C4 82 55 F0 CA 89 CB
replace_bytes = 4A1AF8, C9 FE B6 AE E4 06 EA 1F, EC E3 6D 4F F0 10 7A 1F
replace_bytes = 4A1B00, CE 6F CD 71 56 94 35 97, EA AF A2 AA 1E A1 7D 07
replace_bytes = 4A1B08, 40 C9 52 8D 9C 41 5B EC, 88 ED 88 B9 3A 9E F8 87
replace_bytes = 4A1B10, C6 46 43 BB 8C 76 A8 35, 45 AC A1 43 45 3B 29 9A
replace_bytes = 4A1B18, 2C BE 4F 4B 0E 8C EE 4A, C4 F7 C9 61 40 C9 A1 D5
replace_bytes = 4A1B20, 7D BD 02 5F AF 82 EF 83, D7 1C D4 7D 53 4D EE FB
replace_bytes = 4A1B28, 44 84 B3 52 DB B6 5B E0, C0 91 CD 68 AB ED B4 C1
replace_bytes = 4A1B30, 1B 8B DA 58 1A 61 4E 31, 76 9A DB F2 F8 F7 86 60
replace_bytes = 4A1B38, 01 65 AD E1 A6 D6 08 E0, 1B 84 B4 84 1B 45 73 E1
replace_bytes = 4A1B40, AB CA 97 49 82 2D C5 6A, AB CB CA 82 BF 27 58 38
replace_bytes = 4A1B48, A9 59 C3 EE 7F 80 B4 66, 73 75 38 1D FF F3 CB 9A
replace_bytes = 4A1B50, E3 67 EA B2 F0 CB 8A 8D, 8C 5F 29 4B C2 6F AB 35
replace_bytes = 4A1B58, 59 AE DB CB F1 63 CD C6, 63 E9 BA 51 E3 67 9A 8C
replace_bytes = 4A1B60, 4F D7 6A C1 97 F4 7F 22, 5F 2E 55 82 6F 69 3F 27
replace_bytes = 4A1B68, 0D DC 3C 3D D2 32 74 7D, 4D F4 3A 3D D5 2A F4 68
replace_bytes = 4A1B70, 88 AE 50 30 E3 18 4E 66, 13 F1 90 BB 66 18 72 B3
replace_bytes = 4A1B78, 17 34 72 E9 E9 FC 2B E5, 0B 1A B9 74 77 FD 96 EA
replace_bytes = 4A1B80, 5B 8A B5 43 ED 39 86 08, 2D 65 DA 49 79 CE 20 3E
replace_bytes = 4A1B88, 84 31 E0 47 40 18 E4 D4, C2 18 F0 23 20 0C 7C 65
replace_bytes = 4A1B90, E7 6C 6E BE 2B C6 9D 59, 31 BA 89 D7 35 E3 CE 3C
replace_bytes = 4A1B98, 8A 6E 3F 47 8B A4 AB 60, 8A B1 59 A3 A5 D2 55 B0
replace_bytes = 4A1BA0, 67 EE D6 CB C3 7A D7 C3, 33 67 33 EA 30 E3 7A 98
replace_bytes = 4A1BA8, EC EF DD CF B3 FA 31 AB, FC BE CD 3A CB CC 58 5A
replace_bytes = 4A1BB0, 11 1E 7F C4 0B 24 EF 39, 90 FC 85 B7 88 DF 33 2A
replace_bytes = 4A1BB8, 53 88 32 90 E7 3B 5B 0B, 10 A1 C0 CF 77 B6 F3 39
replace_bytes = 4A1BC0, C9 05 48 B5 6F 2A 2E 66, F3 81 8B 63 5F 30 7F 8D
replace_bytes = 4A1BC8, 48 12 CA B4 E3 38 35 31, B8 4D 68 E4 B8 28 4D E2
replace_bytes = 4A1BD0, 6B 70 1A B5 BD F4 EC B8, 67 90 8F 86 B3 F2 2C 79
replace_bytes = 4A1BD8, 61 65 C3 50 20 9F 32 A2, 61 6D C3 C0 47 16 A1 76
replace_bytes = 4A1BE0, EB A8 94 AF A8 E6 C2 7C, 54 47 A7 7C 4D 35 37 E6
replace_bytes = 4A1BE8, C3 F2 7C 6E CF 92 2F 3B, 9B B6 E7 D3 0D 49 BE EA
replace_bytes = 4A1BF0, 4C F2 B5 2A E5 2B 78 99, B0 C8 37 E8 94 AF E1 66
replace_bytes = 4A1BF8, 4B E3 75 6C F1 B2 C3 24, 2E 8D 37 92 C5 AB 0E 8B
replace_bytes = 4A1C00, 5E C7 AB 94 6F 12 EC C3, 78 A3 59 A7 7C 4B F7 18
replace_bytes = 4A1C08, 70 B3 2A 09 98 B8 B5 8F, 04 A1 D7 12 B0 70 1B 26
replace_bytes = 4A1C10, 66 2B 08 43 44 E0 F8 D1, 66 1E 04 01 B2 21 59 B4
replace_bytes = 4A1C18, 02 F9 DF 44 F2 0D C3 4D, 45 D6 B7 CD 59 48 71 DF
replace_bytes = 4A1C20, 9F 07 5C 8E 1C 25 11 D3, 62 2E E3 73 55 70 44 A3
replace_bytes = 4A1C28, 07 24 30 65 32 99 F5 D5, 0D 1C A8 88 33 C5 CF 37
replace_bytes = 4A1C30, 67 CD 25 75 9A 68 03 4F, DA 1B 1F 32 4A 93 BE C0
replace_bytes = 4A1C38, 9A B9 9E 6E 30 2D CA E8, 5C 8B 8F 17 35 58 16 79
replace_bytes = 4A1C40, 7F A0 15 6D E6 1F A7 73, FA 19 C8 BE 02 7F DC DD
replace_bytes = 4A1C48, 6F 5D 00 00 01 9E 00 00, 6F 03 00 00 01 9E 00 00
</Patch>
boriar is offline   Reply With Quote
Old 02-14-2017, 04:08 PM   #132
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 73,957
Karma: 128903250
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by boriar View Post
@GeoffR

Can you help me, please?
I have problems with this two patch but they are supposed to be correct for that FW:

Spoiler:
<Patch>
patch_name = `Increasing the view details container`
patch_enable = `yes`
find_base_address = `qproperty-topMargin: 0;\n\tqproperty-leftMargin: 20;`
#<<Bottom margin top container >>
# Touch
#replace_string = 0050, `qproperty-bottomMargin: 10;`, `qproperty-bottomMargin: 05;`
# Glo\Aura
#replace_string = 00ED, `qproperty-bottomMargin:15;`, `qproperty-bottomMargin:10;`
# Aura HD\H2O & Glo HD
replace_string = 0188, `qproperty-bottomMargin: 25;`, `qproperty-bottomMargin: 15;`
#<<reducing the book Info>>
# Touch
replace_string = 01D9, `min-height: 300px;`, `min-height: 200px;`
replace_string = 01ED, `max-height: 300px;`, `max-height: 200px;`
#Glo\Aura
replace_string = 0233, `min-height: 390px;`, `min-height: 230px;`
replace_string = 0247, `max-height: 390px;`, `max-height: 230px;`
# Aura HD\H2O & Glo HD
replace_string = 028C, `min-height: 550px;`, `min-height: 400px;`
replace_string = 02A0, `max-height: 550px;`, `max-height: 400px;`
#
find_base_address = `#details[qApp_deviceIsTrilogy="true"]`
#<<Increasing the details (text) Container>>
# Touch
replace_string = 0029, `min-height: 292px;`, `min-height: 390px;`
replace_string = 003D, `max-height: 292px;`, `max-height: 390px;`
# Glo\Aura
replace_string = 007C, `min-height: 365px;`, `min-height: 515px;`
replace_string = 0090, `max-height: 365px;`, `max-height: 515px;`
# Aura HD\H2O & Glo HD
replace_string = 00CE, `min-height: 560px;`, `min-height: 710px;`
replace_string = 00E2, `max-height: 560px;`, `max-height: 710px;`
</Patch>


<Patch>
patch_name = `Custom Header menubar - reduce height by 33%`
patch_enable = `yes`
# N.B. *** fw 3.19.5761 only (all models) ***
#
replace_bytes = 4A1AA8, 9C 9D 95 4B 4F 02 31 14, 9C 9D 95 5D 4F C2 30 18
replace_bytes = 4A1AB0, 85 F7 FC 8A 09 6C 25 81, 85 EF F7 2B 16 76 2B 09
replace_bytes = 4A1AB8, E1 39 10 17 A8 0B 59 90, 0C 36 BE E2 05 EA 85 5C
replace_bytes = 4A1AC0, 68 34 B2 30 C6 94 E9 B5, 90 68 34 72 61 8C 29 EB
replace_bytes = 4A1AC8, 34 0E 6D E9 14 81 18 FE, EB D6 B8 B5 A3 EB 04 62
replace_bytes = 4A1AD0, BB 2D 33 8C 99 57 19 D8, F8 EF EE DB EC AB 0C 2E
replace_bytes = 4A1AD8, 9E 3B 3D DF E9 E9 25 34, 39 6F 7B 9E D3 D3 92 69
replace_bytes = 4A1AE0, 5E 14 52 9B F0 0E C9 37, 2F 02 89 30 B8 43 FC 8D
replace_bytes = 4A1AE8, 0A DB F7 F5 44 88 4F 0C, C0 FE 7D B7 F4 FD 4F 0C
replace_bytes = 4A1AF0, 3F D4 87 69 F8 2A 69 C0, 3F C4 82 55 F0 CA 89 CB
replace_bytes = 4A1AF8, C9 FE B6 AE E4 06 EA 1F, EC E3 6D 4F F0 10 7A 1F
replace_bytes = 4A1B00, CE 6F CD 71 56 94 35 97, EA AF A2 AA 1E A1 7D 07
replace_bytes = 4A1B08, 40 C9 52 8D 9C 41 5B EC, 88 ED 88 B9 3A 9E F8 87
replace_bytes = 4A1B10, C6 46 43 BB 8C 76 A8 35, 45 AC A1 43 45 3B 29 9A
replace_bytes = 4A1B18, 2C BE 4F 4B 0E 8C EE 4A, C4 F7 C9 61 40 C9 A1 D5
replace_bytes = 4A1B20, 7D BD 02 5F AF 82 EF 83, D7 1C D4 7D 53 4D EE FB
replace_bytes = 4A1B28, 44 84 B3 52 DB B6 5B E0, C0 91 CD 68 AB ED B4 C1
replace_bytes = 4A1B30, 1B 8B DA 58 1A 61 4E 31, 76 9A DB F2 F8 F7 86 60
replace_bytes = 4A1B38, 01 65 AD E1 A6 D6 08 E0, 1B 84 B4 84 1B 45 73 E1
replace_bytes = 4A1B40, AB CA 97 49 82 2D C5 6A, AB CB CA 82 BF 27 58 38
replace_bytes = 4A1B48, A9 59 C3 EE 7F 80 B4 66, 73 75 38 1D FF F3 CB 9A
replace_bytes = 4A1B50, E3 67 EA B2 F0 CB 8A 8D, 8C 5F 29 4B C2 6F AB 35
replace_bytes = 4A1B58, 59 AE DB CB F1 63 CD C6, 63 E9 BA 51 E3 67 9A 8C
replace_bytes = 4A1B60, 4F D7 6A C1 97 F4 7F 22, 5F 2E 55 82 6F 69 3F 27
replace_bytes = 4A1B68, 0D DC 3C 3D D2 32 74 7D, 4D F4 3A 3D D5 2A F4 68
replace_bytes = 4A1B70, 88 AE 50 30 E3 18 4E 66, 13 F1 90 BB 66 18 72 B3
replace_bytes = 4A1B78, 17 34 72 E9 E9 FC 2B E5, 0B 1A B9 74 77 FD 96 EA
replace_bytes = 4A1B80, 5B 8A B5 43 ED 39 86 08, 2D 65 DA 49 79 CE 20 3E
replace_bytes = 4A1B88, 84 31 E0 47 40 18 E4 D4, C2 18 F0 23 20 0C 7C 65
replace_bytes = 4A1B90, E7 6C 6E BE 2B C6 9D 59, 31 BA 89 D7 35 E3 CE 3C
replace_bytes = 4A1B98, 8A 6E 3F 47 8B A4 AB 60, 8A B1 59 A3 A5 D2 55 B0
replace_bytes = 4A1BA0, 67 EE D6 CB C3 7A D7 C3, 33 67 33 EA 30 E3 7A 98
replace_bytes = 4A1BA8, EC EF DD CF B3 FA 31 AB, FC BE CD 3A CB CC 58 5A
replace_bytes = 4A1BB0, 11 1E 7F C4 0B 24 EF 39, 90 FC 85 B7 88 DF 33 2A
replace_bytes = 4A1BB8, 53 88 32 90 E7 3B 5B 0B, 10 A1 C0 CF 77 B6 F3 39
replace_bytes = 4A1BC0, C9 05 48 B5 6F 2A 2E 66, F3 81 8B 63 5F 30 7F 8D
replace_bytes = 4A1BC8, 48 12 CA B4 E3 38 35 31, B8 4D 68 E4 B8 28 4D E2
replace_bytes = 4A1BD0, 6B 70 1A B5 BD F4 EC B8, 67 90 8F 86 B3 F2 2C 79
replace_bytes = 4A1BD8, 61 65 C3 50 20 9F 32 A2, 61 6D C3 C0 47 16 A1 76
replace_bytes = 4A1BE0, EB A8 94 AF A8 E6 C2 7C, 54 47 A7 7C 4D 35 37 E6
replace_bytes = 4A1BE8, C3 F2 7C 6E CF 92 2F 3B, 9B B6 E7 D3 0D 49 BE EA
replace_bytes = 4A1BF0, 4C F2 B5 2A E5 2B 78 99, B0 C8 37 E8 94 AF E1 66
replace_bytes = 4A1BF8, 4B E3 75 6C F1 B2 C3 24, 2E 8D 37 92 C5 AB 0E 8B
replace_bytes = 4A1C00, 5E C7 AB 94 6F 12 EC C3, 78 A3 59 A7 7C 4B F7 18
replace_bytes = 4A1C08, 70 B3 2A 09 98 B8 B5 8F, 04 A1 D7 12 B0 70 1B 26
replace_bytes = 4A1C10, 66 2B 08 43 44 E0 F8 D1, 66 1E 04 01 B2 21 59 B4
replace_bytes = 4A1C18, 02 F9 DF 44 F2 0D C3 4D, 45 D6 B7 CD 59 48 71 DF
replace_bytes = 4A1C20, 9F 07 5C 8E 1C 25 11 D3, 62 2E E3 73 55 70 44 A3
replace_bytes = 4A1C28, 07 24 30 65 32 99 F5 D5, 0D 1C A8 88 33 C5 CF 37
replace_bytes = 4A1C30, 67 CD 25 75 9A 68 03 4F, DA 1B 1F 32 4A 93 BE C0
replace_bytes = 4A1C38, 9A B9 9E 6E 30 2D CA E8, 5C 8B 8F 17 35 58 16 79
replace_bytes = 4A1C40, 7F A0 15 6D E6 1F A7 73, FA 19 C8 BE 02 7F DC DD
replace_bytes = 4A1C48, 6F 5D 00 00 01 9E 00 00, 6F 03 00 00 01 9E 00 00
</Patch>
Before you try to fix these patches, you do know that there is a new firmware for the H2O and you can update and patch that. Have a look at the following post to see the relevant links to the new firmware.

https://www.mobileread.com/forums/sh...d.php?t=283510

P.S. Those patches are also in the patches for the new firmware. So do you still want help with the patches for 3.19.5761 or are you going to give 4.2.8432 a go?

P.P.S. The H2O is a mark 5 device.

Last edited by JSWolf; 02-14-2017 at 04:15 PM.
JSWolf is offline   Reply With Quote
Old 02-14-2017, 04:28 PM   #133
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
@boriar,

Regarding patch_name = `Custom Header menubar - reduce height by 33%` for 3.19.5761 ... did you make sure you added this patch to the nickel.patch file, not one of the other 3 .patch files?
jackie_w is offline   Reply With Quote
Old 02-15-2017, 02:41 AM   #134
oren64
I need a chapter break
oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.oren64 ought to be getting tired of karma fortunes by now.
 
oren64's Avatar
 
Posts: 4,042
Karma: 56058267
Join Date: Mar 2015
Location: Israel
Device: Kobo Glo
Quote:
Originally Posted by boriar View Post
@GeoffR

Can you help me, please?
I have problems with this two patch but they are supposed to be correct for that FW:
...
In `Increasing The View Details Container` there are three line that are not active, i find a problem in one of the lines and fix it, you can active them now if you want.

https://www.mobileread.com/forums/sh...&postcount=134

Last edited by oren64; 02-15-2017 at 03:23 AM.
oren64 is offline   Reply With Quote
Old 02-15-2017, 09:05 AM   #135
boriar
Evangelist
boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.boriar ought to be getting tired of karma fortunes by now.
 
boriar's Avatar
 
Posts: 407
Karma: 314204
Join Date: Jan 2015
Device: bq Avant XL, Kobo Aura H2O, Onyx Boox M96C Plus
Quote:
Originally Posted by JSWolf View Post
Before you try to fix these patches, you do know that there is a new firmware for the H2O and you can update and patch that. Have a look at the following post to see the relevant links to the new firmware.

https://www.mobileread.com/forums/sh...d.php?t=283510

P.S. Those patches are also in the patches for the new firmware. So do you still want help with the patches for 3.19.5761 or are you going to give 4.2.8432 a go?

P.P.S. The H2O is a mark 5 device.
Sorry but little or nothing interest in new firmwares. At least by now.

Quote:
Originally Posted by jackie_w View Post
@boriar,

Regarding patch_name = `Custom Header menubar - reduce height by 33%` for 3.19.5761 ... did you make sure you added this patch to the nickel.patch file, not one of the other 3 .patch files?
oren64 said here that for that FW is in libnickel.so.1.0.0.patch. But thanks for your answer.

Quote:
Originally Posted by oren64 View Post
In `Increasing The View Details Container` there are three line that are not active, i find a problem in one of the lines and fix it, you can active them now if you want.

https://www.mobileread.com/forums/sh...&postcount=134
Many thanks. I will try ASAP.

Edit: @oren64

Apart from uncomment line in the version I posted before, it seems not to have any difference and produced the same error . Is it supposed that I can not uncomment it?

Last edited by boriar; 02-15-2017 at 09:21 AM.
boriar is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Instructions for patching firmware 3.17.3 GeoffR Kobo Developer's Corner 60 09-17-2015 05:35 PM
Instructions for patching firmware 3.17.0 GeoffR Kobo Developer's Corner 49 08-16-2015 05:20 AM
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.8.0 GeoffR Kobo Developer's Corner 92 10-22-2014 07:22 AM


All times are GMT -4. The time now is 03:00 AM.


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