Invalid extension descriptor - Licensing AIR for Android devices

I'm trying to do licensing app according to this article http://www.adobe.com/devnet/air/articles/android-licensing-native-extensions.html.
If i try to generate the ANE file in ADT command prompt then displays this error - Invalid extension descriptor: extension.xml
My file extension.xml I copied the whole of the AIR 3.1 SDK.
<extension xmlns="http://ns.adobe.com/air/extension/3.1">
<id>com.adobe.air.sampleextensions.android.licensing</id>
<versionNumber>1</versionNumber>
<platforms>
    <platform name="Android-ARM">
      <applicationDeployment>
        <nativeLibrary>SampleAndroidLicensing.jar</nativeLibrary>
        <initializer>com.adobe.air.sampleextensions.android.licensing.AndroidLicensingExtension</ initializer>
        <finalizer>com.adobe.air.sampleextensions.android.licensing.AndroidLicensingExtension</fi nalizer>
      </applicationDeployment>
    </platform>
    <platform name="default">
              <applicationDeployment/>
    </platform>
</platforms>
</extension>
In what may be the reason, tell me please?

Never mind, I was using the wrong runtime. My devices are on eclair and I was using froyo. Grrr.

Similar Messages

Developing and using Adobe AIR native extensions for Android devices

I was using this tutorial:
"Developing and using Adobe AIR native extensions for Android devices"
http://www.adobe.com/devnet/air/articles/ane-android-devices.html
When packing the Flex mobile ANESampleTest to deploy on an Android device, the below error happens
Error occurred while packaging the application:
aapt tool failed:invalid resource directory name: /private/var/folders/k8/1thhvkf92h947n_g22hg_v9m0000gn/T/52ba05aa-9001-4d46-9438-db81ef83 06f0/res/drawable-xxhdpi
invalid resource directory name: /private/var/folders/k8/1thhvkf92h947n_g22hg_v9m0000gn/T/52ba05aa-9001-4d46-9438-db81ef83 06f0/res/values-sw600dp
invalid resource directory name: /private/var/folders/k8/1thhvkf92h947n_g22hg_v9m0000gn/T/52ba05aa-9001-4d46-9438-db81ef83 06f0/res/values-sw720dp-lan
Does anyone know what the issue might be?

Did you find a workaround for the Error? I'm getting the same and I can't seem to find any solution.

Getting Device Properties like OS,Model,Brand,SDK,Version and CPU on Air for Android

