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

        

        
        
        
 (adsbygoogle = window.adsbygoogle || []).push({});
 
        

    
```


>  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)

        

        
        
        
 (adsbygoogle = window.adsbygoogle || []).push({});
 
        

    
```

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.
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](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) , I would make sure there are graphics in each MDPI, HDPI, XHDPI respectively and that they are [optimized](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) and set to the [appropriate DPI](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) . This should ensure that all devices and API levels play well.



  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

Even if that isn't the root of your problem, it's good to keep an eye on efficiency and reliability.
Well just had TAC look into it. They restarted the management plane which fixed the issue.

The reason we believe was due to insufficient resource in the management plane at the time of the update.

Thanks Sandeep for your help.




[View solution in original post](/t5/general-topics/app-version-mismatch/m-p/45216#M33220) have you tried entering safe mode? Let us know if it is the same.



It could be corrupt files and not startup programs. please delete the app and reinstall! it should work try clearing cache in roon settings on the device. hey [@jsteb](/u/jsteb), i was struggling with this and i figured what is going on. the problem is with the action button. if you try with a regular button it will work. i think that should be clarified in the tutorial hi,

do you have joy package installed with all necessary packages/dependencies ?

try to search for joy\_node or run joy package examples to find out what is going wrong. timgoos,there seem to be a few threads about this issue. most people, at least those who bothered to respond back to this forum, seem to indicate that turning off the "lock screen controls" resolved the issue for them. my guess is that there's a bug somewhere in the app, and they haven't either figured it out, or looked at it. i'd suggest that you go to settings -> sonos -> lock screen controls and make sure it isn't green (on). it's inconvenient, if you're accustomed to using the lock screen like i am, but then again if it doesn't kill the battery, that's a plus.and if you'd be so kind as to come back and post here to let us know if it works for you, it might help the next person who may be in your shoes.thanks! Found it…Check out this link [Error 26630.](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk106641)



Basically user does not have permissions to run the install. right click on the gtaiv executable (not the launcher) and open the properties window. then click the details tab and check it yourself. the problem is solved when i run this command:

cd /var/discourse

./launcher rebuild app