NickelMenu: An integrated launcher for Kobo eReaders

[JSWolf]

Originally Posted by DrChiper

I got today a Glo HD with FW 4.31.19086 to work using NM 0.5.4 for darkmode, so it seems to be possible.

I highly suggest you go back to 4.30 and patch it to not update the firmware via WiFi. 4.31 is very buggy to the point that it can cause a database corruption.

[zetaz]

thank you all.
4.30 don't work for me . i had to revert step by step to 4.26...
perhaps i have to reset all the kobo for a fresh install.
best regards

[OldMizio]

I just discovered NM, and I found it usefull. But I am wondering if it is possible to organize a nested menu on a Libra 2. Is it feasible? And how? Thanks

[davidfor]

Originally Posted by zetaz

Hello
Dark mod is not working with my kobo glo HD with firmware higher than 4.26.16704
I use the last nickel menu found on this website.
When i see it failed with 4.31.19086 , i uninstall nickel menu and install it again without success ( only dark mod don't work)
Then i try all others firmwares 4.30.18838, 4.28.18220 without success.
It work with 4.26.16704

"Dark mod"? What do you mean? Kobo added Dark Mode with the Elipsa a firmware 4.28. Before that, there was an inverted screen mode. That is still there but how it works change. From memory, you have to reboot when you turn it on. And Dark Mode is only active when reading. There has been plenty of discussion on how the two modes work with the newer firmware.

[zetaz]

Hello.
I want to say "background black words in white"
I use it for years. But with firmware after 4.26 it stop working.
When I "click" in the menu "night mode" in nickel menu it blink one time but stay white background black words. No need to reboot

[davidfor]

Originally Posted by zetaz

Hello.
I want to say "background black words in white"
I use it for years. But with firmware after 4.26 it stop working.
When I "click" in the menu "night mode" in nickel menu it blink one time but stay white background black words. No need to reboot

And as I stated, this changed after firmware version 4.26. Kobo added better support for Dark Mode but the existing inverted mode is still there. But requires a reboot to take effect. You choice is simple, stay on 4.26 or accept that it works differently.

[koboread]

：竖起大拇指： I may need to check the format of all my ePub contents, which may be the case in many cases. Is there any relevant tool to recommend quick cleaning？

Originally Posted by DNSB

I'm rather puzzled. What does your problem have to do with NickelMenu? As for your sample ebook, it's is a bit of a disaster. You have:

<style type="text/css" class="kobostylehacks">div#book-inner { margin-top: 0; margin-bottom: 0;}</style>

and:

<p class="calibre6" style="margin:0pt; border:0pt; height:1em"><span class="koboSpan" id="kobo.2.1">*</span></p>

Using a class tag inside a style tag is not a permitted function though you might try something like:

<style id="kobostylehacks" type="text/css">div#book-inner * { margin-top: 0 !important; margin-bottom: 0 !important;}</style>
<style type="text/css" id="koboSpanStyle">.koboSpan { -webkit-text-combine: inherit; }</style>

Since Kobo's firmware is not happy with Garbage In, I did some quick cleanup on the file and it seems to work on my Kobo. Could you try the attached file and see if it works?

[koboread]

Maybe I should use Sigil to check all my books

Originally Posted by DNSB

I'm rather puzzled. What does your problem have to do with NickelMenu? As for your sample ebook, it's is a bit of a disaster. You have:

<style type="text/css" class="kobostylehacks">div#book-inner { margin-top: 0; margin-bottom: 0;}</style>

and:

<p class="calibre6" style="margin:0pt; border:0pt; height:1em"><span class="koboSpan" id="kobo.2.1">*</span></p>

Using a class tag inside a style tag is not a permitted function though you might try something like:

<style id="kobostylehacks" type="text/css">div#book-inner * { margin-top: 0 !important; margin-bottom: 0 !important;}</style>
<style type="text/css" id="koboSpanStyle">.koboSpan { -webkit-text-combine: inherit; }</style>

Since Kobo's firmware is not happy with Garbage In, I did some quick cleanup on the file and it seems to work on my Kobo. Could you try the attached file and see if it works?

[DrChiper]

Originally Posted by JSWolf

I highly suggest you go back to 4.30 and patch it to not update the firmware via WiFi. 4.31 is very buggy to the point that it can cause a database corruption.

Rest assured that it is now safe on 4.30. Not being the owner of this device, I assume it was upgraded due to inadvertently enabling the WIFI.

[DrChiper]

Yesterday I installed NM 0.5.4 on several Kobo devices. Today I noticed that my Libra 2 (4.30.18838) was almost down to 17% remaining battery. While I looked on, it went quickly to 10% during the following 30 minutes. So I charged until 100% and started some reading. Literally every time I checked the battery status it was further down. At 95% I uninstalled NM as per provided instruction and checked the Libra 2 again, and again. Up to now (some hours later) the battery remained on 95% which is as expected (seemingly no draining issues on the Libra 2 itself).

I did check the aforementioned Glo HD (see previous post) whether it had the same issues, but it apparently did not.

So there might be some interesting continued activity going on in the NM on the Libra 2 platform: polling, looping?
This is my minimalistic config setting (which worked!):

menu_item : main   : USB               : nickel_misc    : force_usb_connection
menu_item : main   : Screenshot On/Off : nickel_setting : toggle : screenshots
menu_item : reader : Screenshot On/Off : nickel_setting : toggle : screenshots

Is there anything to be said about this finding?

[geek1011]

Originally Posted by DrChiper

Yesterday I installed NM 0.5.4 on several Kobo devices. Today I noticed that my Libra 2 (4.30.18838) was almost down to 17% remaining battery. While I looked on, it went quickly to 10% during the following 30 minutes. So I charged until 100% and started some reading. Literally every time I checked the battery status it was further down.

There shouldn't be anything in NM which could cause it, except for maybe an excessive amount of highlighting (since it checks the config for changes).

To be sure, you can check the syslog since every entry point to NM logs something there.

[DrChiper]

Originally Posted by geek1011

There shouldn't be anything in NM which could cause it, except for maybe an excessive amount of highlighting (since it checks the config for changes).

Lightning was 3% during about an hour, switched off otherwise.
Highlighting was not used at all.

Originally Posted by geek1011

To be sure, you can check the syslog since every entry point to NM logs something there.

I will later-on re-install NM with the following addition in the config file:

menu_item : main : Dump Syslog : cmd_spawn : logread > /mnt/onboard/.adds/syslog.log

Might the phenomenon re-appear I dump the syslog to see whether I can find anything (providing I understand the logs )
Fingers crossed that I am able to replicate the issue.

[DrChiper]

Originally Posted by geek1011

There shouldn't be anything in NM which could cause it...

UPDATE: All seems still to be well now, battery went overnight from 92% to 91% with NM active which is not bad at all.
I did inspect the syslog for any "strange" behavior but found none.

Spoiler:

However I did found some interesting things like repeated packet dumps to ssl.google-analytics and one performance warning "Warning: database transaction took 507ms". I keep an eye on those.

BACKTRACING: what might have happened?
At the moment I wanted to install NM, I got a nasty surprise: my Libra 2 started to install 4.31, likely caused by a sneaky download thereof during my adventures with Bluetooth (BT/WIFI pairing). I let it go-on, an auto reboot (1) followed accordingly, I checked if it now really was on 4.31 and unfortunately it was.
So I quickly connected to the PC, side-loaded 4.30, safely disconnected, got the according auto reboot (2) and checked if 4.30 was now active: it was.
Reconnected to the PC, side-loaded NM 0.5.4, safely disconnected, got the according auto reboot (3) and checked for the expected NM menu. It was there and seemed to function. I did some testing and reading, noticed the battery was on 47% and called it a day.
The next morning the battery indicated 17% left and did quickly reached 10% (triggering charge warning). So I charged to full 100% and then the quick discharging occurred as mentioned in my other posts.
I reasoned that it might have to do with NM, so I uninstalled it with the reboot (4). From then on the discharging stopped.

RETROSPECT:
I think that the changed FW 4.31 & 4.30 & NM installments left some free running process of which we never will know what. The uninstalling of NM caused a reboot, which might have killed that run-away process and place the Libra 2 in a stable situation again. This caused my idea that NM might be the culprit. However the re-install of NM did not induced any new troubles as far as I can see now, so it seems to me that it is unlikely that NM really was causing the problems.
For the moment I leave the NM syslog dump option in place and keep on monitoring for possible future battery draining issues.
Thanks for the pointers geek1011

[AnimalOfArt]

Originally Posted by AnimalOfArt

So I got my Libra 2 now and I am running in to a problem using NickelMenu.
I want to use rclone on my Libra 2 [...]

rclone itself runs fine now. But I have another problem. When I use cmd_output, it will give me a timeout, because the upper limit is 10 seconds.
When I use cmd_spawn it will run the command in the background for how long it takes but I won't get a message about when its done.

Can anyone give me a suggestion how I maybe can echo out a message after rclone process is finished?

[NiLuJe]

Write a shell script and either use NickelDBus or FBInk for visual feedback.