Kobo Start Menu 08

[boriar]

Originally Posted by tshering

I added the new version here. Do not forget to back up your database before you test this version.

Thanks. Downloaded and will try soon.
Return to the work

[pj123]

I installed KSM08 on my Kobo Aura H2O. Thank you! I am wondering whether it is possible to display the time and battery percentage and also whether it is possible to add a notepad.

[tshering]

Originally Posted by pj123

I installed KSM08 on my Kobo Aura H2O. Thank you! I am wondering whether it is possible to display the time and battery percentage and also whether it is possible to add a notepad.

If you want the time and battery percentage displayed at the main menu, and regularly updated, then this is not an available option. You can however get information about the battery percentage by selecting "tools" > "checkbattery.sh".

The PBChess package includes a notepad.

[hharum]

hello tshering

I have an Kobo H2O, software vs. 3.16.17. Installed KSM08 and pbchess_2016.12.31 afterwards, everything works fine, except light on coolreader
Shall I go to 3.19? Can I do that?
Or is there another way to fix this issue?
Thanks

[tshering]

Originally Posted by hharum

hello tshering

I have an Kobo H2O, software vs. 3.16.17. Installed KSM08 and pbchess_2016.12.31 afterwards, everything works fine, except light on coolreader
Shall I go to 3.19? Can I do that?
Or is there another way to fix this issue?
Thanks

ikkentobi reported the same issue in this thread, post #738. See also the posts that follow on it. Finally ikkentobi copied the pbchess files anew, and than the light worked. I have no idea what might have happened when he copied the files the first time.

Independent of the light problem (which is unlikely to be related to the FW),I would recommend that you update to the most recent FW for H20. See this post on how to install the FW under KSM.

If you by-passed the Kobo registration and you update the FW to the recent version, you might get a pop-up saying something to the effect, that the device is not registered and that the database will be deleted. If this happens, do not confirm this message! Rather force the device to power down by pressing the power-off button and holding it for 25 secs or so. In KSM select:
tools > nickel diverse.msh > activate device > deactivate device.sh
and then select:
activate device empty.sh

Since I understand that you are a new KSM user, I would like to mention that the last step of the KSM installation is important:
select "tools" > "activate" > "set runmenu settings.msh" > "always"
If you have not already done it, do it now! Otherwise things might get confusing.

[tshering]

The information in this post is obsolete. See this post.

Spoiler:

I want to share an idea that might never make it into an updated version of KSM. Imagine you are running KOReader and leave the device alone for a long time, trusting that KOReader's automatic suspend function will kick in (or maybe you manually suspend the reader), but for some reason there occurs a problem and KOReader exits and gives control back to KSM. Since KSM does not have an auto suspend function, the device will stay awake until you return, or until the battery will be flat.

To prevent this from happening we try to do the following. 1) We modify KOReader so that it informs KSM whether the user made KOReader exit. 2) We modify KSM to display a message if KOReader exists without being explicitly asked by the user to do so; and to power the device down, if there is no user input for 20 seconds or so.

1.1) Modification of KOReader: modify .adds\koreader\frontend\apps\filemanager\filemanag ermenu.lua; code to insert is marked in red.

Spoiler:

        home = {
            icon = "resources/icons/appbar.home.png",
            callback = function()
                local file = io.open("/tmp/koreader_exit_message","w")
                if file then
                  file:write("userexit")
                  file:close()
                end
                if SetDefaults.settings_changed then
                    SetDefaults.settings_changed = false
                    UIManager:show(ConfirmBox:new{
                        text = _("You have unsaved default settings. Save them now?"),
                        ok_callback = function()
                            SetDefaults:saveSettings()
                        end,
                    })
                else
                    UIManager:close(self.menu_container)
                    self.ui:onClose()
                end
            end,
        },

1.2) Modification of KOReader: modify .adds\koreader\frontend\apps\reader\modules\reader menu.lua; code to insert is marked in red.

Spoiler:

        home = {
            icon = "resources/icons/appbar.home.png",
            remember = false,
            callback = function()
                local file = io.open("/tmp/koreader_exit_message","w")
                if file then
                  file:write("userexit")
                  file:close()
                end
                self:onTapCloseMenu()

If KOReader exits spontaneously, you will find a log file /log/koreader_exit_log.txt. Use "explore" to navigate there and read the file.


You can test the function by launching KOReader with the new script, and then kill it by telnet:

[root@(none) ~]# killall reader.lua

I removed the archives here, since they are not needed if you install the patch for Auro One and Auro Edition 2 (which is compatible with all devices):

[oldhasbeen]

@tshering
wow - what a service.
I just wanted to ask you to enable an KSM auto shut-off when it is in idle state. And you did that already. That borders on spooky!
How do I get into the system partition? I see only the .adds\kbmenu_user part.
You may have followed the suspend issue on GitHub and the memory leak discussion. Is there a memory leak issue with KSM 08 and subsequent reduction of available RAM?

[tshering]

@oldhasbeen
you can get stuff to the user partition by using the upgrade mechanism (KoboRoot.tgz). In the current case, since there is only one file to copy, it might be easier to use KSM's "copy sysmirror to sys" function; see this post for a description (the last point to the end of the post). As for memory leak in KSM, I am not aware of any.

[hharum]

Thanks tshering
Installed FW3.19 and reinstalled coolreader, works fine now

Thanks again

[tshering]

Originally Posted by hharum

Thanks tshering
Installed FW3.19 and reinstalled coolreader, works fine now

Thanks again

I am glad it works.

[tshering]

@oldhasbeen
I have added a KoboRoot.tgz that installs the new start_koreader.sh to post #366 (start_koreader_replacement.zip). Extract KoboRoot.tgz from the archive and copy it into .kobo. In KSM select: (home) "handle update" > "install update".
If there is some interest, I think shouldl change the script a little (showing the power-off screen, and maybe writing to a log file).

[boriar]

Originally Posted by tshering

@oldhasbeen
I have added a KoboRoot.tgz that installs the new start_koreader.sh to post #366 (start_koreader_replacement.zip). Extract KoboRoot.tgz from the archive and copy it into .kobo. In KSM select: (home) "handle update" > "install update".
If there is some interest, I think shouldl change the script a little (showing the power-off screen, and maybe writing to a log file).

I think the log file will be interesting for testing purpose (may be with a flag) but I don't know what you say with "showing the power-off screen". Is it show the poweroff screen of koreader?

[tshering]

Originally Posted by boriar

I think the log file will be interesting for testing purpose (may be with a flag) but I don't know what you say with "showing the power-off screen". Is it show the poweroff screen of koreader?

No, I meant the power-off screen of KSM. Currently, the device is simply powered off without any change on what is displayed on the screen. That means, it displays the KSM menu, informing that KOReader has exited irregularly and offers the options to power off or to continue. You do not see on the first sight that the device is powered off.

[trekk]

Originally Posted by tshering

If there is some interest, I think shouldl change the script a little (showing the power-off screen, and maybe writing to a log file).

Thank you, tshering! Personally I would be interested in both - the power-off screen and the log file.

[tshering]

Originally Posted by trekk

Thank you, tshering! Personally I would be interested in both - the power-off screen and the log file.

I uploaded the new archive to post #366.