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 10-03-2013, 02:29 PM   #226
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,251
Karma: 16539642
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by Nick_1964 View Post
So a little bit of white under the "page .. of .." would be nice ( place it a little bit higher ) would be fantastic, can anyone help me ?
I also wanted to do this. The only solution I could find was to combine the Footer settings from v05/v06 into the v07 kpg.conf file.

Try replacing line 12 in your kpg.conf file with this:
Code:
replace_zlib = 1205FF4, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 40px;\n\tmax-height: 40px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 24px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`
If you need to change the footer depth/font-size on the AuraHD, just tweak the 3 red numbers.

Another note: Once you have re-applied the Patch, before you decide the numbers need to be tweaked again, please see the last paragraph of this post.

Edit: Just for clarification, the above assumes you are Patching fw 2.8.1 not fw 2.6.1

Last edited by jackie_w; 10-03-2013 at 05:05 PM. Reason: clarification
jackie_w is offline   Reply With Quote
Old 10-03-2013, 04:02 PM   #227
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 jackie_w View Post
I also wanted to do this. The only solution I could find was to combine the Footer settings from v05/v06 into the v07 kpg.conf file.

Try replacing line 12 in your kpg.conf file with this:
Code:
replace_zlib = 1205FF4, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 40px;\n\tmax-height: 40px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 24px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`
If you need to change the footer depth/font-size on the AuraHD, just tweak the 3 red numbers.

Another note: Once you have re-applied the Patch, before you decide the numbers need to be tweaked again, please see the last paragraph of this post.
Try'd to do the font trick, but it stays down, so gonna look into your red numbers
Nick_1964 is offline   Reply With Quote
Advert
Old 10-03-2013, 04:20 PM   #228
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: 197
Karma: 82624
Join Date: May 2013
Device: Kobo Forma, Kobo Aura One, Kobo Aura HD, Kindle, Amazon Fire HD
Thanks Jackie_w!
forster01 is offline   Reply With Quote
Old 10-03-2013, 04:28 PM   #229
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,168
Karma: 168983734
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Quexos View Post
Also I don't understand what you mean by "from 1024 to 920" ?
At a wild eyed guess and the Glo having a 1024x758 screen with 212ppi, assuming that you lose 104 pixels at the bottom of the screen to the footer, the resulting area would be 920x758.

Regards,
David
DNSB is offline   Reply With Quote
Old 10-03-2013, 07:35 PM   #230
Mora
Junior Member
Mora began at the beginning.
 
Posts: 9
Karma: 10
Join Date: Oct 2013
Device: PocketBook Touch HD 3
That is correct. I was referring to the resolution. Waiting for an update on the patcher then.
Mora is offline   Reply With Quote
Advert
Old 10-03-2013, 10:10 PM   #231
parkher
Evangelist
parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.
 
Posts: 467
Karma: 369018
Join Date: Nov 2010
Device: BL Alita/Mimas/Ares, OB Note2/Note, KA One/H2O/HD, S PRS T2/T1, PB 902
Quote:
Originally Posted by Mora View Post
That is correct. I was referring to the resolution. Waiting for an update on the patcher then.
You could try downgrading from 2.8.1 to 2.8.1
What is so new and great in this new 2.8.1 (b2c05cda0e)?
And what this number b2c05cda0e actully stands for?
Not md5, not crc32, is it a build number?

I see changes in 28 files and one new file added - a hyphenation dictionary for the Dutch language.
Unfortunately, libnickel.so.1.0.0 has been changed too, its size is different:
old: 19,109,944 bytes
new: 19,074,964 bytes
So hex replacements may cause unpredictable effects.

But perhaps it is enough to replace just libnickel.so.1.0.0 file (with the one from the previous 2.8.1 firmware) and then you can apply the patch, because the patch changes only that one file.
That file is already included in the patch itself, so even if you don't have the older 2.8.1 firmware, you have that file.
So the question is: does the old libnickel file work without problems in the new firmware.
I am not going to try this but perhaps somebody will. Or already tried.

