Kobo Start Menu 07 - Page 31

tshering · 07-28-2015, 02:45 PM

Quote:

Originally Posted by kleinenun

hi @tshering, are there any disadvantages if I keep the USB enabled. Just about the battery or any other else? Thanks. (3.16.0 Glo HD)

I am not sure about that.

tshering · 07-28-2015, 02:46 PM

There might be some issue with FW 3.16.1!
After I installed 3.16.1 and launched nickel and exited back to KSM, I was unable to connect via usb (nor as usb storage, nor via usbnet), instead nickel started spontaneously. After rebooting the reader, I was unable to repeat exactly this behaviour. But still, after exiting nickel and plugging in the usb cable for the first time, the screen goes blind for some seconds, and only then can I navigate the menu and connect to the pc or enable usbnet.

Edit: See post 454 for a more accurate depiction of the problem.

davidfor · 07-28-2015, 07:40 PM

Quote:

Originally Posted by tshering

There might be some issue with FW 3.16.1!

Don't you mean "3.16.10"?

As to the connection issues, I haven't seen any with a straight 3.16.10 install. I haven't had a look at the various scripts and things in the package to see if there are any interesting changes.

tshering · 07-29-2015, 03:25 AM

Quote:

Originally Posted by davidfor

Don't you mean "3.16.10"?

As to the connection issues, I haven't seen any with a straight 3.16.10 install. I haven't had a look at the various scripts and things in the package to see if there are any interesting changes.

Sure, it is 3.16.10. The issue might be related to sickel. Differently from what I thought yesterday, usb is not directly concerned. The device simply reboots after exiting nickel after some time. I just repeatedly happened to connect to usb exactly at that point.

This issue might be related to a new feature:

Quote:

Originally Posted by davidfor

This was released to the beta list with the following list of changes:
...

If the device becomes unresponsive, it will try to reboot itself instead of requiring a manual reset

...

After deleting sickel, the rebooting after exiting nickel has stopped. But I would prefer a more elegant way.

PeterT · 07-29-2015, 06:06 PM

Quote:

Originally Posted by tshering

Sure, it is 3.16.10. The issue might be related to sickel. Differently from what I thought yesterday, usb is not directly concerned. The device simply reboots after exiting nickel after some time. I just repeatedly happened to connect to usb exactly at that point.

This issue might be related to a new feature:

After deleting sickel, the rebooting after exiting nickel has stopped. But I would prefer a more elegant way.

This would make it seem that there is an expected handshake between nickel and sickel, and when sickel does not get a regular message from nickel it forces a reboot.

Ken Maltby · 07-29-2015, 06:47 PM

OK I give up, what is "sickle" ? It doesn't sound healthy, is it something new?

Luck;
Ken

PeterT · 07-29-2015, 07:26 PM

Nod it's new. Based on the name (and the behavior that has been seen) it's a monitor designed to detect when the device has hung and reboot it.

frostschutz · 07-31-2015, 08:05 AM

sickel breaks a few mods, including my AutoShelf, which sends nickel to sleep for but a few seconds but the sickel pings nickel and does not get a reply so it reboots the device. Fun. I half expected it but was hoping that sickel would have a grace period but it reboots instantly.

Alan_S · 07-31-2015, 09:14 AM

Is it easy to remove sickel from new firmwares? At the moment I'm on old firmware (don't need nickel for reading when I have KSM and koreader), but I'm just wandering if it would be easy to solve this new problem with latest firmwares.

tshering · 07-31-2015, 09:28 AM

Quote:

Originally Posted by Alan_S

Is it easy to remove sickel from new firmwares? At the moment I'm on old firmware (don't need nickel for reading when I have KSM and koreader), but I'm just wandering if it would be easy to solve this new problem with latest firmwares.

The easiest way is to delete sickel. This is how I have now 3.16.10 on a Touch. But it would be nice to provide the option to let sickel watch nickel, and stop watching it when nickel has exited. However, I do not think I would use this option. I will wait for Frostschutz' solution and copy it if it is applicable to the needs of KSM.

After reading your post again: As long as you do not start nickel, sickel is not active.

frostschutz · 07-31-2015, 09:45 AM

There is a ping every ~5 seconds and sickel seems to be simply waiting for those. If nickel keeps sending pings even when sickel is not running, where do they go? Best case they are discarded but worst case a buffer fills up somewhere and nickel hangs once its full.

Sending sickel to sleep (STOP, CONT signal) is not an option either; once you wake it, it reboots even though nickel is running fine and dandy.

I wonder what happens if you ever do anything that takes nickel longer than 5 seconds? Opening a large image or PDF perhaps.

My current workaround is: send sickel to sleep (SIGSTOP). And when nickel is back, kill it entire. It's automatically restarted as a d-bus service and does not kill nickel then. The sending to sleep is only to prevent that auto-restart.

Not sure if that's a great solution though.

Alan_S · 07-31-2015, 10:50 AM

I hope you guys will have elegant solutions for us plain users.

