Hi all,

I’ve been developing a sensor monitoring service for the Samsung Gear Sport, using Tizen OS.

The service successfully captures data from the IMU and PPG sensors and stores them to a local sqlite database, but after 2.5 hours it mysteriously stops.

I ran it in the debugger and saw this:

Temporary breakpoint 2, main (argc=30, argv=0xfffef324) at ../src/testservice.c:81 81 char ad[50] = { 0, };

    c Continuing.

                                                   [2.5 hours pass…. ]

Program terminated with signal SIGKILL, Killed. The program no longer exists.

So Tizen is killing my service, despite the manifest including the ‘sensor’ and ‘background-network’ background categories set, and a CPU lock being applied.

The only thing I could find mentioning this online was here:

https://wiki.tizen.org/Service:Guideline

which implies that the systemd configuration for services includes the ‘TimeOutSec’ setting, causing the app to be automatically killed after a set period of time.

Is there any way I can stop this happening? Are all Tizen background services expected to be restarted after a couple of hours?

Appreciate any help or pointers you can give me.

Thanks in advance.