Kobo Start Menu 07

[Ken Maltby]

Originally Posted by pickyaxe

This works well! That said, is there any way to make the device boot straight to Nickel and launch Start Menu from Nickel?

Sounds like a nutty idea, but there was a startup option to start in Nickel in the same place you set it to "always" or alternate.

The runsettings.txt file, I guess you would want "runmenu=never"

Luck;
Ken

[pickyaxe]

Originally Posted by Ken Maltby

Sounds like a nutty idea, but there was a startup option to start in Nickel in the same place you set it to "always" or alternate.

The runsettings.txt file, I guess you would want "runmenu=never"

Luck;
Ken

Thanks! Should have spent more time reading - the pngs and runsettings do exactly what I want.

[tshering]

Originally Posted by pickyaxe

Thanks! Should have spent more time reading - the pngs and runsettings do exactly what I want.

Unless you have a special reason to do it this way, I would recommend to change the value for runmenu back to "always" and change

ksmAutoselectafter=20

in usersettings.txt to a smaller value. I would, however, not set it to 0, so that you still have access to KSM in case nickel cannot run for some reason.

[nilsoli]

Hi,

I've been using KSM 7 on my one month old aura h2o for a few days now, and everything seems to work fine since. Thanks for that.

However, yesterday, while my device was in Nickel's stand-by state, my battery went from 60% to completely discharged within a few hours... I really have no idea why, maybe a syncing problem on nickel. Have some other users of KSM been experimented this ?

On another point, when my device is completely powered off from nickel, and I then plug the usb cord for charging, KSM automatically starts. I would like the device to stay off at this moment as it was before installing KSM. Is that possible ?

[tshering]

Originally Posted by nilsoli

However, yesterday, while my device was in Nickel's stand-by state, my battery went from 60% to completely discharged within a few hours... I really have no idea why, maybe a syncing problem on nickel. Have some other users of KSM been experimented this ?

Lately, there were reports of battery discharging with the stand-by function of Coolreader and Koreader. KSM was certainly running on some of the concerned devices, but it is difficult to tell from the reports. Since not all KSM users seem to experience this problem, it might be triggered by some specific usage or settings. As far as KSM is concerned, you could try:

• Switch off wifi before you start nickel, in case it is switched on.
• Switch off usbnet before you start nickel, in case it is switched on.
• In .adds\kbmenu\usersettings.txt change

  preventfreeze=true

  to

  preventfreeze=false

  You have to use a unix style editor for this.

Originally Posted by nilsoli

On another point, when my device is completely powered off from nickel, and I then plug the usb cord for charging, KSM automatically starts. I would like the device to stay off at this moment as it was before installing KSM. Is that possible ?

Are you sure that this was the case before installing KSM?

[nilsoli]

Originally Posted by tshering

Lately, there were reports of battery discharging with the stand-by function of Coolreader and Koreader. KSM was certainly running on some of the concerned devices, but it is difficult to tell from the reports. Since not all KSM users seem to experience this problem, it might be triggered by some specific usage or settings. As far as KSM is concerned, you could try:

• Switch off wifi before you start nickel, in case it is switched on.
• Switch off usbnet before you start nickel, in case it is switched on.
• In .adds\kbmenu\usersettings.txt change

  preventfreeze=true

  to

  preventfreeze=false

  You have to use a unix style editor for this.

I will try and report.

Originally Posted by tshering

Are you sure that this was the case before installing KSM?

I think it was the case when the usb cord was only plugged to a sector adaptator, without any data connection.

[Ken Maltby]

Originally Posted by tshering

Lately, there were reports of battery discharging with the stand-by function of Coolreader and Koreader. KSM was certainly running on some of the concerned devices, but it is difficult to tell from the reports. Since not all KSM users seem to experience this problem, it might be triggered by some specific usage or settings. As far as KSM is concerned, you could try:

• Switch off wifi before you start nickel, in case it is switched on.
• Switch off usbnet before you start nickel, in case it is switched on.
• In .adds\kbmenu\usersettings.txt change

  preventfreeze=true

  to

  preventfreeze=false

  You have to use a unix style editor for this.

Are you sure that this was the case before installing KSM?

I am seeing this:

# prevent freezing (use it only, if your device constantly freezes)
# preventfreeze=true

Is having "true" commented out enough, or do I need to uncomment it and have it equal "false"?

OT: What is this used for? Is it needed if you are not using the Nickel UI?:

#set preload libraries for nickel 
nickelpreload="/opt/cfw/preload/hook.so /root/screenInv.so"

Luck;
Ken

[tshering]

Originally Posted by Ken Maltby

I am seeing this:

# prevent freezing (use it only, if your device constantly freezes)
# preventfreeze=true

Is having "true" commented out enough, or do I need to uncomment it and have it equal "false"?

It is necessary to set it to false, since one has to overwrite the pre-set "true" value. If I remember correctly, this was different in an earlier version of KSM. The reason for having changed it is that I had the opportunity to witness how soon some devices freeze after powering on.
(The next update will introduce setting values of usersettings.txt, and of the configuration file for nickel by menu.)

Originally Posted by Ken Maltby

OT: What is this used for? Is it needed if you are not using the Nickel UI?:

#set preload libraries for nickel 
nickelpreload="/opt/cfw/preload/hook.so /root/screenInv.so"

It only concerns nickel. This line makes the "nightmode hack" and the so-called "screensaver kobo Glo" hack work, even though the install routines of both hacks do not take into account KSM users. If one does not use nickel, the line is not needed (but it does no harm).

[Ken Maltby]

Ah So, thanks.

Luck;
Ken

[JFeole]

I tried KSM07 on my new H20, and I like it. But I have a question. It was quite easy to install KSM, and then KOReader and Coolreader.

But if I wanted to completely remove KSM07 and the added readers, what is the correct process to do that?

Is it simply to remove the .adds directory, and the added files in the .kobo directory?

Thanks,
JFeole

[tshering]

Originally Posted by nook_nerd

Is it simply to remove the .adds directory, and the added files in the .kobo directory?

As for KSM, I added an uninstall package and instructions to the first post. (You could simply delete the folders kbmenu and kbmenupngs, but there would still remain some traces on the device. Note: You can apply the uninstall package also, if you have already deleted the folders.)

As for the two readers, you can delete the concerned folders. There will remain however traces of vlasovsoft launcher, but that should be negligible.

[JFeole]

Thanks for the clarification.
I missed the uninstall script in my excitement to get an CoolReader installed

So, If I wanted to get the H2O back to its default state, I would need
to do a Factory Default Reset?(which I don't want to do at the moment, as I like the KSM), but I like to document any software I add to devices.

Nice work on the KSM.

Regards,
JFeole

[Ebri]

The launcher changes only on-animator by starting on_start.sh and adds g_ether.ko. In practice you will not notice this change (if you remove on_start.sh from .kobo, only the check for this file happens, slowing boot by an immaterial amount of picoseconds).

BTW it is nice that without Sergei's system modification the launcher itself can run, as I upgraded anyway to firmware 3.12.1, I now have only a different rCs, but no other files in the system (besides the udev files). Easier to track what I have changed.

[tshering]

Originally Posted by nook_nerd

I missed the uninstall script in my excitement to get an CoolReader installed

You did not miss it, I uploaded the package only after you posted your question. But I hope your excitement did not prevent you from installing the first update package (available in the frst post).

Originally Posted by nook_nerd

So, If I wanted to get the H2O back to its default state, I would need
to do a Factory Default Reset?(which I don't want to do at the moment, as I like the KSM), but I like to document any software I add to devices.

You do not necessarily need to factory reset your device for that purpose. KSM can be completely removed by using the uninstall package (and manually deleting the two folders on the user partition.).
As for vlasovsoft, you can delete the g_ether.ko that vlasovsoft copies to the system partition (you can do this for instance with KSM), and you can replace on-animation.sh by the original version. As Ebri mentioned this file is replaced by the original version as soon as you update to a new firmware anyway. But you can do without the g_ether.ko and modifying on-animation.sh to start with (look at this post, esp. the spoiler.)

Originally Posted by nook_nerd

Nice work on the KSM.

I am glad you like it.

[tshering]

Originally Posted by Ebri

BTW it is nice that without Sergei's system modification the launcher itself can run, as I upgraded anyway to firmware 3.12.1, I now have only a different rCs, but no other files in the system (besides the udev files). Easier to track what I have changed.

I feel the same. Therefore, I never do the "official" install, but only copy the vlasovsoft folder to .kobo, or since KSM 07 rather to .adds.