Tizen Developers

did you ever set "background-support" and "background-category" in your config.xml?

for example, like there lines

<tizen:background-category value="sensor"/>

<tizen:setting background-support="enable" encryption="disable" hwkey-event="enable"/>

you can find them on "Tizen" tab on your config.xml editor.

And when you test it, you'd better use the operations other than 'default'. usually 'main' or your custom one.

good luck.

Hello Maciej,

What's your current state? Seems there's no response from your side.

As far as I know,  Setting 'http://tizen.org/appcontrol/operation/main'  instead of 'default' should do the trick.

In addition, You may also check out this question on Stack Overflow. The issue is not exact similar of yours but thanks to tymbark ,you can grab some useful hints from the question.

https://stackoverflow.com/questions/49752776/is-it-possible-to-keep-tizen-application-alive-non-stop

Hello. Thanks for the suggestions. Unfortunately I haven't been able to fix this issue. My very simplistic code:

        //schedule alarm
        var appId = tizen.application.getCurrentApplication().appInfo.id;
        var appControl = new tizen.ApplicationControl("http://tizen.org/appcontrol/operation/main");
        var newAlarm = new tizen.AlarmRelative(240, 300); 
        tizen.alarm.add(newAlarm, appId, appControl);
        
        tizen.power.turnScreenOff();
        tizen.application.getCurrentApplication().exit();

I have also added the mentioned parameters in the config.xml:

    <tizen:setting background-support="enable" encryption="disable" hwkey-event="enable"/>
    <tizen:background-category value="sensor"/>

Using the "main" operation doesn't help. After 4 minutes (240 seconds), the screen is activated on the watch and then the UI of my app is shown. 

It happens only on Tizen 3 (Gear S3, probably Gear Sport too). It does not happen on Gear S2 (screen stays dark, although the app is launched).

Could anybody explain why there is such a difference? It ruins the concept of my app. Also, I think it doesn't make sense to let the app work in background (background-category), if the screen is activated anyway. 

Can somebody suggest a solution for this problem?

@Armaan-Ul- Islam: thanks for your answer, but I am afraid you are wrong.

First of all, it doesn't have anything to do with the Power API and turnScrennOff/On() calls. The problem happens when the app is woken up by the alarm, not when I schedule the alarm and exit the app (and turn off the screen, although it doesn't actually matter). After several minutes, the app is woken up and the screen is activated. There is no code related to turning the screen on or off manually.

Secondly, the Power API and turnScrennOff/On() calls might be deprecated in Tizen 3, but they work. When some API or method is deprecated, it means it will probably stop working in the future. Now it still works.

So I am still looking for some solutions...

Well.. then try this. create a service app and put the alarm app control on this service app id.

if this works for you, you can use it by re-designing your app as consisting of UI and service app.

Otherwise.. well I think there is no more solution I can think right now.

​Hello. Yes, I am treating a service component as a last solution in this case, because it would needs quite a lot of redesign. By the way, do you mean a native service or web service?