Hi all,

I'm a beginner on developing watch apps, got an Inpulse watch yesterday and I'm now playing around with it A problem I have is that the OpenWatch Android app craches ("the process has terminated etc...") on my HTC Desire as soon as I try to test my watch (I've selected Allerta InPulse as device and installed the notification app on the watch). From looking at the bluetooth icon in the watch, it seems that tha bluetooth connection is disabled, but on the other hand it loooks the same when connecting from my PC (and sending test messages and such works anyway).

Is OpenWatch compatible with HTC Desire (Android 2.2) and Allerta InPulse? Firmware version is 3.8.4 (where do I find the latest, if there is a newer version?).

Thanks,
Anders

If openwatch crashes when you push the test button then your watch doesn't have the L2CAP protocol, which the Inpulse watch requires.

You'll need to get a custom ROM to make it work. Here is a link to ROMS for the HTC Desire http://forum.xda-developers.com/wiki/index.php?title=HTC_Desire
I would try either the cyanogenmod, or one of the gingerbread ones. Cyangenmod seems to work everytime for multiple phones.

I'm having a similar problem with my htc incredible. I checked with sdptool browse and it looks like the incredible does have L2CAP support. Any ideas on what else it could be?

I know I had the same problem but I'm not 100% sure how I fixed it. I believe the problem was fixed for me after I held down the button on my watch for 15 seconds to reset itself.

So waht is everybody's battery lifew with open watch?

I've tried changing every setting I could and I still get exactly 6 hours of battery life. I've sent the Openwatch maker an email to see if there is a planned fix or not.

This isn't an Openwatch issue - it's an issue with the protocol the Inpulse watch is using. At this point the notification app is not usable for Android due to the 6-7 hour battery life.

I use it everyday, just have to charge the phone at lunch, and late afternoon.

It has to be an openwatch issue, if the bb app does't cause it to drain as quick. Or is my thinking is flawed

I know I'm not an expert at programming, especially C, but is there a way to just send messages to the watch like when using the test_msg.py code, inwhich the only time there is communications is when a message gets pushed to the watch, and the comm stops? This to me seems like it would be the most ideal way, since the power drain would be substantially lowered.

Here is what Marcel, the creator of Openwatch, had to say about my question if there was a way for me to improve battery life with OpenWatch and inPulse:

"No, I’m afraid. OpenWatch uses not finished parts of Bluetooth API that may affect BT stack and battery life. The only way is for Allerta to switch from L2CAP to RFCOMM that is officially supported on Android – and they said they plan to (with their 1st party Android app and update watch firmware/watch bt stack)."

While your logic make sense, I do not see any reason why a guy with this much experience would make this this stuff up.

Yeah, Marcel is correct. We're working on the RFCOMM solution. That's why we don't feel comfortable supporting Android from a 1st party perspective yet (official inPulse app) but soon...

So it's not really as much a watch issue as it is an Android Bluetooth issue. I know the creator of the cynagenmod for my phone has had problems with getting bluetooth completely functional. I understand now.