Using Out of the box with Android - is it possible?

dba · **Joined:** Wed Feb 23, 2011 4:16 pm **Posts:** 3

Hi
The Watch displays the pair code, and i can pair it to the phone (Android)
OpenWatch beta is installed and finds the device, but keeps prompt that the device is disconnected.
I assume software isnt loaded on it. how can i load the notification system in?

I dont have a blackberry, never have, never will.

Jon · **Joined:** Tue Feb 15, 2011 1:00 am **Posts:** 60

You'll need to load a notifications app on the watch using a PC (Mac, Windows, or Linux).
Follow the getting started guide, then run the compileandload.py command with -n to load the standard notifications app.

Then you can try it with your Android phone. Let us know if it works or not. We're building up a list of supported Android phones.

joshuaguild · **Joined:** Fri Feb 25, 2011 1:32 pm **Posts:** 8

I'm running into the same issue. I've downloaded the SDK but I have no way to bluetooth my watch to my computer, can I just not plug it straight in?

Are you guys planning to write an Android quickstart guide similar to the Blackberry? That would be helpful.

Jon · **Joined:** Tue Feb 15, 2011 1:00 am **Posts:** 60

We don't have a way to update the watch firmware without a computer. USB bluetooth dongles are cheap.

We don't have a full-fledged getting started guide, but there's some info here: http://www.getinpulse.com/guide/android/

joshuaguild · **Joined:** Fri Feb 25, 2011 1:32 pm **Posts:** 8

Sounds good, I'll give it a shot.

Failing that though, is it possible to get it up and running via a Blackberry then just pair it to my Android phone? or is the notification firmware specific to platform?

Sorry if I'm being a bother, just excited about the product is all

Jon · **Joined:** Tue Feb 15, 2011 1:00 am **Posts:** 60

@joshuaguild
It's possible to get the standard notifications app on inPulse with a computer (instructions to be written, but contact [email protected] if you want the info sooner) or a Blackberry.

The standard notifications app works with Blackberry or Android, nothing device-specific. Though our Blackberry app supports changing fonts and other preferences that OpenWatch (for Android) hasn't implemented.

joshuaguild · **Joined:** Fri Feb 25, 2011 1:32 pm **Posts:** 8

So I got the firmware flashed via an old Blackberry that I had lying around. I downloaded the Inpulse app to the BB, flashed the firmware to the watch. After that, it worked with the BB test messages (email, SMS, etc.) so I turned off the BB, reset the Inpulse watch and tried to pair with my original Droid. Unfortunately I'm running into the same issue as before, my phone with pair but not connect and OpenWatch just says "Watch Disconnected" or "Waiting for Connection".

I know it has not been confirmed to be working with the original Droid but I get the same error when I use a Droid X.

Any suggestions? I would really love to get this up and running soon, the quality is really a step above Sony's LiveView (which I had before).

Eric · **Joined:** Mon Feb 14, 2011 7:07 pm **Posts:** 172

Hi Joshua. Did you manually type your inPulse Bluetooth address into OpenWatch?

joshuaguild · **Joined:** Fri Feb 25, 2011 1:32 pm **Posts:** 8

SUCCESS! Those wonderful people behind Open watch added Inpulse support in the latest update. I had to jump through a few hoops but finally it works. I'll check back in a few days to let you how how it goes.

Thank you for all of your help so far!

PolySynDactyly · **Joined:** Wed Feb 23, 2011 2:24 pm **Posts:** 8

