Instructions for patching firmware 4.9.11311 - Page 3

DNSB · 07-21-2018, 04:08 PM

Deleted....

jcn363 · 07-22-2018, 06:44 PM

jcn363 · 07-28-2018, 03:48 AM

Nickel 'Bad Eyes Progressive' Dragon and Daylight optimized.
You can change the values you want into 'Replace' zone (even cook for another device, why not?).
If you test it, please, share your impressions.

Good luck.

Edit: Nova (ClaraHD) added. I can't test on the device, therefore the risk is all yours (as always).

Good luck.

Nemo1984 · 08-01-2018, 06:56 PM

Quote:

Originally Posted by jcn363

Two typo on nickel

Good luck.

Hi. I just wanted to know exactly what this does what are the effects?

Thanks!

jcn363 · 08-02-2018, 03:49 AM

Quote:

Originally Posted by Nemo1984

Hi. I just wanted to know exactly what this does what are the effects?

Thanks!

Me too

Code:

#138 (zlib) pos 483c52:
      Find:    "#bottomVerticalSpacer[qApp_deviceIsPhoenix=true] {\n  min-height: 24x;\n  max-height: 24px;\n}"

This affects to Aura and alike.
I don't have any of these devices and therefore I can't prove/see the effects.
But, if bottomVerticalSpacer means that it says, change a bottom vertical spacer from default to 24px.

Code:

#48 (zlib) pos 4781f5:
      Find:    "#highlight[qApp_deviceIsDaylight=true],\n#search[qApp_deviceIsDaylight=true] {\n  margin-right: 7x;\n}"

This affects to Aura One and alike.
This is my device and therefore I can prove/see the effects.
But, if SelectionMenuView means that it says, change the margins from default to 7px in the highlight and search.
It's a little change but it works.

A lot of words to say... nothing?
Grandma says: "if you want to know how is its flavour you have to taste it".

Good luck.

Nemo1984 · 08-02-2018, 02:27 PM

Quote:

Originally Posted by jcn363

Me too

Code:

#138 (zlib) pos 483c52:
      Find:    "#bottomVerticalSpacer[qApp_deviceIsPhoenix=true] {\n  min-height: 24x;\n  max-height: 24px;\n}"

This affects to Aura and alike.
I don't have any of these devices and therefore I can't prove/see the effects.
But, if bottomVerticalSpacer means that it says, change a bottom vertical spacer from default to 24px.

Code:

#48 (zlib) pos 4781f5:
      Find:    "#highlight[qApp_deviceIsDaylight=true],\n#search[qApp_deviceIsDaylight=true] {\n  margin-right: 7x;\n}"

This affects to Aura One and alike.
This is my device and therefore I can prove/see the effects.
But, if SelectionMenuView means that it says, change the margins from default to 7px in the highlight and search.
It's a little change but it works.

A lot of words to say... nothing?
Grandma says: "if you want to know how is its flavour you have to taste it".

Good luck.

Thank you. I thought there were typos in the Kobo file that might create bug.

NiLuJe · 08-02-2018, 02:46 PM

Well, they *are* typos in Kobo's code that might create bugs.

.

We're just not quite sure when/where and to what extent. @jcn363 just shined a light on that, and explained that it's probably minor, though

.

jcn363 · 08-02-2018, 06:13 PM

Quote:

Originally Posted by Nemo1984

Thank you. I thought there were typos in the Kobo file that might create bug.

That's right!

Quote:

Originally Posted by NiLuJe

Well, they are typos in Kobo's code that might create bugs.

.

We're just not quite sure when/where and to what extent. @jcn363 just shined a light on that, and explained that it's probably minor, though

.

Totally agree.

Good luck.

07-21-2018, 04:08 PM	#31
DNSB Bibliophagist Posts: 46,149 Karma: 168983734 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Deleted.... Last edited by DNSB; 07-21-2018 at 04:15 PM.

07-28-2018, 03:48 AM	#33
jcn363 absolute beginner Posts: 323 Karma: 1750999 Join Date: May 2017 Location: Go with the wind (43°19'17.7"N 2°00'19.4"W) Device: ka1	Nickel 'Bad Eyes Progressive' Dragon and Daylight optimized. You can change the values you want into 'Replace' zone (even cook for another device, why not?). If you test it, please, share your impressions. Good luck. Edit: Nova (ClaraHD) added. I can't test on the device, therefore the risk is all yours (as always). Good luck. Last edited by jcn363; 07-28-2018 at 07:29 AM. Reason: Nova (ClaraHD) added

08-02-2018, 02:46 PM	#37
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Well, they are typos in Kobo's code that might create bugs. . We're just not quite sure when/where and to what extent. @jcn363 just shined a light on that, and explained that it's probably minor, though . Last edited by NiLuJe; 08-02-2018 at 06:44 PM.

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.16.0	GeoffR	Kobo Developer's Corner	74	08-12-2015 02:12 PM
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.0	GeoffR	Kobo Developer's Corner	165	02-07-2015 09:22 AM
Instructions for patching firmware 3.8.0	GeoffR	Kobo Developer's Corner	92	10-22-2014 07:22 AM

07-22-2018, 06:44 PM	#32
jcn363 absolute beginner Posts: 323 Karma: 1750999 Join Date: May 2017 Location: Go with the wind (43°19'17.7"N 2°00'19.4"W) Device: ka1	Two typo on nickel Good luck.

Advert

Advert