Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Software > KOReader

Notices

Reply
 
Thread Tools Search this Thread
Old 01-27-2015, 05:25 AM   #61
rkomar
Wizard
rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.
 
Posts: 2,387
Karma: 8693558
Join Date: Oct 2010
Location: Vancouver, BC, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840
Quote:
Originally Posted by mikmak View Post
Hm, ok. Is there any way I can further debug this on the PB 630? In the crash log only "segmentation fault" is reported, so not really helpful.
Not easily. There's a thread in the development forum where I gave some tips on running gdb on the devices. Running gdb remotely is a pain, though. And running it locally doesn't seem possible since none of the terminals seem to be able to support it. However, I've found that you can set up a file of input commands to gdb to run the program and then print out the stack frame where the crash took place, and redirect standard input for gdb to that file. In this case, though, I'm not sure which process you should run the debugger on. The event forwarder? Some lua interpreter? Who knows.
rkomar is offline   Reply With Quote
Advert
Old 01-27-2015, 12:09 PM   #62
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Quote:
Originally Posted by rkomar View Post
No, the white lines are quite short, only about a centimeter long. It is hard to capture in a photo, because it's most obvious when a black bar comes up, but that only lasts for about 1 second. So, I tried taking a movie with my camera, and cropping out part of a frame that showed the problem. It's blurry, but hopefully you can see what's going on in the black region. I'm wondering if the same thing isn't happening in the text, as well, making it faint in places. You can see where it says "Page 1 of 1" that the text is missing some "ink".

By the way, I also have to press a button the first time something is opened before it appears on the screen.
It looks like the waveform mode used when refreshing the screen is not right. But I diffed the latest SDK with the unofficial pbsdk-1.1 and found no difference on the waveform mode definition. This probably needs more investigation.
chrox is offline   Reply With Quote
Old 01-27-2015, 01:46 PM   #63
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Could some one install this test build on their PocketBook devices? It will log detailed information on the framebuffer configuration of the device from which developers could find a way to solve the display problem on some PocketBook devices.

How-to-test:
Just download the unzip the zip package from the above linked page and copy the extracted "applications" directory to your PocketBook devices. Then launch Koreader in the applications menu. And a "koreader.log" file will be generated in the "applications/koreader" directory on your device. It will be very helpful to post the first few lines of that file to this thread.

Sample info you may need to post:
Code:
PocketBook framebuffer info
framebuffer finfo pitc	1200
framebuffer finfo size	1921024
framebuffer finfo pann	1	1
framebuffer vinfo xres	1200	1200
framebuffer vinfo yres	1600	1600
framebuffer vinfo offs	0	0
chrox is offline   Reply With Quote
Old 01-27-2015, 02:24 PM   #64
WS64
WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.WS64 ought to be getting tired of karma fortunes by now.
 
WS64's Avatar
 
Posts: 644
Karma: 506380
Join Date: Aug 2010
Location: Germany
Device: Kobo Aura / PB Lux 2 / Bookeen Frontlight / Kobo Mini / Nook Color
Code:
PocketBook framebuffer info
framebuffer finfo pitc	758
framebuffer finfo size	786432
framebuffer finfo pann	1	1
framebuffer vinfo xres	758	758
framebuffer vinfo yres	1024	1024
framebuffer vinfo offs	0	0
WS64 is offline   Reply With Quote
Old 01-27-2015, 03:00 PM   #65
rkomar
Wizard
rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.
 
Posts: 2,387
Karma: 8693558
Join Date: Oct 2010
Location: Vancouver, BC, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840
This is for my Touch Lux 623 with firmware 4.4.180:

Code:
PocketBook framebuffer info
framebuffer finfo pitc  768
framebuffer finfo size  3145728
framebuffer finfo pann  1       1
framebuffer vinfo xres  758     768
framebuffer vinfo yres  1024    2048
framebuffer vinfo offs  0       0
# initializing for device PocketBook
# framebuffer resolution: {
        ["h"] = 1024,
        ["w"] = 758
}
and by the way, the log shows some errors like this:

Code:
# INFO: invalid widget for setDirty() stack traceback:
        frontend/ui/uimanager.lua:204: in function 'setDirty'
        frontend/ui/widget/button.lua:157: in function 'action'
        frontend/ui/uimanager.lua:296: in function '_checkTasks'
        frontend/ui/uimanager.lua:444: in function 'run'
        ./reader.lua:138: in main chunk
        [C]: at 0x0000bdf1
rkomar is offline   Reply With Quote
Advert
Old 01-27-2015, 05:11 PM   #66
Zetmolm
Fanatic
Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.
 
Posts: 570
Karma: 2017692
Join Date: Jan 2010
Device: Onyx Boox 60, PocketBook Touch (622), PocketBook Touch Lux 2 (626)
This is for my Touch 622:

Code:
PocketBook framebuffer info
framebuffer finfo pitc	608
framebuffer finfo size	2179072
framebuffer finfo pann	1	1
framebuffer vinfo xres	600	608
framebuffer vinfo yres	800	1792
framebuffer vinfo offs	0	0
# initializing for device PocketBook
# framebuffer resolution: {
	["h"] = 800,
	["w"] = 600
Zetmolm is offline   Reply With Quote
Old 01-31-2015, 09:52 AM   #67
druss67
Connoisseur
druss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notesdruss67 can name that song in three notes
 
Posts: 53
Karma: 24492
Join Date: Jul 2013
Location: France
Device: Kindle 4 NT, PocketBook Lux 2 (626), PocketBook Lux 3 (626)
This is for my PB 626
(Firmware : W626.4.4.1151 date: 20141024_140004)

Quote:
PocketBook framebuffer info
framebuffer finfo pitc 758
framebuffer finfo size 786432
framebuffer finfo pann 1 1
framebuffer vinfo xres 758 758
framebuffer vinfo yres 1024 1024
framebuffer vinfo offs 0 0
# initializing for device PocketBook
# framebuffer resolution: {
["h"] = 1024,
["w"] = 758
druss67 is offline   Reply With Quote
Old 01-31-2015, 10:49 AM   #68
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Quote:
Originally Posted by Zetmolm View Post
This is for my Touch 622:

Code:
PocketBook framebuffer info
framebuffer finfo pitc	608
framebuffer finfo size	2179072
framebuffer finfo pann	1	1
framebuffer vinfo xres	600	608
framebuffer vinfo yres	800	1792
framebuffer vinfo offs	0	0
# initializing for device PocketBook
# framebuffer resolution: {
	["h"] = 800,
	["w"] = 600
@Zetmolm Is there any problem on the screen display with the latest koreader? Can you take a picture of what koreader shows? I expect the screen looks normal with koreader on your device.
chrox is offline   Reply With Quote
Old 01-31-2015, 11:02 AM   #69
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Now we need the above framebuffer info on PocketBook Mini(515) to verify my hypothesis that on PocketBook the actual framebuffer pitch may need 16-bytes padding but not revealed in the fixed framebuffer info. That's to say, pitch size 758 from finfo is not reliable and should always be modified to 768, like PB626. And pitch size 600 should be modified to 608, like PB515(? needs verification). And pitch size 768 on PB623 and pitch size 1200 on PB840 does not need to be modified.

Last edited by chrox; 01-31-2015 at 02:28 PM.
chrox is offline   Reply With Quote
Old 01-31-2015, 12:33 PM   #70
gyeben
Member
gyeben began at the beginning.
 
Posts: 11
Karma: 10
Join Date: Apr 2014
Device: Pocketbook 614W (Basic 2)
koreader.log from my PocketBook Basic 2 (614):

