In Android 5.0.1, selecting ANT+ sensor in Settings crashes My Tracks

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install current ANT+ Enabler (v2.0.5)with Bluetooth Patch (v1.07) 
2. Launch My Tracks with Sensor set to "None" and begin recording a new track
3. Change Sensor setting from None to ANT+

What is the expected output? My Tracks should begin logging data from  ANT+ 
Heart Rate Sensor (Garmin)when this is present.
What do you see instead? Crash Notification "Unfortunately, My Tracks has 
stopped". 

The screen offers to Report the Crash to Google, which I have done several 
times. However, it does not seem to let me save a copy. 
Partial Stack trace is: 

"Caused by java.lang.IllegalArguementException:Service Intent must be explicit: 
Intent 
{act=com.dsi.ant.IAnt_6} 
at
Android.app.ContextImpl.validateServiceIntent(ContextImpl.java:1674)

...
at
com.google.android.apps.mytracks.services.sensors.ant.AntSensorMannager.setUpCha
nnel(MT:131)

... several more "at"

This crash occurs whether or not any ANT+ sensor is actually present. Just 
switching the My Tracks Sensor Setting to "ANT+" is sufficient to make it occur 
in either case.  The crash gets "reversed" and My Tracks begins running again 
if the Sensor Setting is switched back to :"None"

Separately from the issue with My Tracks, the Garmin Heart Rate Sensor is 
detected normally by ANT+ Plugins Service and is able to send HRT data to the 
ANT+ Demo app with no problem. This would appear to indicate that the bug is in 
the the ANT+ interface of My Tracks, rather than in ANT+ enabler

What version of MyTracks are you using? 2.0.9
On what version of Android? Android 5.0.1 LRX22C
On what phone? Nexus 5

If possible please provide a log by uploading here.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by djvn...@gmail.com on 4 Feb 2015 at 6:43

[GoogleCodeExporter]

I have this same issue using a Samsung Note 3. 

Original comment by Daniel.A...@gmail.com on 22 May 2015 at 8:29

[GoogleCodeExporter]

Same issue on my Samsung S5
Changing sensor setting from None to Ant+, then starting to record a track, 
crashes My Tracks

Original comment by bob...@zivix.net on 22 May 2015 at 3:05

[GoogleCodeExporter]

Same issue on Samsung S4 and S6

Original comment by Sergei.E...@gmail.com on 22 May 2015 at 11:55

[GoogleCodeExporter]

Same Issue on Samsung Galaxy S5!!!

Original comment by carusos...@gmail.com on 25 May 2015 at 9:47

[GoogleCodeExporter]

Same issue on Sony Xperia Z1 :-(

Original comment by nikekrun...@gmail.com on 3 Jun 2015 at 4:35

[GoogleCodeExporter]

I have since found the problem can be resolved by reverting from Android 5
to Android 4. 4. 4. Not a great solution but at least it does resolve it
temporarily. Moreover it does demonstrate that the problem lies in the Ant+
interface of Android 5 and not with any of the Ant+ utilities.

Original comment by djvn...@gmail.com on 7 Jun 2015 at 4:41

[GoogleCodeExporter]

djvn...@gmail.com This solution is unacceptable.

In the case of Nexus 5 this is a problem in the app My Tracks and Android 5 too.

I use other apps - Orux Maps and Pulsometer - that work seamlessly with Ant+ 
through patch called Ant+ Enabler. 

The fact is that app Google My Tracks is not working even through patch Ant+ 
Enabler.

It is an annoying flaw we need paid third-party patches to enable the Nexus 5 
Ant+ and there deficiencies in ecosystem apps like My Tracks.

That's a shame and we need support and immediate correction.

Original comment by ofirgo...@gmail.com on 7 Jun 2015 at 5:28