Instructions for patching firmware 3.18.0

[MGlitch]

Originally Posted by jackastor

I have no issue with the full screen mode on my H20

regards
JAck

Have you updated to 3.18.0 and done one of the things which triggers the glitch?

At first I thought the H2O was fine, then I checked a word in the dictionary and bam refreshes on every page turn.

[GeoffR]

Originally Posted by jackastor

I have no issue with the full screen mode on my H20

What do you have your page refresh rate set to? The issue others are having (except on the Aura) is that it refreshes every page, but if you have it set to do that anyway then you might not notice.

The issue is only triggered after putting the device to sleep from within the book, or using certain functions such as the dictionary from within the book. It doesn't happen when you first open the book.

If you can put the device to sleep and wake it again in full-screen mode, and then continue reading without it refreshing every page, then maybe we can figure out what is different about your book or settings.

[GeoffR]

Could someone with an Aura, and someone with a device other than a Glo, check the following please?

Go to Help > Getting started, page forward to the end (on the Glo there are 8 pages), and then page backwards to the beginning.

On my Glo, when I reach page 7 it does a full refresh, and after than it refreshes every page until I exit the Getting started booklet.

It would be instering to know if this happened in 3.17.3 too, as it could be related to the FullScreenReading refresh bug.

[davidfor]

Originally Posted by GeoffR

Could someone with an Aura, and someone with a device other than a Glo, check the following please?

Go to Help > Getting started, page forward to the end (on the Glo there are 8 pages), and then page backwards to the beginning.

On my Glo, when I reach page 7 it does a full refresh, and after than it refreshes every page until I exit the Getting started booklet.

It would be instering to know if this happened in 3.17.3 too, as it could be related to the FullScreenReading refresh bug.

On the Aura H2O and the Glo HD, the text area gets a full refresh. The heading and what would be the footer don't refresh. This happens for all pages from when I open it.

On the N905 Touch, I don't see a refresh no matter what I do.

[GeoffR]

Originally Posted by davidfor

On the Aura H2O and the Glo HD, the text area gets a full refresh. The heading and what would be the footer don't refresh. This happens for all pages from when I open it.

On the N905 Touch, I don't see a refresh no matter what I do.

Thanks.I don't know what of make of that yet.

The full refresh on the Glo also excludes the header and footer. The behaviour on the Glo is not related to the number of page turns, because I can page back and forwards as much as I like with no refresh before I reach page 7, but once I reach page 7 it turns on the refresh switch.

[outlandos]

Originally Posted by GeoffR

Thanks, so this patch is only needed on the Glo. It prevents the "Pinch to adjust font size" and "Two-finger swipe to adjust brightness" settings from showing on the Reading Settings page.


This patch prevents the Multi-touch options being displayed on all devices, only useful for the Glo.

Firmware 3.18.0, paste into libnickel.so.1.0.0.patch:

Spoiler:

<Patch>
patch_name = `Don't show Aura-specific reading options`
patch_enable = `yes`
replace_bytes = 764A90, 01 46, 00 21
</Patch>

Edit: This alternative should cause the multi-touch options to display only on devices that support multi-touch gestures (i.e. only on the Aura, or other devices with a custom multi-touch kernel.) It should be okay to apply to all devices, but only tested on the Glo so far.

Firmware 3.18.0, paste into libnickel.so.1.0.0.patch:

Spoiler:

<Patch>
patch_name = `Only show multi-touch options on multi-touch devices`
patch_enable = `yes`
#
# The Glo's Reading settings page shows "Pinch to adjust font size" and
# "Two-finger swipe to adjust brightness" even though those options don't
# work on the Glo.
#
# This patch causes those options only to be displayed on devices which support
# multi-touch gestures: the Aura, and devices with a custom multi-touch kernel.
#
# Device::isPhoenix() --> Device::supportsMultitouch()
replace_bytes = 764A8C, 87 F4 18 EA, 9E F4 60 EE
</Patch>

So i assume this patch is not needed on the Glo HD then?

[GeoffR]

Originally Posted by outlandos

So i assume this patch is not needed on the Glo HD then?

