Does the watch always have to be "rebooted" back to the starting Bluetooth Pairing screen to receive code? It seems pretty finicking when I try to upload code from my Mac 10.6.7 where it can't connect if an app is running.

Also, it seems like *what* app is already on the watch will dictate how easy it is to get the watch to the "pairing" screen in the first place. For example, the sample app (yellow square) is pretty easy while the example Psychodelic Clock is damn near impossible. Meaning, you hold down the button for awhile and it while it buzzes/etc like it is going to reset, it just goes right back into the Clock app and you can't upload any code. Takes literally 10+ tries.

Still learning. Any thoughts appreciated.

You're correct, it does depend on the app currently on the watch. If the app is doing a lot of processing (i.e. the psychedelic clock or doomed) the only way to switch apps is by putting it into VLF (blue pair screen) and then transferring it. Otherwise you can send a new app while running the old one; it is recommended to use this method if possible because the transfer will be much quicker.

@Ryan. Thanks, that helps.

Is there a foolproof way to alway go back to the VLF screen? Press and hold doesn't always work. For example, the Psychodelic Clock I get the "sad mac" screen with 0x0000bbbb (if memory serves) a lot. Then I release the button and it goes right back to the app

Should every app have a pulse_update_power_down_timer(LARGE_TIMEOUT) both on init and button_down to make sure that the watch will go to sleep after a large_timeout with no interaction to prevent the resident app from "spin locking" the watch and causing havok like this?

Thanks,

Ah, if you're getting the 0x0000bbbb error, that means you're holding down the button for a bit too long. You need to hold down the button just until 'loading...' is displayed on screen. Then you need to let go!

My experience after a few hundred reflashings was that 20 seconds was the length of time: at ten seconds it would reboot to the app, and then at twenty it would print "Loading..." and I would release the button as it started the VLF. If I continued to hold the button beyond the loading message, it would give me the same unhappy 0xbbbb message.