1) the picture is cut off, overscan in the android settings seems to change nothing, my TV has no overscan setting for HDMI. Snes9x and other official Ouya store apps show this (eg. in Snes9x it is "ad Game" instead of "Load Game" etc. same on most sideloaded APKs.) Implement an overscan setting like in XBMC, where you adjust the screen so that it is completely visible!
2) Why is bluetooth disabled if I connect a wired controller?!?!?
3) When will you implement resolution selection. (at the moment it upscales to 1080p, and my TV downscales to 720p, also there is a monitor resolution where my TV disables overscan! I just cannot select it, because ouya allways sends 1080 if the TV can show or downscale that
4) Details (U) menu on sideloaded APKs show nonsens (download, and null like and ... as description)
5) attached USB storage should be regarded as the "SDCard" and should be shown in android storage
6) sound gets muted sometimes by itself (you can reenable by going to
android setting, and turn it on again -> but I never turned it off!!)
7) Any news on official XBMC app in ouya store? (works great sideloaded BTW)
8) USB keyboard shows up as BT controller 1
9) any plans to release a bootloader unlocker?
Hope you could comment on those points.
I really like the Ouya, but it would be soo much better if it would not cut off the complete Youtube menu on the left side because of TV overscan ;)
ricsi
Posts: 16Member
Comments
11) optionally disable the wake on HDMI (as the ouya allways turns on, even when the TV is set to the Settopbox!!)
PS: any way to edit posts?? if yes I did not find it
We are working on the HDMI handshake issue, not fixed yet sorry. All your other points are on our radar for the most part. Back to work I go :)
Thanx for the hint on editing ;) (you only need to know HOW it is done, then it is easy ;))
What do you mean with "HDMI handshake issue"?
I guess 11) that Ouya allways turns on??
Could you comment a bit further on 1) apps content gets cut off
Is this being actively worked on? As this is currently really a neck breaker for me ...
What is the proposed solution?
Good to know that they are on the radar! thanx for the feedback.
Is there a public list, where one can see which points have made it to the ouya team?
I am speaking of a helicopter view here.
Issue X (short description) we are aware, and actively trying to correct it.
Issue Y (shhort description) we are aware, but prio is low, will be tackeled later.
etc.
I am glad that you guys made the Ouya ... and I wish you good luck, and much success!
The point is the TV where I have connected my Ouya to does not have such settings for HDMI!
For XBMC the solution is easy, there is a wizard, where you can select what is visible on the screen.
There you drag an arrow for so long, until the whole screen is visible.
Ouya does not have such a setting (yet).
This is NEEDED!!
If for some strange reason your TV/monitor doesn't have this setting (which I believe it does, look in your manual) you need to contact your TV manufacturer about it, and check to see if there is a firmware update for your TV that might address the issue.
The default overscan for any other 480p/i or 720p signal I send (either via HDMI or analog cable) is very minor, but because OUYA is always outputting a 1080p signal, 720p TVs (especially the ones that actually have 768 lines) don't smartly display the image, and you end up with severe overscan, where something like 15% of the pixels are missing.
While pretty much all 720p TVs can accept 1080p signals, but most do it very badly and generally expect the connected device to do the scaling on its end, then send a 720p signal to the TV.
It's not just the overscan, but the scaling quality on these TVs is awful, too, so button prompts and other icons render with a terrible aliasing effect.
There's an argument to be made that this isn't OUYA's problem, and perhaps it's a limitation of Android itself, but I think all it would take would be an option in the HDMI menu to send a 720p or 480p signal instead of a 1080p one.
Of course, developers like the convenience of targeting one screen size, but if this were an OS-level scaler which scaled the raw output before sending it to the TV, devs could still target 1080 as they do now. Of course, that would also allow for a system-wide overscan compensation setting, but frankly, we should all be targeting safe zones anyway.
That said, it might be nice (if undesirably complex) for devs to be able to support different UI for 720 and 1080 screens (or even 480, yes they do exist over HDMI). Not that I'm at all advocating for that solution, but Android devs already have experience/documentation to deal with multiple screen resolutions.
Will check afterwards.
But as far as I have seen there are no options for HDMI.
You CAN change the picutre (zoom, etc.) for other inputs (eg. composit).