On Apr 15, 10:24 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> There is not enough information here to debug your issue ...could you tell
> us more about the steps that you followed and the logcat ouput on each step.
>
> Thanks,
> Megha
>
>
>
> On Tue, Apr 15, 2008 at 8:24 AM, E.D.I <[EMAIL PROTECTED]> wrote:
>
> > after creating an alarm service that starts on boot the adb tries to
> > connect even after i stop the emulator, why is that?
>
> > i continue to see on the consule of the eclips every 30 (sec as i set
> > the alarm)
>
> > [2008-04-15 18:13:36 - adb] This application has requested the Runtime
> > to terminate it in an unusual way.
> > [2008-04-15 18:13:36 - adb] Please contact the application's support
> > team for more information.
> > [2008-04-15 18:13:37 - DeviceMonitor] Connection attempts: 1
> > [2008-04-15 18:13:39 - DeviceMonitor] Connection attempts: 2
> > [2008-04-15 18:13:41 - DeviceMonitor] Connection attempts: 3
> > [2008-04-15 18:13:43 - DeviceMonitor] Connection attempts: 4
> > [2008-04-15 18:13:45 - DeviceMonitor] Connection attempts: 5
> > [2008-04-15 18:13:47 - DeviceMonitor] Connection attempts: 6
> > [2008-04-15 18:13:48 - DeviceMonitor] Connection attempts: 7
> > [2008-04-15 18:13:50 - DeviceMonitor] Connection attempts: 8
> > [2008-04-15 18:13:52 - DeviceMonitor] Connection attempts: 9
> > [2008-04-15 18:13:54 - DeviceMonitor] Connection attempts: 10
> > [2008-04-15 18:13:56 - DeviceMonitor] Connection attempts: 11
> > [2008-04-15 18:13:59 - adb] * daemon not running. starting it now *
> > [2008-04-15 18:19:06 - adb]
> > [2008-04-15 18:19:06 - adb] This application has requested the Runtime
> > to terminate it in an unusual way.
> > [2008-04-15 18:19:06 - adb] Please contact the application's support
> > team for more information.
> > [2008-04-15 18:19:06 - DeviceMonitor] Adb connection Error:An existing
> > connection was forcibly closed by the remote host
> > [2008-04-15 18:19:07 - DeviceMonitor] Connection attempts: 1
> > [2008-04-15 18:19:09 - DeviceMonitor] Connection attempts: 2
> > [2008-04-15 18:19:11 - DeviceMonitor] Connection attempts: 3
> > [2008-04-15 18:19:13 - DeviceMonitor] Connection attempts: 4
> > [2008-04-15 18:19:15 - DeviceMonitor] Connection attempts: 5
> > [2008-04-15 18:19:17 - DeviceMonitor] Connection attempts: 6
> > [2008-04-15 18:19:19 - DeviceMonitor] Connection attempts: 7
> > [2008-04-15 18:19:21 - DeviceMonitor] Connection attempts: 8
> > [2008-04-15 18:19:23 - DeviceMonitor] Connection attempts: 9
> > [2008-04-15 18:19:24 - DeviceMonitor] Connection attempts: 10
> > [2008-04-15 18:19:26 - DeviceMonitor] Connection attempts: 11
> > [2008-04-15 18:19:29 - adb] * daemon not running. starting it now *- Hide
> > quoted text -
>
> - Show quoted text -
there is nothing special on the logcat co's this happens when the
emulator is closed
i wonder maby the service that iv'e scheduled with the alarm at boot
completed shold be stoped on close ( when the emulator is closed )
is there a way to do so.....
and another thing when scedule a service to the alrm but not on boot
complete , on an activity, does it works the next time i run the
emulator
or should i schedule it again, co's this is why i schedule it on boot
completed the first time...
--~--~---------~--~----~------------~-------~--~----~
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]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
