Patch 4.38.23038 don't work on 4.38.23171

[Uncle Robin]

Originally Posted by Sirtel

I drew the conclusion about my patches working after running the .bat file, as usually there's an error when something doesn't work.

Yes, that what puzzled me - I'm used to that kind od error, it's the first time I can recall a patch not triggering a fail but at the same not actually doing anything.

EDIT:

I just ran the same set of patches on my wife's Libra H2O (with the appropriate firmware of course). Same result. No failure or error, no change in display of the 3rd row

[Uncle Robin]

This is really odd. Here is the relevant line from my nickel.yaml

remove footer (row3) and increase cover size on new home screen:
  - Enabled: yes

and here is the relevant line from the log generated by kobopatch.bat

"Remove footer (row3) and increase cover size on new home screen": false,

Other patches I've enabled in the various yaml files all show "true", but this one, it seems ONLY one, does not.

I just ran kobopatch.bat again and this time copied the text about directl, not from the log file.

This is what says on the relevant line:

DISABLE `Remove footer (row3) and increase cover size on new home screen`

Other patches that I have enabled have "APPLY" before them, as

  APPLY `Unify font sizes`

[Sirtel]

Originally Posted by PeterT

The dictionary is independent from the upgrade; it was made available to be updated via the standard WiFi sync / install of dictionaries well before the newest firmware.

Not only that, if it's so important just save a copy pre it being upgraded and install it as a custom dictionary.

Yes, I know that now, and I did save it.

Originally Posted by Aleron Ives

Yes, but why go to the trouble of updating the firmware and patching again when you gain nothing interesting or useful from doing so? It's just a lot of extra work for nothing.

Exactly.

[Sirtel]

Originally Posted by Uncle Robin

This is really odd. Here is the relevant line from my nickel.yaml

remove footer (row3) and increase cover size on new home screen:
  - Enabled: yes

and here is the relevant line from the log generated by kobopatch.bat

"Remove footer (row3) and increase cover size on new home screen": false,

Other patches I've enabled in the various yaml files all show "true", but this one, it seems ONLY one, does not.

I don't have this in my log files either for Sage or Libra 2. Both show "true".

Maybe a conflicting patch was enabled?

[Uncle Robin]

Originally Posted by Sirtel

I don't have this in my log files either for Sage or Libra 2. Both show "true".

Maybe a conflicting patch was enabled?

That is what I assumed. But searching the log turned zero hits for "confl" as a string and in the past when I have enabled two conflicting patches, that tgz was not generated at all.

[Uncle Robin]

VEDI ET VICI (no veni involved)

I took another look at the output from kobopatch (not the log), and saw this:

Loading configuration from kobopatch.yaml

When I checked THATyaml , sure enough the non-applied patches were disabled. So I edited IT, and voilà - a reminder of the dizzy heights I can occasionally scale when both neurons fire at once.

[Sirtel]

Originally Posted by Uncle Robin

VEDI ET VICI (no veni involved)

I took another lok at the out from kobopatch (not the log, and saw this:

Loading configuration from kobopatch.yaml

When I checked THATyaml , sure enough the non-applied patches were disabled. So I edited IT, and voilà - a reminder of the dizzy heights I can occasionally scale when both neurons fire at once.

Happens to the best of us. Glad you got it to work.

[Uncle Robin]

Originally Posted by Sirtel

Happens to the best of us. Glad you got it to work.

It was a useful reminder of the value of kobopatch.yaml - not having to manually edit different yaml files each time. Although I do most of my reading on my Sage in KOReader, the growing chorus of praise for the Libra 2 Colour is tempting me to upgrade my second reader soon, and that one I'll probably use the stock Kobo reader for. If I do get a colour Libra I will definitely want my covers to be as big as possible with no extraneous Kobo marketing guff. So being reminded of of how to use kobopatch.yaml was timely.

[Pascougnou]

Might I ask how you applied patches on the 4.38.23038 (or even the 4.38.23171)?
I only found the 4.38.21908 patch release

[hatuluang]

Originally Posted by Pascougnou

Might I ask how you applied patches on the 4.38.23038 (or even the 4.38.23171)?
I only found the 4.38.21908 patch release

Please see this thread: Firmware 4.38.23171, post #4

[Uncle Robin]

Originally Posted by Pascougnou

Might I ask how you applied patches on the 4.38.23038 (or even the 4.38.23171)?
I only found the 4.38.21908 patch release

In koboatch.yaml, edit the relevant lines so they match the patch release

## Works with kobopatch v0.15.0 and later.
## You can update kobopatch by downloading the latest release from https://github.com/pgaskin/kobopatch/releases. 
version: 4.38.23171
in: src/kobo-update-4.38.23171.zip
out: out/KoboRoot.tgz
log: out/log.txt

That's the function of kobopatch.yaml to serve as template of patches to be applied, so you only have to edit the patch version number each time. It may not always work with all patches, but if you use relatively few (as I do) the odds are good it will save a lot of time. If, UNLIKE me, you remember that you're using it

[JSWolf]

Originally Posted by Uncle Robin

In koboatch.yaml, edit the relevant lines so they match the patch release

## Works with kobopatch v0.15.0 and later.
## You can update kobopatch by downloading the latest release from https://github.com/pgaskin/kobopatch/releases. 
version: 4.38.23171
in: src/kobo-update-4.38.23171.zip
out: out/KoboRoot.tgz
log: out/log.txt

That's the function of kobopatch.yaml to serve as template of patches to be applied, so you only have to edit the patch version number each time. It may not always work with all patches, but if you use relatively few (as I do) the odds are good it will save a lot of time. If, UNLIKE me, you remember that you're using it

Don't do that as the patches are available in the links posted above. Some of the patches have been fixed for the correct locations in the new firmware. Also, DSNB has edited kobopatch.yaml such that it now groups patches that are either or. It's now just a matter of editing the kobopatch.yaml once and you are done. So really, grab the patch ZIP file for 4.38.23171 instead of going with an older version that won't work as well.

[Sirtel]

Originally Posted by Uncle Robin

It was a useful reminder of the value of kobopatch.yaml - not having to manually edit different yaml files each time. Although I do most of my reading on my Sage in KOReader, the growing chorus of praise for the Libra 2 Colour is tempting me to upgrade my second reader soon, and that one I'll probably use the stock Kobo reader for. If I do get a colour Libra I will definitely want my covers to be as big as possible with no extraneous Kobo marketing guff. So being reminded of of how to use kobopatch.yaml was timely.

Heh. I'm not tempted at all by the Libra Colour (or any other current color eink device, for that matter). I'd be very tempted by a new, faster, upgraded black and white Libra, though. Or by a new black and white Sage.

Kaleido tech, which worsens the b/w experience (no matter how slightly) is not at all attractive to me. YMMV, of course.

[Uncle Robin]

Originally Posted by Sirtel

a new black and white Sage..

On this we are in complete agreement. And I am certain we will get one, in the same week I am elected Queen of North Korea

[Sirtel]

Originally Posted by Uncle Robin

On this we are in complete agreement. And I am certain we will get one, in the same week I am elected Queen of North Korea

I do hope you won't have to make such a sacrifice for a new Sage to be released...

It would be sad if Kobo never released a new b/w ereader with 7-8" screen, but only Kaleido ones.