• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

AIR 2.5 app won't run on Droid 2

Guest
Dec 11, 2010 Dec 11, 2010

Copy link to clipboard

Copied

I have two problems and any help would be appreciated!

1) Using Flash Builder Burrito Preview Version when I try to debug it won't publish the apk to my Droid 2, it just hangs at 6% and says "Launching".

I have the latest Google USB Drivers, and I can install the apk to the device manually using "adb install xyz.apk". It has AIR 2.5 installed. I can also see the device when I run "adb devices".

2) When I try to run my app on the Droid 2 it fails and simply doesn't launch. Below is my logcat dump.

Note, I have run this same app on an EVO 4 just fine, and Flash Builder Burrito copied it over to the EVO just fine.

Anyone know what gives with Droid 2?

12-11 17:44:47.598  1235  1374 I ActivityManager: Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=air.Mobile1.debug/.AppEntry }
12-11 17:44:47.629  1857  1857 W WidgetAidService: BroadcastReceiver onReceive called
12-11 17:44:47.637  1857  1857 D WidgetAidService: ACTION_HOME_SCREEN_CHANGED - -1
12-11 17:44:47.637  1235  1436 I ActivityManager: Start proc air.Mobile1.debug for activity air.Mobile1.debug/.AppEntry: pid=5513 uid=10103 gids={}
12-11 17:44:47.676  1857  1857 D WidgetAidService: HomeScreen has lost focus, store the previous state and move to pause
12-11 17:44:47.707  1857  1857 D WidgetAidService: Ignoring the HOME_SCREEN_CHANGED notification as the player is either in paused/playing state
12-11 17:44:47.840  5513  5513 I Process : Sending signal. PID: 5513 SIG: 9
12-11 17:44:47.856  1235  1431 I ActivityManager: Process air.Mobile1.debug (pid 5513) has died.
12-11 17:44:47.863  1235  1429 I WindowManager: WIN DEATH: Window{45b745e8 air.Mobile1.debug/air.Mobile1.debug.AppEntry paused=false}
12-11 17:44:47.879  1235  1431 I UsageStats: Unexpected resume of com.motorola.blur.home while already resumed in air.Mobile1.debug
12-11 17:44:47.957  1857  1857 W WidgetAidService: BroadcastReceiver onReceive called
12-11 17:44:47.957  1857  1857 D WidgetAidService: ACTION_HOME_SCREEN_CHANGED - 3
12-11 17:44:47.973  1235  1349 W InputManagerService: Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@45a62e10 (uid=10005 pid=1347)
12-11 17:44:47.973  1235  1427 W InputManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@45b6a9a8

Views

1.1K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Dec 11, 2010 Dec 11, 2010

Copy link to clipboard

Copied

Okay, I updated my device to AIR 2.5.1 and presto it solved both of my problems. If you have a similar problem, download AIR 2.5.1 from Android Market.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 25, 2010 Dec 25, 2010

Copy link to clipboard

Copied

LATEST

Just a quick tip that is semi-related...

A quick way to get apk files onto your device is to use Dropbox.  I have Flash Builder set to create the apk file directly in a subfolder in Dropbox.  Then I open it on the device and it starts installing!

NOTE: You have to have your device setup to install non-market apps to do this... Menu > Settings > Applications > Check "Unknown Sources"

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines