My USB hubs do not work with the Ouya!
A painful lesson learned during bitcoin mining is that not all USB hubs are created equal!
Above is the pin-out schematic of that an OTG cable (On the Go) looks like. The major difference is pins 4 and 5 in the mini-USB are bridged to let android based smartphones know that you are not plugging in a data cable for your android OS to transmit data from your android to a destination device like your PC. But you are in fact pulling data from a device to your androids such as a keyboard or USB thumb drive.
The wrong time is a result of the Ouyas operating system used more for gaming then it is for any application function like the original intention of the android operating system which is for phones. It’s there you just have to back out of XBMC/KODI to set it. This should technically fall under the core troubleshooting catagory however since it is only noticeable in applications and third-party APKs then it makes more sense to put it down here.
The MP4 files issue goes into a licensing issue that prevented all of the codecs from being compiled into XBMC for ouya (Currently version 12.3 Frodo). Since version 13.x Gothan XBMC has changed its name over to the new platform KODI. If you point your Ouyas Browser over to the New Kodi homepage for downloads and select the Android ARM version. You can download the APK and side-load without the need of rooting your Ouya. The version direct from KODI will upgrade the player to version 14.x helix (At the time of this posting) and you will regain access back to playing videos upon it once again.
Sometimes with Google Play, you will also experience the 920 error during downloads as well. This happens predominantly because Google changed their UI and upgraded their layout and the Ouya is not smart enough to detect and auto-upgrade google play like it should especially with older frameworks loaded.
Google Play failure after a major update to your Ouya is actually by design. When you root your Ouya and the Ouya company detects that you have rooted your device it will push a full update to your Ouya instead of a partial. As a rooted user it has no idea what you were doing in the ADB console (or in some of the scripts made by other peoples APKs) or what sort of mods you have done to the Android OS which Ouya Sits on top of.
Bluetooth lag is possible one of the most complained and criticized issues with the Ouya console. If you don’t have good joystick response time then your not a gaming console. Ouya could have done a slightly better job at giving the Bluetooth controllers a larger antenna on the inside as they have the room for it. I have heard some people stating that they have to tip the Ouya onto its side in order to get a better signal. If that is myth or not is to be debating, however tipping over your Ouya does not really hurt anything and if it works for you then good!
A no USB device issue is when you plug something in and absolutely nothing happens! Certain keyboards may have to have the Ouya hard-booted in order for them to show up. This is a fault once again in Android in general, not just version 4.1! Our Ouya’s from time to time even when using my non-powered USB hub. Put the Ouya in sleep mode. unplug it. And plug your keyboard in. and then plug the power back into your Ouya. Upon bootloader it should activate your keyboard.
There is A LOT of factors associated to why you could be having a rough time getting your Ouya onto the wireless network. Here is just a few:
Android sets aside 500MB of APK space as almost like a ‘temp’ folder for any work it has to do with installing APKs. When it gets to 500MB it simply stops because the android installer takes that 500mb for initializing installation of your apps. You will have to buy a USB thumb drive or remove some programs off of your Ouya in order to install again.