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.4---56# Android device information78Produce a trustworthy profile of a connected device so downstream automation9picks the right coordinates, input mode, and vision fallback.1011## When to use1213- Before driving UI / input / files on an unfamiliar device.14- When the user asks "what device is connected?" or about its specs.15- To choose tap vs. swipe behaviour, DPI, orientation, and resolution.1617## Tools used1819- `device_info` — model, manufacturer, Android/API level, build, SDK features.20- `status` — connection state, serial, online state.21- `screen_info` — resolution, density, orientation, display modes.22- `verify` — confirms the device answers a harmless probe (readiness).2324## Procedure25261. `device_info` to gather identity + build + capability fields.272. `screen_info` for the display surface the UI skills will act on.283. `status` to record transport health alongside the profile.294. Return a single structured profile with fields used by `android-ui` /30 `android-input` (resolution, density, orientation, API level).3132## Evidence3334Profile fields are the evidence: serial, model, API level, resolution, density,35screen state. No profile → do not proceed to coordinate-based work.3637## Related skills3839`android-discovery` · `android-adb` · `android-screen` · `android-control`
SAMRADDHASHRIVASTAVATECH