Need Help with Always-On Display (AOD) on Fitbit Sense - Not Working Despite Multiple Attempts

[Algorithm_Aiden]

Dear Fitbit Community,

I hope this message finds you well. I am currently experiencing a challenging issue with my Fitbit Sense watch that I've been unable to resolve despite numerous attempts and extensive online research. Specifically, I am having trouble with the Always-On Display (AOD) feature. It simply will not show, no matter what I try.

Over the course of several hours, I've attempted various methods found in online guides, forums, and even the Fitbit SDK documentation. Despite diligently following these resources, the issue persists. To ensure that the problem was not due to some error in my initial setup, I even went as far as reinstalling the simulator, but to no avail.

Here's a brief overview of my attempts:

1. I have checked and rechecked my device settings to make sure the AOD feature is enabled.
2. I have tried restarting the device multiple times.
3. I have ensured that my watch's battery level is sufficiently charged as I understand that AOD can automatically turn off at certain low battery levels.
4. I have verified that my Fitbit OS is up-to-date.
5. As mentioned before, I also reinstalled the simulator.

I am trying to program a watch face that utilizes the AOD feature, so this issue is proving to be a significant roadblock in my development process. I am eager to resolve it and move forward with my project.

If anyone has experienced a similar issue, or has any insight into potential solutions, your input would be immensely appreciated. I am open to trying any suggestions that might help to resolve this issue.

Thank you in advance for your time and assistance. I look forward to any guidance that you can provide.

[Gondwana]

There is a couple of issues:

• AOD-enabled apps can't be installed on a watch until they've been approved by Fitbit through the gallery submission review process.
• Relatively few developer accounts are allowed to submit AOD-enabled apps for review. See the Developer Blog announcement for SDK 4.1; the situation hasn't changed since then. There is no process for requesting this privilege; Fitbit approaches developers at their discretion.