AIR 3 Android runtime full of bugs?

I have a Flex SDK 4.5.1 Flex mobile app and i have not compiled it yet using the new SDK. So it's stil being compiled with the current 4.5.1 sdk release.
I took the air Runtime.apk from the sdk, manually installed it on my phone just to see how my current APK runs with the new Air 3 beta runtime...and it's full of bugs.
It starts out fine, but i've noticed after im on a view when I activate and view the raw camera inside the view, the screen sort of flickers, goes black for a second, then comes back.
Then, after this happens it seems like the back button no longer functions properly. Rather than doing a pop view, it seems to quit the application. This only happens after the camera is accessed.
I've also noticed randomly sometimes the view will no longer auto rotate properly, and some things don't scale properly.
I've also noticed the Sideways camera bug is still not resolved. This is extremely important and really needs to gets fixed. You can see the bug report I submitted a LONG time ago right here http://bugs.adobe.com/jira/browse/SDK-30317 Please this has to be fixed.
To solve the random bugs, is it possible once i compile the app with the new sdk it wil work fine? Just seems like it should be able to run fine on the new runtime, what about the devs that don't update their apps right away?

This is all on a Nexus One 2.3.4 and a Xoom 3.1
Is anyone else out there with a flex mobile project? That features using the camera. Or maybe someone that can confirm the camea is sideways, causing flickers, and back button is sometimes exiting the app, rather than popView

Similar Messages

AIR for Android runtime for marktets

hi,
why i can't find AIR .apk installer on other markets? only google?
you should add a icon "get AIR Android" - like "get flash" - and link to download the .apk
now i can't find ANDROID OS:
http://get.adobe.com/air/otherversions/
add immediatley please- hurry ...
ciao

Aren't you seeing Adobe AIR in market of your device? Please be aware that Adobe AIR is available only for ARMv7 devices.
By "other" markets do you mean a modified market application on device, or outside of device market?
What is your use case of finding the Runtime out of market?
Regards
Syed
P.S: You won't be able to find apk on http://get.adobe.com/air/otherversions/, as it isn't available there.

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.

Air 2.5 runtime for android 2.1 (eclair) device

as I understand it Air 2.5 Runtime - Device [For Eclair] was made available over the summer through adobe prerelease, which is for a device using Android 2.1. I believe now there is an Air Runtime available in the Android Market for Android 2.2.
Where can I get the Air 2.5 Runtime for a 2.1 device?

"very unsupported" Wow! as of December 1st 2010 (16 days ago) there are just about as many android users on 2.1 as 2.2; only differing by about 3% - 4%. Having it on 2.1 would just about double the amount of devices we could build for, therefore sale to. Kind of surprising as there was already a prerelease of that version that superseded the current 2.2 which is in the android market already.
Thanks for the advice! I will most definitely be doing that.
here's the link of the pie chart which shows the users on each android platform version.
http://developer.android.com/resources/dashboard/platform-versions.html

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

Video playback issues in Air for Android

Hello everybody
I am developing an advertisement application which plays multiple videos. I have faced a very strange problem: nor the simple Video nor the StageVideo are not visible when I run the app on target android device. I can hear the audio but the only way to get the video is to press back button and then get back to app but in this case the video goes over the UI. This happens only on a target device which is a chinese sibo android tablet. It has android 4.1 on board. I have seen a lot of people had the similar issues:
http://forums.adobe.com/message/5429125
but the solution mentioned there - adding <containsVideo>true</containsVideo> to the manifest xml doesnt help
I am using adobe air 4.0 sdk and the air 4.0 runtime on the device. I have tried to change renderMode to CPU/Direct/Auto but it doesn change anything.
The other three android devices I have - toshiba thrive tablet(4.0.4)/ eken tablet(4.2.2)/ htc desire c(4.0.3) play all the video content without any problem.
Any advice will be highly appreciated,
Max

Hi, Chris,
I think this issue: Bug#3832525 - [Android] Video + Stage3D = Video don't work but sound continue playback
Also there is many critical video playback issues:
Bug#3759420 - [Platform_Windows] GPU accelerated video stop playing when screen resolution changes after NetStream.Buffe…
Bug#3810201 - [Android] H.264 video rotating problem
Bug#3503389 - [Platform_Android]StageVideo attachCamera()
Bug#3802932 - [iOS] Video stops playing
Bug#3840986 - [iOS] Simple Video object doesn't work with H.264 (MP4) videos
Bug#3779843 - StageVideo + NetStream + Starling = R6025 Error
Bug#3626740 - H.264 playback conflicts with Stage3D (Android)
Bug#3832327 - [Android] NetStream decodedFrames don't work
Bug#3832141 - Video is not working if you seek on NetStream.Play.Stop and have a bufferTime
Bug#3810979 - AIR on iOS: Using StageVideo makes 2D Display objects opaque/black over Stage3D
Bug#3578045 - new Video() android black screen
Bug#3703836 - Black screen on Samsung Galaxy S4 and Nexus 7 device
Bug#3837870 - [iOS] StageVideo + Stage3D = video not displaying but sound playback
Bug#3840983 - [Android] Returning from Alarm Clock causes black screen when using Video with GPU acceleration
Bug#3840999 - [iOS] [Android] Turn off screen at NetStream.Buffer.Flush causes video not work or crash with some videos
Bug#3844059 - [iOS[ Switching between multiple NetStreams not work
Bug#3773944 - Video view top at android 4.3
and more
All of these problems very important for our business. Often we cannot create stable AIR applications when we need to use videos.
Could you force for faster fixing these issues?

9/26/2012 - AIR 3.5 Runtime and SDK Beta

The beta release provides access to the AIR 3.5 runtime and SDK for Windows, Mac OS, iOS and Android.
The primary goals of this release are bug fixing, adding Jellybean support, and iOS app enhancements.
Below are some of the key features and benefits of AIR 3.5:
Debug stack trace in release builds of Flash Player — This feature enables developers to display stack trace info in release and debug builds.
Packaging Multiple Binaries — This feature enables developers to include third party static libraries and frameworks and package these with ANE.
Shared ByteArray support for ActionScript Workers — This feature enables developers to share memory between multiple workers.
Packaging and loading multiple SWFs on iOS — This feature will allow developers to load multiple swfs, that contain ActionScript bytecode on iOS .
You can find instructions for getting started with this release here: AIR 3.5 Labs Page
We encourage you to let us know what you think over on our AIR 3.5 Labs Forum

11/12/2013 - Release - AIR 3.9 Runtime and SDK

