Mobileread
PocketBook-KOReader: a document reader for PDF, DJVU, EPUB, FB2, CBZ, ... (AGPLv3)
#11  sadowski 01-19-2015, 07:07 AM
Same crash log on a PB 515 (mini) with FW 4.4
Reply 

#12  WS64 01-19-2015, 07:10 AM
@chros, I'd prefer not to, since 5.2 is pretty useless since neither FBReader nor Coolreader run on it (I am still surprised that Koreader does, I thought PB had removed that option completely).
Since 5.2 also seems slower it would be better to get Koreader on PB running on GLIBC_2.9.
I'll ask at the German forum though, I guess there are enough people still on 5.2!
Reply 

#13  chrox 01-19-2015, 10:02 AM
Quote WS64
@chros, I'd prefer not to, since 5.2 is pretty useless since neither FBReader nor Coolreader run on it (I am still surprised that Koreader does, I thought PB had removed that option completely).
Since 5.2 also seems slower it would be better to get Koreader on PB running on GLIBC_2.9.
I'll ask at the German forum though, I guess there are enough people still on 5.2!
OK, by simply grepping GLIBC_2.* strings from 4.* and 5.* firmware update binaries, I found that 5.* firmware is targeted to GLIBC 2.9 while 4.* firmware is targeted to GLIBC 2.5. Since the original koreader for PocketBook uses some functions from GLIBC 2.7, it should work on firmware 5.* but not 4.*.

A new preview build has been uploaded to support PocketBook 4.* firmware by disabling those GLIBC_2.7 function calls.

@WS64 Could you test if 2014.11-38-preview works on your firmware 4.4?
Reply 

#14  sadowski 01-19-2015, 10:16 AM
The new build does not crash but the display is distorted and completely unreadable as if it would work with wrong assumptions about display lines and pixels. But it responds to page forward/backward.

On a PB 515 (mini), FW 4.4.
Reply 

#15  chrox 01-19-2015, 10:48 AM
Quote sadowski
The new build does not crash but the display is distorted and completely unreadable as if it would work with wrong assumptions about display lines and pixels. But it responds to page forward/backward.

On a PB 515 (mini), FW 4.4.
Could you also post a screenshot of koreader on your device? It would make debugging much easier.
Reply 

#16  sadowski 01-19-2015, 11:05 AM
The screenshot is blank, obviously dumping a different buffer than koreader is using. I need to get hold of a camera to take an external shot.

It looks to me as if something like the pixel depth (bpp) or so is wrong. Like all pixels are extremely smeared out along the lines.

The log file says "xres=600 yres=800 bpp=4 vdepth=8". The first three are as I would assume (600x800, 16 shades of grey). I do not know what vdepth is and whether this is correct.

Jens
Reply 

#17  WS64 01-19-2015, 11:49 AM
I got the same answer for PB Lux 2 with 5.2: some distored lines, unreadable.

Crash log:
Quote
Atached mp shm: id 0 addr 400cb000 size 18284
----------------> USING A2PLUS MODE <-----------------
attach_shm: mtfb key=251330798 size=833044
Atached mtfb shm: id 68008 addr 407bd000 size 833044
-------------------------
The task - koreader.app have
xres=758 yres=1024 bpp=4 vdepth=8
-------------------------
ndepth:4 hqdepth:4 orientation:0
attach_shm: ref key=2130378752 size=776192
Atached ref shm: id 8001 addr 408ad000 size 776192
[INFO] [/srv/einkbuild/test_build/ebrmain_build/inkview/src/partners.c:28: init_partner]Partner from device.cfg is Osiander
[INFO] [/srv/einkbuild/test_build/ebrmain_build/inkview/src/partners.c:35: init_partner]Partner is set to osiander
OpenTheme: /ebrmain/themes/.default.pbt
ts: loading default calibration values
Atached mqueue: id 8001
./luajit: frontend/device/input.lua:488: interrupted!
stack traceback:
frontend/device/input.lua:488: in function 'waitEvent'
frontend/ui/uimanager.lua:477: in function 'run'
./reader.lua:138: in main chunk
[C]: at 0x0000bdf1
Reply 

#18  sadowski 01-19-2015, 12:14 PM
And this is how it looks like:
shot.jpg 
Reply 

#19  chrox 01-19-2015, 01:04 PM
Quote sadowski
And this is how it looks like:
Yes, it looks like the pitch size (bytes for a single line) is detected wrong, more precisely pitch size is less than actual one used in the framebuffer device otherwise the application would very likely have already crashed.

So you can just hack this line: https://github.com/koreader/koreader-base/blob/master/ffi/framebuffer_linux.lua#L64 in the "koreader/ffi/framebuffer_linux.lua" file at line 64:

Code
elseif vinfo.bits_per_pixel == 8 then self.bb = BB.new(vinfo.xres, vinfo.yres, BB.TYPE_BB8, self.data, finfo.line_length)
else
this way:
Code
elseif vinfo.bits_per_pixel == 8 then self.bb = BB.new(vinfo.xres, vinfo.yres, BB.TYPE_BB8, self.data, finfo.line_length + 4)
else
or:
Code
elseif vinfo.bits_per_pixel == 8 then self.bb = BB.new(vinfo.xres, vinfo.yres, BB.TYPE_BB8, self.data, finfo.line_length + 8)
else
until you make it right.
Reply 

#20  wirtold 01-19-2015, 01:50 PM
OK, i've tested version v2014.11-39 on PocketBook InkPad 840 and it works very well. And there is even a small surprise: traslation in Polish - great! No problems with touch control anymore, everything is fast and smooth - just can't belive that

Some comments:
- I think there should be option to disable/reduce momentum on scroll - sometimes i've encountered an effect like it starts accelerating and scrolling too much (after releasing finger) and it becomes uncontrollable.

- I don't know if any multitouch controls are implemented, but i can't get any to work. When i'm trying the only effect is text marking or screen repaint.

- And i don't know how to use pdf multi-column reading with koreader.

- I have installed Georgia EInk fonts in default font directory. Is it possible for koreder to use fonts installed this way?

For now koreader becomes my no.1 for reading pdfs
Reply 

 « First  « Prev Next »  Last »  (2/20)
Today's Posts | Search this Thread | Login | Register