02-24-2018, 04:09 AM | #46 |
Wizard
Posts: 1,619
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
Most Kobos have mirrored coordinates. You can always try:
Code:
touch_mirrored_x = false, |
02-25-2018, 06:35 PM | #47 |
Junior Member
Posts: 5
Karma: 5814
Join Date: Feb 2018
Device: Kobo Aura H2O2
|
Okay, I got it to work I think. The code seems to be written on the premise that the machine is going to tell you if a finger has been taken off. That doesn't seem to be true for the H2O2. It has event logs like this for single touch events:
Spoiler:
But when a finger leaves the screen, it doesn't send anything with an id of -1, it just stops reporting that finger. If there are no fingers on the screen, it sends one SYN_REPORT message: 02/25/18-17:45:49 DEBUG input event => type: 0, code: 0(nil), value: 0, time: 568.579338 by itself without any ABS events. So, I changed Input:handleTouchEv so that it always passed every slot to feedEvent, and set all the ids to -1 after it passed them. Also, I turned off the thing that subtracts one from every id in adjustTouchAlyssum. That seems to work for single touch. The function now looks like this: Spoiler:
This makes touch work, although I seem to have broken the hold gesture. By the way, this might explain why the two-finger procedure worked: Spoiler:
Last edited by cola; 02-25-2018 at 06:51 PM. Reason: come to think of it, this probably explains why the thing with two fingers registered as a one-finger tap |
Advert | |
|
02-25-2018, 08:14 PM | #48 |
Junior Member
Posts: 5
Karma: 5814
Join Date: Feb 2018
Device: Kobo Aura H2O2
|
Okay, I got the hold button to work. Here is the output of diff -r from the tree of koreader-kobo-arm-kobo-linux-gnueabihf-v2015.11-1523-g78284e1.zip (with inessential stuff removed):
Spoiler:
|
02-26-2018, 03:39 AM | #49 |
Wizard
Posts: 1,619
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
Unfortunately as is that doesn't work on older devices. I'm not sure if I have time to look at the specifics right now.
Code:
./luajit: frontend/device/gesturedetector.lua:124: attempt to index field 'timev' (a nil value) stack traceback: frontend/device/gesturedetector.lua:124: in function 'deepCopyEv' frontend/device/gesturedetector.lua:239: in function <frontend/device/gesturedetector.lua:227> frontend/device/gesturedetector.lua:107: in function 'feedEvent' frontend/device/input.lua:497: in function 'waitEvent' frontend/ui/uimanager.lua:741: in function 'handleInput' frontend/ui/uimanager.lua:789: in function 'run' ./reader.lua:190: in main chunk [C]: at 0x00013fc5 |
02-27-2018, 09:00 AM | #50 |
Junior Member
Posts: 5
Karma: 5814
Join Date: Feb 2018
Device: Kobo Aura H2O2
|
I wasn't really intending it as a patch, I just thought it would be an easy way of explaining what was up with my ereader. And whoops, the changes in handleTouchEvPhoenix are there by accident!
I would rather not try to debug multitouch, write a proper patch with a configuration option in device.lua, etc, since my only development environment is my ereader itself. If someone else with an H2O2 is in a similar situation, maybe try it and tell me if it works? |
Advert | |
|
03-01-2018, 03:28 AM | #51 |
Junior Member
Posts: 5
Karma: 10
Join Date: Mar 2018
Device: H2O Edition 2
|
Ok, so this is not a very productive first post but I'll throw my hat in the ring as I am on the verge of returning my H2O2.
I am very familiar with doing weird and wonderful things with my android devices from custom firmware through XPOSED and even a little dabble in making a couple of customised roms for myself. I have NO idea how to try this out on my H2O2 but I absolutely need this if I am going to keep this device: I can't read PDFs at all with the stock system. If I need even a little bit of zoom, the whole show just becomes useless. Does anyone think they could put this into simple step-by-step process from start to finish so that I can test these changes on my H2o2? Please and thank you in advance if anyone can help at all. |
03-01-2018, 03:59 AM | #52 |
Wizard
Posts: 1,619
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
You need to apply these changes.
At the time of writing, that means overwriting the following files with those from the links should work according to cola: frontend/device/input.lua frontend/device/kobo/device.lua |
03-01-2018, 04:32 AM | #53 |
Junior Member
Posts: 5
Karma: 10
Join Date: Mar 2018
Device: H2O Edition 2
|
Ok, thank you very much.
For the H2O2, are the recommended installation instructions on GitHub (install Kobo start menu first) still the recommended way to proceed? |
03-01-2018, 05:29 AM | #54 |
Junior Member
Posts: 5
Karma: 10
Join Date: Mar 2018
Device: H2O Edition 2
|
By Odin's beard, Cola and Frenzie you have done it!
Works an absolute treat. Not quite the custom Android OS I was hoping for, but this handles PDFs much, much better than the stock software! Many, many thanks. So, here's your confirmation that this works on another H2O2 unit. Champions! EDIT: For all passers by: yes, install Kobo Start Menu first. This operates outside of your normal ereader OS. |
03-01-2018, 06:05 AM | #55 |
Connoisseur
Posts: 74
Karma: 28960
Join Date: Oct 2017
Location: Paris
Device: KOBO Libra + H2Ov2 + Aura2
|
ohhhh **** !!!!
Many thanks ! Thank you so much guys ! You are real WARRIORS It's not christmas today, not my birthday too, but what a gift !!!! |
03-01-2018, 06:24 AM | #56 |
Resident Curmudgeon
Posts: 74,037
Karma: 129333114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Does this mean that KSM09 and KOReader now work on the H2O2?
|
03-01-2018, 09:28 AM | #57 |
Wizard
Posts: 1,619
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
Is there anybody with something like a Kobo Mini, Aura HD or Glo or even a Kindle who can try this file to see if it works? Just curious.
frontend/device/input.lua @JSWolf Not out of the box, but close. Based on reading the comment about the kernel this might actually be fixing a bug in our logic. @cola Taking a closer look at your patch, I noticed the nonsensical sounding `ev.value = ev.value`. Logically I think that means you should just get rid of the alyssum_protocol? |
03-01-2018, 10:00 AM | #58 |
Wizard
Posts: 4,465
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
Seems to make no difference on my AuraHD, is there anything I should be looking for?
Luck; Ken |
03-01-2018, 10:32 AM | #59 |
Wizard
Posts: 1,619
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
If it doesn't break anything (regular tap, hold on word, hold and drag to select a bunch of text, slide left/right, pan document, other gestures like diagonal for screenshot) then perhaps we can just use it as is.
|
03-01-2018, 11:20 AM | #60 |
Wizard
Posts: 4,465
Karma: 6900052
Join Date: Dec 2009
Location: The Heart of Texas
Device: Boox Note2, AuraHD, PDA,
|
OK;
Regular tap=OK Hold and drag=OK Slide and Pan= ? don't know how to do that. Screenshot=OK both epub & PDF File Browser ev seem to work as well. Luck; Ken Last edited by Ken Maltby; 03-01-2018 at 11:27 AM. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
H2O2 Edition 2 Release Date? (Australia) | meeera | Kobo Reader | 12 | 09-21-2017 05:23 AM |
Kobo Aura H2O 2nd Edition vs old Kobo Aura H2O screen dimentions. | iXPert12 | Kobo Reader | 1 | 09-18-2017 09:35 AM |
Errors with EPUB rendering on Kobo Aura H2O running koreader-stable-v2015.11 | algernonramone | KOReader | 8 | 03-16-2016 12:55 AM |
[Aura H2O 3.18.0] Koreader/Coolreader Font Problems for a specific .epub | Gnorr | Kobo Reader | 3 | 10-09-2015 04:11 AM |
Koreader (latest install instructions) on H2O | JSWolf | KOReader | 15 | 12-04-2014 09:32 PM |