Typo in AOD event documentation and suggestion for EVENT_AOD timing

[kustomq]

Hi team,

I noticed a small typo in the documentation under the “Toy with AOD capability” section. The sentence currently reads:

If you have set your toy as an AOD toy, your toy will receive EVENT_AOD every minutes when your toy has been selected as aod toy.

It should be “every minute” or "every X minutes" instead of “every minutes”.

Additionally, I wanted to ask if it would be possible for the EVENT_AOD to be sent immediately upon entry into the AOD state, rather than only after the first minute(s) has passed. This would allow toys to react instantly to AOD activation, which could improve responsiveness and user experience.

Is this something that could be considered for a future update?

Thanks!

[equalparts]

While not explicitly stated, it seems the AOD event is timed to fire exactly at the start of every new minute, so 11:05:00 -> 11:06:00 -> etc. Which is perfect for clock AODs. Getting an AOD event at 11:04:52 and then another one just 8 sec later might be surprising behavior.

That said, I second that a separate event or flag (like MSG_ENTER_AOD or gm.isAod()) would be useful. Right now, we can react to the onServiceConnected callback firing, but there's no documented way to tell if that's from the AOD switching on or not.