Bump for the weekend crowd. Anyone know how to test BOOT_COMPLETED intents? Looking into it further, the package being added doesn't recieve a PACKAGE_ADDED intent so that option is out.
On Jun 18, 7:07 am, Micah <[email protected]> wrote: > I'm using Eclipse on windows to do my Android development and I want > to test / debug some code that runs on Android startup. I have setup > my program to receive the BOOT_COMPLETED broadcast intent (which is > working) and from there it launches a service that runs in the > background on the device indefinitely. > > The problem I'm having is that when I debug my application by clicking > "Debug As Android Application" it boots up Android and then after > bootup is complete it installs my program and then attaches the > debugger to it. Of course, this isn't much use to me since my program > does things that I need to debug at Android bootup, before the updated > version of my program is installed (at bootup it runs the previous > version I tried to debug) and no debugger is yet attached to it. > > So the question is, how do I setup the debugger to install and attach > my program *before* BOOT_COMPLETED intent is sent out? > > In a worst case scenario I can change the intent it listens for to > PACKAGE_ADDED or whatever it's called but I would really rather test > and debug the real code and not a contrived test case. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
