View Single Post
Old 01-26-2015, 01:18 AM   #46
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 sadowski View Post
Here comes a shot with yres/2 and line_lenght+8. The screen is smaller and rotated but otherwise undistorted.

As for the basic framebuffer information: Where does the output from the print() statements end up? It is not in crash.log.
It will show up on the terminal screen when you run koreader in SSH session.

In order to write the print output to log file you need to change line 30 in the "applications/koreader.app"
Code:
./reader.lua "$args" 2> crash.log
to

Code:
./reader.lua "$args" 1> koreader.log 2> crash.log
This will redirect standard output like the "print" to local file koreader.log. After you exit koreader you can find the framebuffer info in the "applications/koreader/koreader.log" file.
chrox is offline   Reply With Quote