BroadcastReceiver dilemma

by Klaus Kartou » Fri, 23 Apr 2010 15:26:18 GMT


Sponsored Links
 Hi,

I recently added functionality to my app that does a simple state check on a
boolean when the connectivity state changes.
In order to do this i register a broadcast receiver that is invoked as soon
as the phones connectivity state changes.
This is all fine and works just as intended. However, a side effect of this
is that the application context is launched every time there is a change in
the connection. As a developer I know that this is ok, because the system
can just kill the context whenever it wants. But users that use any kind of
app-killer sees that the app is regularly reoccurring on the list of running
app, and therefore thinks that the app does unnecessary background work and
takes up resources.
So how do i 'solve' this 'issue'. I cant expect the users to understand the
underlying functionality of the OS...and people are uninstalling the app
because they dont like that it is reoccuring on the app-killer list...

Any thoughts? :)

Cheers

--



BroadcastReceiver dilemma

by Kumar Bibek » Fri, 23 Apr 2010 15:35:42 GMT


 Well, it's a difficult and funny situation. I will provide a funny
solution as well.

When your receiver is waking up, hunt down for the App-Killer app and
kill it. :) There's always a compromise that has to be made in such
cases. You cannot really do anything. Maybe, your receiver needs to
wake up less frequently to get away from the Killer program.

Thanks and Regards,
Kumar Bibek

But, yes, this is kind of irritating.



>


Sponsored Links


Other Threads

1. Just wondering that can I use C2DM service without uploading App to Android Market?

In case of using C2DM service, it is necessary to uploading App to
Android Market?
Is it impossible that I upload App using C2DM service to another
market? (not Android Market)

-- 

2. java.lang.ExceptionInInitializerError while loading a provider from an external .jar file

Hi,

I added an external .jar file to my android application through
eclipse. However, when I run my application in android I get
java.lang.ExceptionInInitializerError exception while loading a
provider for java.security. This provider is taken from RSA share .jar
package and I load it as follows:

Provider jsafeProvider = new com.rsa.jsafe.provider.JsafeJCE() ; //
the exception from this line.
Security.addProvider( jsafeProvider ) ;

Is there anything extra that needs to be done to load external .jar
file before running it on android phone or does eclipse do everything
automatically? Any idea how I can fix this exception?

thank you

-- 

3. Native VPN client

4. There is new issue being introduced in Froyo of search dialog after its window type has been changed from "TYPE_SEARCH_BAR" in Eclair to "TYPE_APPLICATION"

5. Opinions wanted on ExpandableListView - debug or rewrite?

6. Android and Java card link

7. Knwon issues and limitations on running Android applications on Android 2.1 smartphone