Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

   

Watch Downloader broken !

Rank

Total Posts: 11

Joined 2014-06-18

PM

Hello,

I'm using watch downloader functionnality for a while and it worked well, but since the update of ANT Radio Service and ANT+ Plugins Service, it's not working anymore.

I have the issue and all my users too, whatever their devices !

I downloaded the last version of ANT+ Plugin sampler, activated all logs with ANT Service Settings App and here is what I get:

02-14 15:25:55.664: D/AntPluginService(11598): BBC30400: ReqAcc Handler received: 0
02-14 15:25:55.664: D/AntPluginService(11598): BBC30400: Requesting PluginLib reports as v.3.4.0
02-14 15:25:55.724: I/AdapterProvider(9834): Built-in ANT Service detected: ANT+ Enabler
02-14 15:25:55.724: I/AdapterProvider(9834): Checking for service libraries.
02-14 15:25:55.734: I/ANTAidlInterface(9834): initService: Bound with ANT HAL Service: false
02-14 15:25:55.734: D/AntPluginService(11598): BBC30400: ReqAcc Handler received: 0
02-14 15:25:55.734: D/AntPluginService(11598): BBC30400: Requesting PluginLib reports as v.3.4.0
02-14 15:25:55.734: V/AntPluginService(11598): BBC30400: ReqAcc Mode: 300
02-14 15:25:55.734: I/AntChannelProviderImpl(9834): Acquiring channel by capabilities...
02-14 15:25:55.734: I/AntChannelProviderImpl(9834): Service is not initialized
02-14 15:25:55.734: W/ActivityManager(983): Unable to start service Intent { act=com.dsi.ant.server.IAntHal cmp=com.dsi.ant.server/.AntService } U=0: not found
02-14 15:25:55.934: I/AntChannelProviderImpl(9834): Acquiring channel by capabilities...
02-14 15:25:55.934: I/AntChannelProviderImpl(9834): Service is not initialized
02-14 15:25:56.134: I/AntChannelProviderImpl(9834): Acquiring channel by capabilities...
....
....
....
02-14 15:26:10.354: I/AntChannelProviderImpl(9834): Service is not initialized
02-14 15:26:10.564: I/AntChannelProviderImpl(9834): Acquiring channel by capabilities...
02-14 15:26:10.564: I/AntChannelProviderImpl(9834): Service is not initialized
02-14 15:26:10.764: E/AntPluginService(11598): BBC30400: Acquire channel stuck in acquire loop for 15s, aborting.
02-14 15:26:10.764: V/AntPluginPcc(9426): BBD30400: ReqAcc Handler received: -4
02-14 15:26:10.764: W/AntPluginPcc(9426): BBD30400: RequestAccess failed: OTHER_FAILURE
02-14 15:26:10.764: D/AntPluginService(11598): BBC30400: ReqAcc Handler received: 1
02-14 15:26:10.764: D/AntPluginService(11598): BBC30400: Requesting PluginLib reports as v.null
02-14 15:26:10.784: V/AntPluginService(11598): BBC30400: Entering OnDestroy()
02-14 15:26:10.784: I/ANTAidlInterface(9834): ANT HAL Service was not connected
02-14 15:26:10.804: E/ActivityThread(9834): Service com.dsi.ant.service.AntRadioService has leaked ServiceConnection com.dsi.ant.chip.hal.AntAidlInterface$3@42fbf018 that was originally bound here
02-14 15:26:10.804: E/ActivityThread(9834): android.app.ServiceConnectionLeaked: Service com.dsi.ant.service.AntRadioService has leaked ServiceConnection com.dsi.ant.chip.hal.AntAidlInterface$3@42fbf018 that was originally bound here
02-14 15:26:10.804: E/ActivityThread(9834): at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:989)
02-14 15:26:10.804: E/ActivityThread(9834): at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:883)
02-14 15:26:10.804: E/ActivityThread(9834): at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1649)
02-14 15:26:10.804: E/ActivityThread(9834): at android.app.ContextImpl.bindService(ContextImpl.java:1632)
02-14 15:26:10.804: E/ActivityThread(9834): at android.content.ContextWrapper.bindService(ContextWrapper.java:517)
02-14 15:26:10.804: E/ActivityThread(9834): at com.dsi.ant.chip.hal.AntAidlInterface.initService(AntAidlInterface.java:538)
02-14 15:26:10.804: E/ActivityThread(9834): at com.dsi.ant.chip.hal.AntAidlInterface.init(AntAidlInterface.java:239)
02-14 15:26:10.804: E/ActivityThread(9834): at com.dsi.ant.adapter.AdapterProvider$ChipInitProcess.run(AdapterProvider.java:223)
02-14 15:26:10.804: E/ActivityThread(9834): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
02-14 15:26:10.804: E/ActivityThread(9834): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
02-14 15:26:10.804: E/ActivityThread(9834): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
02-14 15:26:10.804: E/ActivityThread(9834): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
02-14 15:26:10.804: E/ActivityThread(9834): at java.lang.Thread.run(Thread.java:841)

Do you agree with me that it's critical ?