Today we're pleased to announce that the next version of AIR is available for immediate download. This update includes the following new features and improvements:
New Features:
Mobile Workers (concurrency) BETA - Android
Our hugely popular desktop feature, AIR Workers, is now making its debut on mobile! We have added support on Android devices so that you will be able to execute code in the background without interrupting your application’s main code. Your UI will remain responsive, enhancing the user experience. We haven’t forgotten about iOS! Look for news on iOS workers in an upcoming release (NOTE: this feature will undergo an extended beta period.)
AIR Mobile Support for Background Execution in “Direct” Render Mode
AIR now supports background execution on iOS and Android when render mode is set to “direct”. This will allow your applications to perform tasks such as audio playback even when invisible to the user. Due to power and CPU considerations, we recommend reviewing our release notes for additional details and guidance.
In the past AIR on iOS and Android did not support background execution when render mode direct was set. Due to this restriction, Stage3D based apps were not able to execute background tasks like audio playback, location updates, network upload/download etc. iOS does not allow OpenGLES/rendering calls in the background. Applications which attempt to make OpenGL calls in the background are terminated by the iOS. Android does not restrict applications from either making OpenGLES in the background or other background task(like audio playback).
With this feature, we will now allow AIR mobile apps to execute in background when renderMode direct is set. AIR iOS runtime will throw an error if OpenGLES calls are made in background. However no error will be thrown on Android, as Android native apps are allowed to make OpenGLES calls in the background. It's recommended to not make rendering calls while your app is executing in the background as its important to utilize the mobile resources judicially. The following is a list of Stage APIs which may throw the error 3768 - The Stage3D API may not be used during background execution. The swf version should be 22 and above.
Context3D.clear
Context3D.present
Context3D.createVertexBuffer
Context3D.createIndexBuffer
Context3D.drawToBitmapData
IndexBuffer3D.uploadFromVector
IndexBuffer3D.uploadFromByteArray
VertexBuffer3D.uploadFromFloat
VectorVertexBuffer3D.uploadFromFloat4
VectorVertexBuffer3D.uploadFromByteArray
Program3D.upload
Texture.uploadCompressedTextureFromByteArray
Texture.uploadFromBitmapData
Texture.uploadFromByteArray
CubeTexture.uploadFromBitmapData
CubeTexture.uploadFromByteArray
CubeTexture.uploadCompressedTextureFromByteArray
RectangleTexture.uploadFromBitmapData
RectangleTexture.uploadFromByteArray
AIR Support for iOS7
iOS7 has launched and we are making sure that AIR is compatible and performs as expected.
AIR Mac OS 10.9 Support
We have tested against the latest developer releases of OS X 10.9 and are making sure that your applications support the latest technologies such as “App Nap”.
AIR XXHDPI (144 x 144) Icon Support for Android
With this feature we have added support for beautiful, high resolution icons on devices such as the Nexus 10.
Notable bug fixes:
[3650590] [OSX] - App Updater Crashes on MacOS with Air 3.9
[3648442] [iOS7] - Leftmost part of the text in spark TextArea and stageText get clipped when mulitline property is true.
[3640207] [Android] [Captive Application] - orientationChange event handler fetches wrong stage.orientation values.
Known Issues:
[3616981] [iOS] - Sound gets stop on clicking Power button even when UIBackground tag value set to Audio in application.xml
For further information please see our release notes.
Download Locations:
AIR 3.9.0.1210 runtime for Windows: 3.9 Runtime Download
AIR 3.9.0.1210 runtime for Macintosh: 3.9 Runtime Download
AIR 3.9.0.1210 SDK & Compiler for Windows: 3.9 SDK & Compiler Download
AIR 3.9.0.1210 SDK & Compiler for Macintosh: 3.9 SDK & Compiler Download
Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 3.9 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 3.9 SDK & Compiler”.
AIR SDK 3.9.0.1210 (Compatible with Flex) for Windows: 3.9 SDK Windows Download
AIR SDK 3.9.0.1210 (Compatible with Flex) for Macintosh: 3.9 SDK Macintosh Download
Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

9/10/2013 - AIR 3.8 Runtime and SDK

Today we are excited to announce that AIR 3.8.0.1430 is available for immediate download. This update includes multiple stability fixes for both the runtime and SDK.
Notable bug fixes:
3587773 - [External bug][iOS]Creating too many FileStream objects will cause app to crash on iOS
3613819 - [iOS7] - Using Sound.play app asks permission for accessing the Microphone even when microphone API is not used in the app
3587452 - [Android] - 144x144 image size icon should be supported on android
3606308 - [Android][SecureSocket] - Application getting crash when trying to connect with host contains SSL certificate.
3077653 - [iOS] - Creating too many FileStream objects will cause app to crash on iOS.
3560721 - [iOS] - Application crashes having Microphone running for 10 to 20 mins
3572885 - [Android] - 'orienationChange' event is not fired when Stage rotated through setOrientation() method
3554585 - [Android] - Stage is blank in GPU mode because of rotationY property
Multiple stability and security fixes
For further information please see our release notes.
Download Locations:
AIR 3.8.0.1430 runtime for Windows: 3.8 Runtime Download
AIR 3.8.0.1430 runtime for Macintosh: 3.8 Runtime Download
AIR 3.8.0.1430 SDK & Compiler for Windows: 3.8 SDK & Compiler Download
AIR 3.8.0.1430 SDK & Compiler for Macintosh: 3.8 SDK & Compiler Download
Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 3.8 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 3.8 SDK & Compiler”.
AIR SDK 3.8.0.1430 (Compatible with Flex) for Windows: 3.8 SDK Windows Download
AIR SDK 3.8.0.1430 (Compatible with Flex) for Macintosh: 3.8 SDK Macintosh Download
Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

7/24/2013 - AIR 3.8 Runtime and SDK

