Kobo Start Menu 07

[tshering]

Originally Posted by Markismus

After the last line in usersettings.txt I've added:

ksmGeometryValuesN=748x1014+5+5
ksmGeometryValuesS=748x1014+5+5
ksmGeometryValuesE=1014x748+5+5
ksmGeometryValuesW=1014x748+5+5

After rebooting it didn't result in any change.

These are the values for Aura that I took as default for H2O too, because of a misunderstanding. You have to take other values.

[Reventlov]

Originally Posted by Markismus

After the last line in usersettings.txt I've added:

ksmGeometryValuesN=748x1014+5+5
ksmGeometryValuesS=748x1014+5+5
ksmGeometryValuesE=1014x748+5+5
ksmGeometryValuesW=1014x748+5+5

After rebooting it didn't result in any change.

Looking at the koreader code

-- Kobo Aura H2O:
local KoboDahlia = Kobo:new{
    model = "Kobo_dahlia",
   ...
   ...
    -- bezel:
    viewport = Geom:new{x=0, y=10, w=1080, h=1430},

I would assume that values would become:

ksmGeometryValuesS= 1080x1420+5+5

Is this correct?

Well, adding the following to the files did it, thank you.

ksmGeometryValuesN=1080x1430+0+5
ksmGeometryValuesS=1080x1430+0+5
ksmGeometryValuesE=1430x1080+0+5
ksmGeometryValuesW=1430x1080+0+5

(Be sure there is no space after the =)

[Markismus]

Originally Posted by Reventlov

Well, adding the following to the files did it, thank you.

ksmGeometryValuesN=1080x1430+0+5
ksmGeometryValuesS=1080x1430+0+5
ksmGeometryValuesE=1430x1080+0+5
ksmGeometryValuesW=1430x1080+0+5

(Be sure there is no space after the =)

Mine work, too!

ksmGeometryValuesN=1070x1430+5+5
ksmGeometryValuesS=1070x1430+5+5
ksmGeometryValuesE=1430x1070+5+5
ksmGeometryValuesW=1430x1070+5+5

@Tshering Your guess was correct. I now have my line shuffle back as replacement for the lower right window. I'll try Reventlov's values and see whether I can get rid of that, too.

EDIT: Nope. The menu still gets drawn one line down when selecting koreader from the menu.

[tshering]

Originally Posted by Reventlov

Well, adding the following to the files did it, thank you.

ksmGeometryValuesN=1080x1430+0+5
ksmGeometryValuesS=1080x1430+0+5
ksmGeometryValuesE=1430x1080+0+5
ksmGeometryValuesW=1430x1080+0+5

Thank you Reventlov and Markismus. That means the bezel eats 5 pixels on the top and 5 on the bottom, and nothing on the left and right sides. From the koreader code quoted by Markismus (viewport = Geom:new{x=0, y=10, w=1080, h=1430},), I would have understood that the bezel eats 10 on the top side and nothing on the other sides, but maybe I am misunderstanding the code.

Edit: From the discussion below I guess the following values should fit:

ksmGeometryValuesN=1080x1429+0+11
ksmGeometryValuesS=1080x1429+0+0
ksmGeometryValuesE=1429x1080+11+0
ksmGeometryValuesW=1429x1080+0+0

For H2O users: Please add to the file .adds\kbmenu\usersettings.txt the above 4 lines. Attention: You have to use a unix-style editor.

[boriar]

I use the geometry of that post and i'm happy with it. Also apply this geometry in cr3 and kobolauncher.

[NiLuJe]

@tshering: Yup, top 11 pixels are behind the bezel. (ie. 1080x1429+0+11 [I *think*?]). (KOReader's viewport is off by 1 pixel, I haven't gotten around to fixing it yet ).

(And by 'top', I mean in portrait mode, and not upside down. i.e. nickel's default orientation).

[tshering]

Originally Posted by NiLuJe

@tshering: Yup, top 11 pixels are behind the bezel. (ie. 1080x1429+0+11 [I *think*?]). (KOReader's viewport is off by 1 pixel, I haven't gotten around to fixing it yet ).

(And by 'top', I mean in portrait mode, and not upside down. i.e. nickel's default orientation).

Thank you for letting me know. There seem somehow to be contradictory reports. Maybe the position of the bezel varies between different devices.

[NiLuJe]

@tshering: That seems unlikely, given the fact that nickel very specifically blacks out those 11 pixels, and goes to the trouble of special-handling already-processed sleep images to make very sure said 11 top pixels are blacked out, rescaling everything in the process to make sure there's no actual useful content behind the bezel (which, while neat in theory, is annoying in practice, since it potentially rescales an already-dithered image, which is a bad, bad thing. [Yup, I did some extensive testing on the subject, to have pretty sleep covers ;p]).

That, plus the fact that the hidden screenshot feature also uses 11 pixels (although in a broken way, rescaling to 1080x(1440-11) instead of cropping the top 11 pixels off) .

[tshering]

Originally Posted by NiLuJe

@tshering: That seems unlikely, given the fact that nickel very specifically blacks out those 11 pixels, and goes to the trouble of special-handling already-processed sleep images to make very sure said 11 top pixels are blacked out, rescaling everything in the process to make sure there's no actual useful content behind the bezel (which, wile neat in theory, is annoying in practice, since it potentially rescales an already-dithered image, which is a bad, bad thing. [Yup, I did some extensive testing on the subject to have pretty sleep covers ;p]).

That, plus the fact that the hidden screenshot feature also uses 11 pixels (although in a broken way, rescaling to 1080x(1440-11) instead of cropping the top 11 pixels) .

This sounds convincing. Are they doing something similar also for the Aura?

[NiLuJe]

@tshering: I'd be very interested to know. According to KOReader's code, there's a similar shenanigan going on with the *bottom* 12 pixels, but I'd need a proper fbgrab snapshot from an Aura to confirm that, and I don't have an Aura . (That, and I think the Aura is marketed as having a weird screen size off by 10 y px on the Kobo website, so, again, I'm not convinced the value is accurate).

(cf. my previous musings on the subject in the CR thread).

(On a slightly related note: I recently updated the standalone FBGrab builds to handle said cropping automatically on the H2O ).

[tshering]

Originally Posted by NiLuJe

@tshering: Yup, top 11 pixels are behind the bezel. (ie. 1080x1429+0+11 [I *think*?]). (KOReader's viewport is off by 1 pixel, I haven't gotten around to fixing it yet ).

(And by 'top', I mean in portrait mode, and not upside down. i.e. nickel's default orientation).

Thank you again. I edited post 19 accordingly.

[Markismus]

@NiLuje Your settings seem to have eliminated the "line shuffle" on my H2O. Thanks!

[gong]

Hello tshering and thanks for KSM.
I just installed night mode but selected "install partial update" instead of "install update". Is it possible that harms the device in any way??

PS: it's on Aura f/w 3.12.1

[tshering]

Originally Posted by gong

Hello tshering and thanks for KSM.
I just installed night mode but selected "install partial update" instead of "install update". Is it possible that harms the device in any way??

PS: it's on Aura f/w 3.12.1

Everything is okay! In this case both update options will lead to the same result.

[gong]

Originally Posted by tshering

Everything is okay! In this case both update options will lead to the same result.

Ah I'm reassured, thanks!

Also, is the method described here outdated or still the way to go in order to make an alternative setting for koreader?

And where do one set the opening path for koreader?