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

[Ken Maltby]

Originally Posted by gloriousglib

So I do get the crash after hitting the find books button - this doesn't happen the first time I search, but every subsequent time. The paths do line up correctly, however what I did is I copied the metafile and folders manually from my computer to my sd. I'm trying now to send the files directly from Calibre to the sd to see if that'll work (takes a while as I'm transferring 10,000 books lol).

I hope that is into a "hidden" folder. From what I have seen you really need to have calibre do it. Calibre will also manage the files relationship to the metadata folder it searches, so that any changes are properly applied.

If I were using this feature I would create a separate calibre library on my PC for my Kobo AuraHD. It would be a "Save to Disk" to a hidden folder on my device, probably on the external uSD card.

Luck;
Ken

[WS64]

Originally Posted by gloriousglib

So I do get the crash after hitting the find books button - this doesn't happen the first time I search, but every subsequent time. The paths do line up correctly, however what I did is I copied the metafile and folders manually from my computer to my sd. I'm trying now to send the files directly from Calibre to the sd to see if that'll work (takes a while as I'm transferring 10,000 books lol).

As long as you copy the metadata.calibre and the files together so that the structure is still intact this should still work.
And on no reason it should crash...
Like Ken I suggeest to use a hidden folder (starting with a .), that way Nickel will not take ages to process it.
And if the paths are fine it should at least open the books on the first search.

[Ken Maltby]

Chrox adds OPDS support. (Kindle only?) Calibre2opds, copds, are they part of the picture? Setting up a "store" on our own home networks? Lots of irons in the fire.

Luck;
Ken

[WS64]

Originally Posted by Ken Maltby

Chrox adds OPDS support. (Kindle only?) Calibre2opds, copds, are they part of the picture? Setting up a "store" on our own home networks? Lots of irons in the fire.

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...

[Ken Maltby]

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...

Interesting possibilities. I am getting a little concerned that the project might start to experience the effects of "bloat", it may just be me, but page turns seem to be getting slower. Part of it might be that I am on page 9028 of a 14,386 page anthology.

Koreader is getting to be a reader that has more useful features than any other available, as well as not being burdened with all the marketing based "features" of many.

Luck;
Ken

[serdar0020]

I've already mentioned this before, but koreader yet isn't able to handle the apostrophe " ' " in Arabic or Persian names, but always creates a line-break, embedded style on or off makes no difference. Using FW 3.8.0, built 2014.04-675

screenshot https://cdn.anonfiles.com/1410066330429.jpg

edit: joined GitHub, opened a thread https://github.com/koreader/koreader/issues/881

[WS64]

serdar, post it here: https://github.com/koreader/koreader/issues

[Ebri]

Originally Posted by Ken Maltby

Interesting possibilities. I am getting a little concerned that the project might start to experience the effects of "bloat", it may just be me, but page turns seem to be getting slower. Part of it might be that I am on page 9028 of a 14,386 page anthology.

Koreader is getting to be a reader that has more useful features than any other available, as well as not being burdened with all the marketing based "features" of many.

Luck;
Ken

After I set up everything for my Aura HD (btw I also changed readerfooter.lua (footer font size), for kindle it was fine, but Aura small for me, is it my only concern, if not I would propose to move it into defaults.lua), I checked today the sleep power consumption, tonight during about 10 hours battery depleted by 5-7% (after reboot it showed 7%), I haven't checked nickel but I remember lower amount.

Another question: when battery % is refreshed? I didn't see any change (I turned it to sleep yesterday on 67%, today, it was also on that level, exiting nickel presented the 62%).

[jpalacios]

Originally Posted by Ken Maltby

Interesting possibilities. I am getting a little concerned that the project might start to experience the effects of "bloat", it may just be me, but page turns seem to be getting slower. Part of it might be that I am on page 9028 of a 14,386 page anthology.

Not only page turns, but also changing font, font size, margin... is painfully slow in such books.

[Ken Maltby]

Originally Posted by jpalacios

Not only page turns, but also changing font, font size, margin... is painfully slow in such books.

Those changes redefine what each page will look like and how many pages there will be, in each chapter and in the whole book. They take some time but only need to be done the one time (unless you change your mind). In fact the time taken for those types of page definitions should make the page turning faster. When we are talking tens of thousands of pages, as opposed to the usual novel of less than 500 pages, a noticeable difference is to be expected.

The actual rendering of the next page should not be anything more than swapping page buffers. The next page image should have been built into a buffer by the time I've read the first couple of words on the current page.

There has been some changes in the code to render a page lately, I wonder if one of them might have slowed things down a bit?

Luck;
Ken

[NiLuJe]

@Ebri: To make it simple, let's say every 10 page turns.

[Ebri]

I read now a 1100 pages (on stock reader 850) book, and it is very slow on stock reader, and it seems annotating (why I used the kobo reader) makes the database unusable. So I am happy with koreader speed and not spoiling the database . (Though I will check it, as I used both stock reader and koreader when the database killed itself, but it is my understanding, that koreader does not change the files).

Does it cause problems to use kobo original reader and koreader on the same file usually?

[Ebri]

NiLuJe: Thank you, that explains why I had no change after 2-3 turns .

[WS64]

Originally Posted by NiLuJe

@Ebri: To make it simple, let's say every 10 page turns.

Maybe we should reset the counter after suspend...

[chrox]

Originally Posted by WS64

Maybe we should reset the counter after suspend...

Readerrolling has an onResume method which listens on the resume from screensaver event. But it only update battery info on the upper full progress bar. Probably we need the same function in readerfooter.