Last edited by parkher; 10-03-2013 at 10:31 PM.
parkher is offline   Reply With Quote
Old 10-03-2013, 10:23 PM   #232
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by parkher View Post
You could try downgrading from 2.8.1 to 2.8.1
What is so new and great in this new 2.8.1 (b2c05cda0e)?
And what this number b2c05cda0e actully stands for?
Not md5, not crc32, is it a build number?
Yes, it is a build number. What is displayed is the first 8 characters of the number. The fill number is in a file in the usr/local/Kobo directory.
Quote:
I see changes in 28 files and one new file added - a hyphenation dictionary for the Dutch language.
Kobo have stated that this version is to fix a problem with demo devices. That suggests there are no code changes that affect "normal" use. My guess it that they added the Dutch hyphenation dictionary as it would be a safe addition.
Quote:
Unfortunately, libnickel.so.1.0.0 has been changed too, its size is different:
old: 19,109,944 bytes
new: 19,074,964 bytes
So hex replacements may cause unpredictable effects.

But perhaps it is enough to replace just libnickel.so.1.0.0 file (with the one from the previous 2.8.1 firmware) and then you can apply the patch, because the patch changes only that one file.
This will probably work. It has been done before for other firmware versions. At the worst, you would need to do a factory reset afterwards
davidfor is offline   Reply With Quote
Old 10-03-2013, 10:50 PM   #233
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,511
Karma: 78910202
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
Attached find my first version of a new conf file for the patcher and 2.8.1B.

I've only included the patches for
  • My line spacing values
  • Custom fonts sizes
  • Custom left & right margins

Good luck
Attached Files
File Type: zip kpg_281b.zip (7.86 MB, 477 views)
PeterT is offline   Reply With Quote
Old 10-03-2013, 11:07 PM   #234
parkher
Evangelist
parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.
 
Posts: 467
Karma: 369018
Join Date: Nov 2010
Device: BL Alita/Mimas/Ares, OB Note2/Note, KA One/H2O/HD, S PRS T2/T1, PB 902
So you are using it on the new libnickel. Is it really working? So it passes the checks - the values being replaced are with the same offsets.
At least partially compatible.

Last edited by parkher; 10-03-2013 at 11:10 PM.
parkher is offline   Reply With Quote
Old 10-03-2013, 11:14 PM   #235
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,511
Karma: 78910202
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
I've searched and updated the offsets in the conf file to match the new libnickel. No I have not actually installed this as I'm not running 2.8.1B.
PeterT is offline   Reply With Quote
Old 10-04-2013, 01:33 AM   #236
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,168
Karma: 168983734
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by PeterT View Post
I've searched and updated the offsets in the conf file to match the new libnickel. No I have not actually installed this as I'm not running 2.8.1B.
The values you came up with matched the ones that I found. I also added the following change:

<Patch>
patch_name = `Brightness fine control`
patch_enable = `yes`
replace_int = 988CF4, 10, 01
replace_int = 988D24, 10, 01
</Patch>

Regards,
David
DNSB is offline   Reply With Quote
Old 10-04-2013, 04:12 AM   #237
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,168
Karma: 168983734
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
This message has been edited to remove the attached file. A later post adds the Custom Reading Footer Style to the list. See https://www.mobileread.com/forums/sho...&postcount=249 for that message.

If anyone is interested in testing this on an Aura, have fun. I've tested it on an Aura HD running 2.9.0 and it seems to work fine.

Only 4 items have been included:
  • My line spacing values
  • Custom fonts sizes
  • Custom left & right margins
  • Brightness fine control

Regards,
David

Last edited by DNSB; 10-04-2013 at 11:44 AM.
DNSB is offline   Reply With Quote
Old 10-04-2013, 04:16 AM   #238
bartbrat
Junior Member
bartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to beholdbartbrat is a marvel to behold
 
Posts: 8
Karma: 11516
Join Date: Oct 2013
Device: Kobo Aura HD
Unfortunately, I'm on 2.8.1b. First of all, thank you for making a new patch. It worked, or at least part of it. I don't know for sure yet, but I think line spacing isn't working. The brightness control does work.

I'm especially curious if it's possible to make the reading footer patch work again?

Another option is downgrading to the 'old' 2.8.1. Does anyone have this on his computer by accident? That would be even better and saves you all a lot of work.

Thanks again!
bartbrat is offline   Reply With Quote
Old 10-04-2013, 05:27 AM   #239
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by DNSB View Post
If anyone is interested in testing this on an Aura, have fun. I've tested it on an Aura HD running 2.9.0 and it seems to work fine.

