Clara HD Display time when reading

[jamalau]

Originally Posted by davidfor

That means you have developers mode turned on. There will also be a syslog file. Turning developer mode off will prevent them being created. But, will also take away whatever function in the developer mode that you wanted to use.

Hello, i have disabled the developer mode, and these files will create again!
Also in times when i not use may Kobo!

[davidfor]

Originally Posted by jamalau

Hello, i have disabled the developer mode, and these files will create again!
Also in times when i not use may Kobo!

The file should be created when you connect the device to USB. If you are using a hack that simulates a USB connection, it would probably create them as well.

To stop them completely, you might need to delete the "Log" line in the config file. This will be in the "DeveloperSettings". Turning off the developers mode might still eave these active.

[jamalau]

@davidfor Thanks, fore your Answer, can you tell me what line i have to delete, i cannot find a line with log inside?
And why was the file createt in the Night, when i not use my Kobo?
I think you mean the Kobo eReader.conf , in /.kobo/Kobo?

[NiLuJe]

@jamalau: IIRC, some the patches to enforce/toggle dev options automatically and/or from somewhere else enable logging as a side-effect.

A fake/manual usb session shouldn't, on the other hand .

[jamalau]

Thanks for the Answer, but how can i switched this off?
When i not look in my KoboDirectory, i have, after a short Time, more then 100 Files inside!

I think it is OT in this Thread, can anyone move this to a Single Thread?

[jsessions]

Out of interest how easy would it be to tweak miniclock to save its config files in .adds (like many other programs incl KFMON, KOReader, Plato, PBChess, NickelMenu etc) rather than it's own new directory .addons?

[NiLuJe]

@jsessions:

┌─(niluje@illyria:pts/5)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(~/MPLAYER/Frostschutz-Kobo/MiniClock)─┐
└─(0.35:48%:18:58:%)── grep -r '.addons'                                                                                                                                                                                                                                                                                                               ──(Tue, Jun 23)─┘
usr/local/MiniClock/miniclock.sh:BASE="/mnt/onboard/.addons/miniclock"
mnt/onboard/.addons/miniclock/miniclock.example.cfg:#     copy or rename this file to .addons/miniclock/miniclock.cfg
mnt/onboard/.addons/miniclock/miniclock.example.cfg:# To debug, set to 1 (will create .addons/miniclock/debuglog.txt)

[jsessions]

Interesting so just by changing the BASE value in miniclock.sh it could sit nicely in .adds

[jamalau]

Hello, Minclock doesn´t toggle on my Aura Second Editon v1, i have tried the newe Version fom #311, and in miniclock.cfg overlay=0, both not work, what can ido?

[NiLuJe]

@jamalau: Actually actionable information would be nice, for a start. ("not working" doesn't mean anything to me).

You can also enable debug mode in the config and check the log (.addons/miniclock/debuglog.txt).

[jamalau]

Oh sorry, i mean toggle in Nightmode, the same how my Kobo Forma,/Aura but this was solved, some posts before!

Gesendet von meinem SM-T835 mit Tapatalk

[NiLuJe]

@jackie_w mentioned in another thread (and earlier here) that having the patch to toggle nightmode from somewhere else (epub page? dunno) was causing duplicate entries in the config, breaking the detection.

[MGlitch]

Originally Posted by NiLuJe

@jackie_w mentioned in another thread (and earlier here) that having the patch to toggle nightmode from somewhere else (epub page? dunno) was causing duplicate entries in the config, breaking the detection.

The patch and miniclock get along, it’s the patch plus nickelmenu plus miniclock where the issue of toggling nightmode with nickelmenu comes in. Because the patch stores the setting in one place while NM stores it in another. I’m not sure if jamalau had the nightmode patch on their Forma but disabling the patch and removing the line it adds to the kobo config file resolved the issue when I had it.

Of course she explains it better than I am:

Originally Posted by jackie_w

NickelMenu will store the InvertScreen=true setting in its correct section, [FeatureSettings] in the .conf file.

The earlier Adobe page numbers kobopatch will store that same setting in the [Reading] section, because it had no choice. If you haven't already you need to:
- disable the patch
- manually delete InvertScreen=true from the [Reading] section.

If you don't do that you'll get the 2 entries fighting each other and the MiniClock display may have a white background after inverting the screen.

[jamalau]

@MGlitch Thanks, deleting from InvertScreen=true/false, has solved the Problem!

[LucyOne]

Now that there is a constant clock on the home screen, would it be possible to have miniclock only shown in the book view? I.e. hide it whenever the other clock is shown?