Air app on Android fullscreen

I'm building an AIR mobile app for android >= 4.0. I must be missing something or doing something wrong because no mater that i do, i can't get the fullscreen working rigth.
The tablet bottom bar always shows up. In current version the bar only shows 3 dots and have somekind of alpha but it doesn't allow me to draw above it or below it.
In my app description XML i have:
<initialWindow>
<aspectRatio>landscape</aspectRatio>
<renderMode>direct</renderMode>
<autoOrients>false</autoOrients>
<fullScreen>true</fullScreen>
</initialWindow>
And the bar is still there
Tried set the fullscreen to false and then:
stage.fullScreenSourceRect = new Rectangle(0,0,1280,768);//Capabilities.screenResolutionX, Capabilities.screenResolutionY);
stage.displayState = StageDisplayState.FULL_SCREEN_INTERACTIVE;
No effect... the damn bar is still there.
Using FB 4.7, Air 3.8 and -swf-version=21
Any help or a pillow to put between the head and the wall would be very apreciated!!
Thanks

The same here... I tried this:
stage.displayState = StageDisplayState.FULL_SCREEN_INTERACTIVE;
stage.showDefaultContextMenu = false;
and:
<fullScreen>true</fullScreen>
but it doesn't work.
I have rooted device (Tracer OVO 1.2 tablet, Android ICS 4.0.3) with three physical (touchable) navigation buttons on the right side.
Using Flash CS6, Air 3.9.
I'm sure it's possible because other apps and games run in fullscreen like a charm.
Is ANY way (maybe third party apps) to get rid of that damn staus bar?

