Appsurfer Problems

Hi,

 

Ran across this solution http://www.appsurfer.com/ that allows Android apps to be tried in browser. Presumably it’s a cloud streaming thing with a virtual machine running on their servers and streamed to user. I thought this might be an interesting for presskits / getting someone to review your game. Any-hoo, decided to signup and uploaded an apk and got this error

 

 

Porting existing ARM apps to x86.

Looks like your app uses ndk to build native code. Your app currently runs ARM code, which is not compatible with AppSurfer platform as of now. So you could recompile your APK to be compatible with AppSurfer.

 

This is how you can do it.

 

You should add x86 to your APP_ABI definition in your Application.mk file to build for x86 platforms. For example, the following line instructs ndk-build to build your code for both ARM and x86 :

 

APP_ABI := armeabi x86

 

As you can see we just added x86 to your existing line.

 

 

Unless you rely on architecture-specific assembly sources, such as ARM assembly code, your app should run fine on x86.

* App is required to target Android 2.3 (API Level 9) or higher.

 

Since that’s the stuff under Corona hood, sounds like something that’s probably not easy to resolve? Anyone with more details/experiences.

 

Matias

I’ll ask the engineers about this, but we only support ARMv7 processors and I doubt this is something that will work.

 

Rob

Corona for Android currently only supports ARMv7 devices.

We do not currently support x86 Intel Atom processors.

 

Although that said, Android devices running an Atom processor can run apps built for ARMv7 devices, making Corona built apps compatible on those devices.  So, we’ve avoided building for x86 because of this.  Mostly to reduce the size of the APK file which many Corona developers are sensitive about.

 

Currently, supporting x86 on Android is not a priority right now.  If you want, you can vote for it on our feature request web page (link below).  If enough votes have been made for it, then that’ll give it priority.

http://feedback.coronalabs.com

Thanks,

 

I can’t really say having x86 support would be a priority. I would like that tool to work, but there are other things I’d rather have from Corona implement before x86 (like native video) :wink:

 

Also I would assume their priority would be to support Arm…

Thanks for understanding.  Also, we do eventually want to support x86 Android devices.  We even picked up an Atom processor device.  We just want to address the highest priority features on our feature list first to be fair to all of our customers.  The next feature we plan on implementing is expansion file support (which is nearly done).  I suppose once we have that, adding to the size of the APK might no longer be an issue.

I’ll ask the engineers about this, but we only support ARMv7 processors and I doubt this is something that will work.

 

Rob

Corona for Android currently only supports ARMv7 devices.

We do not currently support x86 Intel Atom processors.

 

Although that said, Android devices running an Atom processor can run apps built for ARMv7 devices, making Corona built apps compatible on those devices.  So, we’ve avoided building for x86 because of this.  Mostly to reduce the size of the APK file which many Corona developers are sensitive about.

 

Currently, supporting x86 on Android is not a priority right now.  If you want, you can vote for it on our feature request web page (link below).  If enough votes have been made for it, then that’ll give it priority.

http://feedback.coronalabs.com

Thanks,

 

I can’t really say having x86 support would be a priority. I would like that tool to work, but there are other things I’d rather have from Corona implement before x86 (like native video) :wink:

 

Also I would assume their priority would be to support Arm…

Thanks for understanding.  Also, we do eventually want to support x86 Android devices.  We even picked up an Atom processor device.  We just want to address the highest priority features on our feature list first to be fair to all of our customers.  The next feature we plan on implementing is expansion file support (which is nearly done).  I suppose once we have that, adding to the size of the APK might no longer be an issue.