Skip to main content
A
Anonymous
January 3, 2012
Answered

Kindle Fire and Adobe Air plug in + Air 2.7 + gpu + landscape + full screen

  • January 3, 2012
  • 22 replies
  • 9839 views

Alright I got a couple of issues here.

First I was on air 2.7 trying to convert an app that is designed to run in gpu mode, in landscape orientation, and full screen, well this is a known bug on 2.7 and the work arounds I found did not solve my problems or I was not clear on implementing them.

Then I figured I go 3.1, surely that issue is fixed by now, run the app on my Kindle Fire and it tells me my air is out of date so it prompts me to go to the Amazon app store for an update except when I do it just takes me to the free app of the day page and I can't manually find the air app through the built in amazon app store, I see it on the web version but cannot download it, and if I am having this problem all the users will too so some solution like getting it off the android market and putting on the fire manually is useless.

It seems that there is no plug in available on the amazon app store that will allow the fire to run applications built in 3.1, is this true? I've seen a few posts regarding this. And if true, why and when will this be fixed? I wasted a day with this problem when I could have been doing some design.

Any ideas or suggestions are welcome.

This topic has been closed for replies.
Correct answer

Alright I just solved my own problem, as always thanks for Colin for all the ideas and suggestions also this post got me thinking along the right lines http://forums.adobe.com/message/3798614#3798614. Funny enough I am the first poster on that post saying I will have this problem in the future and I did, foresight is 20/20 with me and these apps.

Anyhow when I would launch in Landscape + GPU + Full Screen the elements would come up all screwed up if the app is opened from the Kindle home screen being oriented in Landscape, this problem did not exist if launched from Kindle home screen being in Portrait, but unacceptable non the less. However after moving to the next frame everything was fixed including the proper detection of the screen size. So since going from frame 1 to frame 2 fixed the issue I thought what if I added a blank frame 1 and then auto skip to frame 2 (truly frame 1 as far as the user is concerned)

The solution is to add a simple delay and then skip to the next frame. This fixes the orientation issue and the not knowing the right screen dimensions issue.

Here is the code below, simply add it to the first blank frame. So far 100% problems solved, app ready for release.

stop();

var delayFunctionActive:Boolean = true;

setInterval(delayBeforeProperLaunch,100);

function delayBeforeProperLaunch()

{

    if (delayFunctionActive == true)

    {

        gotoAndStop(2);

    }

    delayFunctionActive = false;

}

22 replies

A
Anonymous
February 6, 2012

So is it safe to say that Captive Runtime with KF and NOOK is still a valid path to take when trying to put out a 3.1 or 3.2 app on devices that have air 2.6 or 2.7 pre-installed on them?

Colin Holgate
Colin Holgate
Inspiring
February 6, 2012

Yes. I heard from someone who has a captive runtime 3.1 app in the Nook store.

A
Anonymous
Correct answer
January 10, 2012

Alright I just solved my own problem, as always thanks for Colin for all the ideas and suggestions also this post got me thinking along the right lines http://forums.adobe.com/message/3798614#3798614. Funny enough I am the first poster on that post saying I will have this problem in the future and I did, foresight is 20/20 with me and these apps.

Anyhow when I would launch in Landscape + GPU + Full Screen the elements would come up all screwed up if the app is opened from the Kindle home screen being oriented in Landscape, this problem did not exist if launched from Kindle home screen being in Portrait, but unacceptable non the less. However after moving to the next frame everything was fixed including the proper detection of the screen size. So since going from frame 1 to frame 2 fixed the issue I thought what if I added a blank frame 1 and then auto skip to frame 2 (truly frame 1 as far as the user is concerned)

The solution is to add a simple delay and then skip to the next frame. This fixes the orientation issue and the not knowing the right screen dimensions issue.

Here is the code below, simply add it to the first blank frame. So far 100% problems solved, app ready for release.

stop();

var delayFunctionActive:Boolean = true;

setInterval(delayBeforeProperLaunch,100);

function delayBeforeProperLaunch()

{

    if (delayFunctionActive == true)

    {

        gotoAndStop(2);

    }

    delayFunctionActive = false;

}

Colin Holgate
Colin Holgate
Inspiring
January 3, 2012

The only option at the moment seems to be to make the app have captive runtime. AIR 3.1 captive runtime apps work fine on the Kindle Fire.

A
Anonymous
January 3, 2012

HI Colin always look forward to your input. Please explain how I would go about that? I have heard that term many times but never really understood its meaning and how does it apply to Flash CS 5.5?

Colin Holgate
Colin Holgate
Inspiring
January 3, 2012

My lawyer tells me that I can't say how I managed to make captive runtime apps! As far as how anyone else might do it, you would want to make a normal app and then use command line instructions to make it be captive:

This might be a good starting point:

http://stackoverflow.com/questions/8657002/adobe-air-captive-runtime

Firefly Community Gallery
Adobe Firefly

Remix with Firefly Community Gallery

Thousands of free creations to fall in love with and remix in Firefly.

Explore now
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices