Android Studio Running Device Not Showing | Fix It Fast

Guide / By

A hidden panel, stale ADB, or a bad USB link is the usual cause when android studio running device not showing.

You hit Run. The build finishes. Then the device dropdown is empty, or the chooser keeps spinning with no target. That blocks everything that matters: installing, debugging, testing, even a quick UI check.

Android Studio relies on several links: tool windows, ADB, USB approval, and an emulator that can render. When one link breaks, the list can look blank.

The steps below follow a simple order. Start with UI and layout fixes that take seconds. Then reset ADB. Then handle USB and drivers. Last, repair the emulator when it boots in a broken state. Stop as soon as the device appears and your app installs.

Why The Device List Goes Empty

Android Studio shows a run target only when three things line up. A device must be available, Android Studio must detect it, and your project must be able to deploy to it. A slip in any one of those spots can make the list look empty.

  • A tool window is hidden — The device exists, but the panel that shows it is closed, undocked, or off-screen.
  • ADB is out of sync — The phone is connected, yet the debug bridge is stuck on an old session.
  • USB access is blocked — Charging works, data does not, or the host machine lacks the right driver.
  • The emulator is misbehaving — The AVD boots, then the window never surfaces or the instance fails at boot.
  • The app is filtered out — The device is present, but your build cannot install on it, so it never shows as a target.

Do one fast reality check before you change anything else. Open a terminal and run adb devices. If the list is empty, this points to USB, drivers, or authorization. If it lists a device but Android Studio shows none, the IDE side needs attention.

Android Studio Running Device Not Showing

The table below maps what you see to a first move that fixes the most cases. After each step, retry Run so you know what worked.

What You See Most Likely Cause First Move
Run menu shows no devices ADB server stuck or device not approved Restart ADB, reconnect, approve prompt
Emulator boots but no window Saved window position is off-screen Reset emulator window position
Device Manager is missing Tool window closed or moved Reopen Device Manager from the View menu
Phone charges but never appears Power-only cable, wrong USB mode, or driver issue Swap cable, set File Transfer, refresh driver
adb sees a device, Studio does not IDE state or ADB integration glitch Invalidate caches, restart Studio, restart ADB

If two rows match at once, start with the UI rows first. It is faster to restore a hidden panel than to reinstall drivers.

Running Device Not Showing In Android Studio On Windows

Windows adds one extra variable: drivers. A phone can charge and still fail to expose an ADB interface. Aim at the right layer in order: phone settings, USB mode, then the driver stack.

Confirm Debugging And Authorization

When you connect a phone for the first time, Android may ask to allow USB debugging for your computer. If you miss the prompt, Android Studio never gets a stable session.

  1. Enable Developer Options — Open Settings, go to About phone, then tap Build number until the developer menu appears.
  2. Turn On USB Debugging — In Developer options, switch on USB debugging.
  3. Reset Debug Authorizations — Revoke USB debugging authorizations, unplug, then plug back in and approve the prompt.

If adb devices shows an unauthorized entry, keep the phone screen on, reconnect, then approve the prompt.

Use A Data Cable And The Right USB Mode

Many cables carry power only. Some phones also default to charging mode, which blocks data. Fix both before you chase drivers.

  • Switch To File Transfer — From the USB notification, choose File Transfer or MTP.
  • Try A Known Data Cable — Use the cable you have used for file transfers before.
  • Plug Into A Direct Port — Connect to the computer, not a monitor port or a hub.

Repair Drivers When ADB Sees Nothing

If adb devices stays blank after you confirm debugging plus cable, Windows may not have a driver that exposes the ADB interface for your model.

  1. Update Platform Tools — In SDK Manager, update Android SDK Platform-Tools so ADB is current.
  2. Install Google USB Driver — In SDK Manager on Windows, install the Google USB Driver package.
  3. Update The Phone Driver — In Windows Device Manager, locate the phone entry, update the driver, then reconnect.
  4. Restart ADB — Run adb kill-server then adb start-server.

Once adb devices lists your phone as device, Android Studio should show it soon after. If it does not, jump to the next section and reset the IDE state.

Bring Back The Missing Panels And Selectors

Sometimes the device exists and ADB is healthy, yet Android Studio shows nothing because the relevant window is closed, undocked, or hidden behind a layout state. This section fixes the “it is there, I just cannot see it” class of problems.

  1. Open Device Manager — Use View > Tool Windows > Device Manager and confirm your virtual devices list shows up.
  2. Open Running Devices — Use View > Tool Windows > Running Devices so an embedded emulator can appear.
  3. Restore Default Layout — Use Window > Restore Default Layout to bring back panels that drifted off-screen.

Fix A Tool Window That Opened Off-Screen

