Not by default; but there is a way to do it.Originally Posted by Jake53
By default, OUYA is configured to not allow background processes; but the setting can be changed. Set the "Background Process Limit" to "At most 3 processes": from the main menu, select "System", then "Advanced", then "Developer Options" (2nd from the bottom), then select "Background Process Limit" (also 2nd from the bottom). Set it to "At most 3 processes" (which is the Android default). It may be a good idea to set "Don't Keep Activities" to false as well. If you choose to do this, please read the "Major Caveats" section at the end of this post, first.
Once that's done, if you double-tap the Options button, to return to the home screen, 2player will continue to play in the background. Note that selecting "Options/Exit", or pressing the back (A) button until 2player quits will stop the currently playing track. You have to double-tap the "Options" button to get this to work.
You can also remotely start tracks and play tracks on 2player for OUYA using a copy of 2player for Android running on an Android phone or tablet, when the background process limit has been set to three processes. This is actually a great feature, and one of the major features of 2player on Google TV: the ability to remotely play music on your TV-connected home-audio system, without having to launch a program on Google TV first. The copy of 2player running on Google TV just starts automatically when the copy of 2player running on your phone or tablet tells it to. 2player on OUYA will do the same thing; but ONLY if OUYA has been reconfigured to allow "at most 3 background processes".
Major caveats: in theory, the Android operating system should automatically trim the background 2player processes if a foreground app runs short of system resources or memory. In practice, running 2player in the background may cause undesirable behavior in some games (jitter and refresh problems in the display). Presumably, OUYA developers changed the background process settings default value to improve consistency of response in foreground applications. So if you do this, and start running into problems with certain games , be prepared to change the setting back. That being said, it's likely to affect only a very small subset of games, and it will probably work most of the time.
Strictly speaking this is an "unsupported" suggestion. Do it at your own risk, and be prepared to suffer potential responsiveness problems with other games. But I would be interested in hearing whether anyone actually runs into problems if they do this.
Reply With Quote
Bookmarks