Hi there,
I just wanted to share this old blog post in case no one knew about this here (like i didn't). I have no affiliation with this person, i just think its great!
Getting Device Properties like OS,Model,Brand,SDK,Version and CPU on Air for Android
http://www.funky-monkey.nl/blog/2010/11/11/getting-device-properties-like-os-model-brand-s dk-version-and-cpu-on-air-for-andoid/
I was able to correctly identify DroidX and Motorola Xoom family edition in my test, with no ane, pretty cool!

Okay. I've found an answer:
yes, you can and have to add these icons via the descriptor file, since flash wont let you. But before you do that, go into the "Air publish" settings in flash. Here, right on page 1, there is the "include files" section. Add your icon pngs there. Hit OK and exit these settings. Now open the descriptor with an editor outside of flash and write in the files like I posted above. Close. Save. Make it write protected. No go to flash and publish.

Why is debugging an AIR for Android on device via USB so awful?

I've used Flash 8, Flash Pro CS4, CS5, CS5.5, and now CS6 and I have to say when it comes to debugging it is absolutely the worst environment I've ever worked in. Over the years the number of times I've successfully debugged an application can be counted on one hand. Really, its that bad. Flash will crash or stop responding. I place a breakpoint in the code and Flash will either: A) Ignore it, B) "Breakpoint not set; No executable code at line ###" C) Crash and burn. D) breakpoint turns on but can never be turned off.
Its infuriating and maddening. After this much time why can't Adobe make the debugger work?
Frankly, because of this I have to write ALOT of trace statements into my code.
Has Adobe just given up on the debugger in Flash Pro? As a developer should I be trying to convince my company to switch over to Flash Builder?
For example, right now I'm trying to debug an AIR for Android 3.4.0.2540 via USB on a Motorola Droid 2. I can publish and run in debug mode and see all my trace statements just fine. But I know the instant I need to try to set a breakpoint I'm doomed. Or if my code gets in a race condition like right now. The breakpoints in the new code I added were ignored (see B above) and I can find no options in the Debug menu to break into my app and observe what code it is currently executing. My only option is to end the debug session.
Can anyone comment on debugging in Flash Builder vs. Flash Pro? Is it any better?
Can anyone suggest a solid development environement with debugging that supports Actionscript 3 or can compile it to some other language or object code that would allow me to reliably debug code?
I'm sorry for venting like this. I like Actionscript 3 and I even like Flash Pro until it comes to debugging. But at this point I really need to consider other options so I can get some work done.

Hi Chris,
I also have an HTC Legend, and I'm trying to make some tutorials about publishing from Flash Builder to Android.
I've notice this also, and I must say, it's a complete deception that AIR cannot support this phone, and certainly it seems that upgrading to the Android 2.2 was a bad option, since I defenitly was able to make a simple flash game, and some other exeperiments, and got them to work with AIR when this phone had Android 2.1
If it runs on Android 2.1, maybe it was a an upgrade that make AIR incompatible with this device on Android 2.2. Is there any way of running it, maybe forcing to install a AIR version that works.
I was starting to program on Flash Builder, and experimenting on my Legend, but now I stumbled on this.
Thanks,
Leonel

Best way to preview AIR for Android projects for different devices?

So if I am developing an AIR for Android app, is there a good, simple way to preview the app on any android device? I have installed it on my phone of course, but is there a simulator/emulator of some sort available so we can see how it would look on both an Android phone and a tablet? Thanks in advance to anyone who can help!

DPI aside, you can just set your resolution on the project to the target devices resolution to preview how it will look. While vectors will render much smoother on the device (higher DPI), it's a very easy way to target various resolutions for testing.
If you have the full CC suite you might want to consider using Flash Builder 4.7 which has many different device presets and allows you to create your own presets to mimic tablets and phones. It really depends how complex your project is to move over to FB.

The Error Message 'Application descriptor file cannot be parsed' shows when compiling (Ctrl + Enter) Adobe AIR for Android applications on Flash Professional CS5.5

The Error Message 'Application descriptor file cannot be parsed' shows when compiling (Ctrl + Enter) Adobe AIR for Android applications on Flash Professional CS5.5
This is happening for most of the pupils and staff at our school and they are unable to complete their work.
This also happens on a fresh copy of windows and CS5.5 without any updates and also with all latest updates.
I have tried it on 32-bit and 64-bit CS5, Windows, Air and Java with the same error every time.
There are a small minority of users where this works fine for them with no issue.
I have tried re-setting user profiles.
I have tried a local admin and domain admin account with the same issue
I have noticed however that if the file is moved to the shared area it will compile. If it is on their documents area it will not compile. The users have full control in both locations. This is fine for staff but we are unable to give full control or modify access to the shared area for the pupil's
I have been through the online support section and it directed me to phone Adobe Customer care who informed me that all support has been discontinued for CS5, CS5.5 and CS6 and they will only support creative cloud.
Any ideas what to try next? There is no other information about this error and I cannot work out what is causing it.

I have tried and able to package an apk using your XML file.Could you please make sure your XML file starting from line 1 and coloumn 0.Any space will results in the error (Application Descriptor file cannot be parsed)
-Pranali

Using Google Play Developer License RSA code with Air for Android App?

What is the procedure for using Google Play Developer's provided license code (Base64-encoded RSA public key to include in your binary) for an Air for Android app in Flash?
I see the need to load a p12 file and have gone through the process of creating one for Air for iOS with OpenSSL but the Google provided key is in a different format. To start with it is delivered by copy/paste off a webpage.
I am using Flash CS5.5. I could switch to CS6 if neccesary.
Thanks

Follow this link, see post number 12.
http://forums.adobe.com/thread/1115438

AIR for Android - best video specs?

Hello everyone,
I'm trying to develop a custom video player app using the AIR for Android extension in Flash Pro CS5.
I tried out an FLV and an MP4 video with the most stripped back code snippet, but the video still seemed a bit jerky on my phone. (Samsung Galaxy S)
// Code
var video:Video;
var connect_nc:NetConnection = new NetConnection();
connect_nc.connect(null);
var stream_ns:NetStream = new NetStream(connect_nc);
stream_ns.client = this;
video = new Video();
addChild(video);
video.attachNetStream(stream_ns);
stream_ns.play("video.flv");
Would anyone know what the ideal encoding specs are for non-jerky video? Is it something to do with H.264, or perhaps CPU vs GPU? (I tried that too, with no visible difference.) Even with the app running at the appropriate frames per second (in this case, 24fps), the video seemed less than smooth.
Any comments would be much appreciated!

Hi [email protected]
These should help you:
http://www.adobe.com/devnet/devices/articles/encoding-guidelines-android.html
http://www.adobe.com/devnet/devices/articles/video-player-optimization.html
regards Mike

AIR for Android video issue

On Android, in an app that I’ve developed successfully for iOS, I’m seeing this problem:
There are 5 videos built-into the app. On Samsung phones (S3 and S4), running Android 4.4.2, at the first attempt to play a video there’s sound but no picture. After returning to the video menu and attempting again, video and sound play normally. If a video is stopped and another one is started, initially a frame of the previous video is displayed (for a fraction of a second), then play resumes normally with the chosen video.
The sound-but-no-video problem does NOT show up on a Nexus 7 running 4.4.3, although the flash-frame problem does.
I’m publishing with AIR SDK 15 packaging both with and without captive runtime to try to isolate the source of the problem. I’m using <contains video> true </contains video> in the descriptor.
This feels like AIR-for-Android buggishness. Any confirmation out there? Similar problems? Workarounds?
I’ve read somewhere that AIR runtime v.3.3 may solve some video problems on Android, but not sure where to find an archived Android version of AIR that old.

Well, as it sometimes happens with me, I have spoken too soon. The answer that I marked as ‘correct’ the other day (Colin, are you there?), seems to be not quite the right answer. At least, it doesn’t solve the video problem that I’m having with some, but not all, Android devices.
After trying Colin’s suggestion – using if (stage.stageVideos.length != 0) to make sure that a stageVideoAvailabilityEvent hasn’t already fired when I try to play my first StageVideo instance – and getting perfect results in 10 consecutive tries on my Samsung S4 and S3 phones, I figured that was IT.
Next day, same devices and same code, it DIDN’T work! I pulled hair, issued profanities, hammered on the table. It didn’t matter—I still got a ‘mis-fire’ on the first play of a video whenever (almost whenever) I opened the app. After the first play everything was good – which is the exact problem that I started with many days ago. When I played Colin’s Sesame Street ‘Let’s Get Ready’ app again – the same first-play-of-video problem shows up there too.
This problem does not show up on Nexus 7 and the Samsung Galaxy 5 Tab. It is a royal p.i.t.a. on Samsung phones, where I need my app to work.
I created a bare-bones app to reproduce the problem, code below. Just a single class to play a single video with no controls. A few parameters (path to the video, and viewport stuff) are passed in from the document Class. I run it 10 times on my S4. It fails 7 times and plays well 3 times. The 'initialize2()' function never fires, proving that the stageVideos array already exists by the the time the 'initialize1()' function is called.
I'm pretty sure that this is not a coding problem (because it works well on some Androids and in iOS), but WHAT is it??
package vidTestSource
import flash.desktop.NativeApplication;
import flash.desktop.SystemIdleMode;
import flash.display.MovieClip;
import flash.display.Sprite;
import flash.display.StageAlign;
import flash.display.StageScaleMode;
import flash.events.Event;
import flash.events.NetStatusEvent;
import flash.events.StageVideoAvailabilityEvent;
import flash.geom.Rectangle;
import flash.media.StageVideo;
import flash.media.Video;
import flash.media.StageVideoAvailability;
import flash.net.NetConnection;
import flash.net.NetStream;
public class MobileVideosolo extends MovieClip
      public var stream:NetStream ;
      public var video:StageVideo;
      var xx:Number;
      var yy:Number;
      var ww:Number;
      var hh:Number;
      var mymoov:String;
public function MobileVideosolo(mymoov,xx,yy,ww,hh)
      this.xx = xx;
      this.yy = yy;
      this.ww = ww;
      this.hh = hh;
      this.mymoov = mymoov;
     addEventListener(Event.ADDED_TO_STAGE, onstage);
function onstage(e)
    if (stage.stageVideos.length != 0)
       initialize1();
     else
      stage.addEventListener(StageVideoAvailabilityEvent.STAGE_VIDEO_AVAILABILITY, stageVideoState );
function stageVideoState(e)
       initialize2();
       stage.removeEventListener (StageVideoAvailabilityEvent.STAGE_VIDEO_AVAILABILITY, stageVideoState);
function initialize1()
      var nc:NetConnection = new NetConnection() ;
      nc.connect(null) ;
      stream = new NetStream(nc) ;
      stream.client = this ;
      video = stage.stageVideos[0] ;
      video.viewPort = new Rectangle(xx,yy,ww,hh) ;
      video.attachNetStream(stream) ;
      stream.play (mymoov) ;
      MovieClip(parent).sVtext.text = "Init 1";
      stream.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
function initialize2()
    var nc:NetConnection = new NetConnection() ;
     nc.connect(null) ;
     stream = new NetStream(nc) ;
     stream.client = this ;
     video = stage.stageVideos[0] ;
     video.viewPort = new Rectangle(xx,yy,ww,hh) ;
     video.attachNetStream(stream) ;
     stream.play (mymoov) ;
     MovieClip(parent).sVtext.text = "Init 2";
     stream.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);

