12-25-2016 11:39
12-25-2016 11:39
Have upgraded from the Charge HR (it died a few months ago) to the Blaze. However, the Charge HR 101 guide red link bar (which is dead BTW) lingers on in the Android app on my Note 4. Everything is functional, it's just annoying. How can I get this irrelevant red bar off of my app? Thx.
Answered! Go to the Best Answer.
12-26-2016 14:20
12-26-2016 14:20
Wendy -
I contacted customer service and they told me to tap on the Blaze icon in the upper right corner of the app, and select the Charge icon that came up under that submenu and delete it. That idea didn't work because the Charge icon was not there in the first place.
I tried logging out and logging back in, and that was the solution: so simple, right?
Thanks for your suggestions. I hope this helps somebody in the future.
12-25-2016 11:46
12-25-2016 11:46
Have you removed the Charge HR from your phone?
If not click on the device name and then you shold see a trash can to remove it
Wendy | CA | Moto G6 Android
Want to discuss ways to increase your activity? Visit the Lifestyle Forum
12-25-2016 11:48
12-25-2016 11:48
You could try and shut down the phone turn it back on and see if it goes away
Or un-install the app and re-install it
If that does not work Contact Support
http://help.fitbit.com/?cu=1
Wendy | CA | Moto G6 Android
Want to discuss ways to increase your activity? Visit the Lifestyle Forum
12-25-2016 11:57
12-25-2016 11:57
Thanks for the suggestions Wendy -
I have removed the Charge from the Bluetooth pairing list, and restarted the phone, to no avail.
I have not deleted and reloaded the app, for fear of losing the last year's worth of data I have accumulated. Is there a way to backup the data before uninstalling / reinstalling the app?
12-26-2016 14:20
12-26-2016 14:20
Wendy -
I contacted customer service and they told me to tap on the Blaze icon in the upper right corner of the app, and select the Charge icon that came up under that submenu and delete it. That idea didn't work because the Charge icon was not there in the first place.
I tried logging out and logging back in, and that was the solution: so simple, right?
Thanks for your suggestions. I hope this helps somebody in the future.