Kobo Start Menu 08

[tshering]

Originally Posted by Alan_S

How should I run this script (let's call it settime)?

./settime 20:44:21

This from terminal? Where should I put script in that case (what directory)?

I put this and another script into a package. You can install it by copying the contained KoboRoot.tgz to .kobo. Then select "handle update > install update."

Now you have to options:
1) manual input

• in KBTerminal write "settime.sh 20:45:00" (without the quotes) and press enter

2) with ntpd

• enable wifi
• select (in the same wifi menu) "x ntpd set time.sh"
• wait until you see a response (might need 20 secs or so)

Edit: In version 02, I improved the script for option 2. Asking the time server is now about 8 seconds quicker than in the old script. The script has still to wait 10 seconds before the hardware clock can be synchronised. Usually one would not synchronise the hardware clock at this point, but at the time of powering off. Maybe we should consider doing this.

[Alan_S]

Thank you!

Tested it, it works great (didn't tested wifi), hardware clock gets set along system one.

Something like this probably should be a part of KSM installation, for future versions and updates. I think that there's also some people that don't know about hardware clock, how to set it and it would be useful for them.

[tshering]

@Alan_S
I am glad it works for you.

I updated the settime.zip two posts above.

[tshering]

I guess KSM 8 (with this patch) works on KA1. If this is the case it would be meaningful to upload a new KSM 8 package that contains the KA1 specific modifications. My question is therefore: Are there a number of people who use KSM on KA1 without problems?

[trekk]

Hi tshering,

KSM8 with patch v2 for the KA1 (FW 4.0.753) works great - except that I am not able to connect to PC via USB.

[tshering]

Originally Posted by trekk

Hi tshering,

KSM8 with patch v2 for the KA1 (FW 4.0.753) works great - except that I am not able to connect to PC via USB.

Thank you for the information. I was not sure whether usb is working because of this post. But now it is clear.

Unfortunately, I have no idea how to fix this. When you select "usb enable.sh," does KSM report that USB support is enabled, and it does however actually not work. Or doesn't KSM report this?

[trekk]

Originally Posted by tshering

... When you select "usb enable.sh," does KSM report that USB support is enabled, and it does however actually not work. Or doesn't KSM report this?

The screen just refreshes once and it still shows USB support: disabled.

[tshering]

Originally Posted by trekk

The screen just refreshes once and it still shows USB support: disabled.

This seems to indicate that g_file_storage.ko for some reason does not get loaded.

I guess after that you have to reboot the device in order to get the full main menu back, or how do you continue?

[trekk]

Originally Posted by tshering

I guess after that you have to reboot the device in order to get the full main menu back, or how do you continue?

Yes, I had to reboot to get back a fully populated menu.

[tshering]

@Trekk

Could you or some other KA1 owner with KSM+patch v2 please test the uploaded package?
Installation and test:

• extract KoboRoot.tgz from the archive, copy it to .kobo, safely eject and disconnect the device.
• in KSM select "handle update" > "install update"
• wait until the device has rebooted
• select usb > "usb enable test.sh"

If it works, that would be great.
If it does not work, it becomes a little laborious (might be easier, if you have already some experience with KBTerminal), please

• reboot your device
• select "tools" > "start kbterminal.sh"
• enter "sh -x /adds/kbmenu/scripts_intern/usb/usb_enable_test.sh" (without quotes), and press "Enter"
• some seconds later you should see an output. Have a look somewhere close to the end of the output, there should be some error message. (press at the bottom to zoom out, at the left and right border to page forward and backward).
• you can save the output for later reference: "history" > "kbt:save"; then "keyboard" > "Enter"
• exit KBTerminal by selecting "exit" on the keyboard

[tshering]

Changed behaviour of nickel under FW 4.0.7523. Previously, it was possible to establish a Wifi connection, for instance with KSM, and then launch nickel. As long as nickel did not try itself to enable Wifi, it was not aware of the fact that there was already a wifi connection. This was convenient for certain purposes.

With FW 4.0.7523, if one launches nickel with wifi already enabled, nickel freezes.

If one starts nickel with (KSM) "start nickel", and wifi is enabled, there is a warning and the option to turn wifi off. However, if one changes from koreader to nickel in a (KSM) nickle-koreader-loop or koreader-nickel-loop, there is currently only a warning, if wifi is enabled, but no option to turn it off. Therefore, one has to be careful to turn wifi off before one exits koreader in order to switch directly to nickel.

[Alan_S]

Originally Posted by tshering

Edit: In version 02, I improved the script for option 2. Asking the time server is now about 8 seconds quicker than in the old script. The script has still to wait 10 seconds before the hardware clock can be synchronised. Usually one would not synchronise the hardware clock at this point, but at the time of powering off. Maybe we should consider doing this.

Why we wouldn't synchronize hardware clock immediately?

When I set time, it is correct time. It should be reflected with hardware clock also. I had problems with clock being late 3 minutes, I first noticed this after crash. This can also happen to other people, having crash, need to forcefully reset device or something similar.

In such case clock wouldn't be synchronized and therefore not correct.

From my point of view, I want clock as soon as possible to run correctly.

[tshering]

Originally Posted by Alan_S

Why we wouldn't synchronize hardware clock immediately?

When I set time, it is correct time. It should be reflected with hardware clock also. I had problems with clock being late 3 minutes, I first noticed this after crash. This can also happen to other people, having crash, need to forcefully reset device or something similar.

In such case clock wouldn't be synchronized and therefore not correct.

From my point of view, I want clock as soon as possible to run correctly.

Usually it is said that hardware clocks in general (not specifically that of Kobo devices) are not as accurate as the software clock is, and that the inaccuracy of the hardware clock is constant. So the idea is that you once set the software clock and relay on it as long as the device is on. If you power off you synchronize the hardware clock, so that the hardware clock has the most accurate time available at the system, and you save that point of time to a file. When powering on you look how much time according to the hardware clock has past since powering off. Since you know the ratio of inaccuracy you can calculate the correct time and write it to the software clock. I do not know how such things are actually implemented. Anyway, that is why I mentioned that usually the hardware clock is synchronised at power off. At least this is my understanding. My point was that we could save 10 seconds, when setting the time, if we postpone the synchronization of the hardware clock to some later point. Practically, the 10 seconds would not be a problem for me. The last time I set the clock on one of my Kobos (apart from yesterday or day before) was possibly in 2014, when I bought my last one (or maybe the clock was already set correctly, when I bought the device. I not sure).

[trekk]

Originally Posted by tshering

@Trekk
Could you or some other KA1 owner with KSM+patch v2 please test the uploaded package?[/LIST]

Tested and approved! I was able to establish a USB-Connection after installing the files from usb_test.zip.

[tshering]

Originally Posted by trekk

Tested and approved! I was able to establish a USB-Connection after installing the files from usb_test.zip.

Thank you for testing and especially for the approval!