View Single Post
Old 01-19-2022, 03:08 PM   #25
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by llinfeng View Post
[*] When I toggle the "Finger Touch" function, I found the following patterns:
Code:
01-18 12:23:59.437  1436  1436 I TouchInteractionService: onReceive Intent { act=onyx.action.DO_NOT_INTERCEPT_GESTURE flg=0x1000010 }   flags 0

01-18 16:54:08.631  1436  1436 W TouchInteractionService: Intercept gesture TP disable
can I assign a dedicated key to disable/enable "Finger Touch" by editing /system/usr/keylayout?
Nope.

When you click the "finger touch" quick pane an intent is generated, as you can see in logcat.

You can use an app that uses the accesibility framework, catches a defined key press and emits the same intent you see on your log. That's it "onyx.action.DO_NOT_INTERCEPT_GESTURE"

You need to know if the flags change based on current state (enabled/disabled) or they are the same on both and the service that catches the intent just flips current state. You can do that pressing the "finger touch" thingy a few times and watching at the log. Do you see the same flags?.

An example of an app that uses the accesibility framework to map keys to other things is https://github.com/sds100/KeyMapper. They have wonderful docs available following the links in the link
pazos is offline   Reply With Quote