help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ECG reports not showing up.

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎04-24-2021 22:24 - edited ‎04-24-2021 22:25

‎04-24-2021 22:24 - edited ‎04-24-2021 22:25

I've been using the ECG app quite a lot, and as recently as 2 days ago, after completing an ECG 30 second run, syncing with my phone, I could get a one page copy of the ECG through my phone. Tonight, the ECG reports don't show up even after multiple syncs, and restarting the sense device. I've gone back to do additional ECG runs, and nothing is showing up in phone newer than 2 days ago.

 

While I'm at this, perhaps I should mention that the path from getting a report to show up in the list to a PDF or a printed page could really really use some streamlining. I have to select a reading, tell it to make a pdf, wait for the pop up, press view, select share, select print, wait for a connection to the printer, select print again. Why not a one button print, save to file (with the date and time in the file name), or email, now that we're in the 21st century?

 

Best Answer
Labels:
0 Votes
1 REPLY 1

‎04-25-2021 21:25

‎04-25-2021 21:25

After the above, plus a few "Force Stop" cycles and a few phone restarts and it finally seems to be operating again. Fitbit needs to take a course in remedial programming because they seem to be ignoring return status in some of their procedure calls - this was failing with ZERO error messages.

 

Maybe now that they're part of Google, someone from the mothership can fix their awful android app.

 

Best Answer
0 Votes