View Single Post
Old 01-25-2017, 04:07 AM   #414
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by davidfor View Post
Looking at nook_nerd post, I think nickel downloaded the update as part of a sync and prompted to do the install. nook_nerd said no. Then at some time powered off. The firmware was then installed during the power-on.
KSM prevents that the relevant code of rcS is executed and asks the user for permission to apply the update, to do nothing or to remove the update files. Therefore, there should not have happened an automatic FW update at this point.
Quote:
Originally Posted by davidfor View Post
This will also happen if you connect and disconnect to a PC.
If am not mistaken nickel reboots the device when it detects the update files and starting from this point the same process as above happens.
Quote:
Originally Posted by davidfor View Post
I have seen firmware installed after a sync without a prompt when a sleep was involved. For some reason, the download to my Glo is very slow. It has gone to sleep while doing it and I woke it and download finished. Then it just did the install. This has only happened two or three times - just enough to know something is going on, but not enough to be completely sure of the pattern.
Generally, I think after downloading the firmware archive, nickel used to extract KoboRoot.tgz and so on from the downloaded zip file and then rebooted the device. Since I did not do this for a long time, I am not sure whether things have changed. I could be possible that nickel itself extracts KoboRoot.tgz etc. and only then reboots, instead of simply rebooting and letting rcS do the work. If this is the case KSM would be bypassed. (I know, my thoughts are not specifically related to nickel going to sleep while downloading, but rather with FW update via wifi in general.)

Quote:
Originally Posted by davidfor View Post
The other possibility here is if something was wrong. For example, if the database is corrupt, then a restart can take you through the setup. This will include downloading and installing firmware and the registration. There are probably other things that can trigger this, but the database is the one I know.
In the case of KSM, the restart that "can take you through the setup" would be the start of nickel by the KSM menu. According to nook_nerd's description ("When i rebooted later, it came up and automatically applied the kobo update, and asked me to reregister with Kobo, etc.") KSM seemed not be involved at all. But maybe nook_nerd skips some details in his description, and without these details it is difficult to know what really happened (or what one could have done in this situation).

Last edited by tshering; 01-25-2017 at 04:12 AM.
tshering is offline   Reply With Quote