What research is needed? You had said that History was stored on the FulGaz server and refreshes to the app from there. It updates the date of each of the spurious entries updates, it doesn’t add more entries. Seems the problem is in your server, so it seems YOU need to fix the software on YOUR server?? If I delete it on the app it will just come back?
You weren’t optimistic re fixing it, so I quit using History and devised a workaround. Now I keep a pen & pad by the trainer, at the end of a session I write down the data I want from the screen and transfer it to my training log. Ride history is unusable.
At least two clocks run in a video, one stops during a pause (to adjust fans or use the bathroom), other doesn’t. Obviously a discrepancy of several MINUTES. During a ride the first is shown on the display and later in History, and I record them in my log The second shows in the post-ride email of ride data, which is why I used History instead. It’s unclear if 0’s from pauses are included in final averages (speed, watts, bpm), making the email’s values of those questionable.
So many bugs it’s like walking my dog in the woods in the summer. It seems somebody has been monkeying with the algorithm: for a while my times for the same route suddenly got a lot quicker than they had been, often with a LOWER average wattage and HR. And suspiciously faster than the original time (usually by Rob Bennett). I notice this because when entering a session into my log I usually copy/paste from a previous time I did that ride, changing only data that is different from the previous session.
Klem (FulGaz)
Team•
Sep 23
Confirmed on iOS. Looks like they are rides that I completed a long time ago, all showing as today’s date and with zero data:
Log in to comment and vote
Comments2
P Flory
Sep 23
What research is needed? You had said that History was stored on the FulGaz server and refreshes to the app from there. It updates the date of each of the spurious entries updates, it doesn’t add more entries. Seems the problem is in your server, so it seems YOU need to fix the software on YOUR server?? If I delete it on the app it will just come back?
You weren’t optimistic re fixing it, so I quit using History and devised a workaround. Now I keep a pen & pad by the trainer, at the end of a session I write down the data I want from the screen and transfer it to my training log. Ride history is unusable.
At least two clocks run in a video, one stops during a pause (to adjust fans or use the bathroom), other doesn’t. Obviously a discrepancy of several MINUTES. During a ride the first is shown on the display and later in History, and I record them in my log The second shows in the post-ride email of ride data, which is why I used History instead. It’s unclear if 0’s from pauses are included in final averages (speed, watts, bpm), making the email’s values of those questionable.
So many bugs it’s like walking my dog in the woods in the summer. It seems somebody has been monkeying with the algorithm: for a while my times for the same route suddenly got a lot quicker than they had been, often with a LOWER average wattage and HR. And suspiciously faster than the original time (usually by Rob Bennett). I notice this because when entering a session into my log I usually copy/paste from a previous time I did that ride, changing only data that is different from the previous session.
Klem (FulGaz)
Sep 23
Confirmed on iOS. Looks like they are rides that I completed a long time ago, all showing as today’s date and with zero data: