Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

david_bennett

About

Username
david_bennett
Joined
Visits
48
Last Active
Roles
Member
Posts
9

Comments

  • Thanks SpoonThumb.   I have found this specific sequence of actions works pretty reliably: 1.  "adb kill-server"2.  unplug usb, replug usb3.  "adb devices"
  • This worked well for me too.  Thanks. I needed to do one additional thing in the SDK manager -- "install" (actually downgrade) Android SDK Platform-tools to Rev 16.0.2.
  • This didn't work -- the latest version of the Android SDK manager changes the paths.  Well, it downloads parts of 17.  I guess that changing the paths in OuyaPanel.cs as rubix has done is the simplest route. david_bennett said: I guess that do…
  • I guess that downloading "17" was the issue.  I am going to try completely uninstalling my android sdk, then reinstalling it taking care to only install "16".
  • LostAeon said: I am having a similar error Error building Player: Exception: android (invokation failed)ERROR: unknown errorcmd:android list target -cstdout;stderr:Exception in thread "main" java.lang.NullPointerException at SDKMain.main(SDKM…
  • After upgrading to the 1.0.3 SDK, I found that I had to modify the lines in the android_winusb.inf file again: ;OUYA%SingleAdbInterface%        = USB_Install, USB\VID_2836&PID_0010&REV_0232&MI_01%CompositeAdbInterface%     = USB_Install,…
  • Thanks. It turned out that I needed to recompile the NDK.  Going through Tim Graupmann's how-to videos reminded me of this step -- http://forums.ouya.tv/discussion/200/sticky-ouya-unity-package-videos#latest - David Bennett