MobileRead Forums
Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader
Reload this Page All new Ultimate Manga Reader

Notices

Reply
Page 3 of 21 12 3 4567 Last »
 
Thread Tools Search this Thread
Old 09-16-2020, 01:48 PM   #31
nuetron
Member
nuetron began at the beginning.
 
Posts: 16
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
Test on my Libra H2O:

UltimateMangaApp: Behaves the same way. The power button will activate the screen saver. Pressing the power button again will bring up the Connect to Wifi popup but the screen is still unresponsive to inputs. Have to force restart in order to get back to kobo menus.

Scribble App: Unresponsive to any touch. The FILE, OPTIONS, HELP on the top is unresponsive to touch. Touching anywhere else on the screen has no response. Pressing the power button has no response. Have to hard shutdown and power back on.

Logs from Scribble app:
Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
KoboKb: Attempting to capture input...
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Last edited by nuetron; 09-16-2020 at 01:51 PM.
nuetron is offline   Reply With Quote
Old 09-16-2020, 02:04 PM   #32
nuetron
Member
nuetron began at the beginning.
 
Posts: 16
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
Logs from Ultimatereaderapp:

16777238 and 1677239 is from the page up and page down buttons on the Libra H2O.

Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
KoboKb: Attempting to capture input...
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
ping: sendto: Network is unreachable
Connecting to Wifi...
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
udhcpc: sending select for 192.168.1.101
udhcpc: lease of 192.168.1.101 obtained, lease time 7200
Connected successfully in 6782 ms.
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Powerkey press
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
Powerkey release
ifconfig: SIOCSIFADDR: No such device
Disconnected in 1817 ms.
"09:45:15" Going to sleep...
"09:45:17" suspending to RAM
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
Powerkey release
"09:45:17" Waking up...
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
ping: sendto: Network is unreachable
Connecting to Wifi...
Powerkey release
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
udhcpc: sending select for 192.168.1.101
udhcpc: lease of 192.168.1.101 obtained, lease time 7176
Connected successfully in 4880 ms.
ifconfig: SIOCSIFADDR: No such device
Disconnected in 1809 ms.
"09:45:24" Going to sleep...
"09:45:26" suspending to RAM
nuetron is offline   Reply With Quote
Advert
Old 09-16-2020, 03:40 PM   #33
nuetron
Member
nuetron began at the beginning.
 
Posts: 16
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
Just looking at the logs, is it because Max Pressure is 0?
nuetron is offline   Reply With Quote
Old 09-16-2020, 03:51 PM   #34
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,497
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
That sounds mildly suspicious, and doesn't agree with evemu on my Forma:

Code:
# EVEMU 1.3
# Kernel: 4.1.15-00286-g2a6a4cb08c66
# Input device name: "cyttsp5_mt"
# Input device ID: bus 0000 vendor 0000 product 0000 version 0000
# Supported events:
#   Event type 0 (EV_SYN)
#     Event code 0 (SYN_REPORT)
#     Event code 1 (SYN_CONFIG)
#     Event code 2 (SYN_MT_REPORT)
#     Event code 3 (SYN_DROPPED)
#     Event code 4 ((null))
#     Event code 5 ((null))
#     Event code 6 ((null))
#     Event code 7 ((null))
#     Event code 8 ((null))
#     Event code 9 ((null))
#     Event code 10 ((null))
#     Event code 11 ((null))
#     Event code 12 ((null))
#     Event code 13 ((null))
#     Event code 14 ((null))
#     Event code 15 (SYN_MAX)
#   Event type 1 (EV_KEY)
#     Event code 320 (BTN_TOOL_PEN)
#     Event code 325 (BTN_TOOL_FINGER)
#     Event code 330 (BTN_TOUCH)
#   Event type 2 (EV_REL)
#   Event type 3 (EV_ABS)
#     Event code 48 (ABS_MT_TOUCH_MAJOR)
#       Value        0
#       Min          0
#       Max        255
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 49 (ABS_MT_TOUCH_MINOR)
#       Value        0
#       Min          0
#       Max        255
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 52 (ABS_MT_ORIENTATION)
#       Value        0
#       Min       -127
#       Max        127
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 53 (ABS_MT_POSITION_X)
#       Value        0
#       Min          0
#       Max       1919
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 54 (ABS_MT_POSITION_Y)
#       Value        0
#       Min          0
#       Max       1439
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 55 (ABS_MT_TOOL_TYPE)
#       Value        0
#       Min          0
#       Max          1
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 57 (ABS_MT_TRACKING_ID)
#       Value        0
#       Min          0
#       Max         15
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 58 (ABS_MT_PRESSURE)
#       Value        0
#       Min          0
#       Max        255
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 59 (ABS_MT_DISTANCE)
#       Value        0
#       Min          0
#       Max        255
#       Fuzz         0
#       Flat         0
#       Resolution   0
# Properties:
#   Property  type 1 (INPUT_PROP_DIRECT)
N: cyttsp5_mt
I: 0000 0000 0000 0000
P: 02 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 21 04 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 00 00 00 00 00 00 00 00
B: 03 00 00 00 00 00 00 f3 0e
B: 04 00 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
A: 30 0 255 0 0 0
A: 31 0 255 0 0 0
A: 34 -127 127 0 0 0
A: 35 0 1919 0 0 0
A: 36 0 1439 0 0 0
A: 37 0 1 0 0 0
A: 39 0 15 0 0 0
A: 3a 0 255 0 0 0
A: 3b 0 255 0 0 0
################################
#      Waiting for events      #
################################
E: 0.000001 0001 0145 0001      # EV_KEY / BTN_TOOL_FINGER      1
E: 0.000001 0001 014a 0001      # EV_KEY / BTN_TOUCH            1
E: 0.000001 0003 0039 0000      # EV_ABS / ABS_MT_TRACKING_ID   0
E: 0.000001 0003 003b 0000      # EV_ABS / ABS_MT_DISTANCE      0
E: 0.000001 0003 0035 1820      # EV_ABS / ABS_MT_POSITION_X    1820
E: 0.000001 0003 0036 0118      # EV_ABS / ABS_MT_POSITION_Y    118
E: 0.000001 0003 003a 0038      # EV_ABS / ABS_MT_PRESSURE      38
E: 0.000001 0003 0030 0023      # EV_ABS / ABS_MT_TOUCH_MAJOR   23
E: 0.000001 0003 0031 0011      # EV_ABS / ABS_MT_TOUCH_MINOR   11
E: 0.000001 0003 0034 0125      # EV_ABS / ABS_MT_ORIENTATION   125
E: 0.000001 0000 0002 0000      # ++++++++++++ SYN_MT_REPORT (0) ++++++++++
E: 0.000001 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +0ms
E: 0.076485 0001 014a 0000      # EV_KEY / BTN_TOUCH            0
E: 0.076485 0001 0145 0000      # EV_KEY / BTN_TOOL_FINGER      0
E: 0.076485 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +76ms
For whatever it's worth, on a H2O:

