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

[chrox]

Originally Posted by WS64

Not Kindle only, but simply not part of 680 yet but of 688 which is not yet available for download for Kobo.
Testing it right now. Although downloading seems to work I can't find the books on the device or anywhere...

The filemanger is not refreshed after exiting from OPDS catalog, so you need to re-enter the download directory to find the downloaded file.

[Ebri]

A question on suspend: I checked Nickel consumption during sleep, and it was on the 1% / night level, while koreader eats around 5% per night (aura hd, 3.8.0). Light is turned off at suspend. Should I turn off sg. to decrease consumption? (Or first of all, is it normal or sg. is wrong with my setup?)

[Ebri]

Is it possible somehow to store books differently on the SD card and on the device? (I would upload all my books to the SD, but if Nickel sees it, database refresh takes half day, in case of database error another half day. Some of them I would also like to see from Nickel, so easiest solution would be hidden directory on the SD, visible on the device. Is it possible, or only by changing the template for every upload?)

(I hope it is not off topic, as it relates to both Calibre and koreader).

[WS64]

Ebri, you could attach the SD card directly to your computer (no reader) and connect to folder. As a folder name you choose one starting with a dot (e.g. ".hidden")

[Ken Maltby]

Originally Posted by WS64

Ebri, you could attach the SD card directly to your computer (no reader) and connect to folder. As a folder name you choose one starting with a dot (e.g. ".hidden")

In calibre you would use the "Save to Disk" not save to device. You can have the two calibre managed libraries, one on the device's internal memory and one on the external uSD card. Any library files or folders inside a "hidden" folder will not be subject to the kobo processing. (For most it is convenient to create the hidden folder on the external uSD card.)

Luck;
Ken

[embryo]

A question for the developers.

Is there a way (a setting in some lua file) to make koreader use my custom cover for Pdf files but continue to use the ones from the epubs.
The reason for that is that many of my pdfs don't have covers, or if they have they're not so good.

[WS64]

Originally Posted by Ken Maltby

In calibre you would use the "Save to Disk" not save to device.

With "save to disk" you will have no control which books are already on the device, I think "connect to folder" is a way better way.
The downside is that you can't use it while the reader is connected, unless you disable the Kobo driver (I have it disabled, I'm done with Nickel!)

[WS64]

Originally Posted by embryo

A question for the developers.

Is there a way (a setting in some lua file) to make koreader use my custom cover for Pdf files but continue to use the ones from the epubs.
The reason for that is that many of my pdfs don't have covers, or if they have they're not so good.

I don't think we will have a general way to do that.
If you want to change the code (after each nightly) edit frontend/ui/screensaver.lua and change this function:

function Screensaver:getCoverImage(file)
    local ImageWidget = require("ui/widget/imagewidget")
    local doc = DocumentRegistry:openDocument(file)
    if doc and (string.lower(string.match(file, ".+%.([^.]+)") or "")=="epub") then
        local image = doc:getCoverPageImage()
        doc:close()
        local extension =  or "")
        if image then
            return ImageWidget:new{
                image = image,
                width = Screen:getWidth(),
                height = Screen:getHeight(),
            }
        end
    end
end

Havn't tested it, but it should make sure that your epubs show their covers and all other files your defualt cover. You could change it also to ~="pdf" instead of =="epub"...

[embryo]

Originally Posted by WS64

Havn't tested it, but it should make sure that your epubs show their covers and all other files your defualt cover. You could change it also to ~="pdf" instead of =="epub"...

Thank you.
Tried both ~="pdf" and =="epub"
Suspend crashes back to KSM

./luajit: error loading module 'ui/screensaver' from file 'frontend/ui/screensaver.lua':
	frontend/ui/screensaver.lua:16: unexpected symbol near 'or'
stack traceback:
	[C]: at 0x00041881
	[C]: in function 'require'
	frontend/ui/device.lua:206: in function 'onPowerEvent'
	frontend/ui/uimanager.lua:69: in function 'handler'
	frontend/ui/uimanager.lua:430: in function 'run'
	./reader.lua:162: in main chunk
	[C]: in function 'dofile'
	./koreader-base:22: in main chunk
	[C]: at 0x0000bd85

Is it because of the 2 spaces before 'or'
or the whole 'local extension = or "")' line?

Update: It works!
Commented out the 'local extension = or "")' line.

[WS64]

Yes, the ' or ""' is not necessary here. I just copied it lazily from a few lines below where it was necessary. Hard to keep track of the opening and closing brackets...

[Ebri]

Thank you Ken and WS64, and I like better connecting as device. But I am not done (yet?) with Nickel due to sleep time consumption of KOReader, if it would be the same as nickel, probably I would. Though I have only one problem with nickel, that it is very slow (both highlight and pageturn).

[embryo]

This is just a request:

Is it possible to have a History entry in the reader's menu (while reading a book).

I often find myself reading two or more parallel books and every time I want to switch between them I have to exit to file manager, find the other book and open it.

I don't know if its against the logic of the UI design, but I think it could be practical.

[hawhill]

There _is_ a history in the file manager, though. You've seen that already? I'm just a bit unsure because you talk about "finding" the other book. Placing this (or rather, such a) document history in the menu of the document viewer is a bit more work - and I'm not so sure if it isn't overloading the user interface a bit.

[embryo]

Originally Posted by hawhill

There _is_ a history in the file manager, though. You've seen that already? I'm just a bit unsure because you talk about "finding" the other book. Placing this (or rather, such a) document history in the menu of the document viewer is a bit more work - and I'm not so sure if it isn't overloading the user interface a bit.

Yes, I was referring to the History entry in file Manager, sorry for not putting it more clear.
About the UI, I was thinking that the 'CD-like' icon in the menu has 4 entries in the File Manager (History, OTA update, Version and Help) but only the three latter when you're reading a book, so maybe its an improvement on consistency.

[WS64]

Originally Posted by hawhill

There _is_ a history in the file manager, though. You've seen that already? I'm just a bit unsure because you talk about "finding" the other book. Placing this (or rather, such a) document history in the menu of the document viewer is a bit more work - and I'm not so sure if it isn't overloading the user interface a bit.

I'm pretty sure he wants the history not in the file manager menu but additionally in the reader menu itself.
I am not sure that this really would be as quick as it sounds on first sight because the thing that really takes time is the actual opening of the book. The one click more to leave the reader does not count that much in my opinion...