Android device information
Produce a trustworthy profile of a connected device so downstream automation
picks the right coordinates, input mode, and vision fallback.
When to use
- Before driving UI / input / files on an unfamiliar device.
- When the user asks "what device is connected?" or about its specs.
- To choose tap vs. swipe behaviour, DPI, orientation, and resolution.
Tools used
device_info — model, manufacturer, Android/API level, build, SDK features.
status — connection state, serial, online state.
screen_info — resolution, density, orientation, display modes.
verify — confirms the device answers a harmless probe (readiness).
Procedure
device_info to gather identity + build + capability fields.
screen_info for the display surface the UI skills will act on.
status to record transport health alongside the profile.
- Return a single structured profile with fields used by
android-ui /
android-input (resolution, density, orientation, API level).
Evidence
Profile fields are the evidence: serial, model, API level, resolution, density,
screen state. No profile → do not proceed to coordinate-based work.
Related skills
android-discovery · android-adb · android-screen · android-control
1---2name: android-device-info3description: Read the full device profile — model, Android/API level, build, screen, battery, memory, and capability flags. Use before automation that depends on device capabilities, or to report what a device actually is.4tools: device_info, status, screen_info, verify5dependencies: android-adb6security: Read-only — safe to run freely. No device state is modified.7metadata:8 source: https://skillmd.com/skills/samraddhashrivastavatech/android-device-info9---1011# Android device information1213Produce a trustworthy profile of a connected device so downstream automation14picks the right coordinates, input mode, and vision fallback.1516## When to use1718- Before driving UI / input / files on an unfamiliar device.19- When the user asks "what device is connected?" or about its specs.20- To choose tap vs. swipe behaviour, DPI, orientation, and resolution.2122## Tools used2324- `device_info` — model, manufacturer, Android/API level, build, SDK features.25- `status` — connection state, serial, online state.26- `screen_info` — resolution, density, orientation, display modes.27- `verify` — confirms the device answers a harmless probe (readiness).2829## Procedure30311. `device_info` to gather identity + build + capability fields.322. `screen_info` for the display surface the UI skills will act on.333. `status` to record transport health alongside the profile.344. Return a single structured profile with fields used by `android-ui` /35 `android-input` (resolution, density, orientation, API level).3637## Evidence3839Profile fields are the evidence: serial, model, API level, resolution, density,40screen state. No profile → do not proceed to coordinate-based work.4142## Related skills4344`android-discovery` · `android-adb` · `android-screen` · `android-control`