Skip to main content

BroadcastReceiver not working on Android 3.0



I have a plugin framework which uses broadcast intents for communication between main application and plugins. On start main app sends a broadcast intent







sendBroadcast(new Intent("com.mypackage.myapp.custom.intent.action.ADDON_REQ"));







Each plugin app has a broadcast receiver registered in its manifest file.







<receiver

android:name="IncomingReceiver"

android:enabled="true">

<intent-filter>

<action android:name="com.mypackage.myapp.custom.intent.action.ADDON_REQ" >

</action>

</intent-filter>

</receiver>







Plugin application does not have any activities defined. This framework works fine on all Android versions lower that 3.0. Starting from Honeycomb the broadcast receiver in plugin is never called. I could not fix this until I added a main activity in the plugin app. With the activity defined in manifest existing broadcast receiver started to receive broadcast messages. What is the possible reason for such behavior? Is there any way to fix this without adding activity?





Thank you


Comments

  1. From honeycomb onward you need to specify a flag to start the receiving app if it's not already running: Intent.FLAG_INCLUDE_STOPPED_PACKAGES.

    Intent intent = new Intent("com.mypackage.myapp.custom.intent.action.ADDON_REQ");
    intent.setFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
    sendBroadcast(intent);

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex