Kobo Start Menu 08 - Page 33

adrians · 02-21-2017, 01:33 PM

Quote:

Originally Posted by tshering

I overlooked one detail in your first post:
With this FW you have to install all three components of the update package (you have to copy all three items: KoboRoot.tgz, (the folder) upgrade, and the checksum file to .kobo).

Thanks, that was the problem. Now I'm questioning whether Nickel didn't work after the initial 4c patch.

Is there a way to know when downloading the firmware that it needs all files? I don't recall seeing mention of this on the wiki page I got it from.

tshering · 02-21-2017, 02:48 PM

Quote:

Originally Posted by adrians

Now I'm questioning whether Nickel didn't work after the initial 4c patch.

I wonder too what happened. If the 4c patch prevents running nickel with FW versions smaller than 4.2.8432, I have to do something. I will wait until there a further reports.

Quote:

Originally Posted by adrians

Is there a way to know when downloading the firmware that it needs all files? I don't recall seeing mention of this on the wiki page I got it from.

Since then the information has been added to the wiki.

tshering · 02-21-2017, 02:56 PM

Since these days several people are having problems with the nightmode (for nickel), I mention some details (as far as they concern KSM users). I have nothing new to say, but it may help some people nonetheless.

The nightmode hack has an initalization routine that does not work when a certain line of a certain file (rcS) changes. Since some firmware updates make changes to the rcS file, the initialization routine can stop working and someone has to modify the script. Up to now this happend at least twice. With KSM, however, the nightmode hack does not rely on this installation routine; actually the installation routine did never work with KSM. In KSM you have instead to select in (KSM home) "configure," in the section [nickel], nickelpreload="/root/screenInv.so."

There are several methods to switch nightmode on and off; not all are available on all models and with all versions of the nightmode hack.

On devices that have a hardware home button or a hardware frontlight button, you can toggle nightmode with those buttons.
You can toggle also with the help of fmon. KSM has this build in. Therefore you can toggle by opening toggle_nightmode.png.
With one version (some versions?) of nightmode you can use the light slider to toggle nightmode on and off. We are told that this does not work on Aura One. But I do not know for sure.
You can edit the nightmode configuration file to switch nightmode on or off. Instead of using a text editor for doing this, you can do it via the KSM configuration editor. You start the configuration tool by selecting "tools" > "nickel diverse.msh" > "edit nightmode conf.sh." There, you have to select in the section [state], invertActive=yes; or invertAcitve=no, depending on the case. It is not very convenient, but in some cases perhaps easier than to connect the device to a PC and edit the file there.

the_doc · 02-21-2017, 03:19 PM

Quote:

I wonder to what happened. If the 4c patch prevents running nickel with FW versions smaller than 4.2.8432, I have to do something. I will wait until there a further reports.

I have the 4c patch installed and I am running Nickel version 3.19.5761 without problems so far in my Kobo Mini.

tshering · 02-21-2017, 03:30 PM

Quote:

Originally Posted by the_doc

I have the 4c patch installed and I am running Nickel version 3.19.5761 without problems so far in my Kobo Mini.

Thank you for trying nickel and telling.

Starker · 02-25-2017, 06:31 AM

I'm having trouble displaying Chinese characters on the KSM power off screen. They show up fine when I open the file in a browser, but on my Kobo H2O they are just boxes. Any ideas what the issue here could be?

Here's an example of what my poweroff_info.html file looks like:

Quote:

<html>
<head>
<title>poweroffscreen</title>
<meta charset="UTF-8">
</head>

<body>
睡覺運動高興還好
</body>
</html>

I could always just make an image file and display that, of course, but it would be kind of a pain in the ass.

tshering · 02-25-2017, 06:43 AM

Quote:

Originally Posted by Starker

I'm having trouble displaying Chinese characters on the KSM power off screen. They show up fine when I open the file in a browser, but on my Kobo H2O they are just boxes. Any ideas what the issue here could be?

Here's an example of what my poweroff_info.html file looks like:

I could always just make an image file and display that, of course, but it would be kind of a pain in the ass.

Did you see this post about using custom fonts in KSM?

Starker · 02-25-2017, 06:59 AM

Quote:

Originally Posted by tshering

Did you see this post about using custom fonts in KSM?

No I didn't, but I got it working now. Thank you!

ryt · 03-01-2017, 04:12 AM

Hello!

I installed KSM 8 and the patch KSM08_ext_aura_one_etc_04c you proposed on top of it.

Note that when I installed the patch, I took the KSM 8 archive (delivered with this thread), patched it with the archive delivered on the patch thread on my laptop and then moved the whole archive to my device.
I did again the operation a second time, but taking only the KoboRoot.tgz from the patch (without patching the KoboRoot directory delivered with this thread) which is what you expect us to do.
I assume both operation end up with the same result.

I have an issue with the wifi.
Even, when I connect directly to Nickel without logging first to KSM, it keeps searching for a network without finding any whereas the wifi is said to be activated.
It does basically the same in KSM, no wifi network is found.

My device is new, so I'm wondering whether it comes from the device or from the fact that I installed KSM 8.

So here is my question:
Can KSM affect anyhow the wifi module of Nickel when logged directly to Nickel without passing through KSM?

Thank you so much for the time and work you are putting in delivering KSM! Despite this inconvenient, I appreciate a lot having access to an alternative (and way better) reader.

tshering · 03-01-2017, 06:11 AM

Quote:

Originally Posted by ryt

Hello!

I installed KSM 8 and the patch KSM08_ext_aura_one_etc_04c you proposed on top of it.

Note that when I installed the patch, I took the KSM 8 archive (delivered with this thread), patched it with the archive delivered on the patch thread on my laptop and then moved the whole archive to my device.
I did again the operation a second time, but taking only the KoboRoot.tgz from the patch (without patching the KoboRoot directory delivered with this thread) which is what you expect us to do.
I assume both operation end up with the same result.

This is my assumption too. When you installed the patch-KoboRoot.tgz, you did select "install update" (and not "install partial update"). Right? (But this should not make a difference anyway, if the patching on the laptop was successful.)

Quote:

Originally Posted by ryt

I have an issue with the wifi.
Even, when I connect directly to Nickel without logging first to KSM, it keeps searching for a network without finding any whereas the wifi is said to be activated.
It does basically the same in KSM, no wifi network is found.

My device is new, so I'm wondering whether it comes from the device or from the fact that I installed KSM 8.

So here is my question:
Can KSM affect anyhow the wifi module of Nickel when logged directly to Nickel without passing through KSM?

A potential point of error is that the variable WIFI_MODULE does not have the correct value (on the Aura One the value should be "8189fs"). This would happen if the rcS file was not replaced by the patched version.
In order to see which rcS is on your device, you can select "tools" > "backup and restore" > "restore rcS.sh." You can than find a copy of the rcS on the user partition (.adds/kbmenu_user/backups/rcS_someDateAndTime).

Some users have observed that sometimes the configuration file /etc/wpa_supplicant/wpa_supplicant.conf becomes somehow obstinate (cf. this threat). I am not sure whether this might also produce the effect you are describing. But you can select "wifi > xdel wpa supplicant.conf.sh." This will delete this configuration file. The file will be newly created, when you "start nickel," or "wifi > wifi ap scan.sh" or "wifi > wifi_manage_networks.sh."

Note: If these two things do not solve your problem, I will upload a file that disables temporarily KSM, so that you can easily try how nickel connects to the network (without possibly being influenced by KSM). But first I have to get to my computer.

ryt · 03-01-2017, 12:59 PM

Thank you so much for your complete answer

It is now working

I first tried
"tools" > "backup and restore" > "restore rcS.sh."
But you probably did a copy and paste ;) so I tried
"tools" > "backup and restore" > "backup rcS.sh."
the backup version of rcS.sh was different from the one in the patch

So I copied the KoboRoot.tgz in .kobo. Everytime the device restarted automatically (I could not choose "handle update"). I did this twice.

But the wifi started to work again.

Again, I tried "tools" > "backup and restore" > "backup rcS.sh."
This time the version matched the patched one.

Thank you so much for your help and time :) !

tshering · 03-01-2017, 01:44 PM

Quote:

Originally Posted by ryt

Thank you so much for your complete answer

It is now working

I am glad to hear this.

Quote:

Originally Posted by ryt

I first tried
"tools" > "backup and restore" > "restore rcS.sh."
But you probably did a copy and paste

so I tried
"tools" > "backup and restore" > "backup rcS.sh."
the backup version of rcS.sh was different from the one in the patch

Good you figured it out. I simply was confused (without copy and paste).

Quote:

Originally Posted by ryt

So I copied the KoboRoot.tgz in .kobo. Everytime the device restarted automatically (I could not choose "handle update"). I did this twice.

It did install, so it is o.k. But, did you by chance not finish the installation of the basic KSM? Maybe you skipped this step:

select "tools" > "activate" > "set runmenu settings.msh" > "always" *

*) see the first post of this threat.

Quote:

Originally Posted by ryt

But the wifi started to work again.

Again, I tried "tools" > "backup and restore" > "backup rcS.sh."
This time the version matched the patched one.

So you worked it out!

fradav · 03-01-2017, 09:11 PM

Quote:

Originally Posted by tshering

Could somebody with a H2O with FW 4.2.8432 (fully installed; that means: not only the KoboRoot.tgz) please run this test script?

Hello,

I'm on 4.3.8842 on H2O, applied 4c patch (which helps with wifi in ksm, anyway), but the rotation bug is still there. when I launch your script and exit from nickel I didn't get any dialog and it didn't reboot after 10sec.

tshering · 03-02-2017, 06:35 AM

Quote:

Originally Posted by fradav

Hello,

