It does not seem due to the previous and following characters.
Tchap and EteSync typing password misses some in the middle notably.
adb shell input -h
Output:
Usage: input [<source>] [-d DISPLAY_ID] <command> [<arg>...]
The sources are:
touchnavigation
touchscreen
joystick
stylus
touchpad
gamepad
dpad
mouse
keyboard
trackball
rotaryencoder
[axis_value] represents an option specifying the value of a given axis
The syntax is as follows: --axis <axis_name>,<axis_value>
where <axis_name> is the name of the axis as defined in
MotionEvent without the AXIS_ prefix (e.g. SCROLL, X)
Sample [axis_values] entry: `--axis Y,3`, `--axis SCROLL,-2`
-d: specify the display ID.
(Default: -1 for key event, 0 for motion event if not specified.)
The commands and default sources are:
text <string> (Default: keyboard)
keyevent [--longpress|--duration <duration to hold key down in ms>] [--doubletap] [--async] [--delay <duration between keycodes in ms>] <key code number or name> ... (Default: keyboard)
tap <x> <y> (Default: touchscreen)
swipe <x1> <y1> <x2> <y2> [duration(ms)] (Default: touchscreen)
draganddrop <x1> <y1> <x2> <y2> [duration(ms)] (Default: touchscreen)
press (Default: trackball)
roll <dx> <dy> (Default: trackball)
motionevent <DOWN|UP|MOVE|CANCEL> <x> <y> (Default: touchscreen)
scroll (Default: rotaryencoder). Has the following syntax:
scroll <x> <y> [axis_value] (for pointer-based sources)
scroll [axis_value] (for non-pointer-based sources)
Axis options: SCROLL, HSCROLL, VSCROLL
None or one or multiple axis value options can be specified.
To specify multiple axes, use one axis option for per axis.
Example: `scroll --axis VSCROLL,2 --axis SCROLL,-2.4`
keycombination [-t duration(ms)] <key code 1> <key code 2> ... (Default: keyboard, the key order is important here.)
so there does not seem to be a delay that we can specify for text, could emulate key by key, but that's not effective.
adb shell input text -h
does not return anything.
It does not seem due to the previous and following characters.
Tchap and EteSync typing password misses some in the middle notably.
```
adb shell input -h
```
<details>
<summary>Output:</summary>
```
Usage: input [<source>] [-d DISPLAY_ID] <command> [<arg>...]
The sources are:
touchnavigation
touchscreen
joystick
stylus
touchpad
gamepad
dpad
mouse
keyboard
trackball
rotaryencoder
[axis_value] represents an option specifying the value of a given axis
The syntax is as follows: --axis <axis_name>,<axis_value>
where <axis_name> is the name of the axis as defined in
MotionEvent without the AXIS_ prefix (e.g. SCROLL, X)
Sample [axis_values] entry: `--axis Y,3`, `--axis SCROLL,-2`
-d: specify the display ID.
(Default: -1 for key event, 0 for motion event if not specified.)
The commands and default sources are:
text <string> (Default: keyboard)
keyevent [--longpress|--duration <duration to hold key down in ms>] [--doubletap] [--async] [--delay <duration between keycodes in ms>] <key code number or name> ... (Default: keyboard)
tap <x> <y> (Default: touchscreen)
swipe <x1> <y1> <x2> <y2> [duration(ms)] (Default: touchscreen)
draganddrop <x1> <y1> <x2> <y2> [duration(ms)] (Default: touchscreen)
press (Default: trackball)
roll <dx> <dy> (Default: trackball)
motionevent <DOWN|UP|MOVE|CANCEL> <x> <y> (Default: touchscreen)
scroll (Default: rotaryencoder). Has the following syntax:
scroll <x> <y> [axis_value] (for pointer-based sources)
scroll [axis_value] (for non-pointer-based sources)
Axis options: SCROLL, HSCROLL, VSCROLL
None or one or multiple axis value options can be specified.
To specify multiple axes, use one axis option for per axis.
Example: `scroll --axis VSCROLL,2 --axis SCROLL,-2.4`
keycombination [-t duration(ms)] <key code 1> <key code 2> ... (Default: keyboard, the key order is important here.)
```
</details>
so there does not seem to be a delay that we can specify for `text`, could emulate key by key, but that's not effective.
```
adb shell input text -h
```
does not return anything.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It does not seem due to the previous and following characters.
Tchap and EteSync typing password misses some in the middle notably.
Output:
so there does not seem to be a delay that we can specify for
text, could emulate key by key, but that's not effective.does not return anything.
Could leverage KeePassDX.
Output:
Related to #5.
May help the issue: