Default aod overwrites my custom aod watchface

[Jemand]

I made a watchface for my versa 2 (4.1 SDK) and have created my own always on display. As soon as I turn off my watch, I can see my aod-watchface but after another second I see the default aod-display from my versa 2. Is there any trick to stop the default aod?

[Gondwana]

You need to use the access_aod permission (among other things). I don't think that's been opened up for all developers to use yet.

[JasminS]

Make sure to set the aodAllowed to true. I have this at the start of my app index.js

if (me.permissions.granted('access_aod')) {
  if (display.aodAvailable) display.aodAllowed = true
}

 https://dev.fitbit.com/build/reference/device-api/display/

[derekwilson]

Does this work? Or do you need to be approved by Fitbit in some way before you can do this?

[Gondwana]

It should work in the simulator for all developers. Only Fitbit can approve AOD-enabled clockfaces/apps for installation on physical watches (even for testing).

[derekwilson]

Thanks for the info - that is good to know.

Do you know what the process is to get Fitbit approval to install on a real device?

I am a bit loath to invest time and effort to develop an AOD mode for my clockface if I cannot get it approved. 

(To be honest I would also be uneasy releasing an app to the public that I haven't tested on a real device)

Derek

[Gondwana]

I think the best bet is to develop AOD for simulator, then show off how great it is via screenshots and maybe videos. If you impress the right people, you might get a tap on the shoulder.

No guarantees, of course.