Kobo Start Menu 08

[tshering]

Originally Posted by kido.resuri

Anyway, there are actually 3 possible UpgradeTypes.
1 - Let's the user decide to update or skip it, and there is an option to view the release notes. If the user accepts the update, it will act as UpgradeRequired type.
2 - (UpgradeRequired) This type downloads and "prepares" the update (by unziping it), and lets the user decide to install it now or later. If the user selects later, then the update is done upon next boot. (KoboRoot.tgz sits in .kobo untill next restart.)
3 - (UpgradeForced) This type will download, prepare and install the update without asking the user. The install is done by a reboot, I guess the usual way, but without user interactions.

This sounds reasonable.

[tshering]

Originally Posted by nook_nerd

Hi,

Thanks for trying to explain.. Luckily, with my backups, was easy to re-setup..
The evening before the behaviour, I had downloaded a reserved book via Overdrive on the Kobo, so had turned on wifi to get it. I usually don't leave wifi on, but i did forget to turn it off after getting the book, then i fell asleep.

When i woke up next morning, it was in the registration menu..

I figure it must have gotten a push of the 4.2.8283 latest(even tho i had already installed it the day after release).. Is there any setting i can put in the conf files that would disable it from accepting the push update when wifi is on?

Thanks,
John Feole

Since I do not exactly understand how it could have happened that the FW update got installed, I do also not know how to prevent such a thing from happening.
Once the FW update is downloaded to the device, KSM is supposed to prevent it from getting installed. This seemed to have failed in your case.
Among GeoffR's patches, there is one (Block WiFi firmware upgrade) that prevents downloading the FW. If you want to apply this patch, read carefully the warning.

[davidfor]

Originally Posted by kido.resuri

I missed that thread(s) discussing affiliates, but maybe I'll do a search on it. I just tested for Beta and Kobo, so don't know the others.

Anyway, there are actually 3 possible UpgradeTypes.
1 - Let's the user decide to update or skip it, and there is an option to view the release notes. If the user accepts the update, it will act as UpgradeRequired type.
2 - (UpgradeRequired) This type downloads and "prepares" the update (by unziping it), and lets the user decide to install it now or later. If the user selects later, then the update is done upon next boot. (KoboRoot.tgz sits in .kobo untill next restart.)
3 - (UpgradeForced) This type will download, prepare and install the update without asking the user. The install is done by a reboot, I guess the usual way, but without user interactions.

I don't think Kobo use type 1 any more. I think they stopped using when they changed to the tiled home page. Type 2 is what they usually, and I don't think I have seen type 3. Except that that is what effectively is done if the update is found during the daily auto-sync.

So if KSM is set to handle the updates, then nickel's update shouldn't bypass this mechanism, even with forced upgrade.

I'm not sure what you mean by that. If KSM is handling the update, then nickel won't get a chance to do anything with them.

[tshering]

Originally Posted by davidfor

I'm not sure what you mean by that. If KSM is handling the update, then nickel won't get a chance to do anything with them.

The assumption is that in any kind of update (forced/required) the step of extracting the content of KoboRoot.tgz and copying files from the upgrade folder is done by the rcS. If this is the case, KSM can prevent this from happening without consent of the user. So nickel can download the update zip, extract KoboRoot.tgz and so on from it, can decide whether there is enough space to install it, but not more. My question is whether the assumption holds.

[davidfor]

Originally Posted by tshering

The assumption is that in any kind of update (forced/required) the step of extracting the content of KoboRoot.tgz and copying files from the upgrade folder is done by the rcS. If this is the case, KSM can prevent this from happening without consent of the user. So nickel can download the update zip, extract KoboRoot.tgz and so on from it, can decide whether there is enough space to install it, but not more. My question is whether the assumption holds.

I'm pretty sure nothing has changed with handling of KoboRoot.tgz. I have only noticed one possible change in the way the beta's I've been getting have been installed. The change is that two or three times, the device has started the install without prompting. This might be the "UpgradeForced", but the other devices did prompt. And, each time, the device went to sleep during the download. I have a feeling that waking triggered the install, but I haven't done the experiments to prove it.

[tshering]

Originally Posted by davidfor

I'm pretty sure nothing has changed with handling of KoboRoot.tgz.

I hope you are right.

[sk2003]

KSM 8 is amazing, and so is koreader but... KSM 8 seems to become inaccessible when Wifi is enabled on nickel. In that, if Wifi is enabled and I switch to KSM and back again, the kbmenupngs just become normal png files. I can't use them to enter KSM, only view them.

What I did: I switched to KSM using exit_nickel while Wifi was enabled, and I got the "turn Wifi off message" when I went to boot back into nickel. I chose yes. When I went back into nickel, the Wifi icon disappeared, but reappeared after I did a restart.

And when I went to my Library to enter KSM again, the icon went back to being a .png! I had to reflash the root zip. This happens every time I go into KSM while Wifi is enabled.

I'm on 13.19.5761 on a Kobo Aura H2O. Is this normal behaviour? Is it not possible to use KSM while Wifi is running in nickel? Will downgrading to an older firmware fix this?

[tshering]

Originally Posted by sk2003

KSM 8 is amazing, and so is koreader but... KSM 8 seems to become inaccessible when Wifi is enabled on nickel. In that, if Wifi is enabled and I switch to KSM and back again, the kbmenupngs just become normal png files. I can't use them to enter KSM, only view them.

What I did: I switched to KSM using exit_nickel while Wifi was enabled, and I got the "turn Wifi off message" when I went to boot back into nickel. I chose yes. When I went back into nickel, the Wifi icon disappeared, but reappeared after I did a restart.

And when I went to my Library to enter KSM again, the icon went back to being a .png! I had to reflash the root zip. This happens every time I go into KSM while Wifi is enabled.

I'm on 13.19.5761 on a Kobo Aura H2O. Is this normal behaviour? Is it not possible to use KSM while Wifi is running in nickel? Will downgrading to an older firmware fix this?

Maybe there is something that is not related to wifi at all. Did you do the following?

1. select "tools" > "activate" > "set runmenu settings.msh" > "always"

See the first post of this thread. If you did not do this the device boots every second time directly into nickel, and than the pngs do not have any specific function.
If we can exclude this possibility we can look for other causes.

[sk2003]

Originally Posted by tshering

Maybe there is something that is not related to wifi at all. Did you do the following?

1. select "tools" > "activate" > "set runmenu settings.msh" > "always"

See the first post of this thread. If you did not do this the device boots every second time directly into nickel, and than the pngs do not have any specific function.
If we can exclude this possibility we can look for other causes.

Alright, I will try that, thanks! I just got my Kobo yesterday and I've never owned an e-reader, so I'm extremely new to this. In any case, I'm planning to keep Wifi off from now on because I don't use it, so it's not a huge deal to me. KSM and Koreader are great! No stupid "connect to computer?" message with KSM, I can just directly connect.

EDIT: just tried it out, and your solution works! But I wish I could get rid of the "Wifi is enabled!" message. Is there any way to do so? Also, it keeps asking me if I want to switch Wifi off when I go into nickel. Is it possible to disable that message as well? I always choose no.

Thanks!

[tshering]

Originally Posted by sk2003

EDIT: just tried it out, and your solution works!

Iam glad it was that simple!

Originally Posted by sk2003

But I wish I could get rid of the "Wifi is enabled!" message. Is there any way to do so?

The reason is to prevent battery train when somebody forgets to switch wifi off, especially since KSM does not have a sleep function. Therefore, there is no option provided to switch this message off. But since large parts of KSM consist of sh scripts, one can customize a lot oneself. The concerned file is /adds/kbmenu/onstart/start_nickel.sh.

Originally Posted by sk2003

Is there any way to do so? Also, it keeps asking me if I want to switch Wifi off when I go into nickel. Is it possible to disable that message as well? I always choose no.

The original reason was that nickel did not check on start whether wifi is on. Therefore, it was not possible to switch off the already runnig wifi in nickel, and nickel could also not use it (since there occurred an error when it tried to stat wifi that was already on). But now there is another reason to switch wifi off before entering nickel. Since one of the more recent updates nickel freezes when it is started and wifi is already on. So for these newer FWs it would be reasonable to switch wifi off automatically, without asking the user.

[sk2003]

Originally Posted by tshering

