App Cannot Launch on Samsung Galaxy Tab SII

I've worked on many projects with no problem. But in the current project that I tested on a Samsung Galaxy Tab (GT-P7300), the application cannot launch. The screen will start flashing when I run it and then go home immediately (no force message, start screen pops up immediately). LogCat shows these errors:

03-14 16:18:41.060: E/AndroidRuntime(4144): Set to default setting_6 : region=-Duser.region=US propRegn=US
03-14 16:18:41.070: E/AndroidRuntime(4144): /system/csc/feature.xml ==> cannot open file
03-14 16:18:41.340: E/AndroidRuntime(4154): Set to default setting_6 : region=-Duser.region=US propRegn=US
03-14 16:18:41.360: E/AndroidRuntime(4154): /system/csc/feature.xml ==> cannot open file

      

The consumer input channel is closed or an error has occurred. The channel is irreparably broken and will be disposed of!

Another post from LogCat:

03-14 15:16:40.370: E/TODmobile(650): onReceive action=sec.android.intent.action.HOME_RESUME
03-14 15:16:40.380: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:40.380: E/DigitalClockWidget(650): updateWidgets
03-14 15:16:40.410: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:40.450: E/DigitalClockWidget(650): onReceive action=sec.android.intent.action.HOME_RESUME
03-14 15:16:40.450: E/TODmobile(650): onStartCommand
03-14 15:16:40.450: E/TODmobile(650): onReceive action=com.sec.android.widgetapp.DigitalClock_Start
03-14 15:16:40.460: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:40.460: E/DigitalClockWidget(650): updateWidgets
03-14 15:16:40.510: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:40.980: E/TODmobile(650): onReceive action=sec.android.intent.action.HOME_RESUME
03-14 15:16:41.010: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:41.010: E/DigitalClockWidget(650): updateWidgets
03-14 15:16:41.010: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:41.030: E/DigitalClockWidget(650): onReceive action=sec.android.intent.action.HOME_RESUME
03-14 15:16:41.030: E/TODmobile(650): onStartCommand
03-14 15:16:41.040: E/TODmobile(650): onReceive action=com.sec.android.widgetapp.DigitalClock_Start
03-14 15:16:41.050: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:41.060: E/DigitalClockWidget(650): updateWidgets
03-14 15:16:41.060: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:41.410: E/DigitalClockWidget(650): onReceive action=com.sec.android.widgetapp.APPWIDGET_RESIZE
03-14 15:16:41.410: E/TODmobile(650): onStartCommand
03-14 15:16:41.420: E/TODmobile(650): onReceive action=com.sec.android.widgetapp.DigitalClock_Start
03-14 15:16:41.420: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:41.420: E/DigitalClockWidget(650): updateWidgets
03-14 15:16:41.420: E/TODmobile(650): hour : 15    minute : 16
03-14 15:16:41.570: E/RemoteViews(362): Cannot setOnClickPendingIntent for collection item (id: 2131755055)
03-14 15:16:41.570: E/RemoteViews(362): Cannot setOnClickPendingIntent for collection item (id: 2131755055)

      

The program works well on LG GT540 and Samsung Ace.

What is causing this problem? I searched for the error message and found many people came across it but there is no clear solution.

EDIT: More info, I tried on Galaxy Tab (GT-P1000, running Android 2.3.3), it works too. And when I try it on Android SDK Emulator with 3.0 device, the program also blinks and then disappears. So only Android 3.0 (maybe 4.0 also) throws this problem.

+3


source to share


1 answer


How a. ch said I have also seen this with insufficient memory issues and also packages that were left with the same package id and even if the graphics need to be resized. What was said:

If you support multiple screens , I would make sure there are graphics in each MDPI, HDPI, XHDPI respectively and that they are optimized and set to the appropriate DPI . This should ensure that all devices and API levels play well.



Even if that isn't the root of your problem, it's good to keep an eye on efficiency and reliability.

+1


source







All Articles