Quote:
Originally Posted by ebrahimpak
When Nickel cannot boot, it shows two bars (two square shaped elements of the status bar) and immediately returns to KSM. I have to OPEN NICKEL FROM FMON.SH and in the next run, I can simply tap Start Nickel in the KSM and even do the switching from within Nickel. It is only the second time (after nofmon.sh) that I can use Nickel and the PNGs within it.
|
I understand now what you mean by "two bars."
Quote:
Originally Posted by ebrahimpak
1- What do you mean by; the PNGs are not fully processed? As I can see them both on the drive and in the right place in the home page on each startup.
|
When you launch nickel by "start nickel," KSM starts the program "fmon" before it starts nickel. This program "fmon" watches whether the KSM png files are opened. If one of these png files are opened, fmon calls a script that is associated with the png file. For instance, the script associated with exit_nickel.png kills nickel (this is how you can return from nickel to KSM). Another script that kills nickel is associated with switchtokoreader.png. Sometimes nickel opens certain files by itself in order to create one or several thumbnails (or to analyse its content in order to make some entries in the database). In the case of the KSM png files, opening them triggers the execution of certain scripts, when fmon is running at the this time. Therefore it is important that nickel creates all thumbnails of the KSM png files while fmon is not running. In order to start nickel without having fmon running in the background one can use "start nickel no fmon.sh."
What is happening on your device is this: You start nickel by selecting "start nickel" (this does also start fmon). nickel tries to open exit_nickel.png or switchtokoreader.png in order to create a thumbnail of it. As soon as nickel opens this file, fmon calls the associated script, and the script kills nickel.