How can I request permission to use access_aod?

[Kyouki_IE]

Hi all,

I developed a clock face and had Always-On-Display functionality implemented.

I followed the guidelines and I can confirm pixel usage is at maximum 8.4%, at minimum 1.6%, and typically less than 5%. Also, I lower the opacity to reduce brightness during AOD.

When I submitted my clockface for review, I had information in the description about always on display, and a screenshot, and I left a note for reviewers stating that I was unable to upload the an .fba file with the access_aod permission, so I requested for permission to use this permission. My clockface was approved, so I published it and then tried to upload a new .fba with access_aod permission, but I am still not allowed.

I understand it's not a widely allowed permission and needs to be requested to use. How can I request permission to use AOD on my clockface? Thanks.

[JonFitbit]

Please do not abuse the APIs like this. Forcing the display to stay in full power mode will cause physical device damage and invalidate your warranty. AOD is a special low power mode, it's not just keeping the screen on in full power mode. Any clocks abusing the Display API will be removed from the gallery.

[McFIT_Design]

I agree, AOD would be better option... but isn't available.

Even for personal watchface sideloading.

So there is a workaround to use the device on own way.

And it works. (in some cases like outdoor/sunlight readability even much better than AOD).

Please do not abuse users who paid you by buying your products.

Abusive is keeping AOD permissions only for mutual admiration clique and treating users like idiots.

[seraphiel]

That is ... unacceptable @JonFitbit. Advertising AOD as a feature and part of the SDK is false advertising if no one can use it! Fitbits own unattractive AOD is not an answer either (the battery icon has been broken for months!).

How can the review process mentioned in the announcement take literally 18 months and not improve at all? https://dev.fitbit.com/blog/2019-12-19-announcing-fitbit-os-sdk-4.1/

I spent money on this watch, and as a developer I can't run my code on my personal device using _official API calls_  that other people are allowed to profit from on it! This is infuriating, especially since this was announced 18 months ago.

[ehnane1]

Any news on that 3rd party API? I had a qucik search for it and coulnd't find anything. Thankfully I'll be able to switch to the Pixel watch soon and say my goodbyes to this ancient UI, but I'd like to make the most of my Fitbit in the time being.

[ceriboo]

I made a feature suggestion here: https://community.fitbit.com/t5/Feature-Suggestions/Open-new-wave-of-allowed-developer-to-release-cl...

pleaase vote and invite your friends to vote too

[Elegac]

Hello @JonFitbit,

Is it always impossible to obtain authorization from Fitbit for access_aod permission for a simple developer ?

If it is the case, please change your documentaton and clearly write that you don't give this permission. It will avoid new developers to waist their time.

I spent time to understand this function and optimise it better than the default AOD from fitbit (about 3% of lit pixels). I am very disappointed.

[Andrew_in_Devon]

Did you ever get to publish your SemiAOD on github.  I've had a look but can't find it.  I've just bought a new sense (1) with the specific intention of writing an AOD face.  So bit annoyed to say the least that Fitbit should be holding back on this feature.  Surely, its up to me if I want to run my battery down quickly.  All they need to do is include a page saying you accept the risk.  

[Guy_]

Hi @Andrew_in_Devon - Fitbit aren't permitting new developers to make AOD clock faces for publishing, but for personal use you can still simulate this by keeping the screen on but it is not really advisable without the proper access which is no longer given.

The Sense has a builtin AOD function, for watches that don't have their own AOD, which can be configured either Analog or Digital and if you insist on doing your own, take the necessary precautions to avoid screen burden or heavy battery usage. There may be some conditions where your routines get overridden and the screen blanks. However on this model the automatic screen wake time is pretty short so it may not even be necessary to keep it on permanently. An option is to program your AOD simulation on/off only when you need it.