NickelMenu: An integrated launcher for Kobo eReaders

[RobertJSawyer]

Originally Posted by NiLuJe

The Aura's kernel is broken, nightmode will either crash or misbehave, so, that's not terribly surprising .

(The legacy nightmode hack reverts to software inversion on that device; so does KOReader).

Under discussion is the Kobo Aura HD (6.8-inch) not the Kobo Aura (6-inch). Which model are you referring to, NiLuJe? (And, yes, the nightmode hack works just fine on the Kobo Aura HD.)

[NiLuJe]

@RobertJSawyer:

Oh, right, I'm once again foiled by the terrible model names, thanks for the correction ;p.

I was indeed strictly speaking about the Aura .

The Aura HD *did* have some issues with nightmode, but, AFAIK (as it's a very close sibling to the H2O, where I can vouch for the feature), it was fixed at one point, and so should behave properly on an up-to-date firmware.

[JSWolf]

Originally Posted by NiLuJe

@RobertJSawyer:

Oh, right, I'm once again foiled by the terrible model names, thanks for the correction ;p.

I was indeed strictly speaking about the Aura .

The Aura HD *did* have some issues with nightmode, but, AFAIK (as it's a very close sibling to the H2O, where I can vouch for the feature), it was fixed at one point, and so should behave properly on an up-to-date firmware.

I can vouch for nightmode working on the original Aura H2O.

[Elektron]

I can for the edition 2 (v2)

[Semwize]

@geek1011

Why doesn't the span tag work in the config? for example

menu_item :main   :<span style='font-style:normal'>KOReader</span>  :cmd_spawn :

(this is an example, in general I wanted to use letter-spacing)
At the same time, the tags <i>, <b>, <big> etc work great

What am I doing wrong?

[geek1011]

Originally Posted by Semwize

@geek1011

Why doesn't the span tag work in the config? for example

menu_item :main   :<span style='font-style:normal'>KOReader</span>  :cmd_spawn :

(this is an example, in general I wanted to use letter-spacing)
At the same time, the tags <i>, <b>, <big> etc work great

What am I doing wrong?

That's the colon. There's not currently a way to escape them, although I suppose I could implement that.

[Semwize]

Originally Posted by geek1011

That's the colon.

If it doesn't take much of your time, can fix it?

[charlitos]

Originally Posted by geek1011

That's interesting. Does it happen with devmode on? Also, does the syslog or dmesg say anything interesting?

I enabled devmode in my Aura HD and the issue is still happening, I enabled dark screen and suddenly go back to normal screen. Here's an extract from the syslog (I do not know if there is anything useful):

Jan 24 11:41:35 nickel: (NickelMenu) showing menu (src/nickelmenu.cc:393)
Jan 24 11:41:36 nickel: ( 4221.614 @ 0x154adf0 / performance.debug) 10 ms to composite
Jan 24 11:41:36 nickel: ( 4221.614 @ 0x154adf0 / eink.debug) QRegion KoboScreenNXP::blit(const QRegion&) QRect(704,813 376x523) wf=257 upd=0 flags=1 can_collide=1
Jan 24 11:41:36 nickel: ( 4221.615 @ 0x154adf0 / eink.debug) QRegion KoboScreenNXP::blit(const QRegion&) QRect(864,1336 216x104) wf=257 upd=0 flags=1 can_collide=1
Jan 24 11:41:37 nickel: ( 4223.070 @ 0x1863248 / input.debug) 0 : QPoint(973,178) => QPoint(902,973) QFlags(0x1) 100
Jan 24 11:41:37 nickel: ( 4223.097 @ 0x1863248 / input.debug) 0 : QPoint(972,178) => QPoint(902,972) QFlags(0x4) 101
Jan 24 11:41:37 nickel: ( 4223.127 @ 0x1863248 / input.debug) 0 : QPoint(971,177) => QPoint(903,971) QFlags(0x4) 100
Jan 24 11:41:37 nickel: ( 4223.130 @ 0x1863248 / input.debug) 0 : QPoint(971,177) => QPoint(903,971) QFlags(0x8) 0
Jan 24 11:41:37 nickel: ( 4223.142 @ 0x154adf0 / performance.debug) 9 ms to composite
Jan 24 11:41:37 nickel: ( 4223.142 @ 0x154adf0 / eink.debug) QRegion KoboScreenNXP::blit(const QRegion&) QRect(704,813 376x523) wf=257 upd=0 flags=1 can_collide=1
Jan 24 11:41:37 nickel: (NickelMenu) item 'Dump Syslog' pressed... (src/nickelmenu.cc:387)
Jan 24 11:41:37 nickel: (NickelMenu) action 0x325e50fd with argument logread > /mnt/onboard/.adds/syslog.log : (src/nickelmenu.cc:658)

Nonetheless if I enable "Invert Screen" from "Drawing" section in the developers options, the dark mode remains.

Thanks for your help!

[JSWolf]

@charlitos what version firmware are you running?

[charlitos]

Originally Posted by JSWolf

@charlitos what version firmware are you running?

I'm running NickelMenu v0.5.1 on firmware 4.25.15875

[Semwize]

delete

[de Salier]

Is there any way to hide the configuration file from the booklist?

[DNSB]

Originally Posted by de Salier

Is there any way to hide the configuration file from the booklist?

Yes.

Try adding the following to your Kobo eReader.conf file found in the .kobo\Kobo directory;

[FeatureSettings]
ExcludeSyncFolders=(\\.(?!kobo|adobe).*?|([^.][^/]*/)+\\..+)

Use a Linux EOL aware editor (I use Notepad++) and if [FeatureSettings] already exists, just add the ExcludeSyncFolders line.

[trcm]

<removed>

[Brain]

I own Kobo Aura One (not limited edition) and currently have KSM with Koreader installed. However device is really overcrowded and for a long time the battery only held for few days. I'd like to clean it up completely and install Nickelmenu, Koreader and preferably a friendly program for reading manga. What steps should I take? Do I have to remove KSM manually, using these instructions https://www.mobileread.com/forums/sh...&postcount=327 or can I somehow do a complete reset of the device, allow the firmware to update (or maybe download firmware from this site, not sure which is a better option), install Nickelmenu following instructions in this thread and then proceed to install Koreader?