[Ouya Android Development] professorpoptart:
This thread will be used for the discussion of packaging the ouya store into a flashable zip for easy install onto CM10, or hopefully any other custom rom that might not have the ouya store on it (or dare I say phone! untested, just a thought).

---------------------------------------------

Notes:

The good news up front we have both the ouya and play stores running on CM10!

I was working on this a few days ago and was running into what looked like issues with the data/system/packages.xml file giving out the right permissions. Toast message FC about ouya framework, and tv.ouya permissions to uid="10032".

I flashed back to OTA to try the exposed play store. After playing with that for a bit I decided to go back to work on this so we can have both the play store and the ouya store working on both OTA and CM10. I flashed over the ouya bits and set perms and was getting ready to look at the logcat expecting the same errors... but the launcher came right up, asked for my login and into the play menu I went!

What changed? I said I was working on permissions in the /data/system/package.xml... well I forgot to wipe data before flashing CM10. I think that was the secret, it must have skipped some step that was causing the error as something it was looking for was already there.

In any event the store and framework are working... mostly. I am still having issues getting into the "discover" menu as I get a toast message that says something about "attempted read from closed stream". in logcat it looks like "error checking for update". so I think it may be that I'm working on old apk's from an old download.

There is also an issue with the controller mapping, home seems not to work and while testing shadowgun the x/y axis on the right thumb stick was reversed. I think I remember someone saying something about that.

In the end it turned out to be about the same process as getting google music to work on stock OTA. basically grab the framework and launcher apks and put them in system. (At least up to this point! lol) The Idea will be to use this to build a complete install zip without the need to have a data partition from OTA. Who knows what other issues this might cause as usually its not a good idea to keep data from different roms.

------------------------------------------------------

So manual step...

!!!This is for Dev purposes only, this does not work 100% yet!!!

If you want to give it a try and/or help solve an issue or 2, by all means continue!

-1. Make sure you have access to OUYA store on an OTA based rom.

0. Flash CM10 via cwm !!!DO NOT WIPE DATA!!!

http://xdaforums.com/showthread.php?t=2348548

instructions on flashing the google apps are also there to get play store working.

1. I used the deodexed files from IncognitoMan's stock plus rom. Basically from /system/app/ grab anything that starts with "ouya" at this point I'm not sure all are need but this is what I did to get to where I'm at now... I will update as I test further on what all exactly is needed or not.

link to rom http://xdaforums.com/showthread.php?t=2347214

a. ouya-framework.apk

b. OUYAKeyboard.apk

c. OUYALauncher.apk

d. OUYAOOBE.apk

e. OUYAWallpaper.apk

For each of these files copy over to sdcard

2. Remount system in rw

3. Copy over to /system/app/

4. Set permissions.

5. Reboot.

6. Launch the "ouya launcher" from the app menu and log in.

All games you had from the OTA rom should be there.

Again issues:

Cant get into "Discover" menu in ouya launcher. - working on this now as this is obviously the deal breaker for most.

Controller keymapping. -biggest issue with this is home button mapping! in android settings the ouyaKeyboard is grayed out... ouya framework issue.

Some games show a ouya-framework fc 2-3 times as the game loads... but once the game is up its fine.

Some games might not like the high dpi.

Some games just wont open (paid?)... - thinking this might be related to the Discover menu issue.

irc, FreeNode/#ouya-dev

Thanks; khanning88 for CM10, IncognitoMan for deodexed OTA.