The main issue with OUYA is that all existing android apps will have to be reworked to support controller/remote input
I dont think the Touch pad on the controller is going to cut it. The creator of the Mupen64 emulator sent me this:
"While originally this was planned as a separate port, having looked at the ODK more closely I've discovered that it can be pipelined inside a single APK. So the Google Play version will in fact include the OUYA port (it is now technically an expansion of the project rather than a port).
That said, there are quite a unique requirements when developing for the OUYA compared to vanilla Android. The most immediate are the lack of a touch screen for menu interfaces such as button mapping (touchpad workaround being awkward and slow), lack of Home and Back buttons on the controllers (OUYA simulating Back with a non-standard keycode), lack of a standard Android action bar and menu overflow button, and serious graphics overscan to name the big ones). Had I not purchased a devkit and actually looked into optimizing the app for the OUYA at all, the Google Play version would certainly not have worked well on the OUYA because of these problems. The most serious concerns would have been no way to access the in-game menu options for things like save-state or load-state, extremely tedious mapping the controllers, and borders of the screen being cut off."
I go with the above. You can extract an APK and install on Ouya and will more than likely run. The issue is more, will Ouya input controllers allow one to move around the system or within the apps. Maybe trying something like Sixaxias Controller app and controller may give some indication.
As for the rest, it'll be about the apps. I don't thin PS3Server will work since that is DNLA, and I don't believe Ouya is going to have DNLA. But something like XBMC or Plex should work for media distribution. For direct media playback, If you can find a way to navigate, something like Mobo Player, BS Player, or VLC Android should work.
The main issue with OUYA is that all existing android apps will have to be reworked to support controller/remote input
I dont think the Touch pad on the controller is going to cut it. The creator of the Mupen64 emulator sent me this:
"While originally this was planned as a separate port, having looked at the ODK more closely I've discovered that it can be pipelined inside a single APK. So the Google Play version will in fact include the OUYA port (it is now technically an expansion of the project rather than a port).
That said, there are quite a unique requirements when developing for the OUYA compared to vanilla Android. The most immediate are the lack of a touch screen for menu interfaces such as button mapping (touchpad workaround being awkward and slow), lack of Home and Back buttons on the controllers (OUYA simulating Back with a non-standard keycode), lack of a standard Android action bar and menu overflow button, and serious graphics overscan to name the big ones). Had I not purchased a devkit and actually looked into optimizing the app for the OUYA at all, the Google Play version would certainly not have worked well on the OUYA because of these problems. The most serious concerns would have been no way to access the in-game menu options for things like save-state or load-state, extremely tedious mapping the controllers, and borders of the screen being cut off."
The games will all run at 1920x1080, native resolution for any HDTV. 50" or 60" doesn't change that.What is the story with up-scaling the android games? People now have 50-60 inch TVs, so will games just look sad on these big panels? What resolutions can we expect? 4k?
The games will all run at 1920x1080, native resolution for any HDTV. 50" or 60" doesn't change that.
Oreste, are you using the libstagefright Android version of XBMC? Because from your description it doesn't sound like it.Cons
- Choppy frame rate while watching MP4 videos (via XBMC). Unbearable streaming of MKV files
Like all new technology I believe it will get better with time but I don't think it would ever handle MKV files smoothly
Oreste, are you using the libstagefright Android version of XBMC? Because from your description it doesn't sound like it.
XBMC has an alpha build that enables hardware acceleration on Android.
Try the Gotham Alpha 2 build from April 3rd. http://mirrors.xbmc.org/test-builds/android/
It should decode 1080p mkv files smoothly. It works very well on my Nexus 7, which is running a slower version of the Tegra 3 chip that powers the Ouya.
Let us know your results.
Cheers
You have to use the developers version of the samba file sharing app and modify a file this article explains it all http://www.pivosforums.com/viewtopic.php?f=16&t=1383 . Though I actually noticed that I get better transfer speeds using ftpdroid but I like having both options.Worked well. Thank you. Yet, I couldn't access my external hard drive using Samba, only the internal SD. Does anyone have found a solution? Can't imagine I am the only one searching for this convenience.
Oreste, are you using the libstagefright Android version of XBMC? Because from your description it doesn't sound like it.Cons
- Choppy frame rate while watching MP4 videos (via XBMC). Unbearable streaming of MKV files
Like all new technology I believe it will get better with time but I don't think it would ever handle MKV files smoothly
Hmm. Both of those sound like potential issues.I am using N on a linksys e3000. I also keep getting this error saying "the cache is full.." I went to the setting looking for some sort of cache setting but could find it. I am trying to use the PS3 Media server app on the mac but it couldn't communicate well with the Ouya. Now I'm using Divx's built in dnla server and it seems to be streaming more movies but the 1080p or larger files generate the cache is full error.
I got my Ouya yesterday. Like many of you, I backed the kickstarter to have a game console where I can play old NES SNES roms and watch and stream movies. As of this date I don't think the console is ready for prime time. In my two days of using it here are my pros and cons:
Cons
- Unable to power unit on/off via the controller like the PS3/XBOX360
- Limited launch apps and games
- (currently) Does not support USB storage/expansion
- Choppy frame rate while watching MP4 videos (via XBMC). Unbearable streaming of MKV files
- Cumbersome method of sideloading apps (if you're not familiar with adb)
- Controller sticks and it feels really cheap.
Like all new technology I believe it will get better with time but I don't think it would ever handle MKV files smoothly