Multiple requests piling up can break accelerometer. about clock HOT 2 CLOSED

I believe we just need to make sure we ALWAYS register and deregister on view appear and view disappear. We were doing it that way sometimes but also when the view was loaded, which would/could cause problems

from clock.

Reopening this until we get a chance to test. If this works then maybe we don't need any other kind of system to handle this, they will just naturally queue( not actually a queue, note) up and be handled one after another.

note: just so this is documented, as far as I can tell the pebble appmsg system does NOT queue messages, but rather it simply lets them fail. For this reason, in the on_msg_dropped method inside app_msg_handler, we retry the send until it succeeds. This gives the illusion of queueing, when in reality its just blocking at the sender until the receiver is ready for it.

from clock.