Only 4 items have been included:
  • My line spacing values
  • Custom fonts sizes
  • Custom left & right margins
  • Brightness fine control

Regards,
David
If anybody is interested in changing the reading footer style in FW 2.9.0, the address is 13508E4 (instead of 1205FF4 of 2.8.1[a]).

Be aware that the original values have been changed.
Code:
ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 15;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}

USE THIS INFORMATION AT YOUR OWN RISK.

Last edited by tshering; 10-04-2013 at 07:37 AM. Reason: Added original data
tshering is offline   Reply With Quote
Old 10-04-2013, 06:06 AM   #240
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 jackie_w View Post
I also wanted to do this. The only solution I could find was to combine the Footer settings from v05/v06 into the v07 kpg.conf file.

Try replacing line 12 in your kpg.conf file with this:
Code:
replace_zlib = 1205FF4, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 40px;\n\tmax-height: 40px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 24px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`
If you need to change the footer depth/font-size on the AuraHD, just tweak the 3 red numbers.

Another note: Once you have re-applied the Patch, before you decide the numbers need to be tweaked again, please see the last paragraph of this post.

Edit: Just for clarification, the above assumes you are Patching fw 2.8.1 not fw 2.6.1
My config is:
Code:
# Decrease footer example
replace_zlib = 1205FF4, `ReadingFooter {\n\tmin-height: 70px;\n\tmax-height: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kraken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCodeName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfont-size: 26px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr6N;\n}`, `* {\n\theight: 30px;\n\tfont-size: 25px;\n}\n\n`
When I changed it with your value's I get the following error:
Code:
Applying patches ...
        Applying patch [Custom reading footer style] ...
1205ff7 90 50

Data for replace in libnickel.so.1.0.0 and kpg.conf does not match!
libnickel.so.1.0.0 is already patched or from the wrong firmware version.
Replace: replace_zlib = 1205FF7, ReadingFooter {\n\tmin-height: 70px;\n\tmax-hei
ght: 70px;\n\tqproperty-footerMargin: 40;\n}\n\nReadingFooter[deviceCodeName="kr
aken"], \nReadingFooter[deviceCodeName="phoenix"] {\n\tmin-height: 82px;\n\tmax-
height: 82px;\n\tqproperty-footerMargin: 110;\n}\n\nReadingFooter[deviceCodeName
="dragon"] {\n\tmin-height: 50px;\n\tmax-height: 50px;\n\tqproperty-footerMargin
: 20;\n}\n\n* {\n\tfont-size: 16px;\n}\n\n[deviceCodeName="kraken"], \n[deviceCo
deName="phoenix"] {\n\tfont-size: 20px;\n}\n\n[deviceCodeName="dragon"] {\n\tfon
t-size: 24px;\n}\n\n[localeName="ja_JP"] {\n\tfont-family: A-OTF Gothic MB101 Pr
6N;\n}, * {\n\theight: 30px;\n\tfont-size: 25px;\n}\n\n
For some strange reason it tries to patch 1205FF7 while in the conf the rule starts with 1205FF4, when I change it back to the original values, it does patch 120FF4 and works... changes it with the red value's and it try's to patch 120FF7, firmware 2.8.1. kobo patcher 7

Last edited by Nick_1964; 10-04-2013 at 06:18 AM.
Nick_1964 is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Glo How to import reading Life Statistics from Kobo Touch to Kobo Glo? the_m Kobo Reader 5 12-13-2012 03:40 PM
$25 gift card w. purchase of Kobo Touch or Kobo Vox at Frys sufue Deals and Resources (No Self-Promotion or Affiliate Links) 0 07-15-2012 10:39 AM
Touch Kobo Touch defective after 3 months and Kobo Customer Support useless shaf Kobo Reader 5 12-04-2011 05:10 PM
Touch Kobo Touch not ejecting cleanly with Calibre OR Kobo Desktop - Windows 7 JBlyth Kobo Reader 11 08-03-2011 05:38 PM
Kobo Touch not disconnecting properly from Calibre OR Kobo Desktop - Windows 7 JBlyth Devices 1 08-03-2011 06:50 AM


All times are GMT -4. The time now is 02:16 AM.


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