Service closed when main application swipe

[Кирилл Вертипорох]

Create service, example take from here: http://wiki.droidscript.me.uk/doku.php?id=sample_code:file_service

But when I swipe main window application - to close it, service has been closed automatically too.

What am I doing wrong?

[nikhil baby]

Android OS automatically closes background services for freeing the RAM space!!!!!!

[Dave Smart]

I think some phones will kill both app and services if you swipe them away.  You should press the back button or use app.Exit to close the app and leave the service running.

What phone do you have?

[Кирилл Вертипорох]

app.Exit() or back button doesn't give the due effect - the application just go to background and no exit.

The phone is Sony Xperia Z1 Compact.

I want to be able to swipe or close main window and have running service in foreground - like WhatsApp, for example. And Android has nothing to do with it application - so Android it is no main reason about closing service together with app.

[Кирилл Вертипорох]

When I running application from code in DroidScript and than swipe application's main window (called New Activity), service continues to running. When I close or swipe DroidScript application service also continue to running.

[Кирилл Вертипорох]

Maybe problem in BuildAPK plugin?

[nikhil baby]

I think its various with Android OS versions!

In my Jelly bean i have problem like
Кирилл Вертипорох

In my Marshmello, works fine!!!!

[Кирилл Вертипорох]

But WhatsApp works in all versions without any problems.
So waiting for solve the problem.

[nikhil baby]

Whatsapp background service is more different from D.S
in whatsApp when the service is closed by the OS it Whatsapp detects it and start it once more!!!!
:)

[Кирилл Вертипорох]

Anyway, fifth post said about situation, when service continues running after close application - need similar effect not only in DroidScript application, but in apk also.

[Кирилл Вертипорох]

Build APK from alpha 1.5 Apkbuilder - all start works OK.

[Steve Garman]

I am glad to hear the problem appears to be fixed for you.

I was in the middle of composing a reply when you mentioned that the 1.50 builder fixes it for you, so I will paste it below in case it is needed by anyone else.

----------

You can emulate the behaviour Nikhil describes above for WhatsApp by adding an alarm to your service.

In its simplest form, this would be

var now = new Date().getTime();
app.SetAlarm( "Repeat", 4280, null, now + 3000 );

The above code will just cause the service to restart from the beginning if it shuts down, which is fine for many services but it will forget the content of any variables that it has already set.

If your service is reliant on instructions sent to it at startup by
svc.SetMessage, or on any variables it sets itself, you will need to store any data it relies on each time it is changed.
You will also need to change the SetAlarm call to include a callback and retrieve the data in the callback function.

The data can be stored and retrieved by using
app.WriteFile and app.ReadFile
or any other method you find convenient.

[Кирилл Вертипорох]

It seemed to fixed the problem - problem still actual.

Try your advice.

[Кирилл Вертипорох]

app.SetAlarm seems helped. Need some time to make a couple of tests.

[Chris]

Кирилл Вертипорох, the new beta (1.5) was supposed to include DS restarting a service that was killed my the system.

I would start a thread in the beta and report, maybe Dave can work out the problem.

[Chris]

...by the system. :-)

[Кирилл Вертипорох]

OK, thanks!

I test app.SetAlarm() - it working fine. Used DS v1.50a11 with it's Apkbuilder - from that directory.

[Кирилл Вертипорох]

Chris, could you tell me title of the topic, which you create?