Iam glad it was that simple!
The reason is to prevent battery train when somebody forgets to switch wifi off, especially since KSM does not have a sleep function. Therefore, there is no option provided to switch this message off. But since large parts of KSM consist of sh scripts, one can customize a lot oneself. The concerned file is /adds/kbmenu/onstart/start_nickel.sh.
The original reason was that nickel did not check on start whether wifi is on. Therefore, it was not possible to switch off the already runnig wifi in nickel, and nickel could also not use it (since there occurred an error when it tried to stat wifi that was already on). But now there is another reason to switch wifi off before entering nickel. Since one of the more recent updates nickel freezes when it is started and wifi is already on. So for these newer FWs it would be reasonable to switch wifi off automatically, without asking the user.

Thanks for the explanations. Sadly, I'm not able to find start_nickel.sh anywhere in kbmenu_user, or anywhere else on the device. I did find ksm_ini_options.txt, nickel_conf_options.txt and nightmode_conf_options.txt in confoptions, but none of them have any entries that let you disable the Wifi message.

Are you saying I have to create a script called start_nickel.sh with code to prevent the Wifi message from coming up? Sure wish I could code right now.

[tshering]

Originally Posted by sk2003

Thanks for the explanations. Sadly, I'm not able to find start_nickel.sh anywhere in kbmenu_user, or anywhere else on the device. I did find ksm_ini_options.txt, nickel_conf_options.txt and nightmode_conf_options.txt in confoptions, but none of them have any entries that let you disable the Wifi message.

Are you saying I have to create a script called start_nickel.sh with code to prevent the Wifi message from coming up? Sure wish I could code right now.

Sorry, I forgot to mention. This part of KSM is on the system partition (not on the user partition).
There are several possibilities to get a file onto the system partition, one is to use the update mechanism with KoboRoot.tgz. In order to copy files from and to the system partition you can use dropbear (if you install PBChess, KSM's usbNet makes use of PBChess' .) Another way is described here.

[whoops]

EDIT: NM, looks like I was able to delete the breaking change by going to "Handle Update" within KSM. Thanks!!

Hi, after installing KSM08, I was going to load the KoboRoot.tgz for the Kobo Aura One KSM update, but I accidentally loaded the KoboRoot.tgz from koreader.

This seems to have deleted everything in /mnt/onboard (ls -la /mnt/onboard via ksm terminal shows nothing). Most of the scripts for KSM that run off /mnt/onboard/.adds fail obviously and nickel won't load. Can't get USB or USBNet working.

Am I screwed or is there a way to recover from this without having to rip open the Kobo?

[tshering]

Originally Posted by whoops

EDIT: NM, looks like I was able to delete the breaking change by going to "Handle Update" within KSM. Thanks!!

Hi, after installing KSM08, I was going to load the KoboRoot.tgz for the Kobo Aura One KSM update, but I accidentally loaded the KoboRoot.tgz from koreader.

This seems to have deleted everything in /mnt/onboard (ls -la /mnt/onboard via ksm terminal shows nothing). Most of the scripts for KSM that run off /mnt/onboard/.adds fail obviously and nickel won't load. Can't get USB or USBNet working.

Am I screwed or is there a way to recover from this without having to rip open the Kobo?

Hi whoops,
This must have been a terrifying experience. I am glad it finally went well. Several things were happening. I try to give some explanations:
1) When KSM detects an update file (KoboRoot.tgz) it adds a new entry to the main menu "handle update".
2) When there is an update file in .kobo and you try to start nickel from KSM, KSM refuses to start nickel and asks the user to handle the update first. When nickel is started (without KSM) and it detects an update, it reboots the reader (this is part of nickel's normal update process).
3) The basic KSM 8 is not able to handle usb and wifi on Kobo Aura One. The KSM update for Aura one was provided to fix this. If KSM (without the update) tries to enable usb, it prepares this by unmounting /mnt/onboard, and loading two modules, but failes to load one of the modules on Aura One. Unfortunately, there is no error handling and /mnt/onboard remains unmounted, and the one module that was loaded remains loaded. The result in your case was that you did not see /mnt/onboard, and that you could not enable usbNet.

I hope you enjoy your KA1 and KSM nevertheless.

[tshering]

FYI, I just installed the full 4.2.8432 update package on a Kobo C. Everything went well, that means no problem with KSM, Koreader, nickel.
Edit: Did the same with the (simple/old model) Glo. Same result