Today we are excited to announce the availability of the released version of AIR 3.8 and encourage you to download, use, and provide us feedback.
This update includes the following new features and changes:
4096x4096 texture support – With this feature, a new profile, BASELINE_EXTENDED is introduced in the class flash.display3D.Context3DProfile, which will support a maximum texture size of 4096X4096.
Rectangle Texture Support – Rectangle Textures are now supported in BASELINE as well as BASELINE_EXTENDED profile. The texture formats supported for Rectangle Textures are BGRA, BGR_PACKED and BGRA_PACKED. Details for usage can be found in the language reference.
LZMA Support – On iOS and Android, LZMA compressed swfs can now be packaged and are supported.
ServerSocket – ServerSocket APIs are now supported on iOS and Android.
DatagramSocket – DatagramSockets APIs are now supported on iOS and Android.
Notable bug fixes:
Touch events extremely slow on AIR with Stage3D(3536911)
[Android only-> GPU] Stage is blank in GPU mode because of rotationY property(3554585)
[Android] [Screen Orientation] 'orientationChange' event is not fired when Stage rotated through setOrientation() method(3572885)
[iPhone only] Application crashes when the Microphone is on for 10 to 20 mins(3560721)
[Screen Orientation][Android] Application rotates even if tag is set to 'false' and tag is set to 'any'(3562132)
StageWebView.drawViewPortToBitmapData draws incorrect bitmap on retina devices(3558603)
Support PIE enabled Apps on iOS - Apple now encourages developers to have the PIE enabled binaries - A warning is shared when app is uploaded on Apple App Store(3556281)
For further information please see our release notes.
Download Locations:
AIR 3.8.0.870 runtime for Windows: 3.8 Runtime Download
AIR 3.8.0.910 runtime for Macintosh: 3.8 Runtime Download
AIR 3.8.0.870 SDK & Compiler for Windows: 3.8 SDK & Compiler Download
AIR 3.8.0.910 SDK & Compiler for Macintosh: 3.8 SDK & Compiler Download
Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 3.8 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 3.8 SDK & Compiler”.
AIR SDK 3.8.0.870 (Compatible with Flex) for Windows: 3.8 SDK Windows Download
AIR SDK 3.8.0.910 (Compatible with Flex) for Macintosh: 3.8 SDK Macintosh Download
Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

12/11/2012 - AIR 3.5 Runtime and SDK Update

Today, the AIR 3.5 Runtimes and SDK's were updated to address stability and performance issues, in particular the following problems have been addressed:
Video playback broken on Digital Theater AIR app (3364478)
Wrong layering/depth of video component after re-activating app on Nexus 7 (3356240)
Mac AIR not enforcing output protection when switching/dragging from internal to external monitor (3366931)
New Feature:
We have added a new Android-specific xml element <containsVideo> in the application.xml. If an app uses Video, then the app is expected to add <containsVideo>true</containsVideo> in the application.xml as an indication to the runtime. This is necessary to maintain correct ordering of video with other Flash content across different Android OS versions.
AIR 3.5.0.880 Runtime for Windows
AIR 3.5.0.890 Runtime for Macintosh
AIR 3.5.0.880 SDK for Windows
AIR 3.5.0.890 SDK for Macintosh
For full details on the 3.5 release, please see our release notes.

Why is it impossible to find the IOS sdk 6.0 on adobe site or any related forum ? i searched everywhere the only place i found it was on developer apple in a DMG i needed to uncompress to see that it was in a format not reable by windows. as i understand the only way to get it is by installing xcode on a mac and copying it from here. Why adobe not giving it ? or updating the 3.4 sdk with 6.0 in it ?
I mean... with air 3.4 you can use platformsdk.. and you can use it on windows!! BUT NOBODY GIVE THE SDK!! Go on google and i dare you to find sdk 6.0 in a format readable for windows!
anyway i used the beta 3.5 for now i just found that sad that the support for such a obvious request isn't met.

APP created with Air for Android but doesn't work on the emulator for test - Help!

When I create an application using Flash CS5.5>>> AIR FOR ANDROID.
After creating a test page I go to publish settings and send the app on Emulator RELEASE ... The APP is loaded correctly but as soon as you start the emulator, give this error "The application XXnameappXX (process air.XXnameappXX) has stopped unexpectedly. Please try again" Help Please!

Ok i've find this before "Adobe Flash CS5/AIK2.5/runtimes/air/android/emulator/Runtime.apk" and install it on android emulator! Now works all i hope! Thanks for your answer!

