@Bobbie:

According to the doco (http://developer.android.com/reference/android/
app/Service.html#ServiceLifecycle) on services:

"Note this means that most of the time your service is running, it may
be killed by the system if it is under heavy memory pressure. If this
happens, the system will later try to restart the service."

I haven't used services actually, but it seems there are several cases
where the OS will kill the process if it needs to.  I'd suggest a
thorough review of these rules to see how to overcome this.  Even
better would be to review the use-case you have to see if it's
possible to satisfy the requirement without the service running
continuously.  From my reading (and your logs), the OS will restart
the service later.  So the ideal would be to have your app withstand
these restarts without any problems.

@Vinod:

I suggest you start a new thread for your question rather than
confusing this one with two completely different issues.

On Sep 9, 4:09 pm, Vinod <[email protected]> wrote:
> Dear All
>
> How can we configure TCP Window Size for FTP data transfers in
> Android ?
>
> Also, MTU change in Android will be very useful for my work
>
> Kind regards
>
> Vinod
>
> On May 19, 6:10 am, Bobbie <[email protected]> wrote:
>
>
>
> > I am running aTCPclient as a service.  Every 15-20 minutes, the
> > service just dies.  I don't get a force close or anything, the app
> > just closes.  The app launches a main view and theTCPclient is
> > started as a service by clicking a button using this code:
>
> > Intent TCPstart = new Intent();
> > TCPstart.setClassName("com.package.STIX","com.package.STIX.TCPClient");
> >  startService(TCPstart);
>
> > Here is what I get from debug:
>
> > 05-18 17:03:25.418: ERROR/dalvikvm(24664): VM aborting
> > 05-18 17:03:25.637: INFO/WindowManager(1029): WIN DEATH:Window{446f43b8 
> > com.package.STIX/com.package.STIX.STIX paused=false}
> > 05-18 17:03:25.645: INFO/ActivityManager(1029): Process
> > com.package.STIX (pid 24664) has died.
> > 05-18 17:03:25.645: WARN/ActivityManager(1029): Scheduling restart of
> > crashed service com.package.STIX/.TCPClient in 5000ms
> > 05-18 17:03:25.668: INFO/UsageStats(1029): Unexpected resume of
> > com.android.launcher while already resumed in com.package.STIX
> > 05-18 17:03:26.043: WARN/InputManagerService(1029): Got
> > RemoteException sending setActive(false) notification to pid 24664 uid
> > 10062
> > 05-18 17:03:26.864: INFO/DEBUG(14738): debuggerd committing suicide to
> > free the zombie!
> > 05-18 17:03:26.864: DEBUG/Zygote(992): Process 24664 terminated by
> > signal (11)
> > 05-18 17:03:26.879: INFO/DEBUG(25807): debuggerd: Mar 22 2010 17:31:05
> > 05-18 17:03:30.661: INFO/ActivityManager(1029): Start proc
> > com.package.STIX for service com.package.STIX/.TCPClient: pid=25808
> > uid=10062 gids={3003}
> > 05-18 17:03:30.731: INFO/dalvikvm(25808): Debugger thread not active,
> > ignoring DDM send (t=0x41504e4d l=38)
> > 05-18 17:03:30.739: INFO/dalvikvm(25808): Debugger thread not active,
> > ignoring DDM send (t=0x41504e4d l=40)
>
> > Could someone help me out here?
>
> > Thanks!!!
>
> > --
> > 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 
> > athttp://groups.google.com/group/android-developers?hl=en

-- 
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

Reply via email to