Kobo Start Menu 08

[ebrahimpak]

When Nickel (at its bad turn) trys to startup, two bars of status bar are shown and then it returns to KSM. What can cause that?

[tshering]

Originally Posted by ebrahimpak

So strange, because mine is a fresh install! All of them! The problem is that I can now only access Nickel after starting Nickel through "..nofmon.sh".

That indicates that there is a problem with the KSM pngs being not fully processed by nickel.

Originally Posted by ebrahimpak

After booting through nofmon, I have to power it off, and the upon the next startup, the Nickel strangely opens

Does it immediately after you power the device on? Or can you see the KSM home screen for a while?
Did you this: select "tools" > "activate" > "set runmenu settings.msh" > "always"?

Originally Posted by ebrahimpak

and even the switchtoKoreader.png works fine. But it only happens every other time!

You mean switchtoKoreaer.png works when nickel is started automatically? Are you reporting only from your memory? Or did you put down some notes while you were testing?

Edit: I saw your post 691 only now. What do you mean by "two bars of status bar"?

[ebrahimpak]

Originally Posted by tshering

That indicates that there is a problem with the KSM pngs being not fully processed by nickel.


Does it immediately after you power the device on? Or can you see the KSM home screen for a while?
Did you this: select "tools" > "activate" > "set runmenu settings.msh" > "always"?

You mean switchtoKoreaer.png works when nickel is started automatically? Are you reporting only from your memory? Or did you put down some notes while you were testing?

Thanks for such a prompt reply.

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.

2- I have already set it to "always", and I can always see KSM, when the Nickel works as well as its nonworking situation. Nickel starts successfully only after 1 time nofmon.sh startup. And yes, the PNG works on its good turn! while when I return from Nickel to KSM, or poweroff the device, then Nickel won't work unless with fmon.sh.

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

[trekk]

@tshering: always a pleasure.

@ebrahimpak: I truly have no idea, what could be the reason for the behaviour of your device. I suggest one experiment. I will PM you a Dropbox link. Find and download the folder kbmenu_user.

On your KA1 backup the files in the hidden folder .adds . If anything goes wrong, you can just copy them back. Next delete the folder kbmenu_user inside .adds on your KA1 and replace it with the folder from the Dropbox.

Disconnect the KA1 from the PC and reboot your device. Did anything change or is your KA1 still misbehaving?

[tshering]

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

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.

[ebrahimpak]

Originally Posted by tshering

I understand now what you mean by "two bars."

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.

Thanks for all the details. But is there a prescription?

[ebrahimpak]

Originally Posted by tshering

I understand now what you mean by "two bars."

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.

I hope you can find a solution for me.

[ebrahimpak]

Originally Posted by trekk

@tshering: always a pleasure.

@ebrahimpak: I truly have no idea, what could be the reason for the behaviour of your device. I suggest one experiment. I will PM you a Dropbox link. Find and download the folder kbmenu_user.

On your KA1 backup the files in the hidden folder .adds . If anything goes wrong, you can just copy them back. Next delete the folder kbmenu_user inside .adds on your KA1 and replace it with the folder from the Dropbox.

Disconnect the KA1 from the PC and reboot your device. Did anything change or is your KA1 still misbehaving?

Thank you very much, but it didn't change anything.

[tshering]

Originally Posted by ebrahimpak

I hope you can find a solution for me.

Can you check whether you have in the folder .kobo-images\135\255\ the files

file____mnt_onboard_kbmenupngs_exit_nickel_png - N3_FULL.parsed
file____mnt_onboard_kbmenupngs_exit_nickel_png - N3_LIBRARY_FULL.parsed
file____mnt_onboard_kbmenupngs_exit_nickel_png - N3_LIBRARY_GRID.parsed

and in the folder .kobo-images\135\148\ the files

file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_FULL.parsed
file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_LIBRARY_GRID.parsed

?

[trekk]

Originally Posted by ebrahimpak

Thank you very much, but it didn't change anything.

You are welcome. As I have fiddled with some of the files, the solution might have been in there.

Now it's time for a more sophisticated try from tshering Hope you will find a solution.

[ebrahimpak]

Originally Posted by tshering

Can you check whether you have in the folder .kobo-images\135\255\ the files

file____mnt_onboard_kbmenupngs_exit_nickel_png - N3_FULL.parsed
file____mnt_onboard_kbmenupngs_exit_nickel_png - N3_LIBRARY_FULL.parsed
file____mnt_onboard_kbmenupngs_exit_nickel_png - N3_LIBRARY_GRID.parsed

and in the folder .kobo-images\135\148\ the files

file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_FULL.parsed
file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_LIBRARY_GRID.parsed

?

Hi. Thank you very much for your time , and excuse me for my late reply. I had left the ereader at home.
I just checked the .kobo-images\135\255\, and all the 3 files were there.

Regarding the .kobo-images\135\148\, there are 3 files in the folder (you had mentioned only 2 files):

file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_FULL.parsed
file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_LIBRARY_FULL.parsed
file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_LIBRARY_GRID.parsed

Please let me know if this is normal.

Best,
Abe

[ebrahimpak]

Originally Posted by trekk

You are welcome. As I have fiddled with some of the files, the solution might have been in there.

Now it's time for a more sophisticated try from tshering Hope you will find a solution.

I really appreciate your kindness. Hope to solve it soon.

[ebrahimpak]

@tshering: I have just removed (and backed up) the extra file in the .kobo-images\135\148, namely:

file____mnt_onboard_kbmenupngs_switchtokoreader_png - N3_LIBRARY_FULL.parsed

It seems even removing the extra file did not help.

[ebrahimpak]

The only way to access nickel was to somehow keep the pngs away from the nickel's homepage.