Kobo Start Menu 08

[tshering]

Hi Ben,

Thank you for your observations. It is not clear to me what actually was happening.

Originally Posted by BenVL

FWIW.

I had with my Kobo Aura (the original one, NOT Ed 2, ONE, H2O) the same problem as 'ttrek' was facing in post 260 of this thread :
after attempting to enable usb in KSM8,

• USB support stayed disabled

• the menu was stripped from all extras as eg. koreader, start vlasovsoftlauncher, ...

• Only a reboot helped to get everything back.

Evidently the effects were the same as those experienced by trekk, the cause however was different. With the new models (Aura One, and Ed 2) PRODUCT_ID was empty, and therefore loading g_file_storage.ko failed. In your case however the cause is that /dev/mmcblk1p1 exists, even though there is no external sd present. Do you have any idea how this can happen? By the way, umount -l /mnt/sd does not cause a problem, even if the sd is not mounted. Is it possible that the problem started when you removed the sd and tried to enable usb almost at the same time, so that /dev/mmcblk1p1 existed at the time of testing its presence and was gone at the time of loading g_file_storage.ko? Enabling usb should work whether an external sd is present or not.

[tshering]

Originally Posted by kwokhin

Hello! Just drop by to say hello and thank you!
I've updated my kobo Glo HD to KSM08 and I am loving it!
It works perfectly! Thank you very much

I am glad you love it.

[tshering]

Originally Posted by CH23

toggle_nightmode.png -> nothing

This needs nightmode to be installed, and nickelpreload must be set to "/root/screenInv.so" in the section [nickel] (use "configure" from the main menu)

Originally Posted by CH23

switchtokoreader.png -> KSM

This need KOReader to be installed; and nickel has to be started by "start nickel koreader switch" or "start koreader nickel switch" (you can find them under "koreader additions")

Originally Posted by CH23

simulate_usb_connection.png -> 'computer connected' popup pop ups for a second

See this post.

[tshering]

Originally Posted by kido.resuri

Hello!

I haven't read the whole thread, nor did I try KSM8 yet.
I'm interested in the fmon and kbmenupngs feature. Do I need to install the whole KSM8 or is it possible to just install fmon? Do I have to modify anything (in the script), or just "load and use"?

My "plan" is to add extra features by adding images as menu items, put them in a collection, so they are more easy to access. I don't want to use the "classic" KSM menu, it would be more convenient to use a menu from the stock GUI.

KSM assocites the images and scripts to be controlled by fmon with each other each time nickel is launched. Therefore, it is not easy to separate the fmon task from the rest of KSM. But you can configure KSM so that it starts nickel immediately after boot (though I do not recommend this). You will hardly notice KSM, if at all.

Originally Posted by kido.resuri

..., but I don't want to change my sleeping and power off screens, and any other stuff.

KSM does not change them by default.

Originally Posted by kido.resuri

I don't need the koreader, coolreader, pbchess. What I would need is a "notepad", or an editor or something for creating notes and lists, "todo" style maybe, perhaps a calculator, and a calendar would be cool.

PBChess is a package that includes a text editor and a calulator. fmon is also part of PBChess. So this seems to be what you want.

[kido.resuri]

tshering, i tried to set KSM to never start, is this the setting to start nickel instead? Because with this setting, fmon doesn't start. I don't know if this is the normal behavior. Same happens, when set to alternateNickel, and it's Nickel's turn.

Thank you!

[tshering]

Originally Posted by kido.resuri

tshering, i tried to set KSM to never start, is this the setting to start nickel instead? Because with this setting, fmon doesn't start. I don't know if this is the normal behavior. Same happens, when set to alternateNickel, and it's Nickel's turn.

Thank you!

Yes this is the expected behaviour. In the two cases mentioned by you, (almost) everything is as if KSM is not installed at all. You have to start fmon in some other way. Look how PBChess is doing it with /etc/init.d/on-animator.sh. By the way, if KSM is active, it circumvents /etc/init.d/on-animator.sh in order to prevent running multiple instances of fmon. Be aware that the PBChess way of starting fmon does not check whether it is safe doing so, while KSM (if active) does at least some minimal checking, and allows you to interact with the device if something goes wrong.

[schrauger]

Is there a script or other method of changing the white balance in KSM on the Aura One? I haven't found anyone mention it, but perhaps I'm looking in the wrong threads.

The brightness adjuster works fine, but the white balance is a new feature unique to the Aura One, so I imagine it isn't baked into KSM as-is. I am surprised to find no one else requesting it, though.

