AnsweredAssumed Answered

A application startup time is very long!!

Question asked by wan shaowu on May 6, 2018
Latest reply on May 7, 2018 by igorpadykov

The application (see Appendix procedure)startup time is very long(about 18 seconds)  at imx6Q android4.4.2 .  

And the boot time is normal(about 4 seconds)  in other versions of Android system, such as android4.2.2,android5.1 and android6.0.

So we think this application is related to imx6q android4.4.2 Kikt.

Here is a logcat fragment that starts the application under android4.4.2:

 

.....

05-03 11:01:27.760 D/dalvikvm( 3196): GC_FOR_ALLOC freed <1K, 7% free 6717K/7172K, paused 18ms, total 18ms
05-03 11:01:27.770 I/dalvikvm-heap( 3196): Grow heap (frag case) to 10.345MB for 3900472-byte allocation
05-03 11:01:27.790 D/dalvikvm( 3196): GC_FOR_ALLOC freed <1K, 5% free 10526K/10984K, paused 20ms, total 20ms
05-03 11:01:27.810 D/dalvikvm( 3196): GC_CONCURRENT freed <1K, 5% free 10526K/10984K, paused 2ms+2ms, total 18ms
05-03 11:01:27.930 D/dalvikvm( 3196): GC_FOR_ALLOC freed <1K, 5% free 10527K/10984K, paused 13ms, total 13ms
05-03 11:01:27.940 I/dalvikvm-heap( 3196): Grow heap (frag case) to 14.145MB for 3984016-byte allocation
05-03 11:01:27.970 D/dalvikvm( 3196): GC_FOR_ALLOC freed <1K, 4% free 14418K/14876K, paused 24ms, total 24ms
05-03 11:01:27.980 D/dalvikvm( 3196): GC_CONCURRENT freed 3825K, 29% free 10593K/14876K, paused 1ms+1ms, total 17ms
05-03 11:01:27.980 D/dalvikvm( 3196): WAIT_FOR_CONCURRENT_GC blocked 6ms
05-03 11:01:27.990 I/dalvikvm-heap( 3196): Grow heap (frag case) to 14.195MB for 3967672-byte allocation
05-03 11:01:28.010 D/dalvikvm( 3196): GC_CONCURRENT freed <1K, 23% free 14468K/18752K, paused 2ms+2ms, total 16ms
05-03 11:01:28.110 W/FlurryAgent( 3196): Flurry session created for context:com.mm.android.direct.gdmsspad.SplashActivity@41b310b8
05-03 11:01:28.120 W/FlurryAgent( 3196): Flurry session started for context:com.mm.android.direct.gdmsspad.SplashActivity@41b310b8
 
05-03 11:01:37.250 W/ActivityManager( 2794): Launch timeout has expired, giving up wake lock!
05-03 11:01:37.250 E/WindowManager( 2794): Starting window AppWindowToken{41db6388 token=Token{41d5b158 ActivityRecord{41dc8108 u0 com.mm.androt
 
05-03 11:01:43.430 I/ActivityManager( 2794): START u0 {cmp=com.mm.android.direct.gdmsspad/.MainActivity} from pid 3196
05-03 11:01:43.520 D/dalvikvm( 2794): GC_FOR_ALLOC freed 133K, 6% free 5743K/6064K, paused 38ms, total 38ms
05-03 11:01:43.980 D/dalvikvm( 3223): Late-enabling CheckJNI
05-03 11:01:44.090 D/ExternalStorage( 3239): After updating volumes, found 2 active roots
05-03 11:01:44.090 D/ExternalStorage( 3239): After updating volumes, found 2 active roots
05-03 11:01:44.090 D/MediaScannerReceiver( 2899): action: android.intent.action.MEDIA_MOUNTED path: /mnt/media_rw/udisk
05-03 11:01:44.190 W/FlurryAgent( 3196): Flurry session started for context:com.mm.android.direct.gdmsspad.MainActivity@41b4d050

....

 

Please note that:

 

05-03 11:01:28.120 W/FlurryAgent( 3196): Flurry session started for context:com.mm.android.direct.gdmsspad.SplashActivity@41b310b8
05-03 11:01:37.250 W/ActivityManager( 2794): Launch timeout has expired, giving up wake lock!
05-03 11:01:37.250 E/WindowManager( 2794): Starting window AppWindowToken{41db6388 token=Token{41d5b158 ActivityRecord{41dc8108 u0 com.mm.androt
05-03 11:01:43.430 I/ActivityManager( 2794): START u0 {cmp=com.mm.android.direct.gdmsspad/.MainActivity} from pid 3196

 

In other versions of the system will not happen such as "Launch timeout has expired, giving up wake lock! " and "Starting window AppWindowToken"

The 'com.mm.android.direct.gdmsspad.SplashActivity" ,It takes too much time to start!!

But the application can not be modified, and the system can only be modified

 

So please help me!

TKS!

Attachments

Outcomes