|
|
#1 |
|
Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 16
Karma: 14242
Join Date: Jan 2018
Device: None
|
Aura H2O Debian chroot
Hello all,
I am trying to adapt Ah-'s Debian chroot method for my Aura H2O https://www.mobileread.com/forums/sh...d.php?t=203986. I used debootstrap and qemu to create a Jessie image and proceeded to compile the binaries for updating the framebuffer from here https://www.mobileread.com/forums/at...6&d=1369753491. Using the xorg.conf supplied in Ah-'s image I get the xserver up and running, bit of tweaking and it accurately responds to touch by moving the cursor but that's it, I cannot figure out how to get it to register a 'click'. Edit: I have compiled the xf86-input-evdev-2.7.0 package in the home directory of Ah-'s image but it has not helped from what I can tell. I ran 'evtest /dev/input/event1' through telnet and I get the following: Code:
root@(none):/# evtest /dev/input/event1
Input driver version is 1.0.0
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "zForce-ir-touch"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 258 (BTN_2)
Event code 307 (BTN_NORTH)
Event code 308 (BTN_WEST)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min 0
Max 1440
Event code 1 (ABS_Y)
Value 0
Min 0
Max 1080
Event code 16 (ABS_HAT0X)
Value 0
Min 0
Max 1440
Event code 17 (ABS_HAT0Y)
Value 0
Min 0
Max 1080
Event code 24 (ABS_PRESSURE)
Value 0
Min 0
Max 2048
Event code 48 (ABS_MT_TOUCH_MAJOR)
Value 0
Min 0
Max 2
Event code 50 (ABS_MT_WIDTH_MAJOR)
Value 0
Min 0
Max 15
Event code 53 (ABS_MT_POSITION_X)
Value 0
Min 0
Max 1440
Event code 54 (ABS_MT_POSITION_Y)
Value 0
Min 0
Max 1080
Event code 57 (ABS_MT_TRACKING_ID)
Value 0
Min 1
Max 2
Properties:
Testing ... (interrupt to exit)
Event: time 1520552518.917308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1520552518.917336, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1520552518.917341, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), value 1
Event: time 1520552518.917350, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 831
Event: time 1520552518.917359, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 717
Event: time 1520552518.917370, ++++++++++++++ EV_REL ++++++++++++
Event: time 1520552518.917452, -------------- EV_SYN ------------
Event: time 1520552518.998713, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1520552518.998719, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1520552518.998720, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), value 1
Event: time 1520552518.998722, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 830
Event: time 1520552518.998723, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 716
Event: time 1520552518.998725, ++++++++++++++ EV_REL ++++++++++++
Event: time 1520552518.998739, -------------- EV_SYN ------------
Event: time 1520552519.009014, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1520552519.009020, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1520552519.009021, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), value 1
Event: time 1520552519.009022, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 829
Event: time 1520552519.009024, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 713
Event: time 1520552519.009026, ++++++++++++++ EV_REL ++++++++++++
Event: time 1520552519.009037, -------------- EV_SYN ------------
Event: time 1520552519.018832, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1520552519.018838, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 0
Event: time 1520552519.018839, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), value 0
Event: time 1520552519.018841, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 829
Event: time 1520552519.018842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 713
I would like to get this working so I can write an up-to-date tutorial for this, if I understand correctly it mostly comes down to changing the resolution in fast_update.c to make it work for different models? I think it's a fun thing to do and many people could benefit. Thanks, NH Last edited by nohandlebars; 03-09-2018 at 01:52 PM. Reason: Managed to compile xf86-input-evdev-2.7.0 package |
|
|
|
![]() |
| Thread Tools | Search this Thread |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Debian chroot won't upgrade without Kernel Upgrade | Avi Wadhwa | Kindle Developer's Corner | 2 | 12-26-2018 06:54 AM |
| Debian chroot for Kobo | ah- | Kobo Developer's Corner | 17 | 04-29-2018 05:41 PM |
| Aura HD Debian for Aura HD | guang6321 | Kobo Developer's Corner | 107 | 03-25-2018 11:34 PM |
| Kobo Aura H2O 2nd Edition vs old Kobo Aura H2O screen dimentions. | iXPert12 | Kobo Reader | 1 | 09-18-2017 09:35 AM |
| need help with chroot'ing a debian.ext3 file system | don17sch | Kindle Developer's Corner | 1 | 02-10-2016 06:58 AM |