AIR for Android Captive Runtime

Is it possible to package android apps with AIR (or will it be) using Flash CS5.5? I don't see anything on the web about. Just how to do it with Flex and ADT etc...

Hi,
I've made a complete working example for publishing an application with captive runtime, assets and native extensions starting from Flash CS5.5
I was able to make it thanks to hints and suggestions I found in this thread.
Note: english is not my native tongue so I hope you understand what I've written also if sometime it sounds "engrish".
Here it is the link to the zip file:
    http://www.genereavventura.com/hosted/Air3NativeExtensions/AirVibrate.zip
Requirements:
- You must have Flash cs5.5 pro (obviously)
- You must have installed the overlay for Air3.0 sdk on your Flash cs5.5 pro
Here it is a link that explain how to accomplish it: http://forums.adobe.com/message/3939712
Here the steps I made.
1) Open Flash CS5.5 and create a new AIR for Android application
2) Add the swc to the libraries used by your FLA (open Actionscript 3.0 settings and add "VibrationActionScriptLibrary.swc")
   Btw, you can find this "ready to use" native extension inside the zipfile that you can download from here: http://www.adobe.com/devnet/air/native-extensions-for-air/extensions/vibration.html
   However in my example you will find also a directory named "extension" that contains it.
3) Open and then close the "air for android settings": by doing this Flash will create yourapp-app.xml file in the directory where your FLA resides.
   For example my fla is named "vibrate.fla" so Flash created for me a "vibrate-app.xml" file.
