Skip to main content
Participant
October 7, 2010
Question

Android air application crashes while starting it

  • October 7, 2010
  • 2 replies
  • 2038 views

Hi All,

We are  developing an air application for android.

After packaging, running the above application in android emmulator, we are getting below error. Nothing come on screen. Please help.

10-07 15:44:16.800: INFO/ActivityManager(71): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=app.AndersonView_Sulpe/.AppEntry }

10-07 15:44:17.270: INFO/ActivityManager(71): Start proc app.AndersonView_Sulpe for activity app.AndersonView_Sulpe/.AppEntry: pid=292 uid=10032 gids={}

10-07 15:44:18.360: INFO/ARMAssembler(71): generated scanline__00000077:03545404_00000004_00000000 [ 47 ipp] (67 ins) at [0x3067f8:0x306904] in 1286854 ns

10-07 15:44:18.770: ERROR/AppEntry(292): error invoking method onWindowAttributesChanged exception = java.lang.NullPointerException

10-07 15:44:18.790: ERROR/AppEntry(292): error invoking method onApplyThemeResource exception = java.lang.NullPointerException

10-07 15:44:18.800: INFO/StartupTime1(292): :1286446458802

10-07 15:44:18.980: DEBUG/dalvikvm(292): Trying to load lib /data/data/com.adobe.air/lib/libCore.so 0x4a216610

10-07 15:44:19.310: DEBUG/dalvikvm(292): Added shared lib /data/data/com.adobe.air/lib/libCore.so 0x4a216610

10-07 15:44:19.659: DEBUG/qemud(38): fdhandler_accept_event: accepting on fd 10

10-07 15:44:19.659: DEBUG/qemud(38): created client 0x150b8 listening on fd 15

10-07 15:44:19.690: DEBUG/qemud(38): client_fd_receive: attempting registration for service 'sensors'

10-07 15:44:19.690: DEBUG/qemud(38): client_fd_receive:    -> received channel id 8

10-07 15:44:19.711: DEBUG/qemud(38): client_registration: registration succeeded for client 8

10-07 15:44:19.769: DEBUG/qemud(38): fdhandler_event: disconnect on fd 15

10-07 15:44:20.539: DEBUG/ReleaseLogging:(292): 0

10-07 15:44:24.450: DEBUG/StartupTime2(292): :1286446463905

10-07 15:44:26.460: INFO/ActivityManager(71): Displayed activity app.AndersonView_Sulpe/.AppEntry: 9319 ms (total 9319 ms)

10-07 15:44:26.890: WARN/ActivityManager(71): Launch timeout has expired, giving up wake lock!

10-07 15:44:27.159: DEBUG/dalvikvm(292): GC_EXTERNAL_ALLOC freed 3901 objects / 279536 bytes in 200ms

10-07 15:44:28.060: WARN/ActivityManager(71): Activity idle timeout for HistoryRecord{4a30ce90 app.AndersonView_Sulpe/.AppEntry}

10-07 15:44:31.260: DEBUG/SntpClient(71): request time failed: java.net.SocketException: Address family not supported by protocol

10-07 15:44:36.010: DEBUG/dalvikvm(130): GC_EXPLICIT freed 2181 objects / 141584 bytes in 2934ms

Thanks and Regards

Rajul

This topic has been closed for replies.

2 replies

Participant
August 27, 2012

recently i got the similar issue and share with you. anyway, i use FB 4.6. the version for air runtime.apk is 3.1.0.448.

make sure you install runtime.apk for emulator and generate your app by adt -package apk-emulator ...

Participant
October 12, 2010

"10-07 15:44:26.890: WARN/ActivityManager(71): Launch timeout has expired, giving up wake lock!"

Ive seen that error before. :-) It looks like it is bombing out trying to initialize the "WAKE_LOCK" permission. Make sure that you have all the permissions included in your AIR app. If you download the latest Extension for Flash CS5, the App & Installer settings will have a new "Permissions" tab and then you can select the permissions that you would like to include. In your case "WAKE_LOCK". Then publish

In previous CS5 extensions you would have to open up the release notes and then copy and paste, then edit the permissions in your app.xml file. This makes life much easier.

Hope this helps-