Kobo Start Menu 08

[Ken Maltby]

Perhaps, the following wasn't done:

After KSM has started the first time, please change this behaviour:•select "tools" > "activate" > "set runmenu settings.msh" > "always"

Luck;
Ken

[The_Immortal]

Ken Maltby, now Start Menu starts every time, thanks. But anyway KOReader doesn't start automatically after loading Start Menu though as I said before I have ksmAutoselectionoption=start_koreader set (and nothing more) in general section.
So what's the problem?

Do I need to add ksmAutoselectionafter=0 anyway?

[tshering]

Originally Posted by The_Immortal

Ken Maltby, now Start Menu starts every time, thanks. But anyway KOReader doesn't start automatically after loading Start Menu though as I said before I have ksmAutoselectionoption=start_koreader set (and nothing more) in general section.
So what's the problem?

Do I need to add ksmAutoselectionafter=0 anyway?

How long did you wait? koreader is expected to start after about 20 seconds. If you want to have it start quicker, change the value of ksmAutoselectionafter. If you set it to a very short time, you take some risk. If koreader becomes unresponsive for some reason (and you cannot prevent koreader from starting), you have to factory reset your device (possibly by opening the device).

[Ken Maltby]

I would try "ksmAutoselectionafter=5" . There has been a post of someone using "0" and KOReader set to Open in last file, with out problems, but a few seconds, just to be safe, might be your best bet.

Luck;
Ken

[tshering]

With this package you can download and handle patches from pipcat's http://pip.cat/khd/kobo/ (see this thread).

Installation:

• extract KoboRoot.tgz from the uploaded archive, and copy it into .kobo of your device
• safely disconnect and disable usb
• select (KSM home) handle update > install update

How to download a patch collection:

• enable wifi
• select (KSM home) user scripts > tests > returntests user.msh > khd download patches.sh
• (animation)
• you will be presented with a list of patch profiles. Choose one of them (see the attached image)
• (animation)
• if everything went well, you will get informed: everything seems to be ok!

How to apply the downloaded patches:

• select (KSM home) user scripts > tests > returntests user.msh > khd apply patches.sh
• (animation)
• if you are presented with a full report, you can close the info screen by touching the middle of the screen and then choosing "close"

How to restore the original state of the device:

• select (KSM home) user scripts > tests > returntests user.msh > khd_restore_original_state.sh

If you decide to download another patch collection, remove first the already downloaded patches:

• select (KSM home) user scripts > tests > returntests user.msh > khd_delete_patches.sh

If you are finished patching, and you are certain you do not want to restore, delete the patch directory (this includes the backups of the un-patched libraries):

• select (KSM home) user scripts > tests > returntests user.msh > khd_delete_patch_dir.sh

Important points:

• After installing any Kobo Firmware, you must run nickel at least once before downloading a patch collection. If not the scripts cannot correctly ascertain the current firmware version and will try (and fail) to find patches for a FW that does not exist at all!
  
• If you use this package, no patches must have been already applied.
  Spoiler:

  If you did already apply patches, you have to provide the original, not-patched, libraries. The location for these libraries is for the current 3.19.5761 FW:
  /mnt/onboard/.adds/kbmenu_user/patchbase/3.19.5761_0e028f3185/orig
  (The path /mnt/onboard/.adds/kbmenu_user/patchbase/3.19.5761_0e028f3185 will be created by "khd download patches.sh")

Note: Downloading is rather slow. The bottleneck is wget!

[ntanvinh]

I installed KSM 8, and explored file system but I couldn't find the font folder (which contain font displayed on menu of Nickel). Could you tell me where it is?

[tshering]

Originally Posted by ntanvinh

I installed KSM 8, and explored file system but I couldn't find the font folder (which contain font displayed on menu of Nickel). Could you tell me where it is?

The location of the font files is /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts. You can however not view this directory with "explore." The reason is that directories and files that have a "-" or a space in the name are ignored by design. This makes some things easier for me, but has of course disadvantages. In order to investigate the system partition you could use telnet, or the file explorer of PBChess (I think, but I did not use it myself). In many cases the easiest way might be to copy a firmware update package to the pc and investigate it there.

[PeterT]

Additionally the fonts in that location are encoded.

[ael]