4) Make a copy of this "vibrate-app.xml" file by naming it "real-vibrate-app.xml" (or choose whatever name you want)
   I've done this because after modyfing the original one by adding the <extension> tag (see below) I wasn't able to test my app from within Flash IDE (when I compile it it simply doesn't start)
   Instead by doing this all worked fine.
5) Edit the "real-vibrate-app.xml" file by adding somewhere these lines (I added it just before the <initialWindow> tag)
    <extensions>
      <extensionID>com.adobe.Vibration</extensionID>
    </extensions>
6) Add <uses-permission android:name="android.permission.VIBRATE"/> in the <android> <manifestAdditions> part in "real-vibrate-app.xml" file.
   You should do something like this:
   <android>
      <manifestAdditions>
        <![CDATA[<manifest>
          <uses-permission android:name="android.permission.VIBRATE"/>
        </manifest>]]>
      </manifestAdditions>
   </android>
7) Develop your application
   I made a simple one that loads an external jpg and shows it on the stage: then the user can tap on it to make the phone vibrate.
   The function "doVibration" is called only when the app is running on Android Device so I do not get any executions error when I run the app from within Flash Ide
8) Publish and test it to your USB connected device by launching the "publish.bat" file I have created
   Open a dos prompt and move to your project directory then type publish.bat and press enter.
   Note: it can be that you have to edit the bat file in order to change the path to the ADT tool that comes with Air3.0 sdk
   It should be in [your adobe flash cs5.5 directory]\AIR2.6\bin\adt (rememeber, you must have installed the Air3.0 sdk overlying the old Air2.6/2.7 in the AIR2.6 directory)
   Inside the bat file you can change easily the target type (captive or not) simply by commenting/decommenting the right line.
   Captive version is about 8Mb more than the normal one but the big deal is that the user that installs it do not need the air runtime installed on his phone!
   The "big line" that creates the package is the following one:
   call %ADT_LINK% -package -target %TARGET_TYPE% -storetype pkcs12 -keystore certificate/vibrate.p12 -storepass android AirVibrate.apk real-vibrate-app.xml -extdir extensions vibrate.swf icons assets
   where:
   call %ADT_LINK%          it's just the path to the ADT tool
   -package                 it's the command that we want ADT to execute
   -target %TARGET_TYPE%    captive/non captive version
   -storetype pkcs12        certificate related
   -keystore certificate/vibrate.p12 path to your self signed certificate
   -storepass android       certificate related, I created the example certificate with "android" password and this parameters tell ADT to always use it without prompting
   AirVibrate.apk           the name of the Apk
   real-vibrate-app.xml     the apk-xml to use that is the one we modified manually above
   -extdir extensions       it's the path to the directory that contains the native extension
   vibrate.swf              the main swf
   icons                    the icons directory
   assets                   the assets directory (where I put the external jpg)
That's all.
If everything is correct, the batch file creates the AirVibrate.apk then installs it on your attached usb device and run it.
When you tap over the Android image that will appear, your phone should vibrate.
Now.. does someone wants to develop a Native Extension to show Admob banners in our Android Air Applications?
If I missed something, please let me know.
Thanks

AIR for android Sensors

Hi all,
I am developing in AS3 AIR for Android in the flash cs5 IDE.
I want to develop an app that on click logs the users lat, lon, elevation, angle, and direction the phone's camera is pointing.
I know that the there are accelerometer and geolocation sensors in flash.sensors, but i am unclear as to if the accelerometer and geolocation can give me all the data i need. I know i can the lat and lon with geolocation.. i don't know how ever really how to interpret the data of the accelerometer, let alone how to determine the direction (n,e,w,s etc..) of the phone..
also, i am not sure i am running the most up to date AIR for Android extension but my extension manager doesn't seem to prompt me for an update..
Erik

Well Accx,y and z all give accelration in x, y and z direction.
Imagine an AIR application opened with stage in portrait mode. Now imagine
X axis running from bottom left corner to bottom right corner,
Y axis running from bottom left corner to top left corner and
Z axis coming out from the face of the device.
When a device is lying flat on a table on its back z axis is pointing up and is under gravitational accelration of 1 g(9.8 m/s2) downwards. So you can imagine an acceration of 1 g upwards to make that device lie stable on the table.
When a device is under free fall, all three values will be 0.
When device is in upright position with its face poiting your front, accY would be 1 and accX, accZ would be 0.
I hope this helps in understanding the different values in other scenarios. Its just the aceeraltion in a specific direction. As a side note, accelrometer values would not give the direction the device's face is pointing to. For example in the last case above, if you rotate the device about its Y axis, all values would remain same, but the face is still pointing to different directions.
Thanks,
Meet

How to add Google Ads or similar in "AIR for Android" application?

Hello,
I have developed my android application (AIR for Android) in Flash Professional CS5.5. It's completed and fully tested on multiple android phones. Now I want to add Google Ads in my application to make some money.
What I already know:
I know that Adobe provides AdMob native extension API which allows you to add Google Ads in your app. But unfortunately, it's not free.
What I want:
I want a free resource through which I can add ads in my application.
Please guide me how can I achieve this?
Thanks in advance,
momersaleem

Yes, its for me broken, too.
I found the link in this thread:
http://forums.adobe.com/message/4036804
Maybe try to contact the author or one of the thread participants for an unbroken version?

Air For Android - Full Screen not working

Opened CS5.5 > Chose "Air For Android" which gave me a stage dimension of 480x800 default. I then created my app.
I am using a Droid Bionic and testing my app on it. It will not go to full screen, regardless of how I am holding the Droid. When publishing, I clicked "Full Screen" and Portrait, Landscape, Auto Orientation, etc. I tried all of the publishing options, yet still there is white screen on the eastern and southern side of the screen.
I have a picture on the main screen, and it fits perfectly within the 480x800 dimmensions when playing in Flash. After publishing to an APK file and testing it on Droid, I have that white space as mentioned, as if the stage size grew larger than the picture / app. I also shrank the stage(480x800) dimensions to to (340x600) , but still the same amount of white space. When I move the picture to the right a bit, and publish, it shows the white space on the left hand side of the stage. This can only mean that when I publish, the stage size grows but everything on the stage stays the same.
Any ideas?
Thanks!

I removed:
stage.scaleMode = StageScaleMode.NO_SCALE;
stage.align = StageAlign.TOP_LEFT;
from AS3 and it works better. Now there is even white space on the north and south side of the screen. Clicking "Full Screen" in the publish settings, makes a little more white space, which is weird. It as if now the stage is expanding its height, rather than its height and width due to me using the above code. Still, would like to get rid of that extra white space.
Edit: It looks like the stage height grew by 60. If I expand the picture by 60, placing it on the stage at 0x and -30y, it fits fine on the bionic. I don't understand why this is happening, and scared that it may be different for each device.

