Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

   

Que Re Messaging Overflow ( Android )

Rank

Total Posts: 7

Joined 2013-09-23

PM

I'm not sure if anyone has seen this, and what the cause / resolution would be. I am using the latest service via the marketplace ( 4.02.00 )

Background:

I have a service interacting with the ANT service. As various activities occur, over time the callbacks from the ant service appear to become more frequent. For example, I set various setting on each beacon cycle such as ChannelPeriod, ChannelFrequency, ChannelTimeout etc... Each one of these is processed and returns a success /fail to my onReceive. At first there is one response per call, then over time it becomes 2 responses per call, 3,4 etc... and at some point a few hours later things become unwell.

At the end of this post is an example from my logcat showing a flurry of responses from the ant service via my onReceive to a single call to ChannelPeriod,ChannelFrequency and ChannelTimeout.

If anyone has seen this, knows the cause or how to resolve this and could share it would be very much appreciated.

thanks,

Andy

08-31 16:28:33.472: D/AntCommunicator(9369): CHANNEL PERIOD CHANGED SUCCESSFULLY
08-31 16:28:33.472: D/AntCommunicator(9369): CHANNEL PERIOD CHANGED SUCCESSFULLY
08-31 16:28:33.472: D/AntCommunicator(9369): CHANNEL PERIOD CHANGED SUCCESSFULLY
08-31 16:28:33.472: D/AntCommunicator(9369): CHANNEL PERIOD CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL FREQ CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL FREQ CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL FREQ CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL FREQ CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): CHANNEL TIMEOUT CHANGED SUCCESSFULLY
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID
08-31 16:28:33.482: D/AntCommunicator(9369): MESSAGE NOT INTERPRETED:com.dsi.ant.intent.action.ANT_RX_MESSAGE_ACTION MESG_RESPONSE_EVENT_ID

[ note: Snipped, this went on for miles ]
     
Rank

Total Posts: 7

Joined 2013-09-23

PM

In case it can help others who run into this, thanks to folks at DynaStream it appears that I may have old code within this project and they have helped potentially to identify this. Very much appreciated.