Thanks.      
RankRankRankRank

Total Posts: 313

Joined 2011-09-12

PM

Yes, I agree this is critical. However, this is an error with a third party app that we do not support. The ANT+ Enabler app is not an official ANT+ app. You should contact the developer to fix it or suggest they contact us for a resolution. Android 5.0 changed some security restrictions for binding to other services, I am guessing our update to follow the recommended approach is now restricting the approach the ANT+ enabler uses to pretend to be an ANT service.

To avoid this in the future please subscribe as a watcher to our GitHub repo so you can test beta releases. For example, this last release was available for download almost two months ago.      

Signature

Dynastream Developer

Rank

Total Posts: 11

Joined 2014-06-18

PM

Thanks for your feedback.      
RankRankRankRank

Total Posts: 313

Joined 2011-09-12

PM

Just FYI, we are in touch with the developer of the ANT Enabler and are working out a solution. For now if you uninstall the newest ANT Radio Service, you can install the last version 4.7.0 from https://github.com/ant-wireless/ANT-Android-SDKs/tree/release/C.B3-P.B2/ANT_Android_SDK/Services

Edit: The one to install is https://github.com/ant-wireless/ANT-Android-SDKs/blob/release/C.B3-P.B2/ANT_Android_SDK/Services/Android_ANTRadioService_4-7-0.apk
     

Signature

Dynastream Developer

RankRankRankRank

Total Posts: 313

Joined 2011-09-12

PM

To everyone using the ANT Enabler, we just pushed out a new ANT Radio Service version, 4.12.0, to the Play Store that will restore support. You can wait on the Play Store takes several hours to push updates or you can download it directly from https://github.com/ant-wireless/ANT-Android-SDKs/tree/master/ANT_Android_SDK/Services Thank.s!      

Signature

Dynastream Developer

Rank

Total Posts: 3

Joined 2015-03-02

PM

ShaneG - 26 February 2015 06:48 PM
To everyone using the ANT Enabler, we just pushed out a new ANT Radio Service version, 4.12.0, to the Play Store that will restore support. You can wait on the Play Store takes several hours to push updates or you can download it directly from https://github.com/ant-wireless/ANT-Android-SDKs/tree/master/ANT_Android_SDK/Services Thank.s!


while this helped with actual connectivity, there still seems to be an issue - at least with my device. i'm using an ANT+ HRM and i'm able to connect, however the data seems to freeze (actual heart rate) after connecting initially; connecting at 48BPM means it'll only show/register 48BPM the entire connected time.

reverting back to the 4.0.7 (or the one posted above for a quick-fix) does fix this problem, so there's still an issue with ANT Enabler and/or the latest Radio - at least for me.

rob      
RankRankRankRank

Total Posts: 313

Joined 2011-09-12

PM

Hi Rob,
What app are you using to test it?      

Signature

Dynastream Developer

Rank

Total Posts: 3

Joined 2015-03-02

PM

ANT+ Demo (same dev as ant enabler) and Endomondo.      
RankRankRankRank

Total Posts: 313

Joined 2011-09-12

PM

The ANT Enabler guy doesn't make an ANT+ Demo, I am guessing you are referring to our ANT+ Demo https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo&hl=en?

We do not see this issue on phones without ANT Enabler using ANT+ Demo or Endomondo. If it is an ANT Enabler issue I suggest you email that developer to his email on the Play Store listing.

It also might be possible that your heart rate strap isn't transmitting data as you expect. Make sure your contacts are sufficiently moistened and your battery isn't dead. One way you can tell if you are getting live data is to start the app and setup receiving data from the heart rate strap, then remove the HRM battery for 10-20s - wait for the ANT+ Demo display to say 'searching',then replace the battery and see what value is present when the data resumes.      

Signature

Dynastream Developer

Rank

Total Posts: 3

Joined 2015-03-02

PM

ShaneG - 02 March 2015 05:13 PM
The ANT Enabler guy doesn't make an ANT+ Demo, I am guessing you are referring to our ANT+ Demo https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo&hl=en?

We do not see this issue on phones without ANT Enabler using ANT+ Demo or Endomondo. If it is an ANT Enabler issue I suggest you email that developer to his email on the Play Store listing.

It also might be possible that your heart rate strap isn't transmitting data as you expect. Make sure your contacts are sufficiently moistened and your battery isn't dead. One way you can tell if you are getting live data is to start the app and setup receiving data from the heart rate strap, then remove the HRM battery for 10-20s - wait for the ANT+ Demo display to say 'searching',then replace the battery and see what value is present when the data resumes.


edit: my apologies, yes, your ant+ demo. the issue persists with your demo and endomondo, though...

thing is, and i did this WHILE on the recumbent bike today lol: uninstalled most recent radio service update, reinstalled the last known working one (mentioned above), and my HRM was working properly again. definitely not the device itself with that update...      
RankRankRankRank

Total Posts: 313

Joined 2011-09-12

PM

Hi fobert,
Sorry for the long follow up time, but are you familiar enough with what logcat is to be able to send us some logs?      

Signature

Dynastream Developer