Hi,
Since corona doesn’t provide us with a way to edit/add more options in the build settings for Android I had to use apktools to edit the androidmanifest.xml myself.
My problem is once i edit the apk I can’t rebuild the apk again, it always says that it needs proper signing as I upload it to play store. I’m using “apktools b” to rebuild my edited apk.
Has anyone here know what to do if I want to edit/change my manifest.xml and properly rebuild the apk again?
Thanks
Hey, I was able to rebuild and resign an apk using apk manager (osx version - http://www.mediafire.com/download/o4idx4en9ldnwx4/APKManager_2_2_5.dmg)
… but i’m doing it for OUYA and not for the google play store, so im not sure if that makes a difference…
hey, finally there’s someone out here 
Yeah, i managed to edit and rebuild the apk again (using apk manager n various tools)… even sign it back again for google play store but there’s something wrong with the apk.
I guess it won’t be an issue when you build for ouya, though probably when ouya store is real you can’t do the same thing again.
Btw, where can I read about corona and ouya, I keep hearing everyone’s doing it but couldn’t find any links/article
thanks
Hey Yanuar,
Actually the OUYA store is already real and the apk seems to work, although there are big problems between Corona and OUYA right now - the biggest ones being Corona can’t use the in-app-payment system of OUYA so you can’t do paid games, only free games right now. You also can’t access all of the controller or multiple controllers yet. OUYA wants to support Corona but Corona has done very little to reciprocate.
It’s hard to say whose documentation is worse, Corona’s or OUYA’s But these are the two main resources I’ve been using:
http://forums.ouya.tv/discussion/572/corona-sdk-ouya-development-thread
http://developer.coronalabs.com/code/ouya-support
Good luck -
Nick
nicksantan - we are actually working with Ouya on support for Corona. We are working on finishing support for HID devices in Corona, and they are doing the necessary plugin for the IAP.
David,
That’s awesome! Please forgive me for my blasphemy. I’m looking forward to it! I think developing for the TV / game controllers through OUYA will be a great opportunity for Corona.
As David has said, we’re actually hard at work on Ouya support. It’s a pretty big project, and because of that, we’ll be providing incremental changes via daily builds adding each of the features that people will need/want for Ouya. In fact, the newest daily build already contains some new features now that you can play with on Ouya.
First, we’ve added Ouya app icon support, which we’ve documented here…
http://docs.coronalabs.com/daily/guide/distribution/buildSettings/index.html#ouya
We’ve also added support for all keys on a keyboard and for gamepad/joystick buttons via our “key” event. You can see this in action now via sample app “Interface/KeyEvent” that is included with the Corona Simulator.
http://docs.coronalabs.com/daily/api/event/key/index.html
http://docs.coronalabs.com/daily/api/event/key/keyName.html
http://docs.coronalabs.com/daily/api/event/key/nativeKeyCode.html
We’ve add a new “mouse” event feature which allows you to track the mouse cursor movement and mouse clicks that can be generated by the Ouya controller’s trackpad, USB mouse, or bluetooth mouse. In fact, mouse events are supported on Android 3.1 and higher devices (phones and tablets) too via bluetooth. Mouse event support has been added to the Corona Simulator for Windows when simulating an Android device… but not for Mac yet. Also note that apps running on Ouya do not have touchscreen support (because your TV is not a touchscreen), making mouse/touchpad support important.
http://docs.coronalabs.com/daily/api/event/mouse/index.html
We have one undocumented feature that allows you to set the category in your AndroidManifest.xml file for Ouya, which is an Ouya requirement. You can do this by adding the following to your “build.settings” file…
settings = { android = { mainIntentFilter = { categories = { "tv.ouya.intent.category.GAME" }, }, }, }
Next, we’re working on the ability to get information about the device that an input event came from.
After that, we’ll be adding analog axis event support so that you can get the input events from the gamepad’s thumbsticks and analog triggers.
I’m sure more changes will follow, such as the ability to simulate a 720 and 1080 TV in the Corona Simulator. There is lots to do. So, we’ll be rolling out these changes incrementally via daily builds.
Ouya (the company) will be creating the Corona plugin that will allow you to do in-app purchases and game network support. They’re actively working on it now.
So, yeah, there’s lots of stuff going on. :)
Cool guys! As an indie you guys really make the pro subscription worth my money…
OMGOMGOMG, so glad I took the time to reactivate this thread and find this out! You guys just saved me so much time decompiling and recompiling APKs you don’t even know!
Thanks!!
Is joystick movement possible? I only see references for button pushes.
Not yet. Joystick (ie: axis input) support will come later, as I’ve mentioned in my post above.
First, we need to add support to recognize which device the input events came from and the ability to acquire information about that device. That’s a far bigger job and we hope to make this change available in a daily build soon. Axis input support will come after that.
Okay, thank you for your detailed response. I’m very excited to see Corona working on OUYA!
Actually, we’re doing more than adding Ouya support. We’re adding general game controller support to Android so that we can support GameStick, NvidiaShield, Moga controllers, and any other controller that supports the HID protocol. Heck, even Mad Catz has announced that they’re going to do an Android console system in the future. That’s why we’re taking the extra time to make sure we do this right.
Ouya (the company) will be creating an Ouya plugin for Corona. They’re working on it now.
that’s great news Josh. gluon pays off!
Can’t wait to get my hand on this, I’m getting my first controller soon this week.
Is there a way for us to get the experimental build/daily build that has this long awaited feature?
@yanuar, the current daily build has the features Joshua was talking about. If you look at the current daily build’s API docs, you will see that most of this is already documented as part of the daily build process. Only the build.settings isn’t documented formally, but Joshua listed what you need above.
Hey, I was able to rebuild and resign an apk using apk manager (osx version - http://www.mediafire.com/download/o4idx4en9ldnwx4/APKManager_2_2_5.dmg)
… but i’m doing it for OUYA and not for the google play store, so im not sure if that makes a difference…
hey, finally there’s someone out here
Yeah, i managed to edit and rebuild the apk again (using apk manager n various tools)… even sign it back again for google play store but there’s something wrong with the apk.
I guess it won’t be an issue when you build for ouya, though probably when ouya store is real you can’t do the same thing again.
Btw, where can I read about corona and ouya, I keep hearing everyone’s doing it but couldn’t find any links/article
thanks
Hey Yanuar,
Actually the OUYA store is already real and the apk seems to work, although there are big problems between Corona and OUYA right now - the biggest ones being Corona can’t use the in-app-payment system of OUYA so you can’t do paid games, only free games right now. You also can’t access all of the controller or multiple controllers yet. OUYA wants to support Corona but Corona has done very little to reciprocate.
It’s hard to say whose documentation is worse, Corona’s or OUYA’s But these are the two main resources I’ve been using:
http://forums.ouya.tv/discussion/572/corona-sdk-ouya-development-thread
http://developer.coronalabs.com/code/ouya-support
Good luck -
Nick
nicksantan - we are actually working with Ouya on support for Corona. We are working on finishing support for HID devices in Corona, and they are doing the necessary plugin for the IAP.