KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

[WS64]

Originally Posted by mmjoshi

The connect to folder menu is greyed out.

Might be that Calibre just can connect to one device (or folder) at a time.
So it should be available again when you disconnect your Kindle.
This is actually how I do it, I connect to a folder on my computer, then I use the Windows utility robocopy to sync this folder to my two Kobos.

[mmjoshi]

Originally Posted by WS64

Might be that Calibre just can connect to one device (or folder) at a time.
So it should be available again when you disconnect your Kindle.
This is actually how I do it, I connect to a folder on my computer, then I use the Windows utility robocopy to sync this folder to my two Kobos.

Finally got this working Amongst many things I tried, I guess what worked for me was deleting all the epub and djvu books from the device and the Calibre library and added them back. Of course I added these formats to Kindle supported formats as suggested by NiLuJe. Another thing I tried was to delete metadata.koreader as suggested by WS64. Also, added the path /mnt/us/ to the SEARCH_LIBRARY_PATH in defaults.lua and defaults.persistent.lua.

Now everything works perfectly well almost The only problem I am facing now is the following:

1. I search for books using the FM search books command. It finds the books correctly and can even open them.
2. However, if I try to use the search command again, the FM exits and comes back to KUAL. Just a minor nuisance

Anyway, thanks to the excellent support I received from the forum members

[NiLuJe]

@mmjoshi: 2. looks like a crash. What's in koreader/crash.log?

[mmjoshi]

Originally Posted by NiLuJe

@mmjoshi: 2. looks like a crash. What's in koreader/crash.log?

@NiLuJe these are the contents of crash.log. Hopefully, this gets fixed soon

./luajit: frontend/apps/filemanager/filemanagersearch.lua:331: bad argument #1 to 'gmatch' (string expected, got nil)
stack traceback:
[C]: in function 'gmatch'
frontend/apps/filemanager/filemanagersearch.lua:331: in function 'find'
frontend/apps/filemanager/filemanagersearch.lua:227: in function 'close'
frontend/apps/filemanager/filemanagersearch.lua:198: in function 'callback'
frontend/ui/widget/button.lua:154: in function 'action'
frontend/ui/uimanager.lua:270: in function 'checkTasks'
frontend/ui/uimanager.lua:296: in function 'run'
./reader.lua:207: in main chunk
[C]: in function 'dofile'
./koreader-base:22: in main chunk
[C]: at 0x0000bd75

[Doitsu]

While testing the PDF viewer I stumbled upon the following undocumented options whose function is not obvious from the context:

1. Settings > Writing Direction > LTR, RTL, TBRTL

What does TBRTL do?

(Note that the Document Language option is flush with the left screen border. Ideally, all options should be moved a couple of pixels to the right. Or simply shorten Document Language to Language.)

2. Page Crop > manual, auto, semi-auto

What's the difference between the auto and semi-auto options?

(Note that the auto and semi-auto buttons partially overlap each other.)

[WS64]

Originally Posted by mmjoshi

@NiLuJe these are the contents of crash.log. Hopefully, this gets fixed soon

./luajit: frontend/apps/filemanager/filemanagersearch.lua:331: bad argument #1 to 'gmatch' (string expected, got nil)
stack traceback:
[C]: in function 'gmatch'
frontend/apps/filemanager/filemanagersearch.lua:331: in function 'find'
frontend/apps/filemanager/filemanagersearch.lua:227: in function 'close'
frontend/apps/filemanager/filemanagersearch.lua:198: in function 'callback'
frontend/ui/widget/button.lua:154: in function 'action'
frontend/ui/uimanager.lua:270: in function 'checkTasks'
frontend/ui/uimanager.lua:296: in function 'run'
./reader.lua:207: in main chunk
[C]: in function 'dofile'
./koreader-base:22: in main chunk
[C]: at 0x0000bd75

I can't confirm this, neither on the emulator nor on my Kobos.
I can search as often as I want, no problems at all...

[Ebri]

Yesterday pressing "browse tags" caused also a crash for me on PW2 (I returned back to the list of books view, with no refresh, when I touched the unchanged screen, one of my books was revealed and opened.) Shoudl I search for logs, or this feature is yet experimental?

[mmjoshi]

Originally Posted by WS64

I can't confirm this, neither on the emulator nor on my Kobos.
I can search as often as I want, no problems at all...

On my Kindle Touch, this happens very consistently . Do you need any more information to identify the problem?

Any other users of Kindle Touch having this issue?

[WS64]

@mmjoshi, do you use tags in Calibre?
If your metadata.koreader file (in the temp dir) is not too big, can you zip it send it to me in PM? Then I can try searching with your book-data.

[WS64]

Originally Posted by Ebri

Yesterday pressing "browse tags" caused also a crash for me on PW2 (I returned back to the list of books view, with no refresh, when I touched the unchanged screen, one of my books was revealed and opened.) Shoudl I search for logs, or this feature is yet experimental?

A crash will exit Koreader completely, not go back to the File Manager. So I don't think there really was an error.

[WS64]

I got mmjoshi's file. But I still am not able to reproduce this issue. So I guess it is Kindle-related. I am afraid I can't help at all here.

[mmjoshi]

Originally Posted by WS64

I got mmjoshi's file. But I still am not able to reproduce this issue. So I guess it is Kindle-related. I am afraid I can't help at all here.

Oh shoot, that's bad. Hopefully some of the Kindle experts can help.

[knc1]

Originally Posted by mmjoshi

Oh shoot, that's bad. Hopefully some of the Kindle experts can help.

There is more than one model called a: "Kindle Touch" here.

Start by giving us the first four characters of your serial number and the version of the firmware you are running.

[mmjoshi]

Originally Posted by knc1

There is more than one model called a: "Kindle Touch" here.

Start by giving us the first four characters of your serial number and the version of the firmware you are running.

The first 4 characters of the serial number are B011 and the firmware version is 5.3.7.2.

[ssholloway]

I've tried to update to the latest nightly build (688) using the OTA option in filemanager. I get the prompt to verify I want to update to 688, then the message about the download taking some minutes. After a short time, the downloading message disappears but when I check the version installed, it still shows the older one (605). I also don't see the OPDS menu that should be in 688 so it's clear the OTA update didn't work. The header of the koreader-kindle-latest-nightly.zsync file says 688 so it appears the update was downloaded, just not applied. I also tried using the update koreader option in KUAL after doing the OTA download but that says there is no update file. I'm sure I'm missing something but I can't figure out what it is. I manually updated to 688 so I can't recreate the problem until there is a newer nightly. Thanks.