Search Issue Tracker

Fixed in 2017.1.0f3



Found in


Issue ID




'adb.exe forward' is executed despite build platform set to Standandalone (Windows



In Edit > Preferences > External tools I have my Android SDK + JDK both set
to valid locations, which means Unity is able to run adb.exe if it wants to.

I'm using Windows 10 64bit.

To reproduce:
0. Confirm in the Windows task manager that adb.exe is not running
* If it is, end/quit/kill that task so adb.exe is no longer running
1. In Unity create a new empty/default project
2. Confirm that then build platform is "standalone" (which is the default)
3. Hit CTRL-P to run the empty scene
4. Check the Windows task manager; A moment later you'll see adb.exe
running, which is *not* expected

fixed in

Version 2017.1.0b2 (48952a94fb3b)

Comments (6)

  1. ahmedaniss

    Dec 09, 2020 03:28

  2. Paul_Bronowski

    Oct 11, 2018 08:36

    Old thread, but something worth adding: If you have the GoogleVR SDK unity asset bundle installed, and you have a GvrControllerInput.cs script in your scene. When you hit play, GoogleVR\Scripts\Controller\Internal\Emulator\EmulatorClientSocket.cs will find adb.exe and launch it, if (serialized field) GvrControllerInput.ConnectionMode == USB or WIFI. You need to set GvrControllerInput.ConnectionMode == OFF when not working with a test device.

  3. fredsa

    Mar 04, 2017 21:13

    For the `adb` subprocess issue here are a couple of tips:
    - You can run `adb kill-server` to get rid of that adb process, although the next time you enter play mode, Unity will spawn a new adb process.
    - As a workaround you can run `adb forward tcp:7201 tcp:7201` *before* starting Unity, which makes it so that Steam will no longer consider adb a subprocess (because it's not spawned from Unity editor).

  4. MrLucid72

    Mar 04, 2017 07:20

    Still annoying, but here's a "Lazy man's workaround" >>

    (Still need to click the batch file after every time you close Unity)

  5. MrLucid72

    Mar 04, 2017 06:31

    (confirmed in 5.5p4)

  6. MrLucid72

    Mar 04, 2017 06:31

    Confirmed. This is actually a pretty HUGE issue for those that are not aware of this -- for anyone that uses Steamworks.NET (a GREAT majority of people here):

    You actually can NEVER exit your Steam app until you reboot!! ....or if you know about the bug, you can end task ADB ... Every. Single. Time. That is incredibly annoying.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.