SEPTEMBER UPDATE: Dynastream released a fix for this in the ANT+ radio service 4.14, so that should be the end of the story, for now :-). Just get the latest radio service from google play. If it works, I suggest that you disable automatic updates.




JUNE UPDATE: Dynastream has finally confirmed the problem, at least for some devices. For LG and HTC phones, it seems to be an interplay between an update from the manufacturer and a limitation in the dynastream service. After some work, they have built a new radio service which should fix the problem. I have the APK, so If you're willing to install a beta version of their radio service, please contact me from the "contact" page above or via email, and I'll send it with instructions.


If your phone is not HTC / LG but you're affected by this problem (that basically ends up with a sequence of ANT_DISABLED notification in my log) please get in touch and send me a log, as it could be a different issue with the dynastream service.


A recent update to the dynastream services (ant+ radio service and ant+ usb service) is causing problems to some android devices. I don't have the full picture yet. So far, what I've seen is:

- some devices cycle between ant enabled / ant disabled
- some devices don't get the ant+ channel, so they can't progress
- there might be other cases that I have to understand / categorize

I'll try to contact the guys at dynastream, because it doesn't look like something I can fix on my side. My suggestions:

- as I always say: disable automatic update of the dynastream services. Do not blindly assume that I can fix things. Dynastream has its own strategy, and it is not well aligned with the needs of my app.

- if you have already upgraded, and are experiencing problems, downgrade. I suggest that you do not get the old services from unverified sources. Dynastream keeps an archive of previous versions on github, and the latest good one is here. You need to click on each service and then on "raw" to download the apk. After that, you have to uninstall the service and install the apk manually.

- I understand that some devices running lollipop do not accept the old services. At this stage, I don't have a fix for that.

update: this problem is fixed in Sportablet 7.8 / Uploader for Garmin 6.8. I've just pushed those versions to Google Play, so it may take a few hours for you guys to get them.

Yesterday the guys at Garmin Connect made some changes to their website. My app uses an "unofficial" integration, as access to the official Garmin API would require a 100x increase in sales to be economically sensible. Their update broke my integration.

I'm working on that. There were basically 4 issues to solve, and I've basically solved them all. I need more time to test the new version thoroughly.

- Please follow sportablet on facebook or twitter, or subscribe to the rss feed on this blog, or visit this blog periodically. I'm just one - I can either answer your emails or work on the app.

- If you send me an email, and while you're at it you ask me other questions about the app, please understand it's not the right time. I'm getting way too many emails when GC breaks down. Get in touch later on, thanks.

- Yeap, downrating the app in google play won't help a bit :-)

-----