execute the following command to insert the text into a view with a focus (if it supports text input)

adb shell "input keyboard text 'Paste text on Android Device'"

input text 'Paste text on Android Device'

adb shell "input keyboard text 'Paste%stext%son%sAndroid%sDevice'"

Send events

To simulate pressing the hardware power key

adb shell input keyevent 26

or alternatively

adb shell input keyevent POWER

Even if you don't have a hardware key you still can use a keyevent to perform the equivalent action

adb shell input keyevent CAMERA

Send touch event as input

adb shell input tap Xpoint Ypoint

Send swipe event as input

adb shell input swipe Xpoint1 Ypoint1 Xpoint2 Ypoint2 [DURATION*]

*DURATION is optional, default=300ms. source

Get X and Y points by enabling pointer location in developer option.

ADB sample shell script

To run a script in Ubuntu, Create script.sh right click the file and add read/write permission and tick allow executing file as program.

Open terminal emulator and run the command ./script.sh

Script.sh

 for (( c=1; c<=5; c++ ))
    do  
       adb shell input tap X Y
       echo "Clicked $c times"
       sleep 5s
    done

For a comprehensive list of event numbers

• shortlist of several interesting events ADB Shell Input Events
• reference documentation https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_POWER.

Prints all packages, optionally only those whose package name contains the text in <FILTER>.

adb shell pm list packages [options] <FILTER>

All <FILTER>

adb shell pm list packages

Attributes:

-f to see their associated file.

-i See the installer for the packages.

-u to also include uninstalled packages.

-u Also include uninstalled packages.

Attributes that filter:

-d for disabled packages.

-e for enabled packages.

-s for system packages.

-3 for third party packages.

--user <USER_ID> for a specific user space to query.

A one-liner that helps granting or revoking vulnerable permissions.

• granting

  adb shell pm grant <sample.package.id> android.permission.<PERMISSION_NAME>
  

• revoking

  adb shell pm revoke <sample.package.id> android.permission.<PERMISSION_NAME>
  

• Granting all run-time permissions at a time on installation (-g)

  adb install -g /path/to/sample_package.apk
  

This command print all relevant application data:

• version code
• version name
• granted permissions (Android API 23+)
• etc..

adb shell dumpsys package <your.package.id>

Notice, that in order to change file prmissions, your device need to be rooted, su binary doesn't come with factory shipped devices!

Convention:

adb shell su -c "chmod <numeric-permisson> <file>"

Numeric permission constructed from user, group and world sections.

For example, if you want to change file to be readable, writable and executable by everyone, this will be your command:

adb shell su -c "chmod 777 <file-path>"

Or

adb shell su -c "chmod 000 <file-path>"

if you intent to deny any permissions to it.

1st digit-specifies user permission, 2nd digit- specifies group permission, 3rd digit - specifies world (others) permission.

Access permissions:

--- :   binary value:   000,  octal value: 0 (none)
--x :   binary value:   001,  octal value: 1 (execute)
-w- :   binary value:   010,  octal value: 2 (write)
-wx :   binary value:   011,  octal value: 3 (write, execute)
r-- :   binary value:   100,  octal value: 4 (read)
r-x :   binary value:   101,  octal value: 5 (read, execute)
rw- :   binary value:   110,  octal value: 6 (read, write)
rwx :   binary value:   111,  octal value: 7 (read, write, execute)

adb shell am start -n com.android.settings/.DevelopmentSettings

Will navigate your device/emulator to the Developer Options section.

This is relevant for apps that implement a BootListener. Test your app by killing your app and then test with:

adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -c android.intent.category.HOME -n your.app/your.app.BootListener

(replace your.package/your.app.BootListener with proper values).

View content:

adb shell ls \$EXTERNAL_STORAGE
adb shell ls \$SECONDARY_STORAGE

View path:

adb shell echo \$EXTERNAL_STORAGE
adb shell echo \$SECONDARY_STORAGE

Sometimes Android's logcat is running infinitely with errors coming from some process not own by you, draining battery or just making it hard to debug your code.

A convenient way to fix the problem without restarting the device is to locate and kill the process causing the problem.

From Logcat

03-10 11:41:40.010 1550-1627/? E/SomeProcess: ....

notice the process number: 1550

Now we can open a shell and kill the process. Note that we cannot kill root process.

adb shell

inside the shell we can check more about the process using

ps -x | grep 1550

and kill it if we want:

kill -9 1550