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 11-14-2017, 11:55 AM   #31
gilali
Member
gilali began at the beginning.
 
Posts: 21
Karma: 10
Join Date: Oct 2017
Location: Paris
Device: [Kobo Aura 2, Kobo H2O2]
Quote:
Originally Posted by Frenzie View Post
Btw, have you tried one of the latest nightlies like http://build.koreader.rocks/download...1406-gaa7d4f9/
If I understand correctly that should kind of work?
Here's my test on youtube
And its crash.log attached
As you can see, multitouch works better than unitouch

Build 1406 out of the box, + upside down patch + "-d" argument
Attached Files
File Type: zip crash.zip (1.15 MB, 16 views)
gilali is offline   Reply With Quote
Advert
Old 11-14-2017, 02:41 PM   #32
Frenzie
Addict
Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.
 
Posts: 350
Karma: 111400
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
Nice video! Does the device and/or the kernel driver support actual multitouch? If so then an evtest with multitouches and multitouch gestures would probably be helpful to have. In principle that should work out of the box too but maybe one of the non-standard Kobo workarounds is getting in the way.
Frenzie is offline   Reply With Quote
Old 11-14-2017, 04:28 PM   #33
gilali
Member
gilali began at the beginning.
 
Posts: 21
Karma: 10
Join Date: Oct 2017
Location: Paris
Device: [Kobo Aura 2, Kobo H2O2]
Here's the multitouch log.
I suppose is't not possible to put ksm's touch driver into Koreader. Because in pbchess, touching works nice. And Koreader not need multitouch, isn't it ?
Attached Files
File Type: zip crash.zip (609.5 KB, 14 views)
gilali is offline   Reply With Quote
Old 11-15-2017, 01:01 AM   #34
geekraver
Addict
geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.
 
Posts: 339
Karma: 1010197
Join Date: Jul 2006
Location: Redmond
Device: iPad Pro,Nexus 7,Kindle Paperwhite,Kobo H2O Ed 2
Tried the one at that link; display is upside down and it doesn't respond to any touch presses.
geekraver is offline   Reply With Quote
Old 11-15-2017, 05:07 AM   #35
gilali
Member
gilali began at the beginning.
 
Posts: 21
Karma: 10
Join Date: Oct 2017
Location: Paris
Device: [Kobo Aura 2, Kobo H2O2]
@geekraver
Yes, according to #31, your result is as expected.
Quote:
Build 1406 out of the box, + upside down patch
Upside down patch
For touch presses, it's expected too. You have to use multitouch for better response like this
gilali is offline   Reply With Quote
Advert
Old 11-15-2017, 11:30 AM   #36
geekraver
Addict
geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.
 
Posts: 339
Karma: 1010197
Join Date: Jul 2006
Location: Redmond
Device: iPad Pro,Nexus 7,Kindle Paperwhite,Kobo H2O Ed 2
Doesn't seem practical.

I'm struggling to understand why pbChess and KSM are working but KOReader not? Do they all use completely different mechanisms for touch?
geekraver is offline   Reply With Quote
Old 11-15-2017, 05:26 PM   #37
Frenzie
Addict
Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.
 
Posts: 350
Karma: 111400
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
@gilali
KOReader supports multitouch gestures, which can make some user interactions easier but of course it doesn't depend on them. It may not be supported on any Kobos atm (hardware-wise) but don't quote me on that. It shouldn't need special support if it's standard in any case. There's definitely multitouch on Kindle and Android, presumably also on PocketBook and Ubuntu Touch.

@geekraver
It's some of the Kobos that use non-standard mechanisms for touch instead of the standard Linux kernel events. They emit something that's close to it, but not quite. This is contrary to the kernel principle that user-space applications shouldn't have to worry about this kind of thing. Linus Torvalds would firmly reject whatever kernel patches they applied, probably coupled with some profanity.

Anyway, you can see KOReader's Lua implementation of the Linux single touch and multi touch protocols here, including a reverse-engineered implementation of what was dubbed the Phoenix protocol (because it's the first device where that particular creature showed up).

KSM/vlasovsoftlauncher depends on something similar written in C or C++ instead. Possibly just a few Kobo-specific workarounds on top of something straight from Qt.

Anyway, I guess Sergey can just look at some evtest output and immediately translate it to some relevant code without needing to take a good hour or two to really wrap his head around it. But he probably wrote that code, whereas I didn't implement any of KOReader's stuff so that I only have a passing knowledge of it. I almost got started for the H2O when I noticed that it reused the Phoenix protocol.

You could say I could've used the time I spent writing this post parsing the events and the code instead but it's already 22:26 and trust me, that's a lot more exhausting.
Frenzie is offline   Reply With Quote
Old 01-15-2018, 10:33 AM   #38
gilali
Member
gilali began at the beginning.
 
Posts: 21
Karma: 10
Join Date: Oct 2017
Location: Paris
Device: [Kobo Aura 2, Kobo H2O2]
Hello,
Happy new year

Is it usefull for you to share ssh access to my kobo over internet ?
I'm ok with this.
gilali is offline   Reply With Quote
Old 01-16-2018, 10:16 AM   #39
Frenzie
Addict
Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.
 
Posts: 350
Karma: 111400
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
Happy New Year. I'm afraid not. It's more a matter of time.
Frenzie is offline   Reply With Quote
Old 02-03-2018, 02:26 AM   #40
geekraver
Addict
geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.
 
Posts: 339
Karma: 1010197
Join Date: Jul 2006
Location: Redmond
Device: iPad Pro,Nexus 7,Kindle Paperwhite,Kobo H2O Ed 2
Couldn't koReader leverage the driver code from Sergey that KSM uses? It's been years since I wrote Lua code but IIRC it was quite easy to wrap native code. Or does KSM have a Qt dependency too?
geekraver is offline   Reply With Quote
Old 02-03-2018, 12:52 PM   #41
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,140
Karma: 2815023
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by geekraver View Post
Couldn't koReader leverage the driver code from Sergey that KSM uses? It's been years since I wrote Lua code but IIRC it was quite easy to wrap native code. Or does KSM have a Qt dependency too?
Yes KSM has a Qt dependence.
tshering is offline   Reply With Quote
Old 02-03-2018, 06:58 PM   #42
Frenzie
Addict
Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.
 
Posts: 350
Karma: 111400
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
Quote:
Originally Posted by geekraver View Post
Couldn't koReader leverage the driver code from Sergey that KSM uses? It's been years since I wrote Lua code but IIRC it was quite easy to wrap native code. Or does KSM have a Qt dependency too?
Wrapping C code would be very easy (well, dunno about that specific C code but in principle; much easier even through LuaJIT FFI than in plain Lua C bindings) but adding an extra layer of complexity and uncertainty is almost certainly not easier by any stretch of the imagination.

This is the standard stuff:

https://github.com/koreader/koreader....lua#L366-L426

And here is the Phoenix Protocol:

https://github.com/koreader/koreader....lua#L427-L491

You can imagine a C library that translates all odd Kobo deviations into standard events to simplify things ever so slightly, but there isn't that much going on in the first place.

I'm sure you can do it with some strategic debug statements and tweaks. You just need an SSH connection so you can quickly iterate tests.
Frenzie is offline   Reply With Quote
Old 02-16-2018, 01:25 AM   #43
geekraver
Addict
geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.geekraver ought to be getting tired of karma fortunes by now.
 
Posts: 339
Karma: 1010197
Join Date: Jul 2006
Location: Redmond
Device: iPad Pro,Nexus 7,Kindle Paperwhite,Kobo H2O Ed 2
I looked at the kernel code at https://github.com/kobolabs/Kobo-Reader

I compared the auraonetwo kernel code with h202. Apart from adding a couple of additional low level touch drivers (Parade Truetouch and Focaltech), I didn't see anything different at a higher level related to input.
geekraver is offline   Reply With Quote
Old 02-16-2018, 04:10 AM   #44
Frenzie
Addict
Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.Frenzie knows the difference between a duck.
 
Posts: 350
Karma: 111400
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
Haha, you find reading kernel code easier than Lua?

I would imagine duplicating the Kobo Aura One definition is the first thing we tried (unless I forgot to explicitly state somewhere that same gen is likely to share a bunch of hardware), but did you double check just to be sure?

Code:
-- Kobo Aura One:
local KoboDaylight = Kobo:new{
    model = "Kobo_daylight",
    hasFrontlight = yes,
    touch_probe_ev_epoch_time = true,
    touch_phoenix_protocol = true,
    display_dpi = 300,
    hasNaturalLight = yes,
}
Code:
-- Kobo Aura H2O2:
local KoboSnow = Kobo:new{
    model = "Kobo_snow",
    hasFrontlight = yes,
-- started with phoenix, was changed to alyssum
    touch_alyssum_protocol = true,
-- this almost certainly must've been tried together with phoenix already, but…
    touch_probe_ev_epoch_time = true,
    display_dpi = 265,
    -- the bezel covers the top 11 pixels:
    viewport = Geom:new{x=0, y=11, w=1080, h=1429},
}
Frenzie is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
H2O2 Edition 2 Release Date? (Australia) meeera Kobo Reader 12 09-21-2017 06:23 AM
Kobo Aura H2O 2nd Edition vs old Kobo Aura H2O screen dimentions. iXPert12 Kobo Reader 1 09-18-2017 10:35 AM
Errors with EPUB rendering on Kobo Aura H2O running koreader-stable-v2015.11 algernonramone KOReader 8 03-16-2016 01:55 AM
[Aura H2O 3.18.0] Koreader/Coolreader Font Problems for a specific .epub Gnorr Kobo Reader 3 10-09-2015 05:11 AM
Koreader (latest install instructions) on H2O JSWolf KOReader 15 12-04-2014 10:32 PM


All times are GMT -4. The time now is 10:20 PM.


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