Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V800 downloader stopped extracting HRM and GPX files #25

Open
psimps opened this issue Dec 18, 2016 · 2 comments
Open

V800 downloader stopped extracting HRM and GPX files #25

psimps opened this issue Dec 18, 2016 · 2 comments

Comments

@psimps
Copy link

psimps commented Dec 18, 2016

Hi Paul

20161210123908_0.zip
I've been using the V800 downloader without an issue since Aug until today. Polar recently released a new update for the V800 and my watch updated itself when I sync'd it the other week. I've just tried to extract the files and while V800 downloader can see the exercise file dates and allows me to select them and start the download, but no individual .hrm or .gpx files are extracted as before and I now get a folder with a whole load of BPB files and GZB files for the route data.
Have you come across this before when polar released a update? I've attached a zip folder of the folder that I now get instead of individual files for information.

Regards

Paul.

Paul.

@pcolby
Copy link

pcolby commented Jan 10, 2017

Hi @psimps,

Yeah, I've seen / heard of Polar breaking things with firmware updates quite a bit - even breaking their own software and devices. 😠

I myself haven't updated past 1.7.27 yet - I like to wait a little when Polar releases new firmewares, since they've broken watches on a few occasions. Indeed, the 1.8.15 firmware, which you were probably using, got withdrawn. 😒

Have you tried the new 1.8.31? It may have fixed the issue.

I haven't heard of any lasting issues with 1.8.31, so I'll upgrade my v800 shortly, and see how it goes... 😨

@psimps
Copy link
Author

psimps commented Jan 11, 2017

Hi Paul

Yes, I've updated my V800 with the new 1.8.31 release from polar and that does indeed seemed to have fixed the issue :-)
Fingers crossed that your V800 will also be fine when you update it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants