Quote:
Originally Posted by Frenzie
You could see if there's an updated firmware version that helps, and otherwise it should work if you change the device definition to hasColorScreen=no.
|
I think I am on the latest firmware.
However most probably Pocketbook does not serve any new FWs for this old device anymore. I Stand corrected, you can download the fw here:
https://download.pocketbook-int.com/...riton_user.zip
However it is an older Version, than I have right now and it won't update.
The latest Koreader which is working "better" than 2018.12 is v2019.03.1. After that Koreader ain't gonna start or create a crash.log.
I'll try hasColorScreen=no, however this is not ideal^^
Edit:
Just tested hasColorScreen=no. It works as expected
(however, crashes when opening the top Menu, with touch. Button works -.-
I think this device is flawed) now it is working...
Koreaders Fileexplorer on the otherhand does use colours nonetheless and works.
How is the Framebuffer handling different between fileexplorer an Reader?
-----
Ok Ok. After changing
canHWDither from
yes to
no color is working again. However I am unable to open the top Menu (with button or touch)
-----
edit 301:
undefined symbol: PartialUpdateHQ gave a hint, and looking through the code I changed it to the following:
/applications/koreader/ffi/framebuffer_pocketbook.lua Line 36-40
Code:
if fb.device.hasColorScreen() and hq then
inkview.PartialUpdateHQ(x, y, w, h)
else
inkview.PartialUpdate(x, y, w, h)
end
quick and dirty to
Code:
if fb.device.hasColorScreen() and hq then
inkview.PartialUpdate(x, y, w, h)
else
inkview.PartialUpdate(x, y, w, h)
end
Now the Menu is working, I'll test it further.
There is inkview.FullUpdateHQ() also. I think this is doing a fullscreen Update e.g. after 6 pageturns. But this is working as expected.