I have the 235 ans mostly very good apart from tgr very inaccurate indoor run pace. Ru nning at 8:45 pace but 235 is onky showing 10:15 pace on my run. I have had this a couple of years, has it always been an inaccurate feature and is there any way to make it better?
If you purchase a footpod AND do some running using Indoor Run with the GPS set to ON you'll "re-Program" the Indoor Run function to your actual Stride Length. Just be aware, turn the GPS function OFF after every session running outdoors. Because if you forget just once and have the GPS turned on while using a treadmill inside a gym the lack of any real ground movement will reset your stride length to something between .1 meter and .5 meter and you'll have to do many runs with the footpod and GPS active to get your stride length back to it's actual value. BTW, I know this first hand due to making this exact mistake about 3 weeks ago. In my case it's because I like to have a record of my pace, cadence, and stride length when I take the dog for a walk and using Indoor Run for this allows me to record this data without the slower pace and frequent stops taking my VO2 Max and cutting it by 1/3 or more.
I don't know about Scooterv45's example - but I don't recall of late doing anything like that and my pacing is off at all paces... except for right around 8:30. If I treadmill at 9:00... is says pretty close to 8:35-8:40... if i run at 7:30 it says 8:20ish... if 7:00 it says 8:10. As far as I can tell it doesn't keep track of an array or lookup table of various stride rates and corresponding paces very well. not even a high low reset range. Seems like likely uses a standard offset based on your avg cadence vs avg pace and current cadence.
Essentially it doesn't handle very well that I run at 200-205spm at 6:40/mi.... but 190@ 8:40....and 188@9:00..... [email]185@9:20....lol[/email] has a hard time coping with pace = stride rate x stride length (you can change both...or just one.....to change pace)
