Glo Kobo Night Mode

[yoq]

@Mingyar
I was lazy and diverted the standard output into a file for debugging , I assume that was the problem.
If that is the case, this new version should help.

[Lucas Malor]

@yoq: mmmmhhh, good point
About the file, I mean that in the tweak sh script you create a real file with echo, but not a FIFO.

@tshering: so did you have changed the aspect of bars and dictionaries using CSS? How?

[tshering]

Originally Posted by yoq

And yes, the uninstaller doesn't remove all files but the hack is disabled afterwards. So far I couldn't think of a safe way to remove them on all models.

Maybe I completely miss the point, but wouldn't

rm /mnt/onboard/.kobo/nightmode.sh
rm /mnt/onboard/.kobo/screenInv.so
rm /tmp/invertScreen
rm /mnt/onboard/.kobo/screenInvertLog
rm /mnt/onboard/.kobo/screenInvertLogFB

in autorun.sh do the job?

[tshering]

Originally Posted by Lucas Malor

@tshering: so did you have changed the aspect of bars and dictionaries using CSS? How?

No, I changed only the colors of the books.

[yoq]

@Lucas Malor
OK, so you mean I should use a file to save the state when powering the kobo off?
That's a good idea, I'll implement it in the next release when Mingyars problem is fixed.

[Lucas Malor]

Well, it's a good idea, but I mean that it seem you already create a real file, since in the nightmode.sh there's a echo but no mkfifo.

@tshering: what a pity, it would be fantastic if kobo style could be personalized using CSS

[yoq]

Originally Posted by tshering

Maybe I completely miss the point, but wouldn't

rm /mnt/onboard/.kobo/nightmode.sh
rm /mnt/onboard/.kobo/screenInv.so
rm /tmp/invertScreen
rm /mnt/onboard/.kobo/screenInvertLog
rm /mnt/onboard/.kobo/screenInvertLogFB

in autorun.sh do the job?

The problem is, autorun.sh is execute before the internal sd storage is mounted. If you look into rcS, it starts with "/sbin/udevadm trigger", the mount comes a few lines after that.
Thinking about it, it should be possible to wait for the mount in the script.

[yoq]

Originally Posted by Lucas Malor

Well, it's a good idea, but I mean that it seem you already create a real file, since in the nightmode.sh there's a echo but no mkfifo.

@tshering: what a pity, it would be fantastic if kobo style could be personalized using CSS

No, the hack executes mkfifo on startup, and so echo just writes into the fifo.
But using a real file would be bad for the sd, and make things slower.

[tshering]

Originally Posted by yoq

The problem is, autorun.sh is execute before the internal sd storage is mounted. If you look into rcS, it starts with "/sbin/udevadm trigger", the mount comes a few lines after that.
Thinking about it, it should be possible to wait for the mount in the script.

Maybe one could prepare the uninstall already at the time of the installation in the rcS file.

if [ -e /root/unistallscreenInv.sh ]; then
	/root/unistallscreenInv.sh
	/usr/local/Kobo/nickel -qws \&
else
	LD_PRELOAD=/mnt/onboard/.kobo/screenInv.so /usr/local/Kobo/nickel -qws \&
fi

unistallscreenInv.sh would do the cleanup. I don't know how to restore the original crS from the unistallscreenInv.sh. Would be easy if the "if ... fi" block would be a one-liner. Is this possible by using semicolons? (I am not a linux user and just started with bash because of the kobo. So I am just fooling around.)

[Mingyar]

Originally Posted by yoq

@Mingyar
I was lazy and diverted the standard output into a file for debugging , I assume that was the problem.
If that is the case, this new version should help.

Thanks Yok but problems are still here.

No serial informations transmitted to the Kobo after plugin installed.

After uninstall of the plugin by the uninstaller KoboRoot.tgz, 3 files still remain in .kobo folder (screenInvertLog, nightmode.sh and screenInv.so)

Only thing better, after uninstall completed by deleting manually the 3 files, no need to factory reset.

[yoq]

With "serial informations", do you mean the serial port?
http://www.flickr.com/photos/euphy/8522682330/

Please tell me how I can reproduce the problem.

[tapioco2000]

In my opinion battery drain is normal.

[samhy]

Originally Posted by Mingyar

No serial informations transmitted to the Kobo after plugin installed.

Do you mean the series information as in Harry Potter#1, Harry Potter#2... ?
You seem to use the kepub.epub plugin. Do you also use the shelf management settings?

[Lucas Malor]

@Mingyar: can you reinstall and re-uninstall the plugin, add a test.sh entry to the kobotweaks.ini and write such a file with:

cat /etc/init.d/rcS > /mnt/onboard/.kobo/mydebug.log

restart the kobo and execute the test entry, mount the kobo, search for .kobo/mydebug.log and post here its contents?

@yoq: ok, let me know if I have understood: you are dynamically linking a C library to nickel bin. The library contains a class, which constructor is automatically invoked. The constructor creates the FIFO. Since this is done at startup, any echo will be directed to the FIFO? Right?

Thank you for the C for dummies lesson

[Mingyar]

Originally Posted by yoq

With "serial informations", do you mean the serial port?
http://www.flickr.com/photos/euphy/8522682330/

Please tell me how I can reproduce the problem.

No, not serial port, but, as Samhy says, the line added under the title in the library for collections.

And yes I use the Calibre's plugin to send epub in kepub format (xxx.kepub.epub)
The plugin is described here : https://www.mobileread.com/forums/sho...d.php?t=211135

I'll try to dump the rcS file as soon as possible.

Thanks again to take care