Kobo Start Menu 08

[fradav]

Originally Posted by tshering

Some things work different on different device models. That the old night mode works on Touch does not mean that it work on H2O. Apart from showing only the half side, what happens when you exit back to KSM? Is there a screen rotation, or does this work correctly?
Did you try to install gtalusan's version anew? Maybe when you installed it the first time there where some other problems (like the KSM patch not being installed completely, or something like that).

Ok let's resume the situation:

1. Kobo H20 latest 4.3.8945 installed
2. KSM 8.0, 4b rot user script, 4c patch (wifi and usb working fine)
3. preload in nickel configuration : nickelpreload="/root/screenInv.so"
4. Original nightmode there installed : half-screen bug like the previous image, but no rotation bug back in KSM, rot user script working
5. uninstalled with provided uninstaller
6. Glatusan's version installed there : night-mode working fine in nickel, no half-screen bug, but rotation bug back in ksm and no dialog back from rot user script.

In both case, when nightmode is disabled (nickel config line deleted) everything works fine.

It's frustrating because I'm very fond of the nickel/koreader switch as I read epub/kepubs in nickel and pdfs with koreader, so I frequently switch back and forth. But I can live with the fact I just have to reboot each time I want to get back in ksm/koreader. Or I just disable the nightmode altogeter.

[tshering]

Originally Posted by fradav

It's frustrating because I'm very fond of the nickel/koreader switch as I read epub/kepubs in nickel and pdfs with koreader, so I frequently switch back and forth. But I can live with the fact I just have to reboot each time I want to get back in ksm/koreader. Or I just disable the nightmode altogeter.

Did you try the inbuild night mode of nickel (available since the most recent versions of the FW)?

[FeatureSettings]
InvertScreen=true

I think there have been reported some problems, but I cannot remember exactly. Once you have the variable in the configuration file you can toggle it on and off from within KSM (tools > nickel div.msh > edit nickel conf.sh [or similar, I do not have my reader with me]). This is still not very convenient, but still better than to have to connect to a pc to change the settings. Of course, you would first remove nickelpreload="/root/screenInv.so" from the KSM conf, but I guess you did this already.

[fradav]

Originally Posted by tshering

Did you try the inbuild night mode of nickel (available since the most recent versions of the FW)?

[FeatureSettings]
InvertScreen=true

I think there have been reported some problems, but I cannot remember exactly. Once you have the variable in the configuration file you can toggle it on and off from within KSM (tools > nickel div.msh > edit nickel conf.sh [or similar, I do not have my reader with me]). This is still not very convenient, but still better than to have to connect to a pc to change the settings. Of course, you would first remove nickelpreload="/root/screenInv.so" from the KSM conf, but I guess you did this already.

And that's an excellent suggestion, indeed. Is there any way to simplify further the process and associate the config switch to a ksm home button or even with the toggle_nightmode.png in nickel ?

[boriar]

Originally Posted by fradav

And that's an excellent suggestion, indeed. Is there any way to simplify further the process and associate the config switch to a ksm home button or even with the toggle_nightmode.png in nickel ?

The inbuild nightmode don't work like the hack. You, always need to reset to change between nightmode and lightmode

[fradav]

Originally Posted by boriar

The inbuild nightmode don't work like the hack. You, always need to reset to change between nightmode and lightmode

I know, but a script to relaunch nickel with the toggle should be fine

[oren64]

Originally Posted by tshering

Good! Maybe it is better you do some real life testing for some time before we proceed. Do not forget: If you start nickel with another script than start_nickel_for_restart.sh, do not open restart_nickel.png. Everything else should work.

I test it fore a few days now, I didn't find any problems problems.
I load boos with calibre, sync, and remove tiles with restart_nickel.png, reading...

I did use restart_nickel.png from nickel by mistake. and it just exit to nickel to ksm menu.

[HeavyLiquid]

Can someone tell me how to install the patch at:

https://www.mobileread.com/forums/sh...&postcount=221

The .zip file has an /add and /etc folder what do I do?

[HeavyLiquid]

Wow. I have myself in a predicament. I have KSM working on my Kobo Aura one. I can't access USB because the patch wasn't installed and Nickel isn't starting. The factory reset doesn't seem to be working.... Holding the power button for 30 seconds while plugged in.

Help!
---
My bad. Factory reset fine....phew.

[tshering]

Originally Posted by oren64

I test it fore a few days now, I didn't find any problems problems.
I load boos with calibre, sync, and remove tiles with restart_nickel.png, reading...

I did use restart_nickel.png from nickel by mistake. and it just exit to nickel to ksm menu.

Thank you for testing. I will try to continue with this on the weekend. Would you be ready to test the refresh nickel from within a nickel-koreader or koreader-nickel loop when I prepare a test version?

[tshering]

Originally Posted by fradav

I know, but a script to relaunch nickel with the toggle should be fine

I am thinking of combining the invertScreen with some entry of the nickel configuration file that can be changed from within nickel. For instance, if you set screen refresh to 1, the night mode would be activated the next time you start nickel, and if you set it to any other value, night mode will be deactivated the next time you start nickel.

I think this might be useful together with the nickel-refresh function we are on the way of introducing.

Or we could introduce simply a new entry "start nickel (night)" in the (KSM) main menu. I think I would prefer this approach. What do you thin?

[tshering]

Originally Posted by HeavyLiquid

Wow. I have myself in a predicament. I have KSM working on my Kobo Aura one. I can't access USB because the patch wasn't installed and Nickel isn't starting. The factory reset doesn't seem to be working.... Holding the power button for 30 seconds while plugged in.

Help!
---
My bad. Factory reset fine....phew.

I am glad you were able to factory reset the device! I am curious what caused the problem. When nickel refuses to start after installing KSM, chances are some of the thumb nails of the images in the kbmenupngs fodler were not yet created. Did you follow the instructions of step 1 of First time installation (in the first thread of this post)?

[HeavyLiquid]

Originally Posted by tshering

I am glad you were able to factory reset the device! I am curious what caused the problem. When nickel refuses to start after installing KSM, chances are some of the thumb nails of the images in the kbmenupngs fodler were not yet created. Did you follow the instructions of step 1 of First time installation (in the first thread of this post)?

I did. I was messing around with the patch. I may have done something, I'll take responsibility.

Can you let me know how to install the patch? The instructions for the patch don't make sense to me as the instructions refer to KoboRoot.tgz which isn't in the attached KSM08_ext_aura_one_04d.zip.
---
My bad again... Apple unarchived everything and deleted the .tgz.

[Hopper333]

Hi all

Apologies if this is a question with an obvious or widely-known answer, but I just synced my H20 in Nickel where it restarted after a dead battery (I only ever use koreader normally) and it updated the system software on me. It is apparently now on 4.2.8432. I can no longer get to koreader via KSM (08 I believe - was the latest 6 months ago), the .png doesn't do anything and powering down no longer alternates Nickel and KSM.

I'm assuming that something either needs to be edited manually, 'touched' or else erased and/or reinstalled on the KSM and/or koreader side of things. I have looked through the last few pages on the wiki and seen nothing that I can recognise for my situation. Any advice or links greatly appreciated as the PDF reader in Nickel is completely awful and I use this for work and have become rather dependent upon it.

I am very computer literate so any editing or terminal commands are fine, I just don't want to break anything by over-reacting or corrupting something sensitive!

Many thanks in advance

Michael

[Hopper333]

OK, in answer to my own question above I followed the instructions here:

https://www.mobileread.com/forums/sh...&postcount=221

and now I am into koreader again! Great, however...

• I don't understand where to find the setting for "handle update". Is there a document somewhere showing how to work with all the settings and options in KSM (including USB and wifi settings, actually)
  
• more importantly, when I enter koreader from nickel now everything is upside down!! and worse, menu selections seem to be separated from their icons. Going straight into koreader (every second restart) works fine

I never use Nickel and so is it possible to disable it permanently and always boot into KSM/koreader?

TIA

M

[tshering]

Originally Posted by Hopper333

OK, in answer to my own question above I followed the instructions here:

https://www.mobileread.com/forums/sh...&postcount=221

and now I am into koreader again! Great, however...

• I don't understand where to find the setting for "handle update". Is there a document somewhere showing how to work with all the settings and options in KSM (including USB and wifi settings, actually)
  
• more importantly, when I enter koreader from nickel now everything is upside down!! and worse, menu selections seem to be separated from their icons. Going straight into koreader (every second restart) works fine

I never use Nickel and so is it possible to disable it permanently and always boot into KSM/koreader?

TIA

M

Thank you for telling me about the rotation problem with the H2O!

As for your question, please follow this step of the instructions (cf. first post of this thread):

KSM is by default configured to run only after every second reboot, and nickel automatically runs after every other second reboot. This is a kind of security measure in case KSM does not properly run after installation (something that cannot be excluded with future firmwares or changed hardware). After KSM has started the first time, please change this behaviour:
select "tools" > "activate" > "set runmenu settings.msh" > "always"

Not having done this step was also the reason for the FW update disabling KSM.