Bluetooth does not reconnect if the Bluetooth connection is lost

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start recording with Zephyr HxM. 
2. Break Bluetooth connection. This happens in use when the Zephyr HxM stops 
transmitting because it has a poor connection with the skin. The problem can be 
reproduced during testing by unclipping the HxM from the strap (but it takes a 
while to stop transmitting) or more quickly by moving out of Bluetooth range.
3. After a while the sensor state goes to none.
4. Reestablish Bluetooth signal from the HxM
5. My Tracks does not reconnect.

What is the expected output? What do you see instead?
Expect My Tracks to reconnect when the Bluetooth signal reappears. 

Endomondo is an example of an application that works with the  Bluetooth HxM 
device more reliably. Whenever it expects a Bluetooth signal it will 
periodically try to connect.

What version of MyTracks are you using? On what version of Android? 
1.1.9

On what phone?
Xperia ARC but I think its the same on all handsets.

If possible please provide a log.  

No log provided.

Please provide any additional information here:
I had intended more testing prior to reporting but I was prompted by a comment 
today from k.turek at 
https://groups.google.com/d/msg/mytracks/tUcMm-Z3m_w/QEChXspH1ikJ to report the 
issue before testing of symptoms was complete.

There is also another relevant comment from k.turek and response at 
https://groups.google.com/d/msg/mytracks/GPq92Wb_V6A/_EY8BV9I_d8J

Original issue reported on code.google.com by kenep...@gmail.com on 11 Oct 2011 at 9:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This is a fairly serious deficit in the Bluetooth behavior, one that 
effectively prevents MyTracks from being usable as a consolidated 
GPS-and-heartrate application. With the current state of the app, any momentary 
drop in Bluetooth connectivity results in a permanent loss of further heart 
rate data for the track, since reconnection only seems to occur when the track 
is stopped, and the "pause" feature has not yet been implemented.

I have contacted Zephyr on this, hopefully they will get involved as well to 
see if there's a way to solve this through collaboration from both ends?

Original comment by jasonpor...@gmail.com on 14 Jun 2012 at 3:04

[GoogleCodeExporter]

Issue 819 has been merged into this issue.

Original comment by jshih@google.com on 21 Jun 2012 at 10:11

[GoogleCodeExporter]

Original comment by jshih@google.com on 23 Jun 2012 at 1:30

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed in My Tracks 2.0.

Original comment by jshih@google.com on 23 Jun 2012 at 5:23

• Changed state: Fixed