Adobe AIR with Captive Runtime Support for Mobile | ADC Presents | Adobe TV

In this video, Technical Evangelist Andrew Trice covers Adobe AIR with captive runtime support for mobile application development, which will benefit your Flash Builder projects for the Android OS.
http://adobe.ly/wyNYjD

Witch version of flash builder is this?

AIR 3.7.0.166 Sound Bug Crash APP without error

Hello guys,
The last Adobe Air Mobile update gaves me a lot of head ake!
Im developing a multimidia APP, and since AIR was updated in my device, no more sounds is playing in the application.
It just crashes withou any error in Debug mode, and restarts. When i call Sound.play media function in any ocasion, it happens.
It seams that there is a REALLY BIG CONFLICT with the new AIR and Sound.play.
My references:
Im developing in Flash Builder 4.6, running Adobe AIR 3.7.0.166
on a Motorola Atrix MB860
with Android 2.2.2
To reproduce the bug just install any AIR APP with music controls, like this: http://coenraets.org/blog/air-for-android-samples/voice-notes-for-android/
APK: http://coenraets.org/android/VoiceNotes/VoiceNotes.apk   with the 3.7.0.166 version of AIR, and try to reproduce the sound.
That application was running ok until the update. There is an textflow bug too, witch import only underline <u> and link <a> tag (no more bold <b> and italic <i>) from HTML, but compared to the sound crash this is nothing.
I insist that all this was running OK since the last update (i even run an backup version cause i think i was making any script error).
I´m looking hopelessly the LAST version before that last one so i can continue developing my application. With this error i canot do anything!!!!
If someone can help me where i can find it, id appreciate a lot!
Thanks

