Unable to launch KOReader on PocketBook Basic 611 #6505
Labels
Comments
|
I'd try a current nightly directly, just in case you simply botched the patching ;). |
|
I've tried latest nightly build - v2020.07.1-49-gd935ca6_2020-08-13. At first I've got new error: I've changed And after that it is back to initial error: |
|
Does the device actually have a wifi chip?
…On Sat, Aug 15, 2020, 12:58 Anton Larionov ***@***.***> wrote:
I've tried latest nightly build - v2020.07.1-49-gd935ca6_2020-08-13.
At first I've got new error:
---------------------------------------------
launching...
_ _____ ____ _
| |/ / _ \| _ \ ___ __ _ __| | ___ _ __
| ' / | | | |_) / _ \/ _` |/ _` |/ _ \ '__|
| . \ |_| | _ < __/ (_| | (_| | __/ |
|_|\_\___/|_| \_\___|\__,_|\__,_|\___|_|
It's a scroll... It's a codex... It's KOReader!
[*] Current time: 01/16/37-18:49:52
[*] Version: v2020.07.1-49-gd935ca6_2020-08-13
ffi.load: SDL2
ffi.load (warning): libSDL2.so: cannot open shared object file: No such file or directory
ffi.load: libSDL2-2.0.so
ffi.load (warning): libSDL2-2.0.so: cannot open shared object file: No such file or directory
ffi.load: libSDL2-2.0.so.0
ffi.load (warning): libSDL2-2.0.so.0: cannot open shared object file: No such file or directory
SDL2 not loaded: ./setupkoenv.lua:27: Not able to load dynamic library: libSDL2-2.0.so.0
ffi.load: inkview
01/16/37-18:49:52 INFO SoftwareVersion: E611.15.8.0
01/16/37-18:49:52 INFO Blacklisting the C BB on this device
Tweaking LuaJIT's max loop unroll factor (15 -> 45)
FB: computed size: 1024000
FB: id : mxc_epdc_fb
FB: smem_len : 2179072
FB: line_length : 800
FB: xres : 800
FB: xres_virtual : 800
FB: yres : 600
FB: yres_virtual : 1280
FB: bpp : 8
Atached mp shm: id 0 addr 2b09c000 size 17260
hw_eink_init()
EINK_VERSION: 0000
ndepth:4 hqdepth:4
attach_shm: fb key=10560257 size=979232
Atached fb shm: id 8001 addr 2b190000 size 979232
allocated 244112 bytes for ecmd
ffi.load: inkview
01/16/37-18:49:52 INFO initializing for device PB611
01/16/37-18:49:52 INFO framebuffer resolution: {
["h"] = 600,
["w"] = 800
}
ffi.load: libs/libmupdf.so
ffi.load: libs/libwrap-mupdf.so
ffi.load: libs/libfreetype.so.6
./luajit: frontend/device/pocketbook/device.lua:197: /usr/lib/libinkview.so: undefined symbol: GetNetState
stack traceback:
[C]: in function '__index'
frontend/device/pocketbook/device.lua:197: in function 'isWifiOn'
frontend/ui/network/manager.lua:90: in function 'init'
frontend/ui/network/manager.lua:657: in main chunk
[C]: in function 'require'
frontend/apps/reader/modules/readerdictionary.lua:14: in main chunk
[C]: in function 'require'
frontend/apps/reader/readerui.lua:31: in main chunk
[C]: in function 'require'
./reader.lua:274: in main chunk
[C]: at 0x00013f31
Segmentation fault
I've changed device.lua to:
function NetworkMgr:isWifiOn()
return false
end
And after that it is back to initial error:
---------------------------------------------
launching...
_ _____ ____ _
| |/ / _ \| _ \ ___ __ _ __| | ___ _ __
| ' / | | | |_) / _ \/ _` |/ _` |/ _ \ '__|
| . \ |_| | _ < __/ (_| | (_| | __/ |
|_|\_\___/|_| \_\___|\__,_|\__,_|\___|_|
It's a scroll... It's a codex... It's KOReader!
[*] Current time: 01/16/37-18:56:24
[*] Version: v2020.07.1-49-gd935ca6_2020-08-13
ffi.load: SDL2
ffi.load (warning): libSDL2.so: cannot open shared object file: No such file or directory
ffi.load: libSDL2-2.0.so
ffi.load (warning): libSDL2-2.0.so: cannot open shared object file: No such file or directory
ffi.load: libSDL2-2.0.so.0
ffi.load (warning): libSDL2-2.0.so.0: cannot open shared object file: No such file or directory
SDL2 not loaded: ./setupkoenv.lua:27: Not able to load dynamic library: libSDL2-2.0.so.0
ffi.load: inkview
01/16/37-18:56:24 INFO SoftwareVersion: E611.15.8.0
01/16/37-18:56:24 INFO Blacklisting the C BB on this device
Tweaking LuaJIT's max loop unroll factor (15 -> 45)
FB: computed size: 1024000
FB: id : mxc_epdc_fb
FB: smem_len : 2179072
FB: line_length : 800
FB: xres : 800
FB: xres_virtual : 800
FB: yres : 600
FB: yres_virtual : 1280
FB: bpp : 8
Atached mp shm: id 0 addr 2b07c000 size 17260
hw_eink_init()
EINK_VERSION: 0000
ndepth:4 hqdepth:4
attach_shm: fb key=10560257 size=979232
Atached fb shm: id 8001 addr 2b170000 size 979232
allocated 244112 bytes for ecmd
ffi.load: inkview
01/16/37-18:56:25 INFO initializing for device PB611
01/16/37-18:56:25 INFO framebuffer resolution: {
["h"] = 600,
["w"] = 800
}
ffi.load: libs/libmupdf.so
ffi.load: libs/libwrap-mupdf.so
ffi.load: libs/libfreetype.so.6
01/16/37-18:56:26 INFO opening file ./help/quickstart-en-v2020.07.1-49-gd935ca6_2020-08-13.html
01/16/37-18:56:27 INFO Loading plugins from directory: plugins
01/16/37-18:56:27 INFO Plugin plugins/gestures.koplugin/main.lua has been disabled.
01/16/37-18:56:27 INFO Plugin plugins/hello.koplugin/main.lua has been disabled.
ffi.load: sqlite3
ffi.load: z
ffi.load: sqlite3
01/16/37-18:56:27 INFO Plugin plugins/autosuspend.koplugin/main.lua has been disabled.
01/16/37-18:56:27 INFO Plugin plugins/keepalive.koplugin/main.lua has been disabled.
01/16/37-18:56:27 INFO Plugin plugins/SSH.koplugin/main.lua has been disabled.
01/16/37-18:56:27 INFO Plugin plugins/autofrontlight.koplugin/main.lua has been disabled.
01/16/37-18:56:28 INFO RD loaded plugin autoturn at plugins/autoturn.koplugin
01/16/37-18:56:28 INFO RD loaded plugin backgroundrunner at plugins/backgroundrunner.koplugin
01/16/37-18:56:28 INFO RD loaded plugin batterystat at plugins/batterystat.koplugin
01/16/37-18:56:28 INFO RD loaded plugin calibre at plugins/calibre.koplugin
01/16/37-18:56:28 INFO CoverBrowser: setting default display modes
01/16/37-18:56:28 INFO RD loaded plugin coverbrowser at plugins/coverbrowser.koplugin
01/16/37-18:56:28 INFO RD loaded plugin docsettingtweak at plugins/docsettingtweak.koplugin
01/16/37-18:56:28 INFO RD loaded plugin evernote at plugins/evernote.koplugin
01/16/37-18:56:28 INFO RD loaded plugin goodreads at plugins/goodreads.koplugin
01/16/37-18:56:28 INFO RD loaded plugin kosync at plugins/kosync.koplugin
01/16/37-18:56:28 INFO RD loaded plugin movetoarchive at plugins/movetoarchive.koplugin
01/16/37-18:56:28 INFO RD loaded plugin newsdownloader at plugins/newsdownloader.koplugin
01/16/37-18:56:28 INFO RD loaded plugin perceptionexpander at plugins/perceptionexpander.koplugin
01/16/37-18:56:28 INFO RD loaded plugin profiles at plugins/profiles.koplugin
01/16/37-18:56:28 INFO RD loaded plugin readtimer at plugins/readtimer.koplugin
01/16/37-18:56:28 INFO RD loaded plugin send2ebook at plugins/send2ebook.koplugin
01/16/37-18:56:29 INFO RD loaded plugin statistics at plugins/statistics.koplugin
01/16/37-18:56:29 INFO RD loaded plugin systemstat at plugins/systemstat.koplugin
01/16/37-18:56:29 INFO RD loaded plugin terminal at plugins/terminal.koplugin
01/16/37-18:56:29 INFO RD loaded plugin texteditor at plugins/texteditor.koplugin
01/16/37-18:56:29 INFO RD loaded plugin timesync at plugins/timesync.koplugin
01/16/37-18:56:29 INFO RD loaded plugin wallabag at plugins/wallabag.koplugin
01/16/37-18:56:29 INFO RD loaded plugin zsync at plugins/zsync.koplugin
Called func hw_fullupdate_internal
Called func hw_update_orientation, new orientation 0
01/16/37-18:57:12 WARN got error waiting for events: Waiting for input failed: 4
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA3KZU2M33QJN5MYRQZ3NLSAZS5DANCNFSM4QAGIT6Q>
.
|
|
@NiLuJe It does, according to the manual. This is one of the devices I'd thought might be problematic - it's running Edit: Also, this specific device is running the older 15.8 version, the newer version might have updated Wi-Fi parts, since the changelog mentions some related stuff. |
|
If anything, stuff should behave better on ancient FW on PB ;). |
|
Are you sure? I know the new devices on the 6+ firmware are giving hiccups, but the oldest ones we had before this one were on firmware 4 and that's newer than whatever this firmware is, so I thought it might have an older kernel or whatnot. Either way I'm talking out of my ass, I can send you a link to the firmware update bin if that would be useful :) |
|
It was? PB support goes back to 2015, for the Touch Lux 2, which is from 2013 or 2014 or something. But I don't know any details about firmware versions. |
|
I've updated device to v16.0. Initially still got that error with WI-FI: But after disabling It's launching and I'm able to open books and scroll through them. But it's like only OK, back and forward buttons are working (and arrow buttons are not), so:
|
|
Huh. Someone might want to take a look if inkview is using a different /
older API for Wi-Fi...
…On Sun, Aug 16, 2020, 17:49 roshavagarga ***@***.***> wrote:
You're probably going to have to figure out what codes your buttons use,
so that they can be added @anlar <https://github.com/anlar> - you can
find more info on that in #6311
<#6311>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6505 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA3KZRLFPXOEGTQ7L7PRPTSA75Z5ANCNFSM4QAGIT6Q>
.
|
|
@roshavagarga, how to enable debug logging for keys? |
|
You can enable debug logging through the file browser → tools menu → developer options (might be on page 2). (This should really also be in the reader now that we have that more tools menu…) |
|
If you can't do that, just do an |
2 tasks
|
@anlar When you have information - reach out so somebody can try and fix this, otherwise the device may never be fixed. |
|
I have checked it further and it seems that keys are not working only for selecting items in lists - file browser, file browser context menu, top and bottom menus in book viewer.
I can't enable debug from developer options in menu and not sure how to user
|
|
@anlar Comparing this to my own experience in #6311 shows similarities: What is missing is you using the right button (code 20) or the central button (code 10). Since up and down are registered, that means they were successfully picked up and unless I'm missing something they should be okay? Can you do another log and check right and central buttons before exiting? Just search for 'input event' in the log and confirm whether they use the same codes as mentioned before. An evtest (which might honestly be useless in this case? A dev will have to confirm) is easy to do if you have adb/root on the device. You can see how I did it on a Bookeen device in #6043. @Frenzie @NiLuJe Might this have something to do with lines 132-136 in the PB's device.lua file? My train of thoughts is that this PB is using a kernel predating 3.0 which might mean it handles input events differently. |
|
@roshavagarga: As the comment in that code excerpt says, we trust InkView for input, and we fake evdev events ourselves. So the kernel shouldn't have any impact, only what InkView reports ;) (And, besides, we handle god-awful kernels just fine on a lot of other devices ^^). EDIT: This also means, that, yeah, evtest won't be much use in this context ;). |
|
@roshavagarga Logs from using right and central buttons (both working - context menu and book opening: |
|
Well, the codes for those are the same as on the newer Basic 3 device I have. |
|
re:wifi, on pre-4.x inkview, all one can reliably do is QueryNetwork, EnumConnections and NetConnect. |
|
@roshavagarga Currently I have 2 issues: Issue 1 - Unable to launch application due to Wi-Fi errorSame issue as in #6548. Stacktrace: Workaround - update Issue 2 - Up and Down buttons are not workingAll buttons except Up and Down are working fine. These 2 buttons are detected according to logs, but nothing happens when I press on them. |
|
@roshavagarga I've tried nightly build - both issues still there. |
|
@ezdiy Right, re-downloaded file and app is starting, but all buttons are not working now. Start log: |
|
Now we're getting closer. Replace libinkview-compat.so in koreader/libs with this one |
|
@ezdiy Same behavior - buttons are not working: |
|
@anlar Ok third time is the charm. |
|
@ezdiy Tried third version - all buttons except Up and Down are working fine. |
|
@anlar I was almost losing hope with this remote debug.
The key seems to be sent correctly to koreader, I think the issue is that we simply don't do anything useful with it in UI. |
|
@ezdiy I think the issue was that Up and Down keys weren't being processed or detected when he is in the folder menu, so he can't actually choose books because he'd need to go up and down to choose from the list. By what I read it seemed to work properly when inside the book-reading part of Koreader. |
|
This has not been worked on in a very long time. I'm closing this for that reason. If there is still trouble feel free to tell me. |
|
Hello! edit: typos |
|
Unless you mean it's incorrectly identified as not having a back key (in which case |
Hey! Thank you for the answer. And then there is my device model 611: -- PocketBook Basic (611) As you can see, there is no "hasFewKeys" option in Generic section. |
|
No, the other way around: remove it from PocketBook611. |
Ok, so I removed that line from PocketBook611 and now it moves to the left in menu as I want! But, sadly, I cannot go back. Is it what you are talking about? Seems like it is a situation either/or? Am I right? Can I somehow configure left arrow with long press to execute go back action? |
|
No, that's currently not possible. |
Oh, I see :( Anyway, thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
I'm trying to launch KOReader's recent version on PocketBook 611. I've taken v2020.07.1, added to
device.luadefinitions from #6481 and running it. But after that device is frozen. See attachedcrash.log- last line is from the moment when I have turned off device.Steps to reproduce
applicationsdirectory v2020.07.1 with updateddevice.luaconfig:koreader.crash.logThe text was updated successfully, but these errors were encountered: