How about not finding a work-around, but rather starting yourself up when the user starts your app as intended? Better yet, let them decide whether you will remain running in the background, so if they don't want to be using your app's features during some time they don't have to resort to just uninstalling it.
On Tue, Dec 30, 2008 at 11:32 AM, devileper <[email protected]> wrote: > Upon further reading, this approach is impossible and is by design. I will > find a work around. > > On Wed, Dec 17, 2008 at 11:22 AM, [email protected] <[email protected] > > wrote: > >> >> I need a service to begin the moment my application is installed. Is >> this possible? >> >> My current approach is to create a BroadcastService which receives the >> PACKAGE_ADDED action. However, this only seems to work after my >> application is installed, not when my application is installed. >> >> <receiver android:name=".broadcast.InstallBroadcastReceiver"> >> <intent-filter> >> <action >> android:name="android.intent.action.PACKAGE_ADDED"></action> >> <data android:scheme="package"/> >> </intent-filter> >> </receiver> >> >> >> >> > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