05-29 19:59:00.896: I/DEBUG(3857): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-29 19:59:00.896: I/DEBUG(3857): Build fingerprint: 'sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P-17_20130107.155157:eng/test-ke ys'
05-29 19:59:00.896: I/DEBUG(3857): pid: 4130, tid: 4154 >>> air.com.baijie.learnhanzi <<<
05-29 19:59:00.896: I/DEBUG(3857): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
05-29 19:59:00.896: I/DEBUG(3857): r0 00000000 r1 afd46608 r2 00000000 r3 00000001
05-29 19:59:00.896: I/DEBUG(3857): r4 83195a94 r5 00006d00 r6 00000000 r7 00000017
05-29 19:59:00.896: I/DEBUG(3857): r8 2f8df18f r9 00003120 10 00323dd0 fp 00008ae0
05-29 19:59:00.896: I/DEBUG(3857): ip 00000000 sp 49995cc8 lr afd10e74 pc 8214b238 cpsr 60800030
05-29 19:59:00.896: I/DEBUG(3857): d0 454545656372756f d1 2e2e2e276a634b50
05-29 19:59:00.896: I/DEBUG(3857): d2 203334312020203a d3 6c20746f6e6e6163
05-29 19:59:00.896: I/DEBUG(3857): d4 5f2720657461636f d5 6f72646e61374e5a
05-29 19:59:00.896: I/DEBUG(3857): d6 6f43584d4f386469 d7 6165724336636564
05-29 19:59:00.896: I/DEBUG(3857): d8 0000000000000000 d9 3ff0000000000000
05-29 19:59:00.896: I/DEBUG(3857): d10 0000000000000000 d11 0000000000000000
05-29 19:59:00.896: I/DEBUG(3857): d12 0000000000000000 d13 0000000000000000
05-29 19:59:00.896: I/DEBUG(3857): d14 0000000000000000 d15 0000000000000000
05-29 19:59:00.896: I/DEBUG(3857): d16 5f534e4b52456574 d17 345f534e49707332
05-29 19:59:00.906: I/DEBUG(3857): d18 52454545584d4f49 d19 534e495f31534e4b
05-29 19:59:00.906: I/DEBUG(3857): d20 61446174654d385f d21 4b52624545456174
05-29 19:59:00.906: I/DEBUG(3857): d22 5f534e495f31534e d23 53616964654d3131
05-29 19:59:00.906: I/DEBUG(3857): d24 0000000000000000 d25 0000000000000000
05-29 19:59:00.906: I/DEBUG(3857): d26 0000000000000000 d27 0000000000000000
05-29 19:59:00.906: I/DEBUG(3857): d28 0000000000000000 d29 0000000000000000
05-29 19:59:00.906: I/DEBUG(3857): d30 0000000000000000 d31 0000000000000000
05-29 19:59:00.906: I/DEBUG(3857): scr 60000013
05-29 19:59:01.026: I/DEBUG(3857):          #00 pc 0014b238 /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.046: I/DEBUG(3857):          #01 lr afd10e74 /system/lib/libc.so
05-29 19:59:01.046: I/DEBUG(3857): code around pc:
05-29 19:59:01.056: I/DEBUG(3857): 8214b218 4810bd10 68004478 490fe7fa 68094479
05-29 19:59:01.056: I/DEBUG(3857): 8214b228 b1604788 23014a0d 447a7023 47906812
05-29 19:59:01.056: I/DEBUG(3857): 8214b238 6b4b6801 4a0a4798 6010447a 4809e7e8
05-29 19:59:01.056: I/DEBUG(3857): 8214b248 68004478 bf00e7e4 0102ef30 0104a884
05-29 19:59:01.056: I/DEBUG(3857): 8214b258 0104a880 0104a878 01023cc8 01028ece
05-29 19:59:01.056: I/DEBUG(3857): code around lr:
05-29 19:59:01.056: I/DEBUG(3857): afd10e54 02800016 08bd87f0 e5964000 e5967000
05-29 19:59:01.056: I/DEBUG(3857): afd10e64 e2144903 1a00000e e5965000 ebffee45
05-29 19:59:01.056: I/DEBUG(3857): afd10e74 e2055a02 e3853001 e1500003 0a000006
05-29 19:59:01.056: I/DEBUG(3857): afd10e84 e5865000 e1a00006 e1a01005 e3a02001
05-29 19:59:01.056: I/DEBUG(3857): afd10e94 ebfffea8 e1a00004 e8bd87f0 e3a00000
05-29 19:59:01.056: I/DEBUG(3857): stack:
05-29 19:59:01.056: I/DEBUG(3857):     49995c88 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995c8c 826efaaf /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995c90 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995c94 8276c953 /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995c98 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995c9c 82145e97 /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995ca0 8316e000
05-29 19:59:01.056: I/DEBUG(3857):     49995ca4 831a5e28
05-29 19:59:01.056: I/DEBUG(3857):     49995ca8 0000000a
05-29 19:59:01.056: I/DEBUG(3857):     49995cac 821d0869 /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995cb0 83195a94
05-29 19:59:01.056: I/DEBUG(3857):     49995cb4 00006d00
05-29 19:59:01.056: I/DEBUG(3857):     49995cb8 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995cbc 00000017
05-29 19:59:01.056: I/DEBUG(3857):     49995cc0 df002777
05-29 19:59:01.056: I/DEBUG(3857):     49995cc4 e3a070ad
05-29 19:59:01.056: I/DEBUG(3857): #00 49995cc8 00001000
05-29 19:59:01.056: I/DEBUG(3857):     49995ccc 821d5cdd /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995cd0 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995cd4 8316e000
05-29 19:59:01.056: I/DEBUG(3857):     49995cd8 00323dd0
05-29 19:59:01.056: I/DEBUG(3857):     49995cdc 002b6b98
05-29 19:59:01.056: I/DEBUG(3857):     49995ce0 82ded2d4 /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995ce4 82ded320 /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
05-29 19:59:01.056: I/DEBUG(3857):     49995ce8 00325ba0
05-29 19:59:01.056: I/DEBUG(3857):     49995cec 00009b98 /system/bin/app_process
05-29 19:59:01.056: I/DEBUG(3857):     49995cf0 00008124 /system/bin/app_process
05-29 19:59:01.056: I/DEBUG(3857):     49995cf4 00001074
05-29 19:59:01.056: I/DEBUG(3857):     49995cf8 4278f500
05-29 19:59:01.056: I/DEBUG(3857):     49995cfc 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995d00 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995d04 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995d08 00000000
05-29 19:59:01.056: I/DEBUG(3857):     49995d0c 3ff00000
SC8810, Android 2.3.5

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.

AIR 3 Android runtime full of bugs?

Similar Messages

Maybe you are looking for