Adobe AIR for Android - GPU Mode - Bitmap Auto-Smoothing Issue

Hi everyone
I'm having a bit of an issue with the AS3 bitmap object. I'm currently developing an 8-bit style pixel game for AIR for Android.
This game is being developed at a very low resolution and is being scaled up to maintain the charm of an old retro game.
One of the methods I'm using is drawing pixels directly to bitmap objects and scaling the object up to create the old look.
When testing on a mobile device, this works beautifully when you set the rendering method to Direct but when you change
the render method to GPU the visuals go all blurry and anti-aliased (it's as if the bitmap is being smoothed out). The mini map
for example is rendered using the setPixel method and then scaled up 9 times. Looks great on my PC but once I export it to my phone
it looks absolutely awful! This is no good as I want to keep the clean, solid pixel look to maintain the the old 8-bit feel and obviously
I'd like to stick to GPU mode due to it's speed.
Like I said, this only happens once you test on a mobile device in GPU mode - it doesn't do it on my main desktop machine or
in Direct mode. I already have the stage quality set to low and I've tried setting the bitmap's smoothing property to false but
it does nothing.
Does anyone have any suggestions as to how I can get around this?

How about first blit your image to a small bitmapData, then draw it on a large bitmapData (9X larger)?
Like,
var small_bmd:BitmapData = new BitmapData(SMALL_WIDTH, SMALL_HEIGHT, false);
var large_bmd:BitmapData = new BitmapData(SMALL_WIDTH * 9, SMALL_HEIGHT * 9, false);
var bm:Bitmap = new Bitmap(large_bmd, PixelSnapping.NEVER, false);
var blitRect:Rectangle = new Rectangle(0, 0, 9, 9);
var i:uint, j:uint, blitColor:uint;
small_bmd.draw(SOURCE_IMAGE);
large_bmd.lock();
for(j = 0; j < SMALL_HEIGHT; j++){
     for(i = 0; i < SMALL_WIDTH; i++){
          blitColor = small_bmd.getPixel(i, j);
          blitRect.x = i * 9;
          blitRect.y = j * 9;
          large_bmd.fillRect(blitRect, blitColor);
large_bmd.unlock();
Not sure if the code works or not, but hopefully this helps.

Partial wakelock in Adobe Air for Android

I'm developing Adobe Air (for Android) application which is intended to be constantly on. App has event based operations. However, when phone enters to sleep mode app is able to perform only one or few events in a second which is not good enough. AIR's SystemIdleMode.KEEP_AWAKE -mode is not an alternative since it is too battery consuming.
I'm looking for a solution where phone is allowed to go into sleep mode (screen is off) but still CPU performance is not drastically dropped. Not sure if Android's partial wakelock -mode does the job and is available via ANE?

Well Im a bit puzzled now. I just created a quick AIR app using AIR13 for Android and did a DEACTIVATE test on the NativeApplication.nativeApplication property and used a TextField to "trace" out the frame rate when the app deactivated. The frame rate stayed at 24FPS the entire time. I turned the screen off, let it turn off, went to the home screen, and switched to other apps while the test app was still running. In all cases, the frame rate never dropped to 4FPS as indicated in Adobe's documentation. So it is either something a bug or feature of AIR13+ or it is how Android KitKat handles applications in the background. Im using an unlocked/stock Moto X running Android 4.4.3. The app also appends the getTimer() call to the end so you can see that it does change. Here is a link to the quick app I created: Dropbox - deactivate.apk
I guess if you want to download that and test it out to see how it behaves on your device and let me know the results. What device and OS are you running?
Below is the original message I started to type before I decided to create a quick app to test with. It may or may not still be relevant based on your results from my app test.
If you are looking at just recording information, you could probably setup something on the Android/Java side that gets started when the app "sleeps" using the DEACTIVE event as a trigger to start the ANE side of things. Then when your app "wakes", you could use the ACTIVATE event to trigger a call to the ANE to pull all the data collected in the Java side back to AIR and stop the ANE data capture since the data capture would be back to being handled by AIR.

Invalid extension descriptor - Licensing AIR for Android devices

Similar Messages

Maybe you are looking for