Android connection checks depend on the phone port, cable path, permission prompt, and device screen. Treat each condition as a separate layer so the result is easy to understand and repeat.

Identify the phone connection path
Confirm whether the phone uses a direct USB-C path or an adapter path. Keep this separate from app setup. If app entry is part of the question, start from Official App Download and Installation Guide.
Use a data-capable cable path
Charging behavior alone does not prove a data path. Cable purpose and port behavior are reviewed in USB-C Data Cable or Charging Cable.
Check mobile permission prompts
Android may show USB or nearby-device prompts depending on model and system version. Change one permission state at a time and record whether the device screen changes.
Keep wireless and wired notes separate
If Bluetooth is also being tested, write a separate note. Mobile pairing has a different path, covered in How to Pair Ledger with a Phone over Bluetooth.
For Android, record the phone model, cable or adapter, permission prompt, and visible device screen. Keep wired and wireless checks in separate notes so the result stays easy to compare.