Thread: Modding Libra 2
View Single Post
Old 10-24-2021, 01:45 PM   #29
xor_
Zealot
xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.xor_ ought to be getting tired of karma fortunes by now.
 
Posts: 123
Karma: 1027062
Join Date: Nov 2012
Location: Berlin
Device: Kobo Elipsa 2e, Kobo Forma, Tolino Epos 2
Quote:
Originally Posted by NiLuJe View Post
Okay, so the finger_trace binary from last night https://www.mobileread.com/forums/sh...9&postcount=21 *should* behave properly, right?
I'm afraid it's not so easy. I get a lot of errors like the following, and afterwards weirdness happens.

Quote:
libevdev error in sanitize_event: BUG: Device "Elan Touchscreen" received a double tracking ID 247 in slot 0.
As far as I an tell, with fbdepth -R UR, the movement tracking is always correct. With UD, it's always reversed.

With CW and CCW, it's mostly screen corruption and no easily decipherable correlation to my finger movements.
Attached Files
File Type: zip ftrace-test.zip (162.3 KB, 145 views)
Last edited by xor_; 10-24-2021 at 01:51 PM.
xor_ is offline   Reply With Quote