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

[Markismus]

Originally Posted by mkeles84

Today, I discovered a strange feature about Koreader.
I had bougt used Kobo Glo last week. And it sometimes was being frozen after half an hour later or 5 minutes later. Then factory reset and I downgrade to 3.13.1 but frozen again.

Finally, I set up Koreader, and no freezing while koreader kernel.
Then I passed to nickel kernal 3.13 to use, no freezing.

Again, factory reset and install 3.18, frozen again,
install koreader no frozen, and nickel kernel no frozen 3.18
It is really incredible.

Normally, one would assume the frozen effect would have been demonstrated to be independent of firmware now. The incredibility would than be due to the confrontation with an assumption without the gumption to falsify it.

As my mothers Glo has a similar frozen effect and it cannot be removed by reinstalling and changing firmwares, too, might I suggest that the deterioration of the hardware of the Glo causes a crash in Kobo Nickel?

My first suggestion would be to replace the SD-card. The two strong points of that suggestion is that is an known occurrence for SD-card to deteriorate. Secondly, it is easily done.

For the replacement of the SD-card I would suggest the threads dealing with Kobo
Glo memory upgrade, such as the one here.

EDIT:
I just had a frozen Glo while in KoboStartMenu8.2. So either that KSM8.2 is not stable or the frozen effect manifests itself in other software than Nickel. That last option would really push me over the edge to replace that SDcard.

After reinstalling the Glo, I read an entire book without any crashes and now in the last 3 hours---after my little girl of three played with it and hid it between the screen and keyboard of her laptop (cost me 30 minutes to find it again)---it keeps freezing on me. Maybe the Glo is allergic to little girls. My mother had them at her house quite regularly, too!

EDIT2:
Searching through the forum I found others that had this problem. In the linked thread it is suggested that it is indeed hardware failure.
That makes this question OFF-TOPIC in this koreader thread. You could make a new thread with your problem.

[Yaretzki]

I wonder if it's possible or how difficult it would be to implement additional feature in statistics section: time to read.
There is already everything to calculate it:
- average time per page
- pages left in book
By combination of above it is easy to get rough estimation of time left to read book.
But I don't know how difficult it would be to implement it in statistic - current, and into status bar as additional information on top of already existing ones.
Y.

[Alan_S]

If it would be possible, I'd like to see this new statistic in status bar.

[WolfBack]

My scenes brake line (empty line between scenes) is not longer work in the latest version of Koreader... again...
A few months ago I was trying to figure out how this can be working and at last I do some changes in all of my books, adding the code below in every line that indicate a scene brake:

<div class="calibre1">
    <br />
  </div>

Everything went fine and I do have a empty line in every scene; until the latest version of Koreader. Those empty lines disappeared again.
What have I do this time? I must apply a different code in all of my books (I hope not again), or I can change a setting in Advanced Setting in Koreader itself and make it behave as the previous version?

[jbaumann]

Hi,

I have installed the newest stable version of koreader and am quite happy. When I read PDFs, though, then they are rendered over the full screen of my Kobo Glo, without any margin at the top or the bottom. This is less than perfect if I want to have the minibar, which then is rendered over the last line of the current page. What do I have to change to get margins at the top and the bottom?

Cheers, Joe

[Yaretzki]

Originally Posted by Yaretzki

I wonder if it's possible or how difficult it would be to implement additional feature in statistics section: time to read.
There is already everything to calculate it:
- average time per page
- pages left in book
By combination of above it is easy to get rough estimation of time left to read book.
But I don't know how difficult it would be to implement it in statistic - current, and into status bar as additional information on top of already existing ones.
Y.

Hello,
I did some tests trying to get what I wrote above. Here is what I was able to get:
- edit file main.lua in statistic folder (under plugins folder of koreader)
- add additional line under line #238
- text of additional line:
table.insert(stats, { text = _("Time to read"), mandatory = self:secondsToClock((self.data.pages - tableutil.tablelength(self.data.details)) * (self.data.total_time / tableutil.tablelength(self.data.details))) })

As a result I see additional information in Statistic menu -> Current: Time to Read"

I'm really surprised I was able to do it because my "programming" skills are 0 or even less!
Do it with your file and enjoy!

PS
But I have no idea how to put it on status bar

Y.

[Ken Maltby]

Originally Posted by Yaretzki

