Skip to main content
appandrew
Inspiring
August 16, 2011
Question

Sound runs wild with AIR 2.7.1 for Android

  • August 16, 2011
  • 2 replies
  • 1190 views

My AIR for Android apps worked just fine with AIR 2.7 runtime on a samsung galaxy.

The app uses sounds on timelines.

After 2.7.1 the apps still work fine when compiled in the Flash Pro CS5.5 IDE, and still work fine if exported to iOS.

But on Android-devices after a short while all the sounds in a displayed movieclip are played over and over...

I didn't know that sound relevant issues were changed from 2.7 to 2.7.1.1961.

Anybody has similar problems?

This topic has been closed for replies.

2 replies

Cheezia
Participant
August 18, 2011

Hi.

I just tested Cheezia with the following:

- LG Optimus 2X

- Adobe Air, version 2.7.1.1961

- Cheezia, version 1.0.2

Everything works just like they should. No crashing, sound problems etc.

appandrew
appandrewAuthor
Inspiring
August 18, 2011

Did you use the timeline and sounds in nested movieclips?

Because the problem seems only to manifest if timeline sounds are used - our own sounds loaded and played via actionscript are fine.

Cheezia
Participant
August 18, 2011

No, all our sound FX and music are played using only Actionscript.

Known Participant
August 17, 2011

Yes, we just experienced the exact same symptoms. Timeline sounds, in nested movieclips, that used to play just fine are now running rampant. It sounds like the clip is looping, except that we don't actually see the clip animations happening.

AIR 3.0 beta also does this, even when exported to iOS in my case.

appandrew
appandrewAuthor
Inspiring
August 18, 2011

Exactly. And this is really bad for apps already in the Android Market - if users update to 2.7.1 suddenly the formerly perfectly functioning apps have this problems.

I tested this on the Samsung Galaxy Tab GT-P1000.

On which device/s did you encounter this problem?

And do you have a small example or testcase you can e.g. upload to the adobe bug-database?

Our project is kind of big (the iOS part works perfect, thank you Adobe, great tool!) and I don't have the time right now to code a testcase - but if you don't have this maybe I can do it beginning of september...

This bug must be resolved, think of all the poor support people which will have to answer questions like "My android app behaves kind of strange...".

And my CEO is already dis-app-ointed (sorry for that, I'm a German trying to make a pun, yes) that I now can't upload our apps to the Android Market.