Hello
I'm using the alarm API in a native app to launch a service continuously collecting heart-rate data on a Samsung Galaxy Gear S3 Frontier running Tizen ver. 3.0.0.2. I use the function call
ret = app_control_set_operation(app_control, APP_CONTROL_OPERATION_MAIN);
ret = app_control_set_app_id (app_control, APP_NAME);
ret = alarm_schedule_with_recurrence_week_flag(app_control, &date, ALARM_WEEK_FLAG_MONDAY |
ALARM_WEEK_FLAG_TUESDAY | ALARM_WEEK_FLAG_WEDNESDAY |
ALARM_WEEK_FLAG_THURSDAY | ALARM_WEEK_FLAG_FRIDAY |
ALARM_WEEK_FLAG_SATURDAY | ALARM_WEEK_FLAG_SUNDAY, &alarm_id);
in a loop to set the alarm throughout each of the days at 15 min intervals starting from 9 am to 10 pm, and ensure that the service is always running. One thing I notice, however, is that when the watch still has battery life remaining and is placed on the charger until the next day, that the alarm does not trigger the next day. I have to power off the watch and turn it on again for the alarm to finally be invoked.
Does anyone know if there are certain pre-requisites (apart form the get/set priveleges) for ensuring proper invocation of alarms in Tizen for wearables? Or is there some internal time-out for these types of function calls?
Thanks,
Rich