KOreader on Android

[toancv]

Hi,
My device cannot use Koreader dictionary. Device is Nook Glowlight plus (BNRV510), Android version is 4.42. After manually copy dictionary file in the instructed folder. The dictionary show in "Installed Dictionaries (1)" but every time search for a word, "No results".
Thanks!

[Owl_]

Hi, I had a problem with the autoturn function in my Onyxboox poke2: the autoturn stops after a couple of page.
Months ago I reported the issue here and the people told me there is an android's setting that is stopping the autoturn, and suggested me to inspect the crash.log to find the culprit.
I found this issue that occurs but I cannot read it. Could you help me?

07-06 16:13:01.252 V/KOReader( 3391):  Explicit widgetRepaint: table: 0xc93b01e8 @ ( 0 , 0 )
07-06 16:13:01.255 V/KOReader( 3391):  setDirty via a func from widget table: 0xc93b01e8
07-06 16:13:01.255 V/KOReader( 3391):  INFO: invalid widget for setDirty() stack traceback:
07-06 16:13:01.255 V/KOReader( 3391):     frontend/ui/uimanager.lua:872: in function 'post_guard'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/dbg.lua:68: in function 'setDirty'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/apps/reader/modules/readerfooter.lua:2037: in function 'updateFooterText'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/apps/reader/modules/readerfooter.lua:1934: in function 'updateFooterPage'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/apps/reader/modules/readerfooter.lua:1918: in function 'onUpdateFooter'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/apps/reader/modules/readerfooter.lua:668: in function 'action'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/ui/uimanager.lua:1194: in function '_checkTasks'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/ui/uimanager.lua:1592: in function 'handleInput'
07-06 16:13:01.255 V/KOReader( 3391):     frontend/ui/uimanager.lua:1700: in function 'run'
07-06 16:13:01.255 V/KOReader( 3391):     /data/user/0/org.koreader.launcher/files/reader.lua:323: in main chunk
07-06 16:13:01.255 V/KOReader( 3391):     [C]: in function 'dofile'
07-06 16:13:01.255 V/KOReader( 3391):     /data/user/0/org.koreader.launcher/files/llapp_main.lua:78: in main chunk
07-06 16:13:01.255 V/KOReader( 3391):     [C]: in function 'dofile'
07-06 16:13:01.255 V/KOReader( 3391):     [string "launcher.lua"]:19: in function 'launch'
07-06 16:13:01.255 V/KOReader( 3391):     [string "launcher.lua"]:22: in function 'run'
07-06 16:13:01.255 V/KOReader( 3391):     [string "android.lua"]:2662: in main chunk
07-06 16:13:01.256 V/KOReader( 3391):  ReaderFooter.autoRefreshFooter scheduled
07-06 16:13:01.256 V/KOReader( 3391):  _refresh: Enqueued ui update for region 0 1403 1072 45 
07-06 16:13:01.256 V/KOReader( 3391):  triggering refresh {
07-06 16:13:01.256 V/KOReader( 3391):     ["region"] = {
07-06 16:13:01.256 V/KOReader( 3391):         ["h"] = 45,
07-06 16:13:01.256 V/KOReader( 3391):         ["w"] = 1072,
07-06 16:13:01.256 V/KOReader( 3391):         ["y"] = 1403,
07-06 16:13:01.256 V/KOReader( 3391):         ["x"] = 0,
07-06 16:13:01.256 V/KOReader( 3391):     },
07-06 16:13:01.256 V/KOReader( 3391):     ["mode"] = "ui",
 07-06 16:13:01.256 V/KOReader( 3391): }

[NiLuJe]

We'd need an actual full log, not an excerpt (something which is now easily accessible via the "Report a bug" entry in the hamburger menu).

[Owl_]

Here it is

[NiLuJe]

Looks like it's working perfectly fine here?

[pazos]

Considering how bad are some Boox devices implementing android stuff and the fact the Poke2 is actually flaged as "brokenLifecycle" in KOReader I think there's no workaround possible other than disabling the whole plugin altogether for that specific device or live with current behaviour.

[JSWolf]

Can KOReader be installed on a TV running Android such as a Sony?

[pazos]

Originally Posted by JSWolf

Can KOReader be installed on a TV running Android such as a Sony?

Yes. But you'll need a mouse or gamepad to move across the UI. That's why https://github.com/koreader/koreader/issues/5725 is still open.

I sketched UI navigation using the included controller in https://github.com/koreader/koreader...ion_r450787837 but that's unimplemented.

TL;DR: With a mouse: yeah. Without a mouse: nope.

[JSWolf]

That would be interesting to have a 65" screen for KOReader.

[motherat]

Originally Posted by pazos

the fact the Poke2 is actually flaged as "brokenLifecycle" in KOReader

Well, that's certainly depressing.

[Frenzie]

Originally Posted by JSWolf

That would be interesting to have a 65" screen for KOReader.

Here's 55" as a sample. (Should've probably put the font a bit larger.)

https://github.com/koreader/koreader...ment-570331342

[JSWolf]

Originally Posted by Frenzie

Here's 55" as a sample. (Should've probably put the font a bit larger.)

https://github.com/koreader/koreader...ment-570331342

I'd have done at least two columns. The lines are a bit long.

[Frenzie]

It's not like I actually use it that way, lol.

[JSWolf]

Originally Posted by Frenzie

It's not like I actually use it that way, lol.

If I had a way of connecting KOReader my 65" OLED TV, I'd tryi three column if possible.

[OrangeFlavored]

Was ZSync removed recently, or did it just get moved somewhere else? Couldn't find it the other day when I wanted to send a book over to my phone from my e-reader.