Kobo Start Menu

[Markismus]

Originally Posted by tshering

I did not expect that anybody using the Start Menu would like to start Koreader from nickel. Anyway, how do you do this? I guess you call a script via fmon, the script kills nickel and starts koreader, and then you exit koreader at some point. This should work, I think. Still I wonder: if you don't want to go back to nickel, why don't you exit it and call koreader from the menu.

Thanks for the fast response. Indeed, I found the runsettings only after the post. The reason ---as most reasons go--- comes down to custom. I still enter koreader from Nickel even though it functions better from the Start Menu. I'll probably keep making this mistake for a few days.

I start koreader and Kobolaucher from Nickel with fmon/Kobolaucher.

Does it do this only in specific situations? For instance, only if you call nickel for the 25th time without a power circle, or something like that?

I don't know yet. I uninstalled and reinstalled Start Menu again and now I can start koreader and Kobolaucher both from Start Menu and Nickel and switch between the latter two. No crashes yet. I had an 0 byte file (settings.reader.lua) so it could also mean that it was an IO-error that hung the system. After reinstallation it didn't happen again.

I thought you wrote that Start Menu and fmon were exclusive?

[Markismus]

Is it correct that Start Menu only needs a new user to install Start Menu and copy the koreader-folder of the zipped release to /mnt/onboard/.kobo for koreader to work?

[tshering]

Originally Posted by Markismus

I thought you wrote that Start Menu and fmon were exclusive?

I am afraid I don't know what you are referring too.

It seems that there is a chance that you might use the Start Menu in some non-standard ways. Therefore, I would like to say this: If you really want to launch koreader from nickel and return directly to the Start Menu, make sure that you killall fmon and hindenburg before returning. (Normally exit_nickel.sh would take care of this, but not if you skip it.) If you don't kill them, the number of running instances of those two will increase each time you start nickel. Especially having several fmons with the same target pngs running might create problems.

[tshering]

Originally Posted by Markismus

Is it correct that Start Menu only needs a new user to install Start Menu and copy the koreader-folder of the zipped release to /mnt/onboard/.kobo for koreader to work?

This is correct. And the same holds for the Kobo Launcher.

[Ken Maltby]

I guess adding killall fmon and Hindenburg to the killall -STOP nickel already there, in koreader_kobo.sh, would cover the issue. Of course it might be better to killall nickel, while you are at it.

I have been thinking of doing another install guide "Adding alternative readers using Kobo Start Menu".

Luck;
Ken

[tshering]

Originally Posted by Ken Maltby

I guess adding killall fmon and Hindenburg to the killall -STOP nickel already there, in koreader_kobo.sh, would cover the issue. Of course it might be better to killall nickel, while you are at it.

Right, if there is really anybody who wants to start koreader from nickel, and then go direct to the Start Menu.

Originally Posted by Ken Maltby

I have been thinking of doing another install guide "Adding alternative readers using Kobo Start Menu".

Luck;
Ken

This would certainly be helpful.

[Markismus]

Originally Posted by Ken Maltby

I have been thinking of doing another install guide "Adding alternative readers using Kobo Start Menu".

While your at it, could you check whether the installation instructions for koreader are correct?

[Markismus]

With Start Menu running I somehow have lost USBnet via KoboLaucher: Connection is actively denied.
I can still turn on wifi in Nickel, start the webbrowser and FTP and telnet into the device via WiFi.

Any ideas why the connection is refused, how USBnet can be enabled and how it can be added to the USB menu? What would be ideal is a choice in Start Menu> USB between USB drives and USBnet!

Even more superb would be an extra option allowing WiFi to be turned on/off with a known IP address.

[Ken Maltby]

[QUOTE=Markismus;2841876]While your at it, could you check whether the installation instructions for koreader are correct?[/Q

I would change "Extract the koreader folder of the zip in the ".kobo" directory" to read: Extract the koreader folder of the zip into the ".kobo" directory
The same for the later instructions.

I added the guide to the Kobo Reader forum.

Luck;
Ken

[tshering]

Originally Posted by Markismus

With Start Menu running I somehow have lost USBnet via KoboLaucher: Connection is actively denied.
I can still turn on wifi in Nickel, start the webbrowser and FTP and telnet into the device via WiFi.
...
Any ideas why the connection is refused, how USBnet can be enabled and how it can be added to the USB menu? What would be ideal is a choice in Start Menu> USB between USB drives and USBnet!

I never tried the USBnet with or without the Kobo Start Menu. Frankly, I have no idea about it.

Originally Posted by Markismus

I can still ... telnet into the device via WiFi.

How are you doing this. I am using the hack by KevinShort and can only make it work by starting nickel via Options > Emergency Exit.

Originally Posted by Markismus

What would be ideal is a choice in Start Menu> USB between USB drives and USBnet!

Even more superb would be an extra option allowing WiFi to be turned on/off with a known IP address.

I don't know much about this stuff. But since almost the whole of the Kobo Start Menu consists of script files, everybody can contribute to it.

[tshering]

Not the best solution, but it works:

• extract the two script files from the archive and copy them to .kobo/kbmenu/scripts
• select "scripts" > "usbnet.sh"
• do what you want, e.g. open a telnet session
• select "reboot", or reboot or power off from telnet (You cannot return to the main menu!)

You must have one of the more recent pbchess packages (vlasovsoft) installed.
If you have an older version of the Kobo Touch remove in usbnet.sh the # from this line

#PLATFORM=freescale

I will include this script possibly into the usb menu in the next version of the Kobo Start Menu.

[Markismus]

Originally Posted by tshering

I never tried the USBnet with or without the Kobo Start Menu. Frankly, I have no idea about it. Does it also refuse to work if you start the KoboLauncher via nickel.

Yes

Originally Posted by tshering

If yes, does it also refuse to work if you start nickel by selecting Options > Emergency Exit from the menu bar of the application (note: you have to be on the first page/home of the menu, when doing this), and then start KoboLauncher from nickel?

Will try.

Originally Posted by tshering

How are you doing this. I am using the hack by KevinShort and can only make it work by starting nickel via Options > Emergency Exit.

I am using the same hack. Installation order was first telnet hack, then Kobolaucher, then Start Menu. I can use it via Nickel>browser connects to internet to get an IP address>telnet&FTP work

Originally Posted by tshering

I don't know much about this stuff. But since almost the whole of the Kobo Start Menu consists of script files, everybody can contribute to it.

I'll try to get the first USBnet scripts working on which KoboLauncher was based.

Originally Posted by tshering

Edit: Now I tried it myself. If I start USBnet from the Start Menu (with or without KoboLauncher), Windows lists it among the network connections, I can ping 192.168.2.101, but I cannot use it for telnet. If I start nickel via Options > Emergency exit, however, it works. So I have basically the same problem as with telnet via wifi.

Odd that the behavior for Wifi telnet and USBnet telnet are not the same for you.

[tshering]

Have a look at post 17!

[Cyphox]

had it several times now, that when powering on the reader (glo) and doing nothing (just staying in menu) the device freezes and i have to do a reset

this problem occured with 03 (fw3.2) and 04 (fw3.3 and up), havent tried earlier versions yet.

is there some log i can provide or something like that?

[tshering]

Originally Posted by Cyphox

had it several times now, that when powering on the reader (glo) and doing nothing (just staying in menu) the device freezes

Is there any regularity in this, for instance: it freezes only, if you leave it alone for this or that amount of time after powering on the device? Or does it also happen, if you leave it alone after some interaction?
Maybe this has not happened to me, because I usually interact with the device as soon as I power it on. I just did one test. I left it alone for 90 minutes after powering on, but it did not freeze. Repeating this test would be a bit time consuming. So if you could tell me that according to your experience it freezes within the first five minutes, or ten minutes or whatever, I could do some more meaningful test on my device.

Originally Posted by Cyphox

and i have to do a reset

You could also try to force a power down, if this is more convenient. Hold the power silder in the off position for 20 seconds or so. And then power on again.

Originally Posted by Cyphox

is there some log i can provide or something like that?

Maybe we can run some test at a later point, if you agree.

Edit: Did you run the start menu at your Touch too? If yes, did it also freeze?