Issue 1348 in mytracks: Change from old ANT API to new ANT+ Plugins API

21 views
Skip to first unread message

mytr...@googlecode.com

unread,
Aug 7, 2013, 5:24:34 PM8/7/13
to mytrac...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Enhancement

New issue 1348 by mikmiste...@gmail.com: Change from old ANT API to new
ANT+ Plugins API
http://code.google.com/p/mytracks/issues/detail?id=1348

Convert ANT sensor code to use the new ANT+ Plugins API. The new ANT+
Plugins API contains easy to use plugins that handle the implementation of
the ANT protocol such as connecting to the device, interpreting data,
sending commands, and managing the connection. Using the API roughly
involves implementing result and state receivers, passing these receivers
into a requestAccess method that initiates a connection to a device. Data
can then be gathered from the connected device by subscribing to events
which will pass along the device data such as heart rate, speed etc.
depending on which device you are connecting to.

Switching to use the ANT+ Plugins API will ensure full and complete
compatibility with ANT+ devices as the API also handles the implementation
of the device profiles. As the API grows and more ANT+ device profiles are
added, the effort to add support for these devices will be minimal with no
effort being spent on decoding the ANT messages or managing the channel;
all this is done by the API.

The new API also allows mytracks to run concurrently with other apps using
ANT rather than seizing control of the entire ANT interface and will only
use the ANT channels it requires, allowing other apps to use the remaining
ANT channels.

The current version of the ANT+ Plugins API supports the Heart Rate, Speed
and Distance profiles required by mytracks. The plugins for the Bike Speed,
Bike Cadence, Combined Bike Speed and Cadence and Bike Power are now in
beta testing and can be acquired by developers
(http://www.thisisant.com/forum/viewthread/4057/). The beta version of the
ANT+ Plugins API contains all the functionality and device profiles
required by mytracks.

If the main distribution of mytracks is interested in switching to the new
ANT+ API, I am willing to work on this issue.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

mytr...@googlecode.com

unread,
Aug 21, 2013, 2:42:13 PM8/21/13
to mytrac...@googlegroups.com

Comment #1 on issue 1348 by rohanlma...@gmail.com: Change from old ANT API
Switching to the ANT+ API (using the provided ANT+ device profile
implementations) before September 30 2013 would also allow for free ANT+
certification, adding MyTracks to the list at thisisant.com/directory and
allowing MyTracks to claim ANT+ support (it's not permitted until then).

mytr...@googlecode.com

unread,
Sep 19, 2013, 4:33:51 PM9/19/13
to mytrac...@googlegroups.com

Comment #2 on issue 1348 by mikmiste...@gmail.com: Change from old ANT API
Mercurial clone with changes to be reviewed:
https://code.google.com/p/mikmister02-mytracks-antplus-pluginapi/

Revisions to be pulled from that clone (or "all"):
- all

Purpose of code changes on the clone:
- switching ANT+ Sensor code to use the new ANT+ Plugin API while
maintaining the existing ANT+ sensor support functionality.

When reviewing my code changes, please focus on:
- all files in com.google.android.apps.mytracks.services.sensor.ant (added,
deleted and modified).
- com.google.android.apps.mytracks.services.sensor.SensorManager.java

Did you run the unit tests?
In Eclipse, select the 'MyTracksTest' project, right click, 'Run As' ->
'Android JUnit Test'.
- No, no specific ANT sensor tests.


Did you allow others to review code on your clone?
- Yes. I was unable to create the clone in the way described in the
development process as the "Create Clone" button no longer exists.

mytr...@googlecode.com

unread,
Mar 23, 2014, 1:39:17 PM3/23/14
to mytrac...@googlegroups.com

Comment #3 on issue 1348 by lukas...@gmail.com: Change from old ANT API to
Any changes on that? As I foumd that Endomondo started to work really nice
with ant+ after switch to new API. Would be nice to have this in mytracks.

mytr...@googlecode.com

unread,
Oct 14, 2014, 4:33:20 PM10/14/14
to mytrac...@googlegroups.com

Comment #4 on issue 1348 by js...@google.com: Change from old ANT API to
new ANT+ Plugins API
https://code.google.com/p/mytracks/issues/detail?id=1348

Issue 1469 has been merged into this issue.

mytr...@googlecode.com

unread,
Oct 14, 2014, 4:44:10 PM10/14/14
to mytrac...@googlegroups.com

Comment #5 on issue 1348 by js...@google.com: Change from old ANT API to
Issue 1276 has been merged into this issue.

mytr...@googlecode.com

unread,
Jul 3, 2015, 11:17:42 PM7/3/15
to mytrac...@googlegroups.com

Comment #6 on issue 1348 by viper500...@gmail.com: Change from old ANT API
Up any news?

Devices samsung s5 and garmin footpod / garmin tempe
Reply all
Reply to author
Forward
0 new messages