Inspiring

Question

AIR 14 x86 Feedback

Forum|Forum|11 years ago
May 1, 2014
3 replies
2790 views

Thanks for the developments on x86, which did indeed improve performance of my 2D projects. However, I have the following issues:

- Projects compiled with "arch x86" are no longer compatible with other devices, so it's not as universal as an Android app needs to be.

- Almost all of my native extensions have been thrown off and no longer work properly if at all.

- 3D seems to have stopped being displayed (using Flare3D at least).

This is my experience on Samsung Tab 3 vs Galaxy S2.

This topic has been closed for replies.

Hallo patidu

Participant

I have changed the extension.xml file with xml header <extension xmlns="http://ns.adobe.com/air/extension/14.0"> and packaged ane file again for android with intel x86 but it's not work

Somebody help me !

Nimisha1

Participating Frequently

Have you included Android-x86 as platform in your extension.xml? Also have you packaged required files for Android-x86 platform?

Following is a sample extension.xml for an ANE supporting both Android architectures:

<id>com.adobe.thirdpartyExtension</id>

<nativeLibrary>samplethirdpartyjava.jar</nativeLibrary>

<initializer>com.sample.extensions.ane.SampleThirdPartyExtension</initializer>

<finalizer>com.sample.extensions.ane.SampleThirdPartyExtension</finalizer>

</applicationDeployment>

</platform>

<nativeLibrary>samplethirdpartyjava.jar</nativeLibrary>

<initializer>com.sample.extensions.ane.SampleThirdPartyExtension</initializer>

<finalizer>com.sample.extensions.ane.SampleThirdPartyExtension</finalizer>

</applicationDeployment>

</platform>

</platforms>

</extension>

In packaging command you need to specify contents for Android-x86 platform:

-platform Android-ARM -C platform/Android . -platform Android-x86 -C platform/Android-x86 .

katopz@sleepydesign.com

Participating Frequently

Damanjit Singh

Starling demo mobile also slow/broken with plenty of bugs and non function (e.g. not all filters work, render texture not work, clipping is wrong) there so can you guys (Adobe team) please test/fix Starling demo here Starling-Framework/samples/demo_mobile at master · PrimaryFeather/Starling-Framework · GitHub before next release please? i don't want to fill all that to bug base which could take all day
i try to add -arch x86 "customize lunch" button via FlashBuilder before "-listen" which is working when debug but when switch to run mode it seem like "-listen" flag is not there so FB throw me and error then i've to change it to before "-storetype" instead which is annoying
i can't debug via AIR14+Starling, not just x86 but all android device, my problem is describe here Bug#3756123 - Android+Starling throw Buffer creation failed. Internal error while createVertexBuffer and there Android + AIR 14 break Starling · Issue #539 · PrimaryFeather/Starling-Framework · GitHub

and because i can't debug so it hard to file issue

Nimisha1

Participating Frequently

Hi katopz,

Bug 3756123 is reproducible at our end with both armv7 and x86 runtime on Samsung Tab 3 but not on Nexus5 or Nexus7 and we are investigating the issue.

-Nimisha

katopz@sleepydesign.com wrote:

Damanjit Singh

Starling demo mobile also slow/broken with plenty of bugs and non function (e.g. not all filters work, render texture not work, clipping is wrong) there so can you guys (Adobe team) please test/fix Starling demo here Starling-Framework/samples/demo_mobile at master · PrimaryFeather/Starling-Framework · GitHub before next release please? i don't want to fill all that to bug base which could take all day

i try to add -arch x86 "customize lunch" button via FlashBuilder before "-listen" which is working when debug but when switch to run mode it seem like "-listen" flag is not there so FB throw me and error then i've to change it to before "-storetype" instead which is annoying

i can't debug via AIR14+Starling, not just x86 but all android device, my problem is describe here Bug#3756123 - Android+Starling throw Buffer creation failed. Internal error while createVertexBuffer and there Android + AIR 14 break Starling · Issue #539 · PrimaryFeather/Starling-Framework · GitHub

and because i can't debug so it hard to file issue

D

Damanjit Singh

Adobe Employee

Hi,

- Yes, currently we do not support universal app (with both x86 and ARM support). For now you would need to upload both your x86 and ARM app to Google play store to cater to all your cusotmers. We do intend to provide the support for universal apps in future.

- Your native extensions need to be packaged again, with support for "Android-x86" platform in their extension.xml.

- 3D should work fine. If not, it's a bug. Could you please log this bug at bugbase.adobe.com ?

Thanks,

Daman

N

Neverbirth

Inspiring

How far is the universal support? Will ANEs be universal as well? I as because I wonder if it's worth spending time adding the new platform to the ANEs or is it better to just wait a bit.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded