davidcesarino / PebbleBtTest

Minimal example for a problem I'm having with the Pebble SDK.

PebbleBtTest

I created this small test sample to demonstrate an issue with the Pebble AppMessage system. The original discussion is on Stackoverflow. Same question is here.

Nothing fancy on what I'm currently doing:

1. My watchface is notified that the bluetooth connection with the phone is up, using .pebble_app_connection_handler.
2. In that bluetooth callback I set up, I send a message to the phone using app_message_outbox_send(). When BT connection is up, of course.
3. My Android app has a BroadcastReceiver that listens to these messages and calls an IntentService.
4. This IntentService calculates the data, pushes it to the watch and sets itself to run again after some time.

What I expect:

1. When the BT connection is up, the connection handler to be called.
2. app_message_outbox_send() return a value telling if the message initiation had any errors. Normally, this is APP_MSG_OK, but it can be APP_MSG_BUSY, and I'm perfectly aware of that.
3. The app message callbacks (app_message_register_inbox_received and friends) be called to indicate if the asynchronous process of sending message to phone really worked. This is stated in the docs.

What I'm seeing:

The expected steps happen when the watchface is loaded, because I trigger the update manually. However, when the update is triggered by a BT connection event, expected steps 1 and 2 happen, but not the step 3.

This is particularly aggravating when I get APP_MSG_OK in step 2, because I should reasonably expect that everything on the watch went OK, and I should prepare myself to receive something inside the app message callbacks. Basically, I'm told by the docs to wait for a call that never arrives.

This happens 100% of the time.

Thank you for any help. I have another solution that works, using the watch to keep track of the update interval, but I believe this one allows me to save more battery by making use of recent Android features.