## Launching Activities via ADB
When developing on an Android device or emulator, there are times when you need to check the exact name of an installed package or find information about a specific screen (Activity). 
We summarize how to check this through ADB (Android Debug Bridge) commands and launch the desired Activity directly.
### 1. Get ADB Root Permissions
First, obtain root permissions to run system commands smoothly.
```sh
{
 "title": "Adb root command"
}
---
$ adb root
adbd is already running as root
```
### 2. Check Installed Package List
You can see a list of all packages installed on the system using the pm list packages command.
```sh
{
 "title": "List all installed packages"
}
---
$ adb shell pm list packages
...
package:com.android.bookmarkprovider
//[!code highlight]
package:com.android.settings
package:com.cyanogenmod.eleven
package:com.android.calculator2
package:org.lineageos.updater
package:com.android.cts.ctsshim
package:com.android.vpndialogs
...
```
### 3. Analyze Activity Information for Specific Packages
Use the resolve-activity command to check which Activity a specific component consists of, or what the intent filter information is.
```sh
{
 "title": "Resolve activity for settings"
}
---
$ adb shell cmd package resolve-activity --brief com.android.settings
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=true
//[!code highlight]
com.android.settings/.Settings
```
### 4. Launch Activity Directly
Based on the analyzed Activity information, you can use the am start command to launch the screen immediately.
```sh
{
 "title": "Start activity directly"
}
---
//[!code word:com.android.settings/.Settings]
$ adb shell am start -n com.android.settings/.Settings
Starting: Intent { cmp=com.android.settings/.Settings }
```
Using the package name/class name format as shown above allows you to launch not only the app's main screen but also specific settings screens exposed to the outside.

How to launch a package via ADB commands.