Hi,

I'm preparing our game for Amazon and I know they are kinda picky with settings & permissions. Do you have any suggestions?

Game uses portrait mode and tilt controls so I'm planning to use following based on their FAQ:

android =
{
versionCode = "1",
installLocation="preferExternal", -- app should install to SD if available
},

androidPermissions =
{
"android.hardware.sensor.accelerometer",
"android.hardware.screen.portrait",
"android.hardware.touchscreen",
},

As far as I know CoronaSDK adds following permissions by default:

android.permission.INTERNET
android.permission.ACCESS_NETWORK_STATE
android.permission.READ_PHONE_STATE

Hmm, after looking at Android docs, I don't think I can set those hardware features in androidPermissions list...

Is there a way to further customize Android Manifest or I just shouldn't bother with those?

check this thread for info on editing the manifest file directly:

https://developer.anscamobile.com/forum/2011/10/02/what-androidmanifestxml-file

@producerism,

Thanks for the link, I had no problem expanding the APK but the AndroidManifest.xml is in binary format and cannot be edited with a text editor...

Any suggestions to edit it?

did you expand it using APK manager? If you simply rename apk to zip and unzip it, I don't believe that will work.

You need to actually run APK manager. Just put your APK file inside the folder called "place-apk-here-for-modding"

Then run Script.bat, and select option 9 ("Decompile apk").

Once it's done running, there will be a folder inside of projects called projects/your_apk.apk/

Inside there, you will find the AndroidManifest.xml file, which you can edit as normal.

With that said, I haven't been successful in recompiling an APK yet, but I'm sure it's possible. I just had other things to focus on so I gave up after an hour or two of messing around.

Yes, I have expanded it using the APK manager. AndroidManifest.xml is there but it's in binary format.

I'm using the latest daily build and I think one of the recent changes in the daily builds was using the binary xml...

Ah, that may explain it, I'm still using a slightly older build. Post back if you do find a solution.