That's right, it's only useful for the Glo (or maybe on other devices if they have a custom-built kernel, but I don't know if anyone is using one of those anymore.)

[GeoffR]

I haven't had any luck finding a fix for the FullScreenReading refresh bug, but I have an idea how to make the old-style ePub full-screen mode (i.e. normal mode with the reading footer disabled) a bit better for those who use adjustable top/bottom margins.

On the Glo, the ePub reader has a built-in top margin of 15 pixels, which is 2% of screen width. I'd like to find out if this is the same on other devices.

If anyone wants to help, you can sideload this test ePub and take a screenshot of the first page in normal reading mode, not full-screen mode. It should draw the biggest rectangle that can fit on the screen. I just need to know the number of pixels above the top of the rectangle.

Don't use Calibre to sideload the ePub if you have anything that automatically changes the stylesheet, just copy it to the device instead.

If you have the fixed/adjustable top/bottom margin patch enabled with adjustable top margin, then set the margin slider to minimum before taking the screenshot. If you have a fixed top margin set then let me know what size you have set in the patch. Otherwise if you don't use that patch then you don't need to do anything else.

Edit: Attached is the screenshot from my Glo, just so you know what to expect.

[Nick_1964]

This is on my Glo HD.



This is the page on glo HD



These where the settings during display.

I used: patch_name = `Custom reading footer style` with your default settings and adapted one value to make the "page xx of xx" txt a bit larger:
# Replacement caption font size value for GloHD:
replace_string = 00C5, `font-size: 30px;`, `font-size: 33px;`I am still on 3.17.3 if you want me to change to 3.18 let me know.

It looks to me that my top margin is smaller but don't know how to "measure" how much pixels it is..

[GeoffR]

Thanks Nick, the top margin in that screenshot is 15px, same pixel size as the Glo, but only 1.4% of screen width compared to 2% on the Glo.

I am testing a new patch that adds an extra 2% to the left/right margins when reading ePubs in normal reading mode, but not in full-screen mode. On the Glo this works out neatly because the built-in top margin is 2% in normal mode and zero in full-screen mode, so when the adjustable top/bottom margins are enabled everything will stay in proportion in both modes.

But I can only adjust the margin in 1% multiples if the screen width, so it looks like it won't work out so neatly on all devices.

[Nick_1964]

Originally Posted by GeoffR

Thanks Nick, the top margin in that screenshot is 15px, same pixel size as the Glo, but only 1.4% of screen width compared to 2% on the Glo.

I am testing a new patch that adds an extra 2% to the left/right margins when reading ePubs in normal reading mode, but not in full-screen mode. On the Glo this works out neatly because the built-in top margin is 2% in normal mode and zero in full-screen mode, so when the adjustable top/bottom margins are enabled everything will stay in proportion in both modes.

But I can only adjust the margin in 1% multiples if the screen width, so it looks like it won't work out so neatly on all devices.

I understand.. for the Glo HD it would only be possible for 1% with leaves 0,4.. with 2% it would be missing 0,6.. and I don't know how this counts for the Aura HD,which have another resolution.. but maybe you can calculate the values knowing now how much is left on a Glo HD ?? (or you make it a Glo only patch...)

[NiLuJe]

Keep in mind that on some devices the built-in screenshot function is stupid, and will badly resize the image to handle the 'dead' (behind bezel) pixels instead of cropping them.

A direct dump of the fb (via fbgrab, for instance) will be more accurate .

[norbusan]

Dear all,
here is my mega-update for 3.18.0, this time for Mark4, Mark5, and Mark6. It includes the following addons:

• KSM8 - to fix database corruptions with Calibre and kepub driver
• Metazoa patches - this thread
• KOreader
• pbchess and CoolReader - the vlavasoft stuff
• ssh server from the kobohack project
• several side-loaded fonts

Please see detailed explanations here:
http://www.preining.info/blog/2015/0...tch-ssh-fonts/

Norbert

[MGlitch]

Using Literata with hinting removed and old style kern tables, I find I can get a better result than the fullscreen reading mode by enabling the adjustable top/bottom margin patch, and the force user line spacing patch, then setting margin and line spacing to the lowest settings.

Text is basically on the edge of the screen.

[GeoffR]

Originally Posted by NiLuJe

Keep in mind that on some devices the built-in screenshot function is stupid, and will badly resize the image to handle the 'dead' (behind bezel) pixels instead of cropping them.

A direct dump of the fb (via fbgrab, for instance) will be more accurate .

Do you know which devices are affected by that?

I guess it should still be possible to work out the size of the visible part of the top margin from the screenshot, at least within a pixel or two.