Kobo Start Menu 08

[Ken Maltby]

Kobo is supposed to be issuing (or have issued) a firmware update for the KA1 that addresses a power/battery problem, it might help tshering to know which firmware is in effect as you note the data being reported in the KSM charging tools.

Luck;
Ken

[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.

I was thinking a bit on this.

As I understand, there is no problem with synchronizing hardware with system clock. It can be done whenever and how many times we want.

It looks to me that best solution would be to synchronize hardware clock with system clock as soon as we set system clock (just in case anything goes wrong later) and additionally to synchronize it also when we power off device, to maximize long term clock accuracy.

In this way we get best from both options. And it shouldn't be a problem, as we can synchronize hardware clock whenever we want.

[tshering]

Originally Posted by hkckoo

I do have additional KSM question. when I was charhing my kobo h2O, thvoltage value vas always the same, "5000000", now whenever I am charging my KA1, the voltage varies between "3550000" to "3800000", though I guess this is because there is a different battery inside?

Maybe somebody who knows more than me about these things can explain how we should understand the variation that the KA1 shows opposite to the constancy of the older devices.

[tshering]

Originally Posted by Alan_S

I was thinking a bit on this.

As I understand, there is no problem with synchronizing hardware with system clock. It can be done whenever and how many times we want.

It looks to me that best solution would be to synchronize hardware clock with system clock as soon as we set system clock (just in case anything goes wrong later) and additionally to synchronize it also when we power off device, to maximize long term clock accuracy.

In this way we get best from both options. And it shouldn't be a problem, as we can synchronize hardware clock whenever we want.

I personally do not see a need of a greater accuracy of time keeping as we already have. Another point is, that I would like to keep away from changing to many things outside of KSM. And since there are ways to power off without KSM being informed, we would have to handle this on a more central place. That makes it a non-KSM issue.

[davidfor]

Originally Posted by hkckoo

I do have additional KSM question. when I was charhing my kobo h2O, thvoltage value vas always the same, "5000000", now whenever I am charging my KA1, the voltage varies between "3550000" to "3800000", though I guess this is because there is a different battery inside?

The "5000000" is probably 5V and looks like the input voltage. But "3550000" to "3800000" are probably 3.55V and 3.8V and look like the actual battery level. My guess is that the voltage is being measured in different places on the devices. But, that range seems to small. My memory says the fully charged voltage should be higher. It will depend on the exact battery and maybe Kobo have decided to sacrifice a bit of runtime for longer overall life.

[Alan_S]

Originally Posted by tshering

I personally do not see a need of a greater accuracy of time keeping as we already have. Another point is, that I would like to keep away from changing to many things outside of KSM. And since there are ways to power off without KSM being informed, we would have to handle this on a more central place. That makes it a non-KSM issue.

Actually, I completely agree with you that this isn't KSM issue.

But, I'm referring on your question if we should handle synchronizing hardware clock at powering off versus immediately.

In my opinion, from KSM's perspective, the best course is to immediately synchronize it with system clock, as soon as we set clock (as it is now done by settime.sh script). And maybe, add some additional code in KSM's poweroff script, just in case, if you want to do this, or think there is need to do this.

What other scripts do is outside KSM's scope. And clock would be as accurate as possible, through KSM or some other software.

[hkckoo]

Originally Posted by Ken Maltby

Kobo is supposed to be issuing (or have issued) a firmware update for the KA1 that addresses a power/battery problem, it might help tshering to know which firmware is in effect as you note the data being reported in the KSM charging tools.

Luck;
Ken

the firmware I am using is 4.0.7523

[hkckoo]

I want to ask a question about charging my device. when I charge via KSM and it says 100% battery and below that "not charging", at that point no juice is going into the battery/device? if so, how does this compare to nickel? once its at 100% there, the charging also stops? why does it then say that I have to charge my device for 4 hours before first use? I read it somewhere on the box or kobo website. the device was at 100% battery after 2 hours.

[tshering]

Originally Posted by hkckoo

I want to ask a question about charging my device. when I charge via KSM and it says 100% battery and below that "not charging", at that point no juice is going into the battery/device? if so, how does this compare to nickel? once its at 100% there, the charging also stops?

This is true. There is no difference. KSM and nickel are not actively involved in the charging process, both are only watching and passing on the information they have.

[hkckoo]

Hello again, is it possible for KSM to display on power off on screen the cover of last thing I read in koreader? the same thing nickel displays the cover as screensaver on power off. I never put my e-reader to sleep. when I finish reading, I just turn it off via KSM. when I power it back on, it goes straight to koreader (I dont even see the menu) and opens last file

[tshering]

Originally Posted by hkckoo

Hello again, is it possible for KSM to display on power off on screen the cover of last thing I read in koreader? the same thing nickel displays the cover as screensaver on power off. I never put my e-reader to sleep. when I finish reading, I just turn it off via KSM. when I power it back on, it goes straight to koreader (I dont even see the menu) and opens last file

If Koreader provides the cover as a file in png or jpeg format, and if the path to the file is easily available, then it is possible for KSM to display it on power off. If KSM needs to extract the cover image from the book, or create it itself, than is to much work for the moment.

[MicaOlaAdams]

Hi everybody,

I have set "tools" > "activate" > "set runmenu settings.msh" > "always"
nonetheless my KA1 boots quite often from power off into nickel. Any ideas what might be causing this?

[tshering]

Originally Posted by MicaOlaAdams

Hi everybody,

I have set "tools" > "activate" > "set runmenu settings.msh" > "always"
nonetheless my KA1 boots quite often from power off into nickel. Any ideas what might be causing this?

Does nickel start immediately, or only after 20 seconds or so? If it starts immediately, then there is something wrong. If it starts after some time, it is by design.

[MicaOlaAdams]

Originally Posted by tshering

Does nickel start immediately, or only after 20 seconds or so? If it starts immediately, then there is something wrong. If it starts after some time, it is by design.

So, if I boot the KA1 from power off into KSM8 and don't do anything, it will reboot into nickel after 20sec, right?

[tshering]

Originally Posted by MicaOlaAdams

So, if I boot the KA1 from power off into KSM8 and don't do anything, it will reboot into nickel after 20sec, right?

If you power the device on and you do not select anything, KSM will start nickel after about 20 seconds. There is however no rebooting involved at that point.