ayoola-solomon / mytracks

Automatically exported from code.google.com/p/mytracks
0 stars 0 forks source link

Zephyr HxM bluetooth no longer recognized by 1.1.6 #483

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. strap on Zephyr HxM
2. activate Bluetooth on phone
3. start MyTracks

What is the expected output? What do you see instead?

What version of MyTracks are you using? 1.1.6
On what version of Android? 2.2
On what phone? HTC Desire

Hi
I've been using Zepyhr HxM with MyTracks to record heart rate, and it has been 
working perfectly up to now. Unfortunately MyTracks 1.1.6 does no longer 
connect to Zephyr.I've done a bluetooth unpair-paired with my HTC Desire 
(Android 2.2), and the phone discovers and pairs perfectly but MyTracks still 
doesn't see the Zephyr
Any clues?

Attached is the log,  collected just after starting MYTRACKS with the Zephyr 
strapped on my chest,  bluetooth activated on the phone 

Cheers
Gunnar 

Original issue reported on code.google.com by gunnar.t...@gmail.com on 7 Jun 2011 at 3:23

Attachments:

GoogleCodeExporter commented 9 years ago
I don't see anything worrisome in the logs.  Perhaps we will need to add some 
logging to the Zephyr parser.  Are there different models of Zephyr?

Original comment by sandordo...@google.com on 10 Jun 2011 at 3:27

GoogleCodeExporter commented 9 years ago
I'm not aware of different Zephyr models.

If I remember correctly, I think the problem with MyTracks not recognizing
the Zephyr started when 1.1.5 was introduced, but at that time I did only a
few rides.

Can I d'load the 1.1.4 from somewhere, to give it a try?

Original comment by gunnar.t...@gmail.com on 10 Jun 2011 at 6:55

GoogleCodeExporter commented 9 years ago
FYI
I downloaded 1.1.4, and it recognizes Zephyr without any problem. So it
seems you did introduce a bug from 1.1.5 onwards...

I'll stick with 1.1.4 until a fix/update is available

Original comment by gunnar.t...@gmail.com on 10 Jun 2011 at 7:40

GoogleCodeExporter commented 9 years ago
i have the same error here, hxm not working in >1.1.5

Original comment by ble...@gmail.com on 13 Jun 2011 at 8:10

GoogleCodeExporter commented 9 years ago
Confirm that Zephyr gives sensor status NONE on 1.1.5 and 1.1.6.  
Zephyr works fine with another heart rate app.

Original comment by dliebs...@gmail.com on 15 Jun 2011 at 12:12

GoogleCodeExporter commented 9 years ago
Currently I don't have my Zephyr HxM around to see if it works for me in 1.1.5.

I'm wondering why the logs don't contain any Bluetooth messages. Shouldn't 
there be some messages during connection from the Bluetooth or SPP Service?

Original comment by n...@nclm.de on 15 Jun 2011 at 7:22

GoogleCodeExporter commented 9 years ago
Hi guys
I never reselected the sensor type after installing a new version. Did so just 
now, and out of the blue it connected to my Zephyr sensor and now it works as 
it should
 :-) 
but as with previous MyTracks versions (1.1.4 and below) I didn't have to 
reselect the sensor, so I never thought of doing this after installing. I was 
thinking that all personal settings and configurations is kept from the 
previous version when installing (doesn't it display a message saying something 
like that when installing the newer version...?)

I'm so sorry about any confusion I may have caused by this, my apologies to the 
MyTracks developers team! Keep up the good work!

Guess this issue may be closed now...

cheers
Gunnar

Original comment by gunnar.t...@gmail.com on 1 Jul 2011 at 7:41

GoogleCodeExporter commented 9 years ago
Can anyone else confirm that reselecting the sensor solves this issue?

Original comment by n...@nclm.de on 1 Jul 2011 at 9:18

GoogleCodeExporter commented 9 years ago
Confirmed that Zephyr HxM works with MyTracks 1.1.9.

Original comment by jshih@google.com on 29 Sep 2011 at 2:59