Tizen Developers

Hi,
Thank you for the quick replay,
I am building a wearable application That is intended for meditation.
The user can set a "warm up" duration time (that can be between 1-10 min) and session duration time (that can be between 1-60 min).

Let's say the user wants to start a session and this is his settings:
warmup duration: 2 min.
session duration: 10 min.

The user presses the start button and an instance of System.Diagnostics.Stopwatch starts, and TimeChange event is raised every 10 milliseconds.

In the scenario above we want to notify the user (vibrate and play some .wav file) twice - when the warmup ended and when the session was ended. i, e.  after 2 min and after 12 min. 

I have noticed that after the app is entering to sleep mode, vibration and sound not always executed. I went through some samples from Tizen-CSharp-Samples-master on GitHub and I noticed the use of Power.RequestCpuLock() in the Xstopwatch example app.
I know that locking the CPU can be battery consuming and I dont want my App to be resources absorbing.

Another issue That's also related to this issue, I want my app to be in at the foreground every time the watch display is back to DisplayState.Normal (like the running app on Samsung health)
I have tried registering an event to Tizen.System.Display.StateChanged and calling the Tizen.Applications.AppControl.SendLaunchRequest every time the display is back to normal but it's not working, is there any examples available?  is this the way to achieve such functionality?
if true I will be very thankful for general guidance.

I have tried something like that:

private void stateChanged(object sender, DisplayStateChangedEventArgs e)
{
    if (e.State == DisplayState.Normal)
    {
        Tizen.Applications.AppControl appcontrol = new Tizen.Applications.AppControl();
        appcontrol.Operation = Tizen.Applications.AppControlOperations.LaunchOnEvent;
        appcontrol.ApplicationId = Tizen.Applications.Application.Current.ApplicationInfo.ApplicationId;
        Tizen.Applications.AppControl.SendLaunchRequest(appcontrol);
    }
}

Thanks in advance.

This information has been very helpful and valuable to me.

I had the feeling that I was shooting in the dark with AppControlOperations.LaunchOnEvent

Thanks so much for the detailed explanation.

Hi JONATHAN APPLEBAUM

I'm sorry, I didn't proceed to test it in sleep mode. (I think Timer.Elapsed event won't be fired in sleep mode.)

To keep the CPU running to do something while the screen is off, we need to hold CPU lock only for the time needed.

Or we can use the Alarm API to wake up after a certain time.

Thanks.

Hi,
that is how I handle it now and it works fine.
But in the same matter do you have any advice or enlightenment on this case: 

The application is also locking the CPU when activating the heart rate monitor for a little longer than the vibration. 
the problem is that the OS is alerting this message: "My application is using excessive battery power. Close app?"
the CPU is locked (and released after 20 seconds) in equal segments of 25% of session duration time.
i.e. if session duration is 10 minutes LocCpu() will be called 5 times in that manner:
1. beginning of the session.
2. 02:10 (20 sec before completing 25%)
3. 04:40 (20 sec before completing 50%)
4. 07:10 (20 sec before completing 75%)
5. 9:40 (20 sec before completing 100%)
Total time that CPU is locked is 60 seconds,
I am testing on Samsung gear s3 frontier.
Is there a way to handle it better in order to prevent the OS message?

Thank you again for your support and advice.

This function supposes to handle it safely, its called every time the heart rate monitor needs to be activated:

private static bool _IsCpuLocked = false;
public static bool IsCpuLocked
{
    get
    {
        return _IsCpuLocked;
    }
    private set
    {
        _IsCpuLocked = value;
    }
}

public static void LocCpu()
{
    if (!IsCpuLocked)
    {
        Xamarin.Forms.Device.BeginInvokeOnMainThread(() => Tizen.System.Power.RequestCpuLock(0));
    }
}

public static void ReleaseCpu()
{
    if (IsCpuLocked)
    {
        Xamarin.Forms.Device.BeginInvokeOnMainThread(() => Tizen.System.Power.ReleaseCpuLock());
    }
}

OK...now that I am passing on to my replay I think I found the problem...IsCpuLocked property is never set to true...cant seem to find a delete button for this replay...
allways keep telling myself never write code on the middle of the night... (-: