
Android device information ADB commands: Collect Android OS, kernel, screen and battery information with read-only ADB shell commands for debugging and support. This guide explains what each command does, its syntax, practical examples, useful options, and common mistakes. Commands are shown for typical installations; flags can vary across operating-system and tool versions.
Before you start
Open a terminal appropriate for the operating system shown in the examples. Check that the required tool is installed and that you are running it with the permissions needed for your task. Replace sample names, paths, hostnames and IDs with values from your own environment.
Syntax at a glance
Square brackets usually indicate optional arguments, while uppercase words such as FILE, HOST and PACKAGE are placeholders that you replace. Keep quotes around paths or text that contains spaces. Commands should be tested on a safe sample before being used in production.
Quick command reference
| Command | What it does | Example | Useful options |
|---|---|---|---|
getprop | Read Android system properties | adb shell getprop ro.build.version.release | Without a property it lists many values; output may contain device details |
adb shell uname -a | Display kernel/platform information | adb shell uname -a | Exact output depends on device kernel |
adb shell wm size | Read display resolution overrides | adb shell wm size | No argument queries current configuration |
adb shell wm density | Read display density settings | adb shell wm density | No argument queries configured density |
adb shell dumpsys battery | Show battery service status | adb shell dumpsys battery | Output can include status, level, health and power source |
Command syntax and examples explained
1. getprop
Purpose: Read Android system properties.
Syntax
adb shell getprop PROPERTYExample
adb shell getprop ro.build.version.releaseOptions and notes: Without a property it lists many values; output may contain device details.
Do not publicly share serials or unique identifiers from full property dumps.
2. adb shell uname -a
Purpose: Display kernel/platform information.
Syntax
adb shell uname -aExample
adb shell uname -aOptions and notes: Exact output depends on device kernel.
Useful for collecting a quick kernel report.
3. adb shell wm size
Purpose: Read display resolution overrides.
Syntax
adb shell wm sizeExample
adb shell wm sizeOptions and notes: No argument queries current configuration.
An override may differ from the panel’s physical resolution.
4. adb shell wm density
Purpose: Read display density settings.
Syntax
adb shell wm densityExample
adb shell wm densityOptions and notes: No argument queries configured density.
This can help debug layout issues across device screens.
5. adb shell dumpsys battery
Purpose: Show battery service status.
Syntax
adb shell dumpsys batteryExample
adb shell dumpsys batteryOptions and notes: Output can include status, level, health and power source.
Battery reports are snapshots, not a long-term health test.
Common mistakes and troubleshooting
- Command not found: confirm the tool is installed and available on your PATH; open a new terminal after changing PATH.
- Permission denied: verify the current account, file permissions and target path. Use administrator/root privileges only when genuinely required.
- Unexpected output: check the command version, quoting, current directory and exact arguments. Consult the local help or manual for options supported by your build.
- Destructive operations: preview the target and keep a backup before deleting data, rewriting history, flashing a partition or changing system configuration.
Safety tips
Review every command before running it, especially commands that delete files, change permissions, flash firmware, alter a database or expose a network service. For network scanning and remote administration, work only on devices and systems you own or are authorized to test. Keep credentials, private keys, access tokens and log files private.
Frequently asked questions
Do these commands work on every system?
Not always. Some commands are specific to Windows, Linux, Android, a particular package manager or an installed tool version. Use the syntax shown for your platform and check local help when a flag is unavailable.
Can I copy and run every example exactly?
Use the examples as templates. Replace placeholders such as filenames, package IDs, hostnames and paths with your own values, and verify the effect before executing a command that changes data or system state.
Conclusion
Use this reference as a starting point, then confirm flags in the tool’s official help or manual for your installed version. A clear understanding of syntax, options and side effects makes command-line work more reliable.