Multi-monitor setups can save window coordinates that no longer exist. After a monitor change, Android Studio can keep opening a tool window on a missing display.

  • Toggle Full Screen — Turn full screen on and off so the IDE recomputes window positions.
  • Move A Window With Keyboard — Use Alt + Space, then M, then arrow keys to pull the window onto the visible screen.
  • Reset Layout — Restore the default layout, then reopen Device Manager and Running Devices.

Reset Android Studio State Without Touching Your Code

Android Studio stores UI state and device discovery state. A clean reset often repairs the selector without changing your project files.

  • Invalidate Caches And Restart — Use File > Invalidate Caches / Restart, then pick Invalidate and Restart.
  • Restart The IDE — Close Android Studio and reopen the project before you reconnect devices.

If the device dropdown is missing from the toolbar, widen the window. On a narrow layout it can collapse into an overflow menu.

Reset ADB And Fix Deployment Filters

ADB is the bridge between Android Studio and your device. When ADB gets stuck, Android Studio can lose the device list even while your phone is plugged in. A reset is quick and low risk.

  1. Restart ADB — Run adb kill-server, then adb start-server, then retry Run.
  2. Reconnect The Device — Unplug the cable, wait five seconds, then plug it back in.
  3. Keep The Screen On — Leave the phone screen on so any debugging prompt is visible.

Multiple SDK installs can split ADB: your terminal uses one binary while Android Studio uses another. Keep one Platform-Tools path.

  • Use The SDK Platform-Tools — Run ADB from the Platform-Tools folder inside your Android SDK.
  • End Duplicate ADB Processes — Close other tools that start ADB, end stray adb processes, then start the server once.

Clear Offline And Unauthorized States

If adb devices shows offline or unauthorized, the host and device are not agreeing on the session. A clean reconnect plus new authorization often fixes it.

  1. Revoke Debug Authorizations — In Developer options, revoke USB debugging authorizations.
  2. Restart The Phone — Reboot to clear stale USB sessions.
  3. Reconnect And Approve — Plug in again and approve the prompt with the screen on.

Check App Filters That Hide A Device

A device can be connected and still not show as a run target when the app cannot install. This can happen when minSdk is higher than the device API level, or when the build only includes native libraries that do not match the device CPU.

  • Match minSdk — Confirm the device API level meets your app minSdk value.
  • Match ABI Builds — If you use native code, build for the CPU ABI used by the device.
  • Sync Gradle — Run a Gradle sync after changes so Android Studio refreshes targets.

Once a device appears, run a clean build and install. If install fails with a signing or permission error, solve that next. The discovery step is already complete.

Repair Emulator And AVD Glitches

The emulator can boot but fail to attach, or its window can land off-screen. A quick window reset plus a cold boot clears most cases.

Fix An Emulator Window That Runs Off-Screen

Android Emulator stores window position. If those coordinates point to a display that is no longer present, the emulator can run with no visible window.

  1. Close The Emulator — Exit the emulator, not only Android Studio.
  2. Reset Window Position — Use the emulator menu to reset window state, then restart the AVD.
  3. Start The AVD Again — Launch from Device Manager and confirm the window appears.

Switch Between Docked And Window Mode

If an embedded emulator view is clipped, switch it to a separate window so it can resize freely.

  • Open Emulator Settings — In the emulator, open Settings, then View Mode.
  • Pick Window Mode — Change from a docked view to a separate window view.

Refresh Images, Snapshots, And Acceleration

An emulator that never finishes booting often points to a bad snapshot, an outdated system image, low disk space, or missing acceleration. Start with the steps that take the least time.

  1. Update Emulator Packages — In SDK Manager, update Emulator and Platform-Tools.
  2. Cold Boot The AVD — Use the cold boot option in Device Manager to skip snapshots.
  3. Wipe AVD Data — Wipe data if the AVD still fails after a cold boot.
  4. Check Virtualization — Ensure hardware virtualization is enabled and your hypervisor driver is installed.

After the AVD starts cleanly, retry Run. If you run multiple emulators, close the extras so Android Studio attaches to the one you want without delay.

Keep The Device List Stable Next Time

Once you have fixed the current issue, a few habits reduce repeat failures. They also make your setup calmer when you switch between phones, emulators, and different projects.

  • Keep One SDK Location — Use a single Android SDK path in Android Studio so tools stay consistent.
  • Use A Dedicated Data Cable — Set aside one cable for debugging so you do not waste time on power-only cables.
  • Watch For Debug Prompts — When you switch computers, keep the phone screen on so the approval prompt is visible.
  • Reset Layout After Display Changes — If panels vanish after a monitor change, restore the default layout.

If android studio running device not showing returns, run the same short chain: open Device Manager, restart ADB, reconnect the device, then test adb devices. That gets you back to running builds.