Saturday evening, after entertaining my family with a slightly charred roast lamb joint but a perfectly acceptable bottle of vino (or two), I get an email from Nike. Apparently, if I could resurrect the long dead Nike+ Sportband, and push my sorry arse out of the door, complete with Sunday morning hangover, to complete a 10k of my choosing, I would soon be the proud owner of a freebie Nike Humanrace t-shirt.
Hard to resist a freebie t-shirt, so I left my visitors to rustle up their own breakfast and arranged to meet them in Kew Gardens approx 1hrs 20mins later.
Lovely day for running, providing you don’t have a pointy head or too much body jewellery.
I have a particularly round head and enjoy running through electrical storms and downpours but I was surprised to see quite so many other water babies running along the river. I searched for signs of commitment to the global humanrace but saw none, it seems that some folk don’t need freebies to run.
3 months on the sub-bench allowed the Nike+ Sportband to dry out sufficiently for me to read the screen again, but I thought it prudent to spin the screen round to the underside of my wrist to provide a little water protection. Pity I didn’t do the same for the garmin forerunner 405!
A few weeks ago I had a comment on my forerunner 405 review, warning me of short-circuiting type responses when the garmin bezel gets wet. Apparently a few reviewers had commented on the bezel bleeping and flicking through screens randomly when exposed to water or sweat. I was quick to reject that the forerunner 405 had a problem but I should have kept my mouth shut.
Running through this downpour left my watch bleeping like crazy as I tried to stop the timer and move it off the training mode. In the end I had to wait for it to run out of battery life to switch off. Serious design flaw here.
I’ve had the forerunner 405 for a few months now and as it’s pretty much rained non-stop throughout the whole of summer, I find it hard to believe that I didn’t notice the problem earlier. I’m wondering if it could possibly be related to the recent firmware I downloaded – doesn’t really sound like a software issue but I’ve upgraded to the latest update just in case.