Kobo Firmware 4.12.12111

[Leonatus]

The log file refers to line 734, that's in the third patch and should be this line:

# --> body,p{font-family:%1!important;}\n

[jcn363]

Originally Posted by Leonatus

The log file refers to line 734, that's in the third patch and should be this line:

# --> body,p{font-family:%1!important;}\n

Do you read the previous post?

Good luck.

[Leonatus]

The indent (spaces) is important.

I tried to make it as you proposed:

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; }\n"
     Replace: "body,p{font-family:%1!important;}\n"
     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

but with no result. Shouldn't the values be set to "y"?

[jcn363]

The last one seems malformed too...

 - ReplaceString:

must be

  - ReplaceString:

2 spaces at the beginning.
Let's see the end of /out/log.txt is important to know where the error is.

Good luck.

[Leonatus]

Originally Posted by jcn363

The last one seems malformed too...
Let's see the end of /out/log.txt is important to know where the error is.

Good luck.

Yes, yes, yes! There must have been some error in my own settings. After copying/pasting your code, there was an error message concerning the last patch. I simply set the "- replace string" one space to the left, then it worked.
Thank you so much!

[davidfor]

Can we take the discussion of the patches to the patch threads? This is especially discussion of problems with them or applying them. These threads should be about discussing the firmware version and issues with them. Mention of the patches is fine, especially if a particular patch fixes a problem someone is having, but there are threads for the detailed discussion of the patches and how to use them.

[Dshine]

Does any one experience battery drainage with this update on kobo aura (1st edition)? Mine only last for 3 days since 100% charged.

[Leonatus]

Originally Posted by davidfor

Can we take the discussion of the patches to the patch threads?

Sorry, once more. I only had recognized that I was in the wrong thread when it was already too late.

[s4nder]

Has anyone found a way to force smaller top and bottom margins for full screen reading with the new firmware? I'm wasting several lines' worth of space now.

[Martina Schein]

Originally Posted by s4nder

Has anyone found a way to force smaller top and bottom margins for full screen reading with the new firmware? I'm wasting several lines' worth of space now.

Yes, @GeoffR has done it. Please show this posting.

[Quoth]

Bugs in this Firmware on Kobo H2O original:
1) Impossible to select a word or phrase on last line in "no footer" mode. It rapidly turns pages, even if near the middle of the screen. Page turn to swipe only doesn't fix it.

2)Wifi sometimes presents list of airpoints instead of connecting.

3) Old bug still not fixed: Turn off & on too quickly (flip sleep cover or press button twice), which can happen by accident and "Touch" is disabled. Sleep for a longer period usually fixes it. Sometimes needs a reset. I'm thinking it's not crashed or frozen as sleep cover/ active page appears and usually closing cover for count of 15 (or button) fixes it.

[Quoth]

Originally Posted by Dshine

Does any one experience battery drainage with this update on kobo aura (1st edition)? Mine only last for 3 days since 100% charged.

My battery life seems to have improved (Original H2O). Do you leave WiFi on? I always disable WiFi after a Wikipedia or Google search when dictionary doesn't suffice (why can't we set text & URLS for those on page where SM accounts are, and set URLS & text for those? Facebook & Google breaking EU & USA laws right now).

[ZodWallop]

Originally Posted by Dshine

Does any one experience battery drainage with this update on kobo aura (1st edition)? Mine only last for 3 days since 100% charged.

I haven't noticed that, no.

My battery is currently at 100%. I'll try not charging it and not sideloading anything over the weekend and see where it is at on Monday.

(As Frustrated said, I also leave my WiFi off and always have. But I wouldn't think that alone would cause sudden, rapid battery drain.)

[Tuneraider]

Release: 3.36 [21 Dec, 2018]
New features
Happy Holidays to everyone!
Kobo driver: Add supported for newly released firmware update

Also the was a new update for the Kobo desktop since I'd last used it.

[Uschiekid]

I can't remember if I ever tried this on the last (for Aura One) firmware, but I've found a bug with this firmware in PDFs.

I turn the PDF to be landscape. If I use the double tap method, the bug doesn't occur (but since it zooms too much or too little and then divides the screen into 4, which means to read one line, I have to slide back and forth, it is not much good for me). But if I zoom to a custom level, it treats the page as if it is still in portrait mode (if you look at the small diagram, it is showing the zoomed bit of page to be the wrong direction, compared to what it actually is, and is claiming that the whole page vertically is visible, which it is not), and there is no way to get to the top of the page (because it believes it is showing it already). Swiping up doesn't move you to the very top of the document (which is sometimes ok, if there is a title "bar"), swiping down seems to work, even though the "this is what's zoomed in box" is still portrait, it does move to the bottom of the page. But no matter how much I swipe up, it claims it is showing the top, but it isn't.

When I am testing it at the moment, it is landscape, zoomed to 175%, and I'm pretty sure it is a normal letter sized document with normal margins. I say this because in the past, I have chopped the margins off of documents so they were "pre-zoomed" on my kobo. I also tested at 225% zoomed, seems to be the same. Can't get to the top. I also tested it with an irregular document (without 4 even margins and a title "bar", only has page number at the top middle) and this does mean that I can't read the top of the document at all when zoomed in on landscape. I miss several lines of text.

Also weirdly, even when zoomed in, a tap would move to the next page, but if you want to go back, it is as before (swipe backwards, press black bar with arrow). This is not the case when double tapped in, in that case you have to zoom back out (or with Forma use the buttons) before you can get to the next page. I think maybe if I play with it, being able to turn the page without zooming out, might be good, but when I was trying to test this other issue, it was sure annoying.

If this has already been documented, sorry, I try to keep up and I don't recall seeing it.

Edit: actually even zoomed in (not using double tap), it turns pages both directions by tapping. And at the moment, I can't get the menu to come up, so I can't get out of the document ;-p I'll try a bit more, but I might have to resort to powering off.

Double Edit: Re: getting menu to show. I am an idiot. Because the menu comes up in the normal place, I was hitting the normal spot. But I of course needed to be hitting the side of the device (which is now the bottom in landscape).

See photos in next post to see the issue.