Koreader running on Kobos (all of them, hopefully!)

[Markismus]

Originally Posted by gong

Otherwise, is there a way to change the page overlap to some arbitrary value? And also a way not to dim the overlapped part??

Chrox answered this here.

[xping]

Hi.

On kobo aura (2013) I'm experiencing progressive slowing down in text reflow (pdf).

For the first 5/10 pages, the speed of page turning is ok as well as menu response.

After some time the device stops responding and I have to force turn off and boot again.

Any clue?

(Kobo aura 2013, 3.1.1 firmware)

[Markismus]

Originally Posted by xping

Hi.

On kobo aura (2013) I'm experiencing progressive slowing down in text reflow (pdf).

For the first 5/10 pages, the speed of page turning is ok as well as menu response.

After some time the device stops responding and I have to force turn off and boot again.

Any clue?

(Kobo aura 2013, 3.1.1 firmware)

Interesting. Does it do this with all your pdf-files?

Could you create an new issue on github with ideally this problem description, a link to the pdf-file that generates the bug, a link to your koreader.log for the entire session between starting of koreader and forced turn off?

Please mention that you have a Kobo Aura HD, instead of Kobo Aura (2013).

[xping]

Originally Posted by Markismus

Interesting. Does it do this with all your pdf-files?

Could you create an new issue on github with ideally this problem description, a link to the pdf-file that generates the bug, a link to your koreader.log for the entire session between starting of koreader and forced turn off?

Please mention that you have a Kobo Aura HD, instead of Kobo Aura (2013).

I'm going to open create new issue on github. For now I can say that crash,log contains only "killed" just as if It was stoppet by powering off (?)....
The question is that after some pages kobo aura (not hd) becomes so slow (not responsive) that every command is executed with a delay of (increasing seconds). It happens only with text reflow of pdfs (the interested pdf is a small one - 16 pages - Melville's "Bartleby").
Is just like if a sort of "buffer" become full and every command is processed with delay.

[hawhill]

Sounds like a memory issue. Is this the latest release?

[ktv]

Originally Posted by xping

I'm going to open create new issue on github. For now I can say that crash,log contains only "killed" just as if It was stoppet by powering off (?)....
The question is that after some pages kobo aura (not hd) becomes so slow (not responsive) that every command is executed with a delay of (increasing seconds). It happens only with text reflow of pdfs (the interested pdf is a small one - 16 pages - Melville's "Bartleby").
Is just like if a sort of "buffer" become full and every command is processed with delay.

I have the same problem.
Kobo aura hd with 2.8.1 firmware

[xping]

Originally Posted by hawhill

Sounds like a memory issue. Is this the latest release?

Yes, it is build 806. Going to try 810.

May we try to close ALL processes before launching Koreader???

[xping]

Originally Posted by xping

Yes, it is build 806. Going to try 810.

May we try to close ALL processes before launching Koreader???

Ok the problem persists in 810 built.

I played with this issue and now I know that it is present only if I use bigger fonts.

it seems like if bigger is the font, slower is the device, but if I activate only reflow mode without resizing font, the device is fast and responsive

thx

[Ken Maltby]

Originally Posted by xping

Yes, it is build 806. Going to try 810.

May we try to close ALL processes before launching Koreader???

I am using these in my koreader_kobo.sh:

# Decrease the reasons for crashes. Search forum for cgm999's explanation.
exec 3<&-

# Stop nickel and related processes
killall -STOP nickel
killall adobehost
killall dbus-daemon
killall Hindenburg

That should get almost all of the processes and close any files open for writing.

Luck;
Ken

[PeterT]

Ken; I might well be wrong, but I don't think that the "killall -STOP nickel" would close any files that nickel had open for writing; it will just ensure that the process is paused leaving all resources that it had open, open.

[Ken Maltby]

Originally Posted by PeterT

Ken; I might well be wrong, but I don't think that the "killall -STOP nickel" would close any files that nickel had open for writing; it will just ensure that the process is paused leaving all resources that it had open, open.

3<&- means that file descriptor 3, opened for writing(same as stdout), is closed.

http://pubs.opengroup.org/onlinepubs...ties/exec.html

Luck;
Ken

[michald]

Howdy all.
I believe I found a way to run koreader and nickel from kobo launcher with a fully operational touchscreen in all. Steps below. Appreciate any feedback.

This method involves writing a custom script into /tmp/exec.sh when koreader or nickel buttons are pressed in kobo launcher followed by terminating kobo launcher. When the launcher exits the custom script executes and launches the other software.

1) Add the following script as /usr/local/KoboLauncher/exec.sh

#!/bin/sh

F="/tmp/exec.sh"
echo "#!/bin/sh" > $F
echo "exec $1" >> $F
chmod +x $F
killall launcher

2) Add the following to kobolauncher applications.ini

Koreader = /usr/local/KoboLauncher/exec.sh "/usr/local/Koreader/koreader_kobo.sh /mnt"
Kobo Software = /usr/local/KoboLauncher/exec.sh "/usr/local/Kobo/nickel -qws -skipFontLoad"

3) Run Kobolauncher from the startup script /etc/init.d/rcS (or other) via the following code, appended to the end of rcS, instead of the default nickel (i left the hinderburg process running at all times):

(cd /usr/local/KoboLauncher; while [ 1 ]; do ./KoboLauncherA.sh; if [ -e /tmp/exec.sh ]; then /tmp/exec.sh; rm /tmp/exec.sh; fi; done) &

NOTE THE BRACKETS ABOVE!!!

4) To execute koreader or nickel from kobo launcher, press "Koreader" or "Kobo Software" button in launcher. Koreader or nickel should launch.

5) You may have to change /usr/local/KoboLauncher paths above to the correct path where kobo launcher is installed on your device.

BTW. Great thread. I am enjoying my hacked linux kobo (which ran android before however it was too slow for me).

EDIT: Changed so that koreader and nickel execute directly after pressing the button

[Ken Maltby]

I was thinking that if the history folder were on the external uSD card along with the ebooks, then you could take your SD card from device to device, running Koreader, and have the same reading settings and position. Perhaps the program could check if there is a .History folder in the SD root and use that one, over the internal one?

Luck;
Ken

[sergeyvl12]

Originally Posted by michald

#!/bin/sh

F="/tmp/exec.sh"
echo "#!/bin/sh" > $F
echo "exec $1" >> $F
chmod +x $F
killall launcher

I provided more nice way to exit launcher:

echo "exit" > $VLASOVSOFT_FIFO

Please try.

[Markismus]

Originally Posted by Ken Maltby

I was thinking that if the history folder were on the external uSD card along with the ebooks, then you could take your SD card from device to device, running Koreader, and have the same reading settings and position. Perhaps the program could check if there is a .History folder in the SD root and use that one, over the internal one?

Luck;
Ken

In koreader/frontend/apps/filemanager you can find filemanagerhistory.lua. On line 61:

local history_dir = "./history/"

You could manually edit the file to point to wherever, or use the startup script to check whether there is another history directory with newer files and than use sed to edit the line before starting koreader and reverse it to normal after.

I think you could also write the whole thing at that point in the script.

Your main problem is probably motivation as your sdcard is only a little more mobile than your reader. With the chance of small things getting lost it is probably even less effectively mobile for reading.