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

[NiLuJe]

@nasser: That's perfetcty normal. It restarts the *framework* on exit, else you'd be looking at a black screen . Because no framework, means, well, what's written on the box: the framework is down .

[nasser]

Thanks.. the restart also seems quicker than the usual "press for 20+ seconds" version..

[Aeris]

Because it only restarts the framework, not the all system

[Antoinekamel]

The KOReader is beautifully made to read PDFs! With this latest version (I haven't used it for some time), there is the Go To Option, the frontlight control and, mainly, the speed to read PDFs! It's usable as ever! Thanks, devs!

[flashmozzg]

Is it supposed to lag on K5? Sometimes pages turn fast (1-2 secs), and sometimes it takes 10-15 secs to load next page, so i don't even know if i pressed right. Doesn't depend on page. With latest nightly. Anyway, thanks for this beatiful program. Had to switch to it, after default pdf reader couldn't render fonts correctly (some chars were missing and overall quality was bad with every word pixilated)

P.S. Is there a way to check your battery % inside this app? (like in cr3 for example).

[knc1]

Originally Posted by flashmozzg

Is it supposed to lag on K5? Sometimes pages turn fast (1-2 secs), and sometimes it takes 10-15 secs to load next page, so i don't even know if i pressed right. Doesn't depend on page. With latest nightly. Anyway, thanks for this beatiful program. Had to switch to it, after default pdf reader couldn't render fonts correctly (some chars were missing and overall quality was bad with every word pixilated)

P.S. Is there a way to check your battery % inside this app? (like in cr3 for example).

The kindle only uses power during page turns.
And the battery is good for many thousands of page turns.
You aren't likely to effect its charge level by reading a long pdf.

Ah, but to answer your question: I don't know the answer.

[flashmozzg]

It turns out that this problem(lags) I only experience with certain pdf, so it's probably its fault (in native reader there were bugs with fonts in this pdf, they were pixelated and some random letters were missing). Don't know what's the cause, though.

[hawhill]

PDFs can be difficult - they might be (sometime: overly) complex, have high-res graphics which need *lots* of memory to render and can have so many objects on a single page that they might need a looooong time to load. Not much we can do there from an implementer's perspective, unfortunately.

[flashmozzg]

Yeah, it's probably that. But i had no problem with all my other files and the fact that even native reader has some problems is suspicious.

Anyaway, I have few stupid questions: what is the difference between "none" and regular versions of nightly builds? And is where a changelog somewhere?

[h1ro]

There might be programs for your OS that you can use to compress large images in pdfs and fix problems with e.g. fonts. Then you get a smaller or simpler pdf and koreader might work better.

Most pdfs I read are fine out of the box though.

[hawhill]

Yep. I overlooked the questions that have been asked:
- there are no "none" and "regular" versions: it's just a change in the naming scheme for the same thing. There _is_ a difference between the Kindle and the Kobo versions, however. The "none" in the name is just part of the compiler architecture string.
- the changelog for the nightlies is the changelog of the sourcecode: https://github.com/koreader/koreader/commits/master - some read rather technical, new features or fixed bugs should be recognizable, though.

Maybe it's time we do a formal release, though.

[mmjoshi]

Some one had posted how to edit the cr3.ini to get the clock shown in the statusbar by setting "clock" to 1. It was fine till some days back. However, the in the recent nightlies, the clock is not shown even though this is done. I am using 5.3.7 and the latest nightly. Do I need to do something different?

mj

[Turtledog]

This is not working at all.

I get an error when using:

make TARGET_DEVICE=KOBO koboupdate

This is the result:

make -C koreader-base
make[1]: Entering directory `/home/<user>/koreader/koreader-base'
# To recap: build its TARGET_CC from CROSS+CC, so we need HOSTCC in CC.
# Build its HOST/TARGET_CFLAGS based on CFLAGS, so we need
# a neutral CFLAGS without arch
make -j2 -C luajit-2.0 \
		CC="gcc" HOST_CC="gcc -m32" \
		CFLAGS="-O2 -ffast-math -pipe -fomit-frame-pointer" HOST_CFLAGS="-march=native -O2 -ffast-math -pipe -fomit-frame-pointer" \
		TARGET_CFLAGS="-O2 -ffast-math -pipe -fomit-frame-pointer -march=armv6j -mtune=arm1136jf-s -mfpu=vfp -marm -mfloat-abi=hard -fno-stack-protector -U_FORTIFY_SOURCE -D_GNU_SOURCE -fno-finite-math-only -DKOBO_PLATFORM" \
		TARGET_FLAGS="-DLUAJIT_NO_LOG2 -DLUAJIT_NO_EXP2" \
		CROSS="arm-linux-gnueabihf-"
make[2]: Entering directory `/home/<user>/koreader/koreader-base/luajit-2.0'
==== Building LuaJIT 2.0.2 ====
make -C src
make[3]: arm-linux-gnueabihf-gcc: Command not found
make[3]: Entering directory `/home/<user>/koreader/koreader-base/luajit-2.0/src'
make[3]: arm-linux-gnueabihf-gcc: Command not found
make[3]: arm-linux-gnueabihf-gcc: Command not found
make[3]: arm-linux-gnueabihf-gcc: Command not found
make[3]: arm-linux-gnueabihf-gcc: Command not found
make[3]: arm-linux-gnueabihf-gcc: Command not found
Makefile:231: *** Unsupported target architecture.  Stop.
make[3]: Leaving directory `/home/<user>/koreader/koreader-base/luajit-2.0/src'
make[2]: *** [default] Error 2
make[2]: Leaving directory `/home/<user>/koreader/koreader-base/luajit-2.0'
make[1]: *** [build//luajit] Error 2
make[1]: Leaving directory `/home/<user>/koreader/koreader-base'
make: *** [koreader-base/build//luajit] Error 2

Can anyone give a good explanation how to install this? (on a kobo glo)

[NiLuJe]

@Turtledog: You're confusing 'using' and 'building' .

The devteam provides nightlybuilds so, as an user, you don't have to enjoy the wonderful thing that is cross-compilation.

On the other hand, if you do want to help write some code, you will have to use a properly set-up cross-compilation environment. (Can't say what's used on the Kobo, I think the Kobo guys share one, but on the Kindle, a good bet is the next-to-last CodeSourcery TC).

TL;DR: Read the docs . [As can be guessed from my profile card and the location of this thread, I'm quite unfamiliar with the process on Kobo devices ].

[giorgio130]

Originally Posted by Turtledog

This is not working at all.

I get an error when using:

make TARGET_DEVICE=KOBO koboupdate

You are missing a toolchain:

arm-linux-gnueabihf-gcc: Command not found

However, as NiLuJe said, if you just want to use koreader you don't have to go through building it. Just download the latest nightly with "kobo" in its name, there's a README inside that details the installation steps.