On11 is a watchface that can monitor your physical activity 24 × 7. It tells you how much time you spent on sitting, walking, jogging, and idling (might be sleeping or putting Pebble on the table). Well, it also works as a pedometer just like other activity trackers do.
Website: http://on11.mobi
Source Code: https://github.com/heqian/On11
Thank 胖兔子粥粥 for the cute icons!
Download the Watchface 1.5 (09/18/2014) -- You don't need the companion app to run this watchface. It works independently.
Download the Android Companion App 1.3.3 (05/15/2014) -- (Optional) The companion app is for better presenting the activity data, backup, configuration and sync with RunKeeper.
Changlog:
Watchface 3.0:
1. Redesigned the structure of persistent storage;
2. Redesigned the application-layer Bluetooth protocol for more reliable synchronization;
3. Background running supported since 2.0.
Bugs/Defects in Background Worker API:
1. One-way AppWorkerMessage. If you subscribe app_worker_message_subscribe() in both Background and Foreground, app will crash (struct.error: unpack requires a string argument of length 5). No matter the Background or the Foreground sends a message, both the sender's and receiver's callbacks will be called. It seems to be a bug. I think the crash may be caused by consuming the struct data (message) twice (in two callbacks), or by the #2 defect below;
2. The message between Background and Foreground can only be 3 bytes. Are you kidding me?? It's not even mentioned in the API document! I found it here (slide 28): http://www.slideshare.net/pebbledev/pebble-dev-retreat2014kickoff
Bugs/Defects in Background Worker API:
1. One-way AppWorkerMessage. If you subscribe app_worker_message_subscribe() in both Background and Foreground, app will crash (struct.error: unpack requires a string argument of length 5). No matter the Background or the Foreground sends a message, both the sender's and receiver's callbacks will be called. It seems to be a bug. I think the crash may be caused by consuming the struct data (message) twice (in two callbacks), or by the #2 defect below;
2. The message between Background and Foreground can only be 3 bytes. Are you kidding me?? It's not even mentioned in the API document! I found it here (slide 28): http://www.slideshare.net/pebbledev/pebble-dev-retreat2014kickoff
3. APP_LOG is broken in worker. I cannot print any debug message with it. Something broken in the <pebble_worker.h>?
4. Background worker cannot talk with the Android/iOS companion app through AppMessage API. I can see no reason setting this barrier here. If a user changed configuration through the web, the worker cannot get the update. And the Foreground cannot inform the Background because of the #1 defect I mentioned above.
4. Background worker cannot talk with the Android/iOS companion app through AppMessage API. I can see no reason setting this barrier here. If a user changed configuration through the web, the worker cannot get the update. And the Foreground cannot inform the Background because of the #1 defect I mentioned above.
Android companion app 2.0.0
WARNING: This update will wipe all the data in the database of On11. Please backup the data before updating if you really think the data is important to you.
NOTE: Please update the Pebble firmware to 2.7+ and On11 watchface to 3.0+ by UNLOAD and RELOAD.
NOTE: Please update the Pebble firmware to 2.7+ and On11 watchface to 3.0+ by UNLOAD and RELOAD.
1. Redesigned the database for faster IO;
2. Redesigned the application-layer Bluetooth protocol for more reliable synchronization.