Kobo Firmware 4.12.12111 - Page 10

nAhu · 12-18-2018, 02:42 PM

Hi,

Quote:

Originally Posted by JIPG-reader

But you can select showing the book covers in the menus ...

To be honest, I put this option ON the first day, so I cannot remember if there was a FNAC screensaver.

I have my glo for nearly 6 years, reset it several times, the settings always worked for me and still works (needed to be put back when factory reset).
With affiliate=fnac => fnac screensaver
Actually, lastest firmware, the setting is affiliate=bestbuyca => book cover as screensaver.

Do you "switch off" the kobo and starting it over after the change ?

Regards,

m-p{3} · 12-18-2018, 03:01 PM

Quote:

Originally Posted by JIPG-reader

Finally, run kobopatch.bat (if you use windows), and extract koboroot.tgz from the folder out.

And don't be like me and skip through the readme and flash the patch BEFORE applying the actual 4.12.12111 update XD

I remember patching it in the past and the KoboRoot.tgz was the whole update with patches applied.

Lesson learned, I know how to manually reset my Kobo now! And while I'm starting over I'll probably upgrade the MicroSD card size to a bigger one since my Kobo is now out of warranty anyway.

geek1011 · 12-18-2018, 03:50 PM

This firmware was just released to the fnac affiliate.

Calenorn · 12-18-2018, 06:08 PM

Quote:

Originally Posted by geek1011

This firmware was just released to the fnac affiliate.

Looks like my Kobo affiliated Clara is getting it now.

geek1011 · 12-18-2018, 06:10 PM

Quote:

Originally Posted by Calenorn

Looks like my Kobo affiliated Clara is getting it now.

And now walmart and most of the other ones. I don't think rakutenbooks will get it anytime soon though.

JeanPierre · 12-18-2018, 11:33 PM

The process for highlight text seems to have been modified for this version of the firmware. Has anyone else noticed this?

Previously once text had been highlighted, I had to long press on one of the white circles which appear at the end of the text, which then turned black, and then drag to a new position.

Now, I have to long press and drag to turn the white circle black, then drag again to move the position. It took me a while to realise that I had to press and drag to register that I want to move the circle, rather than just long pressing on the circle to turn it black.

Despite this unintuitive method of registering a desire to expand a highlight, I find that the actual expansion is more accurate than before, since a great degree of movement was previously required to move the cursor at all, sometimes requiring backtracking. Now, once you manage to register that you wish to change a highlight, you can move by a single character more easily.

I see some very strange behaviour when I long press the circle at the front of the highlight, with it sometimes jumping halfway down the page past the circle that previously marked the end point.

A work in progress, perhaps? Anyone else seeing this happen?

codychan · 12-19-2018, 12:56 AM

Quote:

Originally Posted by JeanPierre

The process for highlight text seems to have been modified for this version of the firmware. Has anyone else noticed this?

Previously once text had been highlighted, I had to long press on one of the white circles which appear at the end of the text, which then turned black, and then drag to a new position.

Now, I have to long press and drag to turn the white circle black, then drag again to move the position. It took me a while to realise that I had to press and drag to register that I want to move the circle, rather than just long pressing on the circle to turn it black.

Despite this unintuitive method of registering a desire to expand a highlight, I find that the actual expansion is more accurate than before, since a great degree of movement was previously required to move the cursor at all, sometimes requiring backtracking. Now, once you manage to register that you wish to change a highlight, you can move by a single character more easily.

I see some very strange behaviour when I long press the circle at the front of the highlight, with it sometimes jumping halfway down the page past the circle that previously marked the end point.

A work in progress, perhaps? Anyone else seeing this happen?

I noticed this a month ago, check my post
https://www.mobileread.com/forums/sh...95&postcount=3

JeanPierre · 12-19-2018, 02:21 AM

Quote:

Originally Posted by codychan

I noticed this a month ago, check my post
https://www.mobileread.com/forums/sh...95&postcount=3

Perfect. Thank you for your prompt and informative response confirming the behaviour I observe.

I have recently upgraded from version 4.10.11655 of the firmware, and am making extensive use of geek1011's patch framework and was concerned I'd mucked something up.

genoasalami · 12-19-2018, 02:13 PM

Quote:

Originally Posted by kansaskyle

For the UnlockEnabled=false setting, is the file I need to update \.kobo\Kobo\Kobo eReader.conf?

If so, is there a special text editor I need to use because in Notepad it looks like all the text flows together as shown below.

(click for larger image)

When I tried to add a carriage return and put in the UnlockEnabled=false line, it looks like it just added it to the FullscreenCoverStretch entry.

The strange part is when I copy/paste the entries in the file, it appears there are hidden line breaks (expect for the line I tried to add).

[PowerOptions]
AutoColorEnabled=true
ColorSetting=5910
FrontLightLevel=3
FullscreenCoverStretch="true\r\nUnlockEnabled=fals e\r\n

Quote:

Originally Posted by ReaLx3m

For config files its best to open with wordpad so the text doesnt flow together, or you could install Notepad++.

Brackets (http://brackets.io/) is free and actually a little better than Notepad++, especially for anything involving code of any kind.

DNSB · 12-19-2018, 11:48 PM

Quote:

Originally Posted by genoasalami

Brackets (http://brackets.io/) is free and actually a little better than Notepad++, especially for anything involving code of any kind.

Interesting. I tried Brackets a year or so back and while it was better for html/css/Javascript than Notepad++, Notepad++ was well ahead of it in handling other programming languages. Has Brackets improved it's handling of Powershell, KIXtart and C and it's relatives? Basically, my day job has me living in Powershell these days so that is rather important to me. Unless you want to count ebook editing, I do zero with web development.

As for the cost? Notepad++ and Brackets, at this time, have exactly the same cost--free.

The only downside to Notepad++ is that it is Windows only but Windows is pretty much the only game in town where we need to worry about EOL handling. OTOH, Brackets for Windows is 32 bit only and is very memory hungry compared to Notepad++.

jcn363 · 12-20-2018, 07:25 AM

Geany

Good luck.

Leonatus · 12-20-2018, 08:57 AM

My device is Kobo Touch (N905). I'm on fw. 4.12.12111. I downloaded the relative patch and firmware (zip) just as indicated in the instructions and also followed them further. I edited only four of the patches in libnickel.so.1.0.0.yaml, but at clicking on kobopatch.bat at last, the black box for creating the koboroot.tgz opens for a few seconds and then closes without happening something else.
I tried so hard to find out the reason but couldn't find nothing. So I would kindly ask someone of the cracks to have a look at my settings in order to find out where the error is.
The first is:

Code:

Set KePub hyphenation:
  - Enabled: yes
  - Description: |
      The built-in KePub stylesheet has a line * { -webkit-hyphens: auto; }
      to turn on hyphenation, but it is only used if the device's justification
      button is set to full justification. With this patch enabled hyphenation
      will always be turned on, regardless of justification button setting.
      
      (The publisher can still turn hyphenation off/on in the book's stylesheet.)
  - ReplaceBytes: {Offset: 0x9E4E48, FindH: 3D F6 4E E2, ReplaceH: 01 20 01 20} # Alternative 1: Always turn KePub hyphenation on
# - ReplaceBytes: {Offset: 0x9E4E48, FindH: 3D F6 4E E2, ReplaceH: 00 20 00 20} # Alternative 2: Never turn KePub hyphenation on

but I scarcely think that there could be an error.
The second is:

Code:

Un-force font-family override p tags (std epubs):
  - Enabled: yes
  - PatchGroup: ePub force font alternatives
  - Description: |
      This patch allows the font set for paragraphs by the publisher in the epub
      stylesheet to override the font selected by the reader from the device.
    #     body, p { font-family: -ua-default !important; }
    # --> body    { font-family: -ua-default !important; }
  - FindBaseAddressString: "body, p { font-family: -ua"
  - ReplaceString: {Offset: 0, Find: "body, p", Replace: "body  \x20", MustMatchLength: yes}

but this seems not the problem as well.
The third is:

Code:

Un-Force user font-family in KePubs:
  - Enabled: yes
  - Description: |
      The KePub reader uses a very heavy-handed method of setting the font selected
      by the user, overriding all fonts set by the publisher in the book unless
      "Publisher Default" is selected.
      This patch lets the font-family set by the publisher in the KePub stylesheet
      override the font-family selected by the reader from the device in some
      cases, which allows a mix of user-selected and publisher-selected fonts.
      Alternatives 1-3 give increasing preference to the publisher-selected fonts.
  - FindBaseAddressString: "* { font-family: %1 !important; }\n"
    #
    # Alternative 1:
    #     * { font-family: %1 !important; }\n
    # --> div,p{font-family:%1!important; }\n
 # - ReplaceString:
 #     Offset: 0
#      Find: "* { font-family: %1 !important; }\n"
 #     Replace: "div,p{font-family:%1!important; }\n"
#      MustMatchLength: yes
    #
    # Alternative 2: (Similar to ePub default)
    #     * { font-family: %1 !important; }\n
    # --> body,p{font-family:%1!important;}\n
 - ReplaceString:
     Offset: 0
     Find: "* { font-family: %1 !important; }\y"
     Replace: "body,p{font-family:%1!important;}\y"
     MustMatchLength: yes
    #
    # Alternative 3: (similar to ePub with `Un-force font-family override p tags`)
    #     * { font-family: %1 !important; }\n
    # --> body{font-family:%1 !important; }\n
# - ReplaceString:
#     Offset: 0
#     Find: "* { font-family: %1 !important; }\n"
#     Replace: "body{font-family:%1 !important; }\n"
#     MustMatchLength: yes

There might be a problem, but I tried a lot of things without any change. I set the value of "FindBaseAddressString" to "y", but it didn't help.
And the last is:

Code:

KePub stylesheet additions:
  - Enabled: yes
  - Description: Makes room to add some additional CSS to the default KePub stylesheet.
    # See replacement CSS below for examples.
  - FindBaseAddressString: ".KBHighlighting, .KBSearchResult {"
  - ReplaceString: {Offset: 0x0000, Find: ".KBHighlighting, .KBSearchResult { background-color: #C6C6C6 !important; } \t",                                                                         Replace: ".KBHighlighting,.KBSearchResult{background-color:#C6C6C6!important}.KBSearch", MustMatchLength: yes}
  - ReplaceString: {Offset: 0x004C, Find: ".KBSearchResult, .KBAnnotation, .KBHighlighting { font-size: 100% !important; -webkit-text-combine: inherit !important; } \t",                          Replace: "Result,.KBAnnotation,.KBHighlighting{font-size:100%!important;-webkit-text-combine:inherit!important}.KBAnnotation[writingM", MustMatchLength: yes}
  - ReplaceString: {Offset: 0x00C7, Find: ".KBAnnotation[writingMode=\"horizontal-tb\"], .KBAnnotationContinued[writingMode=\"horizontal-tb\"] { border-bottom: 2px solid black !important; } \t", Replace: "ode=\"horizontal-tb\"],.KBAnnotationContinued[writingMode=\"horizontal-tb\"]{border-bottom:2px solid black!important}.KBAnnotation[writingMode=\"vert", MustMatchLength: yes}
  - ReplaceString: {Offset: 0x0157, Find: ".KBAnnotation[writingMode=\"vertical-rl\"], .KBAnnotationContinued[writingMode=\"vertical-rl\"] { border-right: 2px solid black !important; } \t",      Replace: "ical-rl\"],.KBAnnotationContinued[writingMode=\"vertical-rl\"]{border-right:2px solid black!important}.KBAnnotation[writingMode=\"vertical-lr\"]", MustMatchLength: yes}
  - ReplaceString: {Offset: 0x01E2, Find: ".KBAnnotation[writingMode=\"vertical-lr\"], .KBAnnotationContinued[writingMode=\"vertical-lr\"] { border-left: 2px solid black !important; }",          Replace: ",.KBAnnotationContinued[writingMode=\"vertical-lr\"]{border-left:2px solid black!important}/*********************************************/", MustMatchLength: yes}
    #
    # Replacement value: CSS string of exactly 47 characters in length:
    #
    # Example 1: Make full justification the default:
- ReplaceString: {Offset: 0x023B, Find: "/*********************************************/", Replace: "body{text-align:justify                       }", MustMatchLength: yes}
    #
    # Example 2: text-rendering:optimizeSpeed: Disables kerning, but fixes some
    # rendering problems that affect fully justified text.
# - ReplaceString: {Offset: 0x023B, Find: "/*********************************************/", Replace: "body{text-rendering:optimizeSpeed             }", MustMatchLength: yes}
    #
    # Example 3: text-rendering:optimizeLegibility: Enables ligatures, but causes
    # some additional rendering problems for fully justified text.
# - ReplaceString: {Offset: 0x023B, Find: "/*********************************************/", Replace: "body{text-rendering:optimizeLegibility        }", MustMatchLength: yes}
    #
    # Example 4: Make KePub font sizes match ePub font sizes: ePubs render with
    # 1.5 times the font size of KePubs by default. With this enabled they match.
# - ReplaceString: {Offset: 0x023B, Find: "/*********************************************/", Replace: "#book-inner{font-size:1.5em                   }", MustMatchLength: yes}

but there should be no error either.
I know it's a lot that I'm asking, but I'm really at the end of my possibilities. All the former patches worked. Please, help!

jcn363 · 12-20-2018, 09:06 AM

Quote:

Originally Posted by Leonatus

I tried so hard to find out the reason but couldn't find nothing. ... Please, help!

The last one seems malformed...
Let's see the end of /out/log.txt (you always can try one by one.)

Good luck.

Leonatus · 12-20-2018, 09:16 AM

The log file shows:

Code:

KoboPatch::OutputInit


KoboPatch::ApplyPatches
    KoboPatch::openIn
        Opening firmware zip 'src/kobo-update-4.12.12111.zip'
        Looking for KoboRoot.tgz in zip
        --> found KoboRoot.tgz
        -->    opening KoboRoot.tgz
        Opening gzip reader
        Creating tar reader
    patching entry name:'./usr/local/Kobo/libnickel.so.1.0.0' size:16033948 mode:'509' typeflag:'48' with files: src/libnickel.so.1.0.0.yaml
        reading entry contents
        loading patch file 'src/libnickel.so.1.0.0.yaml' (detected format kobopatch)
          | parsing patch file
        --> could not parse patch file: error parsing patch file: yaml: line 734: did not find expected key

***Sorry, I realize I'm in the wrong thread, that's due to my deception, but anyway ...***

jcn363 · 12-20-2018, 09:28 AM

Quote:

Originally Posted by Leonatus

The log file shows...

Try

Spoiler:

The indent (spaces) is important.

Good luck.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
KOBO firmware	ciemiku	Devices	6	08-26-2015 11:40 PM
Kobo Firmware 3.11.0	DNSB	Kobo Reader	465	04-05-2015 06:07 PM
Kobo Firmware 2.4.0	kaikara	Kobo Reader	253	04-15-2013 10:55 AM
Glo Kobo Firmware 2.3.1	danskmacabre	Kobo Reader	304	02-07-2013 01:52 AM

12-18-2018, 03:50 PM	#138
geek1011 Wizard Posts: 2,804 Karma: 7025947 Join Date: May 2016 Location: Ontario, Canada Device: Kobo Mini, Aura Edition 2 v1, Clara HD	This firmware was just released to the fnac affiliate.

12-18-2018, 11:33 PM	#141
JeanPierre Zealot Posts: 137 Karma: 398492 Join Date: Apr 2018 Device: Kobo Aura One	The process for highlight text seems to have been modified for this version of the firmware. Has anyone else noticed this? Previously once text had been highlighted, I had to long press on one of the white circles which appear at the end of the text, which then turned black, and then drag to a new position. Now, I have to long press and drag to turn the white circle black, then drag again to move the position. It took me a while to realise that I had to press and drag to register that I want to move the circle, rather than just long pressing on the circle to turn it black. Despite this unintuitive method of registering a desire to expand a highlight, I find that the actual expansion is more accurate than before, since a great degree of movement was previously required to move the cursor at all, sometimes requiring backtracking. Now, once you manage to register that you wish to change a highlight, you can move by a single character more easily. I see some very strange behaviour when I long press the circle at the front of the highlight, with it sometimes jumping halfway down the page past the circle that previously marked the end point. A work in progress, perhaps? Anyone else seeing this happen?

12-20-2018, 07:25 AM	#146
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	Geany Good luck.