[tshering]

Originally Posted by schrauger

Is there a script or other method of changing the white balance in KSM on the Aura One? I haven't found anyone mention it, but perhaps I'm looking in the wrong threads.

The brightness adjuster works fine, but the white balance is a new feature unique to the Aura One, so I imagine it isn't baked into KSM as-is. I am surprised to find no one else requesting it, though.

Would be nice if somebody who has access to an Aura One could (find and) provide a means to do this. Up to now, I did not hear of anybody trying to do so.

[Ken Maltby]

There is an open "issue" at the Github project.

Luck;
Ken

[BenVL]

Originally Posted by tshering

Hi Ben,

Thank you for your observations. It is not clear to me what actually was happening.

Evidently the effects were the same as those experienced by trekk, the cause however was different. With the new models (Aura One, and Ed 2) PRODUCT_ID was empty, and therefore loading g_file_storage.ko failed. In your case however the cause is that /dev/mmcblk1p1 exists, even though there is no external sd present. Do you have any idea how this can happen? By the way, umount -l /mnt/sd does not cause a problem, even if the sd is not mounted. Is it possible that the problem started when you removed the sd and tried to enable usb almost at the same time, so that /dev/mmcblk1p1 existed at the time of testing its presence and was gone at the time of loading g_file_storage.ko? Enabling usb should work whether an external sd is present or not.

tshering, tx for the feedback. And my apologies for my late answer.

Actually, the external sd was already out of the Aura for months. So, no that's not it. Also, the Kobo was already powered off and on many times and even reset a number of times to get from Nickel back to KSM.

So regardless if the sd card is there or not, the device /dev/mmcblk1p1 stays once it is created ... you would expect the device tree to get cleaned up if devices disappear. Maybe not so in the (old) Kobo kernel ?

Cheers, Ben

[tshering]

Originally Posted by BenVL

So regardless if the sd card is there or not, the device /dev/mmcblk1p1 stays once it is created ... you would expect the device tree to get cleaned up if devices disappear. Maybe not so in the (old) Kobo kernel ?

Nobody else did report this problem, so it might not be very widespread. The other point is that enable_usb.sh uses the same test as /usr/local/Kobo/udev/usb. Actually, enable_usb.sh is basically a clipping of it. (That explains also why it contains superfluous parts.) As things are, your device should also be unable to connect to pc from within nickel, if there is no sd inserted. Or does this work?
You say that the sd was out of the device for month. Did you never try to connect to pc during this time, or started the problem only recently?

[BenVL]

Originally Posted by tshering

Nobody else did report this problem, so it might not be very widespread. The other point is that enable_usb.sh uses the same test as /usr/local/Kobo/udev/usb. Actually, enable_usb.sh is basically a clipping of it. (That explains also why it contains superfluous parts.) As things are, your device should also be unable to connect to pc from within nickel, if there is no sd inserted. Or does this work?
You say that the sd was out of the device for month. Did you never try to connect to pc during this time, or started the problem only recently?

As good forum member I did a search before reporting it.
But although essentially different, the behaviour described by ttrek was closest to what I saw. As such I thought I better describe it in case somebody else sees the same issue.

Connecting to a PC from within Nickel (and no KSM) and without an sd card never was a problem.

Cheers, Ben

[tshering]

Originally Posted by BenVL

As good forum member I did a search before reporting it.
But although essentially different, the behaviour described by ttrek was closest to what I saw. As such I thought I better describe it in case somebody else sees the same issue.

I only tried to suggest that the problem is not related to having a newer/different kernel. If this were the case, I would have expect to see more reports of usb not working. But, of course, its possible that people have this problem and do not report.

Originally Posted by BenVL

Connecting to a PC from within Nickel (and no KSM) and without an sd card never was a problem.

This is strange, since KSM uses the same lines of code for checking the presence an the external sd as does nickel. Please keep us updated if you have further insights.

[boriar]

@tshering

Please, can you update your autoshelf on demand for ksm for AutoShelf_20160916?
In the old version of autoshelf I can do the changes but now with changes by frostschutz I don't know what is necesary for ksm apart initial variables.

Thanks in advance.

[tshering]

Originally Posted by boriar

@tshering

Please, can you update your autoshelf on demand for ksm for AutoShelf_20160916?
In the old version of autoshelf I can do the changes but now with changes by frostschutz I don't know what is necesary for ksm apart initial variables.

Thanks in advance.

I added the new version here. Do not forget to back up your database before you test this version.