Got the inPulse in the mail today, and sat down to get it up and running. And I'm getting the repeated watch disconnected message as well!
I downloaded the OpenWatch 1.5.0 from the page linked here before (http://www.beta.smartmadsoft.com/) Which is a higher version than what is available in the android market for some reason. After charging the watch I paired to my Mac, and run the compileandload.py script from a freshly downloaded copy of the SDK. So that worked but downloaded the falling block example script. Cleared out the source folder, and copied the Notifications example to my root folders (so, app_resource.h to the /include folder pulse_app.bin to the /resources folder and pulse_app.c to the /src folder from the /featured apps/Notifications App area). Ran the compileandload.py script again and everything seemed to work. Turned off the Mac's bluetooth, and paired my Nexus One(2.2.2 if it matters) to the watch, and ran the OpenWatch app. Changed the device type in settings to Allerta inPulse. Click Start and I get a repeating "Watch Disconnected" Toast message popping up. Also, if I go back into the bluetooth settings it lists the watch as paired but not connected.

Any help? What am I missing, was really hoping to show this off at work tomorrow

joshuaguild · **Joined:** Fri Feb 25, 2011 1:32 pm **Posts:** 8

I know it sounds simple but did you power cycle the phone after you selected the In pulse as your device? I had to do this to get it to connect. Works fine after that though my Gmail alerts don't work (already emailed the Openwatch folks).

heow · **Joined:** Tue Mar 01, 2011 8:30 pm **Posts:** 1

I've got the exact same symptoms as PolySynDactyly. Installed the whole stack on my Android HTC EVO, paired but not connected and OpenWatch 1.5.0 is nothing but the repeated watch disconnected message. Cycling the phone doesn't work.

If I go into OpenWatch's Settings->Discover, it successfully finds the watch's MAC address. Even if I erase the MAC, then it'll find it during Discover. But sending the watch a Test message from OpenWatch causes OpenWatch to crash (stopped unepectedly).

- Heow

Eric · **Joined:** Mon Feb 14, 2011 7:07 pm **Posts:** 172

Hmm thanks for the reports, guys. We'll be experimenting with actual 1st party Android support soon, so we'll hopefully start sorting out this weirdness.

If you don't find that OpenWatch is working, I'd suggest looking inside the SDK to try compiling your own Android app. We've got an example under /examples/smart_phones...

PolySynDactyly · **Joined:** Wed Feb 23, 2011 2:24 pm **Posts:** 8

heow wrote:

I've got the exact same symptoms as PolySynDactyly. Installed the whole stack on my Android HTC EVO, paired but not connected and OpenWatch 1.5.0 is nothing but the repeated watch disconnected message. Cycling the phone doesn't work.

If I go into OpenWatch's Settings->Discover, it successfully finds the watch's MAC address. Even if I erase the MAC, then it'll find it during Discover. But sending the watch a Test message from OpenWatch causes OpenWatch to crash (stopped unepectedly).

- Heow

Finally got mine paired, I also had been auto-detecting the bluetooth address. But I manually deleted and re-entered it (probably a few power cycles in there as well). and finally got it to connect. Test messages come across, and caller id, haven't gotten anything else yet.

daverse · **Joined:** Wed Mar 09, 2011 10:54 am **Posts:** 1

heow wrote:

I've got the exact same symptoms as PolySynDactyly. Installed the whole stack on my Android HTC EVO, paired but not connected and OpenWatch 1.5.0 is nothing but the repeated watch disconnected message. Cycling the phone doesn't work.

If I go into OpenWatch's Settings->Discover, it successfully finds the watch's MAC address. Even if I erase the MAC, then it'll find it during Discover. But sending the watch a Test message from OpenWatch causes OpenWatch to crash (stopped unepectedly).

- Heow

Did you get it working on your HTC EVO? My watch should be here tomorrow and I am wondering how difficult it will be to connect it.

g_pass · **Joined:** Mon Mar 14, 2011 11:22 am **Posts:** 2

I have a Samsung Vibrant with Android 2.2 and am having the same problems as other. The test message works, but openwatch just says disconnected. I tried manual and auto entry of mac addr.

g_pass · **Joined:** Mon Mar 14, 2011 11:22 am **Posts:** 2

I think this is because the OpenWatch release notes say they support fw "3.8.5" and after following the mac install instructions, my phone says sw "3.8.4" . What do I do to get up to 3.8.5? I just did the download/install today, so I'm surprised it's not up-to-date. Is it the mac version?

rolcor · **Joined:** Tue Mar 15, 2011 1:14 pm **Posts:** 1

g_pass wrote:

I think this is because the OpenWatch release notes say they support fw "3.8.5" and after following the mac install instructions, my phone says sw "3.8.4" . What do I do to get up to 3.8.5? I just did the download/install today, so I'm surprised it's not up-to-date. Is it the mac version?

I would like to know how to upgrade the firmware version on the watch to 3.8.5 as well. I loaded the openwatch apk on an HTC Evo and a Nexus S and I only got it to work on the Nexus S. I cannot get the watch to connect to the openwatch app even though it is paired.

Eric · **Joined:** Mon Feb 14, 2011 7:07 pm **Posts:** 172

Hmm I know someone else who got it to work with the HTC Evo, I'll see if I can find the email...

@rolcor, you were able to send test messages from Nexus S to inPulse, correct?

chappedsky · **Joined:** Tue Mar 29, 2011 2:08 pm **Posts:** 3

Hey yall, I'm having similar issues with a HTC incredible. I've tried out all the solutions posted on here but open watch still isn't playing nice with the watch. I've checked with sdptool and it seems like the Incredible does have L2CAP support. Any Ideas?

Eric · **Joined:** Mon Feb 14, 2011 7:07 pm **Posts:** 172

What version of Android is the Incredible running?

chappedsky · **Joined:** Tue Mar 29, 2011 2:08 pm **Posts:** 3

Eric · **Joined:** Mon Feb 14, 2011 7:07 pm **Posts:** 172

Yes, it looks like HTC doesn't expose the right l2cap profile. I know it's a pretty huge thing to change just to get your inPulse working, but have you considered rooting and installing a ROM like Cyanogenmod?

Using Out of the box with Android - is it possible?

Who is online