BroadcastReceiver dilemma

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

Sponsored Links

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



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. Activitity View Window?

English is not my first language.
I've been working with android for about a week now, and some things
really start to annoy me. What I'm trying to do is very simple.
An app with three windows and a background service.
The background service polls information from a webservice and adds
this to a few objects.
First window you choose what kind data you want to list and look at.
Second window shows the list you wanted to see, click a list item you
want detailed info about
Third window shows the info associated with the list item clicked.

Now each window has it's own Activity (1,3 = Activity, 2 =
ListActivity). First of all I'd like to follow android coding
standards/conventions. But I can't really find any? For example I'd
like to NOT start new activities as they are expansive to start. And I
have had a hard time finding something that would just stop a child
activity and not kill it as I heard finish() will do. And using
activities I'm having problems being able to go from window 3 to 1,
and it would feel strange to finish both the info activity and then
finish the list activity if the result from info activity is set to
something. This is how I solved it now. Then sometime in the future I
should add update callbacks to the activities when I poll updated data
but I'd like to understand the basic design concepts.

But as I said I'm not happy with the solution at all. And the
application is just an early prototype for now and will be a lot
bigger in the future.


2. Countries for selling priced applications in Android Market

Yes, exactly , I am curious to see Pakistan in the list G1 is avaliable
here, I came alone with a good alternative SlideME ( ) with
much less restrictions.


3. TranslateAnimation leaves traces

4. Multiple frame based animations

5. codeBeamer, Collaborative ALM Solution for Git and Android

6. Request for a log when Hibernate (alarm) fails. Offer to check your app on my phone.

7. usb for android