can someone who achieved accessibility, post all steps in detail?
i tried tadds version, but don’t get the commands in robot right.
ok. i got it done using e-robot and secure settings.
was quite hard to get the events and actions right, at the very beginning.
anyone needs help doing the same can contact me.
Jul 13, 2017 8:07:35 GMT 1 seb84 said:
ok. i got it done using e-robot and secure settings. was quite hard to get the events and actions right, at the very beginning.anyone needs help doing the same can contact me.
it is better that you open a new thread explaining how you’ve done it:)
done like you told me:
/thread/1329/accessibility-service-enabling-using-robot
guide with picture guide to download
Has anybody tried with adb shell input tap?
adb shell input tap 123 456
The experimenter will have to guess the coordinates of the control in the GUI.
By the way: what is the command to start the Accessibility Settings? Something like
adb shell am start -n com.android.settings/.AccessibilitySettings
(which I just made up. Although it could work…).
Mar 17, 2018 22:41:44 GMT 1 mdp said:
Has anybody tried with `adb shell input tap`? adb shell input tap 123 456 The experimenter will have to guess the coordinates of the control in the GUI.By the way: what is the command to start the Accessibility Settings? Something like
adb shell am start -n com.android.settings/.AccessibilitySettings
(which I just made up. Although it could work…).
I tried tapping around inside and outside the borders of the accessibility information screen we cannot get past
( Accessibility > Services > Button Remapper > “…you have to turn on the service… [but nowhere to click…]” )
but I could not seem trigger anything. Does anybody have an idea of where the “Ok”, checkbox etc. is supposed to be?
I also tried many keys in that screen and got no effect.
But I found out the following: in the LEM6, the two buttons on the left side, by firmware “compass” and “heart rate”, are “Left” and “Right”, or KEYCODE_DPAD_LEFT ( = 21 ) and KEYCODE_DPAD_RIGHT ( = 22 ).
Also, I think I could reduce the brightness through KEYCODE_BRIGHTNESS_DOWN ( = 220 ), which is useful because this watch has a very high brighteness that the standard interface does not reduce.