I'm on 4.3.8842 on H2O, applied 4c patch (which helps with wifi in ksm, anyway), but the rotation bug is still there.

Can you give me some more information?
In which sequence did you install KSM, KSM08_ext_for_all_models_04b_rotation_test.zip , and KSM08_ext_aura_one_etc_04c.zip?

Quote:

Originally Posted by fradav

when I launch your script and exit from nickel I didn't get any dialog and it didn't reboot after 10sec.

What do you see after exiting nickel? The rotated KSM menu from where you started the script?

fradav · 03-02-2017, 09:23 PM

Quote:

Originally Posted by tshering

Can you give me some more information?
In which sequence did you install KSM, KSM08_ext_for_all_models_04b_rotation_test.zip , and KSM08_ext_aura_one_etc_04c.zip?

In this order:

Factory reset
update to 4.3.8842
KSM08
KSM08_ext_aura_one_etc_04c.zip
KSM08_ext_for_all_models_04b_rotation_test.zip

Quote:

Originally Posted by tshering

What do you see after exiting nickel? The rotated KSM menu from where you started the script?

Exactly.

Regards

02-21-2017, 02:56 PM	#483
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	Since these days several people are having problems with the nightmode (for nickel), I mention some details (as far as they concern KSM users). I have nothing new to say, but it may help some people nonetheless. The nightmode hack has an initalization routine that does not work when a certain line of a certain file (rcS) changes. Since some firmware updates make changes to the rcS file, the initialization routine can stop working and someone has to modify the script. Up to now this happend at least twice. With KSM, however, the nightmode hack does not rely on this installation routine; actually the installation routine did never work with KSM. In KSM you have instead to select in (KSM home) "configure," in the section [nickel], nickelpreload="/root/screenInv.so." There are several methods to switch nightmode on and off; not all are available on all models and with all versions of the nightmode hack. On devices that have a hardware home button or a hardware frontlight button, you can toggle nightmode with those buttons. You can toggle also with the help of fmon. KSM has this build in. Therefore you can toggle by opening toggle_nightmode.png. With one version (some versions?) of nightmode you can use the light slider to toggle nightmode on and off. We are told that this does not work on Aura One. But I do not know for sure. You can edit the nightmode configuration file to switch nightmode on or off. Instead of using a text editor for doing this, you can do it via the KSM configuration editor. You start the configuration tool by selecting "tools" > "nickel diverse.msh" > "edit nightmode conf.sh." There, you have to select in the section [state], invertActive=yes; or invertAcitve=no, depending on the case. It is not very convenient, but in some cases perhaps easier than to connect the device to a PC and edit the file there. Last edited by tshering; 02-21-2017 at 03:00 PM.

03-01-2017, 04:12 AM	#489
ryt Junior Member Posts: 6 Karma: 10 Join Date: Mar 2017 Device: Kobo Aura One	KSM 8 + patch: No wifi network found on Aura One Hello! I installed KSM 8 and the patch KSM08_ext_aura_one_etc_04c you proposed on top of it. Note that when I installed the patch, I took the KSM 8 archive (delivered with this thread), patched it with the archive delivered on the patch thread on my laptop and then moved the whole archive to my device. I did again the operation a second time, but taking only the KoboRoot.tgz from the patch (without patching the KoboRoot directory delivered with this thread) which is what you expect us to do. I assume both operation end up with the same result. I have an issue with the wifi. Even, when I connect directly to Nickel without logging first to KSM, it keeps searching for a network without finding any whereas the wifi is said to be activated. It does basically the same in KSM, no wifi network is found. My device is new, so I'm wondering whether it comes from the device or from the fact that I installed KSM 8. So here is my question: Can KSM affect anyhow the wifi module of Nickel when logged directly to Nickel without passing through KSM? Thank you so much for the time and work you are putting in delivering KSM! Despite this inconvenient, I appreciate a lot having access to an alternative (and way better) reader.

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
Kobo Start Menu 07	tshering	Kobo Developer's Corner	644	03-02-2017 06:40 AM
QT Browser for Kobo Start Menu?	gloriousglib	Kobo Developer's Corner	1	05-24-2014 03:59 AM
Calibre start menu icon	Cy1clown	Calibre	1	02-06-2010 02:10 PM

03-01-2017, 12:59 PM	#491
ryt Junior Member Posts: 6 Karma: 10 Join Date: Mar 2017 Device: Kobo Aura One	Thank you so much for your complete answer It is now working I first tried "tools" > "backup and restore" > "restore rcS.sh." But you probably did a copy and paste ;) so I tried "tools" > "backup and restore" > "backup rcS.sh." the backup version of rcS.sh was different from the one in the patch So I copied the KoboRoot.tgz in .kobo. Everytime the device restarted automatically (I could not choose "handle update"). I did this twice. But the wifi started to work again. Again, I tried "tools" > "backup and restore" > "backup rcS.sh." This time the version matched the patched one. Thank you so much for your help and time :) !

Advert

Advert