Hello,
I did some tests trying to get what I wrote above. Here is what I was able to get:
- edit file main.lua in statistic folder (under plugins folder of koreader)
- add additional line under line #238
- text of additional line:
table.insert(stats, { text = _("Time to read"), mandatory = self:secondsToClock((self.data.pages - tableutil.tablelength(self.data.details)) * (self.data.total_time / tableutil.tablelength(self.data.details))) })

As a result I see additional information in Statistic menu -> Current: Time to Read"

I'm really surprised I was able to do it because my "programming" skills are 0 or even less!
Do it with your file and enjoy!

PS
But I have no idea how to put it on status bar

Y.

You could go to GitHub and look through "Issues", you might have already answered someone's Feature Request (FR), if there is no open issue you could make your own and include your working solution. Someone there could add it to the status bar.

Good work, by the way.

Luck;
Ken

[mkeles84]

I'm new at Koreader, bu I can't change fonts while reading e-books. I choose fonts in the font list, see check image near item but no change on e-books. Sorr for silly question.

[Ken Maltby]

Originally Posted by mkeles84

I'm new at Koreader, bu I can't change fonts while reading e-books. I choose fonts in the font list, see check image near item but no change on e-books. Sorr for silly question.

There could be several factors that have that result, but there are Koreader settings that can get around them.

One thing could be if the book's CSS has set an embedded font as "default" or !important. You can try using the bottom reader menu gear icon and turn "Embedded Style" off, and then go to the File Manager and then use "History" menu to return to your book. Then try to change the font. You may have to change the font size a step and wait to see it change all the text, then you can change it back if you want. (Or go to the File Manager and back.)

If that doesn't work you can use the top reader menu page icon "Set render style" option "clear all external styles" selection, and try again.

Luck;
Ken

[jbaumann]

Oops, I forgot to mention that I use PDF reflow...

Cheers, Joe

Originally Posted by jbaumann

Hi,

I have installed the newest stable version of koreader and am quite happy. When I read PDFs, though, then they are rendered over the full screen of my Kobo Glo, without any margin at the top or the bottom. This is less than perfect if I want to have the minibar, which then is rendered over the last line of the current page. What do I have to change to get margins at the top and the bottom?

Cheers, Joe

[Ken Maltby]

Originally Posted by jbaumann

Oops, I forgot to mention that I use PDF reflow...

Cheers, Joe

There are bottom menu items, for PDFs especially, that allow you to adjust margins, line spacing, word gap, text alignment, and others such as those. The selection range for most such adjustments can be modified using the "Advanced options". The "Mini bar" at the bottom of the page can be dismissed and recalled by tapping the bottom right corner.

Luck;
Ken

[jbaumann]

Hi,

I tried those but no matter how high I set the lower and upper margin nothing changes. The right and the left margin can be changed though...

Cheers, Joe

Originally Posted by Ken Maltby

There are bottom menu items, for PDFs especially, that allow you to adjust margins, line spacing, word gap, text alignment, and others such as those. The selection range for most such adjustments can be modified using the "Advanced options". The "Mini bar" at the bottom of the page can be dismissed and recalled by tapping the bottom right corner.

Luck;
Ken

[Ken Maltby]

Originally Posted by jbaumann

Hi,

I tried those but no matter how high I set the lower and upper margin nothing changes. The right and the left margin can be changed though...

Cheers, Joe

See my reply to your PM.

Luck,
Ken

[WolfBack]

Originally Posted by WolfBack

My scenes brake line (empty line between scenes) is not longer work in the latest version of Koreader... again...
A few months ago I was trying to figure out how this can be working and at last I do some changes in all of my books, adding the code below in every line that indicate a scene brake:

<div class="calibre1">
    <br />
  </div>

Case is closed!
I decide to replace the code above in all of my books with:

<p class="calibre1">&nbsp;</p>

This is actually works in Koreader and the results is a blank space between the scene brakes.
(In Nickel I have a 4 blank space lines instead of 1...)... strange...

[jbaumann]

Hi,

tested everything you pointed out, but the problem remains.

Regardless of which of the DCREREADER_CONFIG_MARGIN_SIZES_* I use, when rendering PDFs the upper and lower margins are not used (left and right work ok), and with EPubs all margins are handled as expected. Should I open an issue at the Github repository or is there anything that I don't see?

Second question: I would like to have a larger font for the minibar and tried to set both DMINIBAR_CONTAINER_HEIGHT and DMINIBAR_FONT_SIZE to a higher value, but this had no effect...

Cheers, Joe

Originally Posted by Ken Maltby

See my reply to your PM.

Luck,
Ken