Kobo Start Menu 07

[snazzyapeman]

Hi, I was wondering what's the procedure when new firmware comes out? I have ksm 7 and koreader working with some slight tweaks here and there.

Do I need to uninstall to try the new firmware? Can I save my settings if I must uninstall? Do these fine and needed mods even work with new firmware.... ? And so on. Thanks and sorry for the noobness.

--Snazzy

(On Glo HD)

[tshering]

Originally Posted by snazzyapeman

Hi, I was wondering what's the procedure when new firmware comes out? I have ksm 7 and koreader working with some slight tweaks here and there.

Do I need to uninstall to try the new firmware?

There is no need to uninstall. Usually, the process is rather painless. See the post how to install kobo update packages.

Originally Posted by snazzyapeman

Can I save my settings if I must uninstall?

Even without having to unistall, you might want to save settings and maybe some other files. There is always a chance that something goes wrong and you have to factory reset your device. What exactly you will want to save depends on what changes you did to KSM.
I guess many people only changed the settings available via "configure". In order to preserve them, save the file .adds\kbmenu\ksm_ini. If you added some configuration options (if you did, you will certainly know), save the folder .adds\kbmenu\confoptions\.

Other folders that you likely might want to save depending on your usage are:
.adds\kbmenu\backup\ (if you are using the backup function [currently not recommended on Glo HD])
.adds\kbmenu\Qt\fonts\ (if you added fonts here)
.adds\kbmenu\mynotes\ (if you out any files there)
.adds\kbmenu\fmonsh\ (if you added or modified script files there)

If you added pngs for usage with fmon, you might want to save kbmenupngs\.

As for Koreader, I do not much of personalization. Actually, the only thing I change is "show hidden files". Therefore I do not make any back ups. If I were to make a back up, I simply copied the whole koreader folder.

Originally Posted by snazzyapeman

Do these fine and needed mods even work with new firmware.... ? And so on.

Koreader and KSM usually work with new firmwares, the problem is rather new hardware.

[snazzyapeman]

Thanks tshering! Very helpful.

[kelemi]

Hi, I'm on KSM 07 and kobo 3.15.0. How do I uninstall KSM? The lastest version folder in `KBStartMenu_07_uninstall.zip` is 3.13.1.

[Ken Maltby]

Originally Posted by kelemi

Hi, I'm on KSM 07 and kobo 3.15.0. How do I uninstall KSM? The lastest version folder in `KBStartMenu_07_uninstall.zip` is 3.13.1.

You can use the 3.13.1 for 3.13.1 thru 3.16, see this post

Luck;
Ken

[roger64]

Hi

I just read that recent versions of KSM can start wifi so I decided to upgrade KSM. I have a Kobo Glo running 2.8.1 and the latest Koreader.

My current version of KSM is from 2014.04.23 and I cannot see any menu with "handle updates". It just can enable front light, usb, has some scripts but none related to updates, sleep, reboot and power off and of course can start nickel and koreader.

Would it be better to totally uninstall KSM?

[tshering]

Originally Posted by roger64

I cannot see any menu with "handle updates".

The menu item "handle update" appears only after you copy KoboRoot.tgz to .kobo.
If you follow the instructions in post #1, take especially care on point 4: select in KSM "handle updates" > "install update" (do NOT select "install partial update")

[roger64]

Thanks for your information. I'll update.

EDIT: Success. Everything works as expected.

[tshering]

Originally Posted by roger64

Success. Everything works as expected.

I am glad that everything went smooth.

[embryo]

@tshering (or anybody who knows bash scripting...)

I was thinking about the preventfreeze.sh I use for my Glo, and a timer I used in an old PDA of mine, to calculate my reading time and how long the battery lasted.

The idea was simple.
Start a timer app and then start the reader app.
When not reading, closing the PDA (a standby mode perhaps) made the timer stop.
Re-opening the device and the timer continues.
That way, I knew the battery consumption (more or less)

With the kobo script now.
I don't know anything about bash scripting, thats why I need some help.
As I understand it, it starts; it waits 1 (second?); and finishes.
I made it to wait 5, and it also didn't freeze.

If a script was made to add 5 seconds to a 0:00:00:00 (d:h:m:s) number in a text(?) file every 5 seconds, then the timer would be almost ready.
The only extra thing it would need is an other script that shows the 0:00:00:00 number and maybe has a way to reset it.

Of course this will count the reading time only if you shut down the reader when not reading (which is what I do, since the koreader sleep mode is not that reliable as the battery is concerned).

Is this possible?
TIA

[tshering]

embryo,

From the description of your needs, it seems to me that it would suffice to log the time of powering on and the time of powering off, and maybe the battery charge level at that two points. This of course will not give you any information which applications were running and for how long they were running.

[embryo]

Originally Posted by tshering

From the description of your needs, it seems to me that it would suffice to log the time of powering on and the time of powering off, and maybe the battery charge level at that two points.

Thats true.
I was thinking a different approach just because preventfreeze.sh was already running all the time.
And we could see the values during the time the device is running.

This of course will not give you any information which applications were running and for how long they were running.

Yes, but for me its not important, since I usually use just a reader app.
The stats of the background processes maybe are needed for debugging but not for just reading...

[tshering]

I am not sure whether this is helpful but you can try.
In .adds\kbmenu\log\uptime.txt you will find something like

powering off at: 2015:07:027_12:53:47, after 0:00:03:53 uptime

The log file is only written when you power off the device, not when you only reboot it. If you want the log file to accumulate the information, instead of containing only the most recent, replace in .adds\kbmenu\onstart\poweroff.sh

... > $uptimelog

by

... >> $uptimelog

If you want to read the log file from KSM, select:
scripts > browse > browse kbmenu.msh > log > uptime.txt

If you want to see the current uptime, select:
scripts > tests > returntests.msh > show uptime.sh

[embryo]

Originally Posted by tshering

I am not sure whether this is helpful but you can try.

Well, Thank you!
It is helpful.
I get all the info I asked for.

If you want to read the log file from KSM, select:
scripts > browse > browse kbmenu.msh > log > uptime.txt

An extra request:
How can we write to the uptime .txt something like
power off at: 2015:07:27_18:33:13, after 0:00:18:39 uptime (0:00:18:39 total, Battery 92%)
power off at: 2015:07:27_18:45:19, after 0:00:11:03 uptime (0:00:29:42 total, Battery 91%)

If you want to see the current uptime, select:
scripts > tests > returntests.msh > show uptime.sh

... and an other one:
How can we see here something like
uptime: 0:00:14:32 (total 0:02:42:56)
idle: 0:00:13:32 (total 0:02:24:31)
battery: 68%

The totals should come out off all the values of the uptime.txt.
For a reset we just need to delete it.

Thanks for your time.

Edit: Maybe it would be more convenient to write the last entry on top, so we can avoid scrolling ....

[kleinenun]

hi @tshering, are there any disadvantages if I keep the USB enabled. Just about the battery or any other else? Thanks. (3.16.0 Glo HD)