I understand deleting sickel, if it is just a file somewhere on a disk, for other solution, I don't know how to do it.

Ken Maltby · 07-31-2015, 11:30 AM

Quote:

Originally Posted by Alan_S

I hope you guys will have elegant solutions for us plain users.

I understand deleting sickel, if it is just a file somewhere on a disk, for other solution, I don't know how to do it.

Why not just use a firmware before this "feature" was added? Or, if there is something in the new FW that you really want, then you could try just deleting the sickle file(s) from the KoboRoot.tgz in the update download .zip, before updating your device?

Luck;
Ken

tshering · 07-31-2015, 03:20 PM

Everything seems to be fine now! My problem was that I tried to kill sickel by a script that did not get executed at all. I guess I should clean up a little, I have already lost the overview which script is executed at which time.

Alan_S · 08-01-2015, 07:54 AM

Quote:

Originally Posted by Ken Maltby

Or, if there is something in the new FW that you really want,

Actually, I just want to look too much into future and reading about this new "great feature" sickle, just wanted to know if it could be handled and how.

At the moment I don't plan firmware update, but who knows, in some time it can become something I'm looking into.

07-28-2015, 02:46 PM	#452
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	There might be some issue with FW 3.16.1! After I installed 3.16.1 and launched nickel and exited back to KSM, I was unable to connect via usb (nor as usb storage, nor via usbnet), instead nickel started spontaneously. After rebooting the reader, I was unable to repeat exactly this behaviour. But still, after exiting nickel and plugging in the usb cable for the first time, the screen goes blind for some seconds, and only then can I navigate the menu and connect to the pc or enable usbnet. Edit: See post 454 for a more accurate depiction of the problem. Last edited by tshering; 07-29-2015 at 03:55 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kobo-Adding alternative readers using Kobo Start Menu	Ken Maltby	KOReader	75	01-10-2020 01:35 PM
Kobo Start Menu	tshering	Kobo Developer's Corner	918	10-12-2017 02:32 PM
QT Browser for Kobo Start Menu?	gloriousglib	Kobo Developer's Corner	1	05-24-2014 03:59 AM
kobo menu and message	tshering	Kobo Developer's Corner	26	01-15-2014 09:18 AM
Calibre start menu icon	Cy1clown	Calibre	1	02-06-2010 02:10 PM

07-29-2015, 06:47 PM	#456
Ken Maltby Wizard Posts: 4,466 Karma: 6900052 Join Date: Dec 2009 Location: The Heart of Texas Device: Boox Note2, AuraHD, PDA,	OK I give up, what is "sickle" ? It doesn't sound healthy, is it something new? Luck; Ken

07-29-2015, 07:26 PM	#457
PeterT Grand Sorcerer Posts: 13,535 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Nod it's new. Based on the name (and the behavior that has been seen) it's a monitor designed to detect when the device has hung and reboot it.

07-31-2015, 08:05 AM	#458
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	sickel breaks a few mods, including my AutoShelf, which sends nickel to sleep for but a few seconds but the sickel pings nickel and does not get a reply so it reboots the device. Fun. I half expected it but was hoping that sickel would have a grace period but it reboots instantly.

07-31-2015, 09:14 AM	#459
Alan_S Evangelist Posts: 446 Karma: 1084584 Join Date: Aug 2007 Location: Sisak, Croatia Device: Kobo Aura H2O, Kobo Aura ONE	Is it easy to remove sickel from new firmwares? At the moment I'm on old firmware (don't need nickel for reading when I have KSM and koreader), but I'm just wandering if it would be easy to solve this new problem with latest firmwares.

07-31-2015, 09:45 AM	#461
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	There is a ping every ~5 seconds and sickel seems to be simply waiting for those. If nickel keeps sending pings even when sickel is not running, where do they go? Best case they are discarded but worst case a buffer fills up somewhere and nickel hangs once its full. Sending sickel to sleep (STOP, CONT signal) is not an option either; once you wake it, it reboots even though nickel is running fine and dandy. I wonder what happens if you ever do anything that takes nickel longer than 5 seconds? Opening a large image or PDF perhaps. My current workaround is: send sickel to sleep (SIGSTOP). And when nickel is back, kill it entire. It's automatically restarted as a d-bus service and does not kill nickel then. The sending to sleep is only to prevent that auto-restart. Not sure if that's a great solution though.

07-31-2015, 10:50 AM	#462
Alan_S Evangelist Posts: 446 Karma: 1084584 Join Date: Aug 2007 Location: Sisak, Croatia Device: Kobo Aura H2O, Kobo Aura ONE	I hope you guys will have elegant solutions for us plain users. I understand deleting sickel, if it is just a file somewhere on a disk, for other solution, I don't know how to do it.

07-31-2015, 03:20 PM	#464
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	Everything seems to be fine now! My problem was that I tried to kill sickel by a script that did not get executed at all. I guess I should clean up a little, I have already lost the overview which script is executed at which time.