Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ionic last lap time bug when battery dies

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

So, today I went for a walk with my Fitbit Ionic v27.31.1.29. I was intentionally overtaxing it, by playing music via Bluetooth, using the GPS, and leaving the screen in always-on mode. The battery dying is not my complaint; it was actually the purpose of my testing today, as I wanted to know how it would stack up to a marathon with all that enabled. 

 

The problem is that, since it was in Exercise mode (walking) when the battery died, it apparently compared the time when it died with the time when it charged enough to come back to life and I powered it back on. It then listed my final .34 miles as taking 219 minutes, which kinda killed my overall average time, making it harder for me to plot realistic data. Fitbit.JPG

 

So, there's clearly some sort of bug in that calculation. Just reporting it. Not looking for advice on "how do I make it not do this." (By not running my battery down. Got it.) Not looking for advice on preserving battery life. (Again - got it.) Just reporting a bug with version 27.31.1.29

 

Thanks!

Mike

Best Answer
0 Votes
5 REPLIES 5

@MikeSimone, the problem is probably related to fact that the GPS does not function with the battery below 25%.  I always ensure mine is charged before I leave the house for that reason.

Best Answer
0 Votes

While I thank you for taking the time to respond, I actually built in "don't respond with that" into my initial bug report. The second sentence was "I was specifically overtaxing it to test this scenario". 

Best Answer
0 Votes

@MikeSimonewrote:

While I thank you for taking the time to respond, I actually built in "don't respond with that" into my initial bug report. The second sentence was "I was specifically overtaxing it to test this scenario". 


Sorry, @MikeSimone, I won't bother responding to any more of your posts. Didn't mean to bother you with known facts, not a bug.

Best Answer
0 Votes

That's ideal, some you neither read the whole post, nor understand bug testing. There wasn't even a question in my post, further removing your need for an "answer", and demonstrating that your reading comprehension is lacking.

And now you'll post a threat of violence against me, because that's how comment sections work. I'll be sure to ignore you.

 

For the Fitbit developers, however, the when the battery hits zero, it should assume the exercise more ended there, rather than continuing to add time to the activity until the recharge is complete.

Best Answer

Mike, my experience and expectations were very similar to yours. 

 

While I wasn't trying to make it happen, it went flat anyway.  As I was on a known route I thought "never mind, I'll manually add the rest of my run to strava using my average pace". 

 

So I finished my run, trying to keep my pace consistent (if you can do that without a watch?), only to find my average pace was all screwed up because my run didn't finish when the battery died. 

Best Answer