Tizen Forums

As I see here on Ecore Animations guide,  for  ecore_animator_add() interval is based on the frame rate. So, May be its not performance issue, just syncing with the frame rate.

https://developer.tizen.org/development/guides/native-application/user-interface/efl/animations-and-effects/ecore-animations#infinite

This code snippet shares some Idea to set/change the FPS:

https://developer.tizen.org/community/code-snippet/native-code-snippet/how-keep-animation-fpsframe-sec-you-wish

You can check the Ecore Animator functions API references for details:

https://developer.tizen.org/development/api-references/native-application?redirect=/dev-guide/2.4/org.tizen.native.mobile.apireference/group__Ecore__Animator__Group.html#ga2c7aa7e621cd68562519066ad87a3fa1

By the way you are using ambient life-cycle callbacks (ambient_tick) right? Something like:

void
app_ambient_tick(watch_time_h watch_time, void* user_data)
{
    appdata *ad = user_data;
    __update_watch(ad, watch_time);
}

int
main(int argc, char* argv[])
{
    appdata ad = {0,};
    watch_app_lifecycle_callback_s callback = {0,};

    /* Other life-cycle callbacks */

    callback.ambient_tick = app_ambient_tick;
    callback.ambient_changed = app_ambient_changed;
    ....
    ....
}

Link: https://developer.tizen.org/development/guides/native-application/application-management/applications/ui-application/efl-applications/watch-application#ambient

Hi, thanks for answering. I was intercepting ambient changing event and turn on the ecore animator, but it seems 

that after going ambient mode, the cpu is saving energy and the result animator is not working properly

May be that's what they want. Constant movement of 'Second hand' is discouraged in ambient mode. The ambient analog watches I have seen hold only 'hour' and 'minute' hand.

Look If this statement on Tizen Developers helps:

Link: https://developer.tizen.org/development/training/native-application/getting-started/creating-your-first-tizen-wearable-native-watch-application