XxTIMOxX said:
In your device manager, uninstall your usb hubs, then reboot. It should reinstall the hub drivers and then pick up anything plugged in as well.
One of my systems has to have this done every now and then to detect the same d…
kentsimon said:
I did not see anywhere in this thread that you should check that your drivers are installed properly. Look in the device settings and see if there is an alert badge on the Ouya device.
The device isn't detected AT ALL.…
They said a couple days ago that they have tripled their support staff. It seems like they were getting flooded and are working to get back on top of the situation. I wouldn't take it as a personal insult. Sometimes creating a new business and a new…
Piers said:
Drat. Certainly sounds like it's gone bad, you'll need a replacement almost certainly.
Yeah I contacted support and over the course of a week or so got it sorted and was then told a replacement with a return shipping label …
Piers said:
In cases of micro-USB not working make sure to do the obvious thing and try a different cable, just in case it's not a problem on the console-side of things. And of course check the Android advanced settings under Developer Optio…
That is a bummer. I contacted support and they have a replacement on its way to me. You should do the same just be aware it may take a bit. I waited 3 days then tweeted @OUYAsupport and got it sorted within a couple days.
I actually have one of those cables and was thinking of that. I'll give it a try tonight but at this point I'm pretty convinced that it's dead. Even if it is working somewhat that doesn't help me since there doesn't seem to be any way to get ADB wor…
So I brought the system with me to work and tried connecting to my desktop here. Same thing. No response at all. It seems like the USB port is completely dead. I even tried removing the board from the chassis in case the tolerances were a bit off an…
I have tried a number of cables, these cables all work with other devices. I tried re-running setup and that made no difference. I've tried to manually start adbd on both tcpip and usb.
I installed an SSH server. I'd like to see if I can just start adb tcpip from there but I get this:
u0_a75@android:/ $ adb kill-serveru0_a75@android:/ $ adb tcpip 5555* daemon not running. starting it now on port 5038 ** daemon started successfully …
