Kobo Start Menu

[tshering]

Originally Posted by Jellby

Which package? Did you forget to attach the file?

Yes, I have noticed it right now.

[tshering]

I finally uploaded the archive in post 389.

[ipse]

Originally Posted by tshering

Since there is a new FW 3.5.0 I would like to call to mind that there is always a chance that new firmwares might cause problems in connection with the Kobo Start Menu. If you don't want to take the risk, don't install the new FW, or install the new FW by selecting "handle update" > "install update" (rather than install partial update).

Been away from the forum for a while and got treated with surprises when I got back...new 3.5.0, new KOreader, new CoolReader...sweet!

I followed your advice and did an "install" vs "partial install" to be on the safe side, went then back and did a Start Menu "reinstall" and all is OK.
Not sure I really need the 2 incremental updates over v4 - I remember having to roll back last time, so I'll stay with base v4.

Thanks guys...

[tshering]

Originally Posted by ipse

I followed your advice and did an "install" vs "partial install" to be on the safe side, went then back and did a Start Menu "reinstall" and all is OK.

I am glad to hear that everything is ok. My advice to caution was meant for the then situation: There were no reports that the Start Menu works with FW 3.5.0, and I could not test it myself at that time.

Originally Posted by ipse

Not sure I really need the 2 incremental updates over v4 - I remember having to roll back last time, so I'll stay with base v4.

If you happy without the updates, I am happy too. However, since you own an Aura, I think the addition in post #389 might be of interest to you; cf. post #386 for the problem, which I hope the addition can solve.

[Jellby]

Originally Posted by tshering

For Aura, I set the default values to 758x1014+9+9. For the other models, I left everything at its original state.

Thanks, it seems to be working. But for my device the good settings are closer to 748x1014+1+3 (little overlap in the top and left edges, more on the right and bottom).

Note: The changes concern only the "normal" portrait mode. If you rotate to any of the other three directions, the start menu screen will be displayed in the usual full screen mode.

Any chance of fixing this?

By the way, for the findoptimgwidth.sh script, could you remove the vertical scrollbar, or use a wide image when in landscape mode?

[tshering]

Originally Posted by Jellby

Any chance of fixing this?

It is certainly overkill, but I decided to make the values settable for each direction individually. Since you seem the only one interested in this function, you may choose the default settings for the Aura if you like:

ksmGeometryValuesN=550x750+0+24
ksmGeometryValuesS=
ksmGeometryValuesE=
ksmGeometryValuesW=

Originally Posted by Jellby

By the way, for the findoptimgwidth.sh script, could you remove the vertical scrollbar, or use a wide image when in landscape mode?

My idea for image viewing with the message-application was something like this:

Spoiler:

Most of my pictures on the reader are in portrait format. Therefore, for the case that the reader is in portrait mode, I set the width a little smaller than the width of the reader to prevent horizontal overflow. For most of these images this will also prevent vertical overflow. For the case that the reader is in landscape mode, I set again the width of the images a little smaller than the width of the reader. This however will almost certainly produce a vertical overflow. For a greater part of portrait oriented images the overflow will be a third or so, or even more. Since by tapping on the right or left part of the screen one can page up and down (the main purpose of this application was to display text messages), it is easy to navigate vertically through the image. My idea was this: In normal, that means portrait mode, I see as a whole images, and if I want to see more details I change to landscape mode. And now comes the important point: The possibility to page up and down is closely connected with the presence of the vertical scroll bar.

Anyway, this was an emergency solution. Kind of poor man's zoom. I was on a long trip and had only a text editor as a tool with me to make changes to the KSM, and needed to view maps on the reader. I think that I will try to find another way to display images.

[Jellby]

Originally Posted by tshering

It is certainly overkill, but I decided to make the values settable for each direction individually. Since you seem the only one interested in this function, you may choose the default settings for the Aura if you like

Thanks. Missing attachment again?

I noticed that "(most) Kobo Start Menu screens" apparently does not include script screens, such as browse or findoptimgwidth.

[tshering]

Originally Posted by Jellby

Thanks. Missing attachment again?

Actually, I am waiting for your suggestion for the default values. Of course I could have guessed. But since I do not have an Aura in front of me, your guessing should be better.

Originally Posted by Jellby

I noticed that "(most) Kobo Start Menu screens" apparently does not include script screens, such as browse or findoptimgwidth.

"browse" is included now, others will follow.

[Jellby]

I would suggest (if I get the meaning correctly) something like:

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

That should mean adding a 5-pixel margin on all sides, which then can be more finely adjusted by the user. (it seems the physical screen width is 758, not 768).

[tshering]

@Jellby
Yes, you got the meaning correctly, even thought I inserted my test value for the Kobo Touch as an example value.
I updated the archive in post #389
From your first set of values (748x1014+1+3) I got the impression that at the Aura the screen is masked uneven on the four boarders. From your new values I guess, this is not the case.

[Jellby]

Originally Posted by tshering

From your first set of values (748x1014+1+3) I got the impression that at the Aura the screen is masked uneven on the four boarders. From your new values I guess, this is not the case.

In my particular unit it is uneven, but I can't be sure it is the same with every Aura, that's why I suggest even values as default. Another option, probably just as good, is leave the defaults at 758x1024+0+0.

My personal optimized settings are:

ksmGeometryValuesN=753x1007+1+3
ksmGeometryValuesS=753x1007+4+14
ksmGeometryValuesE=1007x753+14+1
ksmGeometryValuesW=1007x753+3+4

[tshering]

Originally Posted by Jellby

In my particular unit it is uneven, but I can't be sure it is the same with every Aura, that's why I suggest even values as default. Another option, probably just as good, is leave the defaults at 758x1024+0+0.

My personal optimized settings are:

ksmGeometryValuesN=753x1007+1+3
ksmGeometryValuesS=753x1007+4+14
ksmGeometryValuesE=1007x753+14+1
ksmGeometryValuesW=1007x753+3+4

Thank you for this information. It would be helpful to have information how this is on other units. If the position of the mask is different form unit to unit his should effect the reading experience with nickel too on some units.

[Jellby]

Originally Posted by tshering

Thank you for this information. It would be helpful to have information how this is on other units. If the position of the mask is different form unit to unit his should effect the reading experience with nickel too on some units.

The margins with unpatched nickel are rather generous, so I guess this is not a big issue. But when a cover is displayed at full screen, I can indeed notice the masking and the missing bottom pixels (for some covers). And with narrow margins I notice that they are not symmetric.

[HaoZeke]

I've noticed that starting either koreader or coolreader immediately runs a killall nickel (amongst some other processes).
However I was wondering if it is not required to kill any other alternative readers while opening one? Like if I run koreader, cthere should be a killall coolreader or some such? (Unfortunately I don't know the process names for koreader and coolreader)

[tshering]

Originally Posted by Jellby

The margins with unpatched nickel are rather generous, so I guess this is not a big issue. But when a cover is displayed at full screen, I can indeed notice the masking and the missing bottom pixels (for some covers). And with narrow margins I notice that they are not symmetric.

Ah, thank you!