Code:
# EVEMU 1.3
# Kernel: 2.6.35.3-850-gbc67621+
# Input device name: "zForce-ir-touch"
# Input device ID: bus 0x18 vendor 0000 product 0000 version 0000
# Supported events:
#   Event type 0 (EV_SYN)
#     Event code 0 (SYN_REPORT)
#     Event code 1 (SYN_CONFIG)
#     Event code 2 (SYN_MT_REPORT)
#     Event code 3 (SYN_DROPPED)
#     Event code 4 ((null))
#     Event code 5 ((null))
#     Event code 6 ((null))
#     Event code 7 ((null))
#     Event code 8 ((null))
#     Event code 9 ((null))
#     Event code 10 ((null))
#     Event code 11 ((null))
#     Event code 12 ((null))
#     Event code 13 ((null))
#     Event code 14 ((null))
#     Event code 15 (SYN_MAX)
#   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
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 1 (ABS_Y)
#       Value        0
#       Min          0
#       Max       1080
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 16 (ABS_HAT0X)
#       Value        0
#       Min          0
#       Max       1440
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 17 (ABS_HAT0Y)
#       Value        0
#       Min          0
#       Max       1080
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 24 (ABS_PRESSURE)
#       Value        0
#       Min          0
#       Max       2048
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 48 (ABS_MT_TOUCH_MAJOR)
#       Value        0
#       Min          0
#       Max          2
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 50 (ABS_MT_WIDTH_MAJOR)
#       Value        0
#       Min          0
#       Max         15
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 53 (ABS_MT_POSITION_X)
#       Value        0
#       Min          0
#       Max       1440
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 54 (ABS_MT_POSITION_Y)
#       Value        0
#       Min          0
#       Max       1080
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 57 (ABS_MT_TRACKING_ID)
#       Value        0
#       Min          1
#       Max          2
#       Fuzz         0
#       Flat         0
#       Resolution   0
# Properties:
N: zForce-ir-touch
I: 0018 0000 0000 0000
P: 00 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 04 00 00 00 00 00 18 00
B: 01 00 04 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 00 00 00 00 00 00 00 00
B: 03 03 00 03 01 00 00 65 02
B: 04 00 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
A: 00 0 1440 0 0 0
A: 01 0 1080 0 0 0
A: 10 0 1440 0 0 0
A: 11 0 1080 0 0 0
A: 18 0 2048 0 0 0
A: 30 0 2 0 0 0
A: 32 0 15 0 0 0
A: 35 0 1440 0 0 0
A: 36 0 1080 0 0 0
A: 39 1 2 0 0 0
################################
#      Waiting for events      #
################################
NiLuJe is offline   Reply With Quote
Old 09-17-2020, 06:20 PM   #35
Patatas
Member
Patatas began at the beginning.
 
Posts: 11
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
Quote:
Originally Posted by OfficerAction View Post
I would appeciate if you can help me with some tests.
Happy to help!

I'm having the same results in the logs for my Kobo Libra H2O. Info from my setup:

Firmware: Kobo Libra H2O Latest, 4.23.15548
Launcher: NickelMenu, from the 1 click installed latest version (OCP-Plato-0.9.3_KOReader-v2020.09.zip)

Some more info (basically repeated, but might help):
- Both UMR and Scribble app turn off the brightness of the screen as soon as they are launched.
- UMR reacts to the power button by blocking and unblocking the device. (Scribble does not)
- No response at all from the screen touch on both apps. Only solution was to force shut down the device.

Scribble log:
Spoiler:
Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
KoboKb: Attempting to capture input...
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  released
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released


I will change the parameters you mentioned to see if I get some different results. If there is some other info that could make it easier let me know, as I wasn't sure what would be helpful...
Patatas is offline   Reply With Quote
Advert
Old 09-18-2020, 04:27 AM   #36
reexe
Member
reexe began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Apr 2019
Device: Kobo Aura second edition
Wow new version, how have I missed this XD

Does this new version have a way of inverting page flip? I want to turn pages like a real manga book.
If there is none, can someone point me in the right direction to where I could flip it in the code and compile it myself?
reexe is offline   Reply With Quote
Old 09-18-2020, 09:07 AM   #37
OfficerAction
Connoisseur
OfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughing
 
Posts: 80
Karma: 63118
Join Date: May 2018
Device: Kobo Aura One
Quote:
Originally Posted by reexe View Post
Wow new version, how have I missed this XD

Does this new version have a way of inverting page flip? I want to turn pages like a real manga book.
If there is none, can someone point me in the right direction to where I could flip it in the code and compile it myself?
There are options for that in the settings menu.
OfficerAction is offline   Reply With Quote
Old 09-18-2020, 02:52 PM   #38
reexe
Member
reexe began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Apr 2019
Device: Kobo Aura second edition
I am trying the latest verion that was released today, I catn see any setting to invert page flipping on my Aura One, only a setting where you can change hardware buttons, and i dont have those :/

Would also be nice to see page nr in a corner all the time
reexe is offline   Reply With Quote
Old 09-18-2020, 02:57 PM   #39
reexe
Member
reexe began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Apr 2019
Device: Kobo Aura second edition
I was just being dumb and did not understand what the "left" and "right" in settings meant, I also think a miss-spelled entry in the settings had me thrown, it says "Tab:" and it probavly should say "Tap:", my brain told me it had to be a setting for a button that had the name "Tab"... :P

Edit: close button is missleading too, i press it all the time to close the favorites page XD maybe rename it to Quit?

Got to say awesome re-release tho!
reexe is offline   Reply With Quote
Old 09-18-2020, 03:32 PM   #40
OfficerAction
Connoisseur
OfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughing
 
Posts: 80
Karma: 63118
Join Date: May 2018
Device: Kobo Aura One
Quote:
Originally Posted by reexe View Post
I am trying the latest verion that was released today, I catn see any setting to invert page flipping on my Aura One, only a setting where you can change hardware buttons, and i dont have those :/
It's the tab and swipe option. You can set them to left or right.
OfficerAction is offline   Reply With Quote
Old 09-18-2020, 03:37 PM   #41
OfficerAction
Connoisseur
OfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughing
 
Posts: 80
Karma: 63118
Join Date: May 2018
Device: Kobo Aura One
Thanks for the feedback on the Libra. It's quite strange that no touches are recognized. Maybe you can try with this build. I have added some additional logging.

https://we.tl/t-GaWnwMCZFJ
OfficerAction is offline   Reply With Quote
Old 09-18-2020, 04:43 PM   #42
nuetron
Member
nuetron began at the beginning.
 
Posts: 16
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
Here are the logs for "test-v2.3.0" on a Libra H2O:

Scribble:
-Still no touch.
-Pressing power button kills the app? or crashes back to kobo home screen.
-Backlight is on when app is launched. edit: backlight is off on first launch of scribble. Pressing power button crashes the app. If launched again, the backlight now stays on when launched into scribble.
Spoiler:
Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
KoboKb: Attempting to capture input...
KoboKb: Capture keyboard input error: -1
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Key pressed!  16777238
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  pressed
found focusobject: true in.type: 1  | in.code:  193  | code: 16777238  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
Key pressed!  16777239
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  pressed
found focusobject: true in.type: 1  | in.code:  194  | code: 16777239  |  released
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed


UMR:
-Still no touch.
-Backlight is on when app is first launched. Turns off when power button is pressed and stays off when coming back into the app.
-Pressing power button goes into screensaver instead of crashing like Scribble.
Spoiler:
Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
ping: sendto: Network is unreachable
Connecting to Wifi...
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
udhcpc: sending select for 192.168.1.101
udhcpc: lease of 192.168.1.101 obtained, lease time 7200
Connected successfully in 7658 ms.
Powerkey press
Powerkey release
ifconfig: SIOCSIFADDR: No such device
Disconnected in 1823 ms.
"12:40:34" Going to sleep...
"12:40:36" suspending to RAM
Powerkey release
"12:40:37" Waking up...
ping: sendto: Network is unreachable
Connecting to Wifi...
Powerkey release
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
udhcpc: sending select for 192.168.1.101
udhcpc: lease of 192.168.1.101 obtained, lease time 7178
Connected successfully in 7503 ms.
ifconfig: SIOCSIFADDR: No such device
Disconnected in 1822 ms.
"12:40:47" Going to sleep...
"12:40:49" suspending to RAM
"12:41:47" Going to sleep...
"12:41:49" suspending to RAM
Last edited by nuetron; 09-18-2020 at 04:46 PM.
nuetron is offline   Reply With Quote
Old 09-19-2020, 09:44 AM   #43
Patatas
Member
Patatas began at the beginning.
 
Posts: 11
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
Same results on my Libra H20.
If there are other commands that we can try, or some other info that could be useful let us know. Also, maybe it could be useful to create logs from a different app that has a working touch input, like KOReader or Plato?

And thanks for working on it!

UMR:
Spoiler:
Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
ping: sendto: Network is unreachable
Connecting to Wifi...
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
udhcpc: sending select for 192.168.1.128
udhcpc: lease of 192.168.1.128 obtained, lease time 259200
Connected successfully in 6658 ms.
Powerkey press
Powerkey release
ifconfig: SIOCSIFADDR: No such device
Disconnected in 1814 ms.
"13:37:12" Going to sleep...
"13:37:14" suspending to RAM


Scribble:
Spoiler:
Code:
qt.qpa.input: evdevtouch: Adding device at /dev/input/event1
KoboKb: Attempting to capture input...
qt.qpa.input: evdevtouch: Using device /dev/input/event1
qt.qpa.input: evdevtouch: /dev/input/event1: Protocol type A  (multi), filtered=no
qt.qpa.input: evdevtouch: /dev/input/event1: min X: 0 max X: 1679
qt.qpa.input: evdevtouch: /dev/input/event1: min Y: 0 max Y: 1263
qt.qpa.input: evdevtouch: /dev/input/event1: min pressure: 0 max pressure: 0
qt.qpa.input: evdevtouch: /dev/input/event1: device name: cyttsp5_mt
qt.qpa.input: evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s)
Powerbutton Pressed!
found focusobject: true in.type: 1  | in.code:  116  | code: 16777483  |  pressed
KoboKb: attempting to release input...
Patatas is offline   Reply With Quote
Old 09-19-2020, 07:54 PM   #44
nuetron
Member
nuetron began at the beginning.
 
Posts: 16
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra H2O
I think the problem is that Plato and KoReader is not using QT. Can't really compare them since they are using something totally different.

For what it's worth.

Logs from Plato:
Spoiler:
Code:
Plato is running on a Kobo Libra H₂O.
The framebuffer resolution is 1264 by 1680.
Framebuffer rotation: 2 -> 2.
insmod: can't insert '': No such file or directory
ifconfig: SIOCGIFFLAGS: No such device
udhcpc: SIOCGIFINDEX: No such device
Framebuffer rotation: 0 -> 0.
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
Plato is running on a Kobo Libra H₂O.
The framebuffer resolution is 1264 by 1680.
Framebuffer rotation: 2 -> 2.
udhcpc: sending discover
udhcpc: sending select for 192.168.1.101
udhcpc: lease of 192.168.1.101 obtained, lease time 5452
Framebuffer rotation: 0 -> 0.
udhcpc: started, v1.31.1.kobo
udhcpc: sending discover
Plato is running on a Kobo Libra H₂O.
The framebuffer resolution is 1264 by 1680.
Framebuffer rotation: 2 -> 2.
udhcpc: sending discover
udhcpc: sending select for 192.168.1.101
udhcpc: lease of 192.168.1.101 obtained, lease time 7200
Attached Thumbnails
Click image for larger version Name: Capture.jpg Views: 442 Size: 41.5 KB ID: 182031  
Last edited by nuetron; 09-19-2020 at 08:02 PM.
nuetron is offline   Reply With Quote
Old 09-20-2020, 10:01 AM   #45
MacPhernand
Junior Member
MacPhernand began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Sep 2020
Device: Kobo Clara HD
Hi, I'm using the latest version on a Kobo Clara HD, and can confirm, starts up fine from Nickel, wi fi is detected fine, but has NO touch input at all, it needs to be closed with the power button to be able to access the Kobo home screen.
MacPhernand is offline   Reply With Quote
Reply
Page 3 of 21 12 3 4567 Last »

« Previous Thread | Next Thread »

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
The ultimate reader app: Gyan Reader Ti-Ron Android Devices 14 01-08-2013 10:56 AM
Looking for the ultimate reader app olivertimm Apple Devices 8 05-17-2012 04:17 PM
What was your ultimate reason for getting an E-Reader? tiniree General Discussions 202 11-23-2011 03:27 PM
Which product to buy as Manga reader and ebook reader only. Renji Alternative Devices 9 01-16-2010 11:42 PM
LG Solar Cell e-reader: ultimate book for the beach yagiz News 9 10-19-2009 08:04 PM


All times are GMT -4. The time now is 07:12 AM.

Contact Us - FAQ - Guidelines - Privacy - Top

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