Hi all,

I'm new in the e-reader world, I've just bought a Kobo Aura h2o.

I really appreciate your work with the Kobo Start Menu project and since I'm a developer too, I would like to contribute.

I would like to start with these questions:
- I didn't find any public repository with the source code of KSM project. Is there any specific reason for that? How do you usually collaborate?

- I saw that you usually release precompiled package with embedded KSM ready to be flashed. I think that this is very simple and straightforward way to install it. But it would be nice to have also a reproducible procedure that allow to build those packages starting from a brand new firmware. What do you think about it?

I really need to thank you for your amazing work

[tshering]

Originally Posted by ael

Hi all,

I'm new in the e-reader world, I've just bought a Kobo Aura h2o.

I really appreciate your work with the Kobo Start Menu project and since I'm a developer too, I would like to contribute.

I would like to start with these questions:
- I didn't find any public repository with the source code of KSM project. Is there any specific reason for that? How do you usually collaborate?

- I saw that you usually release precompiled package with embedded KSM ready to be flashed. I think that this is very simple and straightforward way to install it. But it would be nice to have also a reproducible procedure that allow to build those packages starting from a brand new firmware. What do you think about it?

I really need to thank you for your amazing work

Welcome to the forum,

I am glad that you like KSM. The packages are tgz-archives. That means you can simply extract the content and see what is inside. You can change things as you see fit, and re-pack them. If you do this under linux you have to take care to set the file permissions. If you do it under windows with 7zip (I am not sure about other applications), all files are automatically given executable status.
You will see that a large part of KSM consists of sh scripts. This makes it easy to change things or add new functionality. Everybody is invited to share his scripts on this thread. As for the included binaries, they have different sources. At the bottom of the first post you can find links that will lead you (eventually) to the sources of some of them (see "The package contains materials provided by ..."). And yes, some sources are not published.

[ael]

Originally Posted by tshering

Welcome to the forum,

I am glad that you like KSM. The packages are tgz-archives. That means you can simply extract the content and see what is inside. You can change things as you see fit, and re-pack them.

Indeed this is true. But according to me there are some problems with this approach:

- It is difficult to keep track of changes from one release to the other.
- Without using a CVS (Control Versioning System) it is very difficult to collaborate and to receive contributions to the project.

Without providing a good documentation and some easy way to collaborate usually project are going to die soon. I know that this is a big effort, and not an easy job, but I'm ready to give my contribution.

Originally Posted by tshering

You will see that a large part of KSM consists of sh scripts. This makes it easy to change things or add new functionality. Everybody is invited to share his scripts on this thread. As for the included binaries, they have different sources. At the bottom of the first post you can find links that will lead you (eventually) to the sources of some of them (see "The package contains materials provided by ..."). And yes, some sources are not published.

Which are the sources that have not been published?


If I understood correctly, flashing the KSM package over an original firmware, the /etc/init.d/rcS is the only original file that is overwritten (Am I wrong?). To make the package compilation/assembling reproducible starting from an original firmware we should provide some kind of patch file instead of the already modified complete file.

In such a way that is also easier to understand which are the addition/deletion with respect to the original file.

I really want to valorize the great work and the effort that you're putting in this project and make it easier to collaborate, giving it a chance to last longer.

[Ken Maltby]

The added lines to rcS seem well delineated, to me. I think that you are underestimating what "tshering" has accomplished within this forum format. I am certainly a fan of Github, for projects that require such development, but most of tshering's efforts, including KSM, were developed into working tools, right before our eyes, out of the discussion and testing on these forums. If tshering is planning some grand expansion of his KSM into something far beyond the great tool it already is, then starting a project somewhere like Github would be a good idea. Maybe I am being small minded but I like KSM as it is, and don't really see how it could be greatly expanded to any great purpose.

Luck;
Ken

[Jellby]

Maybe the question is: if something unfortunate would happen to tshering tomorrow... can KSM be still maintained and developed?

[ksiflhjla8]

Could the usbnet IP (192.168.2.101) be written somewhere in the menu?

[tshering]

Originally Posted by Jellby

Maybe the question is: if something unfortunate would happen to tshering tomorrow... can KSM be still maintained and developed?

I am happy I survived day before yesterday's tomorrow!