Code:
PocketBook framebuffer info
framebuffer finfo pitc  600
framebuffer finfo size  487424
framebuffer finfo pann  1       1
framebuffer vinfo xres  600     600
framebuffer vinfo yres  800     800
framebuffer vinfo offs  0       0
# initializing for device PocketBook
# framebuffer resolution: {
        ["h"] = 800,
        ["w"] = 600
I *think* that the Mini (515) uses the same framebuffer as the Basic 2, since the resolution is the same.
gyeben is offline   Reply With Quote
Old 01-31-2015, 05:04 PM   #71
ArtiiP
Junior Member
ArtiiP began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Jan 2015
Device: PB Mini
Quote:
Originally Posted by gyeben View Post
I *think* that the Mini (515) uses the same framebuffer as the Basic 2, since the resolution is the same.
It's true

PB Mini 515:
Code:
PocketBook framebuffer info
framebuffer finfo pitc	600
framebuffer finfo size	487424
framebuffer finfo pann	1	1
framebuffer vinfo xres	600	600
framebuffer vinfo yres	800	800
framebuffer vinfo offs	0	0
ArtiiP is offline   Reply With Quote
Old 01-31-2015, 06:10 PM   #72
Zetmolm
Fanatic
Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.
 
Posts: 570
Karma: 2017692
Join Date: Jan 2010
Device: Onyx Boox 60, PocketBook Touch (622), PocketBook Touch Lux 2 (626)
Quote:
Originally Posted by chrox View Post
@Zetmolm Is there any problem on the screen display with the latest koreader? Can you take a picture of what koreader shows? I expect the screen looks normal with koreader on your device.
Yes, on the whole the screen looks normal. But in the menus there are smal 'gaps' in some letters. And the contrast in the text is very poor, even though I select darker contrast. And I see the white lines as reported in post #54.
Zetmolm is offline   Reply With Quote
Old 02-01-2015, 02:40 AM   #73
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Thanks for everyone here. The framebuffer issue on PocketBook devices should be solved on the next koreader nightly release.
chrox is offline   Reply With Quote
Old 02-01-2015, 11:09 AM   #74
Zetmolm
Fanatic
Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.Zetmolm ought to be getting tired of karma fortunes by now.
 
Posts: 570
Karma: 2017692
Join Date: Jan 2010
Device: Onyx Boox 60, PocketBook Touch (622), PocketBook Touch Lux 2 (626)
Great job, chrox!
(That's the first thing I should have mentioned yesterday. My only excuse is that it was past midnight for me.)
Zetmolm is offline   Reply With Quote
Old 02-03-2015, 04:19 AM   #75
wirtold
Member
wirtold began at the beginning.
 
Posts: 11
Karma: 10
Join Date: Jan 2015
Device: PocketBook InkPad 840
Some question:

- Does koreader use A2 refresh mode? I am asking about this because builtin apps have faster and better scrolling. In builtin apps when scrolling page is displayed in black and white (high contrast, no grays), and scrolling is fast. In koreader grays are still displayed when scrolling and it is slower.
- Is there any way to go back from filebrowser to already opened document without selecting any file?
wirtold is offline   Reply With Quote
Reply

Tags
calibre, epub, koreader, pdf

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Native KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3) hawhill Kindle Developer's Corner 1108 10-11-2017 02:19 PM
CBZ plugin interaction with FB2/DjVu plugins - First try at pinpointing MrWarper iRex 2 12-11-2011 05:46 AM
Raccoon Reader - reads ePub, fb2, fb2.zip, txt on WP7 for free Andrei_Shvydryk Reading and Management 0 10-31-2011 03:17 PM
v3 vs. v3+ as a pdf/DjVu reader hedonism_bot HanLin eBook 7 11-02-2010 08:16 PM
New PDF to LRF Tool (for DJVU and CBZ files too) RWood Sony Reader 0 08-29-2007 02:13 PM


All times are GMT -4. The time now is 01:22 AM.


MobileRead.com is a privately owned, operated and funded community.