Similar Messages

  • Associate file extension with air app on Android

    Hi,
    I am trying to associate a file extension with my air app on Android. My goal is to be able to start my app by clicking on a file with a specific file type from either a file manager or mail app. I have found a solution that in theory would work in native, but does not with air somehow.
    In the .xml-file for the app, under the <android> tag I have written:
    <activity>
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
                <data android:scheme="file" />
                <data android:pathPattern=".*\\.csml" />
                <data android:host="*" />
            </intent-filter>
        </activity>
    Does anyone have an idea how this could be solved?
    Thanks in advance
    Jens

    If it works in a native app, it should also work in an AIR app in this case. Can you verify that it does work in a native app?
    See also:
    http://www.mail-archive.com/[email protected]/msg47862.html//www.mail-archive.com/[email protected]/msg47862.html
    http://stackoverflow.com/questions/1733195/android-intent-filter-for-a-particular-file-ext ension

  • Flash Builder 4.7 won't debug air app on Android devices  anymore

    Hi there,
    A strange thing happened today to my Flash Builer 4.7 installation on OS 10.8.5 : it suddenly refused installing and debugging AIR apps.
    At -the famous- 57% of compilation completion I can see the "installing app on device" message, but nothing happens then, and the one minute connection to app timeout is finally triggered.
    I had a look at other threads dealing with this problem here http://forums.adobe.com/thread/1154269 and here http://www.androidpolice.com/2013/02/12/new-android-4-2-2-feature-usb-debug-whitelist-prev ents-adb-savvy-thieves-from-stealing-your-data-in-some-situations/ and I downloaded the latets Android SDK and replaced a bunch of files into the /Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/android/bin folder but nothing worked.
    The fun side of the issue is that yesterday it worked, and this morning it did not worked anymore, but I swear I did not ugraded Android on my phone nor I upgraded AIR SDK in FLash Builder or OS X. The Android phone is the same as usual, a Nexus 4 with Android 4.3, that I upgraded 1 month ago.
    I can't debug my Android app anymore, this drives me crazy, and I spent the day trying to find a solution.
    Do you guys had a similar problem ?

    My mistake...
    There was a typo into the XML application descriptor, that prevented the app to install properly on the device.
    Precisely, it wasn't a typo but raher a malformed <intent-filter> node. I launched adb tool from the console with adb install MyApp.apk command, and I saw this : Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED] in the terminal. From here it was easy to find the culprit.
    What would be cool is to have this feature inside the Flash Builder's Console panel.

  • Example working Flex AIR app for Android?

    I'm having trouble getting even the most basic AIR app working on Android. Here is the code:
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                            xmlns:s="library://ns.adobe.com/flex/spark"
                            xmlns:mx="library://ns.adobe.com/flex/mx" xmlns:local="*"
                            width="600" height="600">
         <fx:Declarations>
             <!-- Place non-visual elements (e.g., services, value objects) here -->
         </fx:Declarations>
         <mx:Label text="Hello World"/>
    </s:WindowedApplication>
    It works fine running on  Windows in Flash Builder, obviously it's pretty simple. Here are the  commands I use to put it on a Samsung Galaxy Tab with Android 2.2.
    C:\Users\Ryan\Adobe  Flash Builder 4\Test2\bin-release>adt -package -storetype pkcs12  -keystore C:\Users\Ryan\STG-Android.pfx Test2.air Test2-app.xml  Test2.swf
    password:
    C:\Users\Ryan\Adobe Flash Builder 4\Test2\bin-release>adt -package  -target apk -storetype pkcs12 -keystore C:\Users\Ryan\STG-Android.pfx  Test2.apk Test2-app.xml Test2.swf
    password:
    test
    C:\Users\Ryan\Adobe Flash Builder 4\Test2\bin-release>adb install -r Test2.apk
    2286 KB/s (419172 bytes in 0.179s)
             pkg: /data/local/tmp/Test2.apk
    Success
    A Test2 app icon shows up on my Galaxy Tab  under Applications but when I run the app I just see a plain white  screen, I don't see the words "Hello World". Any ideas? Does anyone have  an example Flex AIR app that works on Android and can post the code so I  can try it on my Galaxy Tab? I know AIR is installed correctly on my  Galaxy because I installed an AIR app called South Park Avatar Creator  that I got from the market and it works fine.
    Thanks,
    Ryan
    P.S.  Here is the Test2-app.xml from my non-working project above in case it  helps. This is the default generated with a new Flex app in Flash  Builder 4 using the Flex 4.1.0 AIR 2.5 SDK but I uncommented the andoid  tags and set the visible tag to true.
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.5
                 The last segment of the namespace specifies the version
                 of the AIR runtime required for this application to run.
         minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                 the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
         Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
         <id>Test2</id>
        <!-- Used as the filename for the application. Required. -->
         <filename>Test2</filename>
        <!-- The name that is displayed in the AIR application installer.
         May have multiple values for each language. See samples or xsd schema file. Optional. -->
         <name>Test2</name>
         <!-- A string value of the format  <0-999>.<0-999>.<0-999> that represents application  version which can be used to check for application upgrade.
         Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
         An updated version of application must have a versionNumber value  higher than the previous version. Required for namespace >= 2.5 .  -->
         <versionNumber>1.0.0</versionNumber>
         <!-- A string value (such as "v1", "2.5", or "Alpha 1") that  represents the version of the application, as it should be shown to  users. Optional. -->
         <!-- <versionLabel></versionLabel> -->
        <!-- Description, displayed in the AIR application installer.
         May have multiple values for each language. See samples or xsd schema file. Optional. -->
         <!-- <description></description> -->
        <!-- Copyright information. Optional -->
         <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
         <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
         <initialWindow>
             <!-- The main SWF or HTML file of the application. Required. -->
             <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
             <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
             <!-- The title of the main window. Optional. -->
             <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
             <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
             <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
             <visible>true</visible>
            <!-- Whether the user can minimize the window. Optional. Default true. -->
             <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
             <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
             <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
             <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
             <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
             <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
             <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
             <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a  width/height pair in pixels, such as "1600 1200". Optional. -->
             <!-- <maxSize></maxSize> -->
         </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
         <!-- which in turn permits your application to be deployed to all -->
         <!-- devices supported by AIR. If you wish to restrict deployment -->
         <!-- (i.e., to only mobile devices) then add this element and list -->
         <!-- only the profiles which your application does support. -->
         <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
         <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
         <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
         specify the path to a PNG file included in the AIR package. Optional. -->
         <!-- <icon>
             <image16x16></image16x16>
             <image32x32></image32x32>
             <image36x36></image36x36>
             <image48x48></image48x48>
             <image72x72></image72x72>
             <image128x128></image128x128>
         </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
         of the AIR file (true), or the default AIR application installer handles the update (false).
         Optional. Default false. -->
         <!-- <customUpdateUI></customUpdateUI> -->
         <!-- Whether the application can be launched when the user clicks a link in a web browser.
         Optional. Default false. -->
         <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
         <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
             <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                 <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                 <!-- <extension></extension> -->
                 <!-- The description of the file type. Optional. -->
                 <!-- <description></description> -->
                 <!-- The MIME content type. -->
                 <!-- <contentType></contentType> -->
                 <!-- The icon to display for the file type. Optional. -->
                 <!-- <icon>
                     <image16x16></image16x16>
                     <image32x32></image32x32>
                     <image48x48></image48x48>
                     <image128x128></image128x128>
                 </icon> -->
             <!-- </fileType> -->
         <!-- </fileTypes> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
         <android>
             <manifestAdditions>
             <![CDATA[
                 <manifest android:installLocation="auto">
                     <uses-permission android:name="android.permission.INTERNET"/>
                     <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                     <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                     <uses-configuration android:reqFiveWayNav="true"/>
                     <supports-screens android:normalScreens="true"/>
                     <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                     <application android:enabled="true">
                         <activity android:excludeFromRecents="false">
                             <intent-filter>
                                 <action android:name="android.intent.action.MAIN"/>
                                 <category android:name="android.intent.category.LAUNCHER"/>
                             </intent-filter>
                         </activity>
                     </application>
                 </manifest>
             ]]>
             </manifestAdditions>
         </android>
         <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                            xmlns:s="library://ns.adobe.com/flex/spark"
                            xmlns:mx="library://ns.adobe.com/flex/mx" xmlns:local="*"
                            width="600" height="600">
         <fx:Declarations>
             <!-- Place non-visual elements (e.g., services, value objects) here -->
         </fx:Declarations>
         <mx:Label text="Hello World"/>
    </s:Application>

  • How to divide and load parts of Large Adobe AIR app for Android

    Hi!
    I want to create an app for Android but it will quite large. It will be larger than the 50MB offered by Google Play Store. This means that I need to find a way and break the app and load parts of it when I need them. Imagine it like minigames inside a bigger app.
    It is not clear to me how to achieve this since every time on AIR, I can export and APK file for a mini-game let's say. Can I later download APKs and integrate them into my main app? How would this be possible? Another question that I have is: In order for a SWF to play on my app, it needs to be built by AIR for Android?
    The best case would be to download content from In-App purchases and integrate in my app.
    But these things are not so clear.
    Thanks in advance for your help and support.

    I don't know how your application is structured, but if you can split sections off into separate SWFs(plain AS3 document) then you could host those section SWFs online and require the user to download them on first run.
    You could use the FileReference object to download the SWFs, save them to the File.applicationStorageDirectory, and then display/load them up with the Loader object when needed from the app storage directory. You would possibly need to check to see if the files are present at every boot of the app though as a user could "Clear Data" or "Clear Cache" of the app in the Settings of their device and one or both of those could/would delete the downloaded files.
    FileReference - Adobe ActionScript® 3 (AS3 ) API Reference

  • Can I run an html/javascript AIR app on Android or iOS?

    Is it possible to compile an already-existing HTML/javascript app to install/run it on any mobile OS (Android or iOS, in particular)? I haven't found anything that says it's possible, only instructions for doing it with a Flash/Flex based AIR app.
    I have a large html/javascript app, with a lot of value put into it, and my client would like to be able to package it for use on tablets. Ideally, I'd like to be able to not only have it run there, but also be able to "hide" the html/js code from prying eyes, if there's a way to do that.
    Thanks much in advance... I've done considerable research trying to get an answer to these questions.
    - Jack

    Hi Ross,
    the certificate used for APK files is a self-signed one so at this point, no need to use Google Console yet.
    See http://helpx.adobe.com/digital-publishing-suite/kb/publishing-process-android-amazon-mobil e.html (Create a certificate file using Keytool)
    Testing is only a matter of installing the APK file on the device where you should be able to test.
    The Android developer account will be useful for testing if you have in-app purchases matching 'retail' folios.

  • AIR app on Android for live chat crashes

    No matter which streaming server I use, I regularly have a crash. My scenario is:
    One side is on browser on PC, the other side is on android air app. Application is receiving a live stream and publishing a live stream at the same time, using two different Netstreams. Half of the time the application crashes. Crashes are rearly occuring during chat, but most of the time after a chat session is ended, and some time after netstreams are closed. There is no exceptions.
    If I run the same AIR application on Windows Desktop, no problem occurs.
    My application also records video and views recorded video. No problem occurs there. So, play("recorded.flv") and publish("someFLV", "record") has no problems.
    When it comes to live streaming, problem occurs.
    I use netstream.buffer = 0 for publishing live content, and netstream.buffer with its default value for playing live content.
    When chat ends, I detach camera and microphone from netstream, remove eventlisteners from netstream, remove camera from Video object, set microphone and camera to null.
    I tried closing and not closing netstreams, but nothing changed.
    I tried sound only and video only streams on both sides, but nothing changed.
    I compiled with AIR on Android 2.6 and 3.0, but nothing changed.
    I tried compiling with Flash Builder Burrito and Flash Builder 4.5, but nothing changed.
    I investigated Android adb logcats, but nothing useful is traced.
    Application just crashes without any message or warning.
    Is there a bug for playing and receiving live content at the same time on AIR on Android?

    For those who are interested in this crash, I'll give a few more experiments and hope for an answer.
    I investigated a few adb logcat deeper and noticed something about AIR runtime:
    1. The crash does not happen all time, but randomly. Followings will explain the reason.
    2. If I try sound-only streams, and if app crashes after disposing resources, logcat has messages related to Android microphone. After painful research, I found that logs mean: "someone requested microphone data, but it didn't consume microphone data fast enough."
    3. If I try video-only streams, and if app crashes after disposing resources, logcat has messages related to Android camera. After painful research, I found that logs mean: "someone requested camera data, but it didn't consume microphone data fast enough."
    So, maybe, only maybe, because AIR doesn not support multi-threading, when we dispose a microphone or a netstream, AIR stops receiving microphone data immediately, but until our calling function ends its execution, AIR does not notify Android OS about dispose. So, in Android's point of view, it sends microphone data but nobody consumes that data, thus nobody empties Android's buffer. Hence Android OS thinks that something is wrong and kills AIR application. That may explain why we get crash randomly: If Android's microphone, or camera, buffer is nearly empty when we dispose, buffer is not get filled until we fully dispose resources and everything is fine. But if the buffer is nearly full when we call dispose, buffer gets filled to its maximum until we finish our disposing and Android OS suspects about buffer and AIR app is killed with a signal 11, a segmentation fault.
    This is only a theory, and I found one evidence that supports the theory: Android developers are suggested not to use camera and microphone resources directly. Instead, they are advised to create another thread to consume camera and microphone and use that thread for their needs. That is impossible in AIR as AIR don't have multi-threading.
    Well, is there anybody now who has an idea?

  • How to set an AIR app on Android to handle filetype

    I've been trying to make my app as default handler of a file type on Android. I have the as3 code to open the file (via InvokeEvent.INVOKE) but I can't seem to be able to register the app as a handler.
    I added this code in the app XML:
      <android>
        <manifestAdditions>
          <![CDATA[
            <manifest android:installLocation="auto">
              <supports-screens android:smallScreens="false" android:normalScreens="false" android:largeScreens="true" android:xlargeScreens="true" />
              <uses-permission android:name="android.permission.INTERNET"/>
              <uses-permission android:name="android.permission.WAKE_LOCK"/>
              <uses-permission android:name="android.permission.DISABLE_KEYGUARD"/>
              <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
            </manifest>
            <intent-filter>
              <action android:name="android.intent.action.VIEW" />
              <category android:name="android.intent.category.DEFAULT" />
              <category android:name="android.intent.category.BROWSABLE" />
              <data
                android:host=""
                android:mimeType="*/*"
                android:pathPattern=".*\\.pgn"
                android:scheme="file"
              ></data>
            </intent-filter>
        ]]>
        </manifestAdditions>
      </android>
    I also tried with
    <data android:mimeType="*/*" />
    <data android:pathPattern="*.*\\.pgn" />
    What am I doing wrong?

    You're going about it the wrong way. Native development allows you to find package names of installed apps and request they start using the Intent system with startActivity (once you verify the app exists), see here:
    http://developer.android.com/training/basics/intents/sending.html
    However that's native. You'll either need to find an existing native extension or create one yourself.
    That aside facebook may supply you with the proper scheme to call to launch the app in which case it would probably prompt you to run facebook in the app or in a browser. More info on defining those schemes here with code:
    http://www.riaspace.com/2011/08/defining-custom-url-schemes-for-your-air-mobile-applicatio ns/

  • Air app for android NOT prompting user to download runtime

    My app tested fine on a DROID ii but when I had a friend download the app on his DROID x the app showed an error when run. It did not prompt the user to download the runtime. Once we did download the runtime, the app worked fine.
    I went through much agony renaming my package name to remove the "air." prefix for reasons that are not important here.  Could this cause a phone not to recognize that the air runtime is needed? I cannot find any documents that say that the prefix does more than help adobe keep track of air apps.
    Here is my app in case it helps:
    https://play.google.com/store/apps/details?id=com.dktimertrial&feature=more_from_developer #?t=W251bGwsMSwyLDEwMiwiY29tLmRrdGltZXJ0cmlhbCJd
    Thanks.

    Have you heard of the expression, "Tampering with this product will void the warranty"?  :-)
    There's no guarantee that the process you went through to remove the air. prefix didn't break the part of the app that automatically triggers the AIR runtime request. You're basically doing things that aren't supported, so I doubt you'd find an answer to that question from Adobe.
    Personally, I would look at using the captive runtime feature of AIR 3.1+ and then you won't have to worry about the user needing to download the runtime separately. If it's really that important for you to remove the air. prefix, captive runtime should fix this problem.
    iBrent

  • Air App for Android - error 301: application descriptor missing

    Greetings!
    I've been building in Flash for a while but am brand new to mobile development.  I'm currently trying to create my first Android app, a very basic game called "302 Saves The Galaxy". I don't intend to sell the game.  I'm really just trying to learn my way through the publication process for future projects.
    I've been able to get to the very last step in creating the apk file and I'm getting this error from the command-line process -
    "Error 301: Application descriptor missing/cannot be opened"
    Here's a screen shot of the command line window -
    Here are a few other details about my process -
    In Flash, I selected to publish to Air 2.0 because that's the only option I had (ie, no Air 2.5 option)
    I've triple-checked and all spellings seem to be correct in my command-line syntax
    I'm sure I'm missing something obvoius here.  Any suggestions?
    Thanks in advance!
    Joel

    Hi, Pahup!
    Thank you SO MUCH for that tip!  That solved the problem!  Like I said, I knew it must be something pitifully easy that I was overlooking. 
    Anyway, I really appreciate your taking the time to respond.
    Joel

  • Use Flash Builder to Develop Adobe AIR Apps for Android | Flash Platform in Action | Adobe TV

    Former Adobe Technical Evangelist Ted Patrick uses Flash Builder to develop and deploy an Adobe AIR application to his Android-powered smartphone.
    http://adobe.ly/wif9U5

    autoplay can cause a tremendous amount of problems for site visitors. is it possible that adobe might turn off autoplay?

  • Unable to access SD Card / External storage from Flash builder / air app in android KitKat.

    Hi
    We are using Adobe Flash builder 4.7 to create an Android app for Andoid Kit kat platform.
    getDirectoryListing() function returns only one folder of SD card i.e. LOST.DIR. It does not return any other directory or file of the SD card.
    Regards
    Sachin

    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                            xmlns:s="library://ns.adobe.com/flex/spark"
                            xmlns:mx="library://ns.adobe.com/flex/mx" xmlns:local="*"
                            width="600" height="600">
         <fx:Declarations>
             <!-- Place non-visual elements (e.g., services, value objects) here -->
         </fx:Declarations>
         <mx:Label text="Hello World"/>
    </s:Application>

  • How to compile the AIR app to android emulator

    How to compile the AIR application to run on emulator ?
    May be use the 'adb' command line ?

    -target The type of package to create. The supported package types are:
    air — an AIR package. “air” is the default value and the -target flag does not need to be specified when creating AIR or AIRI files.
    airn — a native application package for devices in the extended television profile.
    native — a native desktop installer. The type of file produced is the native installation format of the operating system on which the command is run:
    EXE — Windows
    DMG — Mac
    DEB — Ubuntu Linux
    RPM — Fedora or OpenSuse Linux
    apk — an Android package. A package produced with this target can only be installed on an Android device, not an emulator.
    apk-debug — an Android package with extra debugging information. (The SWF files in the application must also be compiled with debugging support.)
    apk-emulator — an Android package for use on an emulator without debugging support. (Use the apk-debug target to permit debugging on both emulators and devices.)
    Use the value as per your need. The you can use adb to push the packaged apk to your emulator.

  • Is Stage3d available for an Air app on Android?

    hello guys~ i have seen some cool videos about Molehill demo on android device ,
    but when i start to learn stage3d and adobe air , i hear someone say stage3d is not available for mobile at this moment (only work on desktop).
    i read adobe air3.0 / air3.1 realease notes and stage3d documents but no information about whether the stage3d hardware accelerated rendering is avaiable right now on android or not .
    could any one tell me ? thanks!!

    As you know Stage3D uses the GPU of the underlying machine. It is therefore a seriously low-level piece of middleware, full of custom assembly language code for every single brand of GPU, of which there are a few in the mobile space.
    Perhaps you consider AIR something other than middleware, that is the best i could do. Anyway Adobe staff are busting their rears making it, but it is not yet released. No one will give a date because until it passes through Quality Assurance it cannot ship. Adobe is loathe to release a buggy version because they will get pounded for it. I have no relationship with Adobe, nor any secret source, but I would venture that it will be June 2012 before we see Android / iOS stage3d availability at the earliest.
    should be great, we haven't seen that many good 3D middleware solutions, and the adobe one looks promising.

  • Need to 'launch' AIR app from SD card on Samsung Galaxy TABLET...

    April/28/11 at 3pm ET
    Hi to the group...
    Not 100% sure if this is proper forum to ask this, if anyone knows a better one please point me to it via ([email protected])
    Ok. Trying to see if my working .AIR app will run on my pals Samsung Tablet (before I buy one for myself)...
    Dropped the 'AIR' file onto the SD card (I can see it (the AIR file, size correct) via the fileBrowser app but clicking it does nothing.
    Of note AIR is installed in background of the device and it is running.
    Cant see/find an 'Adobe AIR launcher?' icon' anywhere (only see Adobe PDF browser).
    In all my web searching I see 10000 developer related tutorials re: creating an APK file / converting to APK file using Flash Professional ect.  Not what I am looking for...
    I think I am missing something very basic here is there a launcher for AIR apps on Android?
    TIA //GregH

    Hello
    Thank you for your post.
    You cannot throw directly from your external device, however you can once that file is transferred to internal memory.
    please review this guide for instructions on how.
    How to throw (send) music, video or picture files to a DNLA compatible device.
    https://us.en.kb.sony.com/app/answers/detail/a_id/34563/c/65,66/kw/34563

Maybe you are looking for

  • Acrobat 8 Pro keeps giving me a "...has stopped working" popup, but....

    it's still running and working fine. And even when it's not running, nor have I used it in a while, out of nowhere I'll get a popup saying "Adobe Acrobat 8 has stopped working". Intersting. How can it stop working if it isn't running? And when it's o

  • Several issues with Logic 10.1.1

    Some problems I've encountered in LPX 10.1.1. 1. Recalling Aux Channels with saved Channel Strips. 2. Using an external controller assignments to control smart controls in Track Stacks. 3. Setting project tempo using Tap Tempo. 4. Track Automation ti

  • BPEL - not generating correct SOAP packet for complex types

    Hi, Below is a snippet from wsdl, correct SOAP request and reply packet (generated using a SOAP test tool) and finally BPEL generated SOAP request and error response (captured using TCP packet monitor) The problem is with element 'XActivationPackageA

  • Urgent ! delivery items and its batch split items

    Exports:     How to find relationship between delivery items and its batch split items. Thanks alot.

  • Why is my battery health decreasing so rapidly????

    I bought a new one like 3 weeks ago .. it has 10 cycles and the battery health has decreased from 98% to 95% in these last few days .. I usually have it connected to Ac power and discharge it like every 4 days.. thats the 10 cycles .. why would the h