Build & Run Not Working - No Android Device Found?

Dark-Muppeteer · August 2013

I've been trying for most of today to get unity to successfully build and run a .apk with no luck.

The error that I'm encountering is the No Android Device Found issue, that occurs during the build and run process. (just building is fine)

For Reference

The Ouya is connected to the PC (has been every time I've tried re-installing the drivers)
I CAN communicate with the Ouya via the Ouya Panel (Advance setting/reboot etc. all work)
All SDK, NDK and Java settings/paths are correct and showing as white in Unity
MiniSDK version is 16
Android SDK/tools is rev 21
The Android _winusb file has the required extra lines of information (in both sections)
The adb_usb file has the required hex code
The device shows up in the list when checking via cmd
Just performing a build works fine
I can sideload a built .apk file and run it perfectly on the Ouya (via cmd transfer)
USB debugging connected notification is shown on the Ouya
I can access the Ouya from the PC and manually transfer files between it and the PC
I am running Win7 64
Ouya Build Number is 1.0.439_r1
I've tried rebooting Unity/the PC/Ouya multiple time
I've re-installed the usb drivers at least 30+ times following the various walk-throughs and videos. (it has installed perfectly every time)

Any help that can be provided would be gratefully appreciated.

tgraupmann · August 2013

If you type:

adb devices

you should see your OUYA device. If not you need to follow the setup docs.

https://devs.ouya.tv/developers/docs/setup.md

I have a video for Windows and Mac setup.

Dark-Muppeteer · August 2013

Hi,

Thanks for the response, but as mentioned in bullet point 8 it shows up correctly when I check devices via the command line.

As per the last part of my original post I've also already followed the docs and videos you've mentioned but I still get the same issue.

tgraupmann · August 2013

Hmmm that is unusual. Well in the Unity preferences you also have an Android SDK path. And it's possible that it's pointed to a different location.

You can also run the command:

adb kill-server

and run adb devices again. Does it still show up?

Try running Unity 4.2.

Dark-Muppeteer · August 2013

Kill and start server give the expected blank list and then list with one item.

I can side-load built .apk's fine, it just seems to be Unity that doesn't want to communicate.

I'm currently using Unity 4.2, though it's pro trial I got with my Oculus.

MightyRabbit · August 2013

It's a slower process, but you can always build an APK and then do "adb install mygame.apk". I had to do that for the longest time before Build and Run starting working correctly (which happened completely inexplicably).

Dark-Muppeteer · August 2013

It's what I've been doing (and works fine), it's just frustrating that it all seems to be setup correctly but fails at that last part.

I'm going to try and get some other devices to test it with.

tgraupmann · August 2013

There's no reason why you can side load where Unity can't auto deploy. Very strange since Unity would use the same commands. Try uninstalling the game on your OUYA and then use File->Build and Run. Try restarting Unity? Try clearing your temp folder?

Howdy, Stranger!

Categories

Build & Run Not Working - No Android Device Found?

Answers