Adding code blocks to posts

One of the things I hate about this blogging platform is there's no easy way to do a code block, and support for entering code is piss poor. Tried the instructions on this blog post and it seems to work, although I don't like that I have to dick around with the HTML.

echo none > /sys/class/leds/led0/trigger
echo 1 > /sys/class/leds/led0/brightness
sleep 1
echo 0 > /sys/class/leds/led0/brightness

It's a pain in the fucking ass, you have to edit the HTML and add exactly the right "pre" tags around your code, but at least there's something. I'm still looking for a blogging platform which provides:

• Easy GUI editor
• I don't have to host anything
• Ability to easily handle code
• Ability to include images without having to copy locations

So far this seems to be a trivial list but I'm not finding anything that's really winning me over.

Initial Hammerhead One review

Warning! This review is long. You've been warned.

I finally received my Hammerhead One a week or two ago. This thing's been a long time in the making, starting as a kickstarter (or one of those crowdfunding sites, I'm too lazy to go back and look it up) that I was really excited about. If you're not familiar with a Hammerhead One, it's a bicycle navigation device - here's the manufacturer's own video:

Hammerhead One demo video

It's a really, really cool concept, so I was more than happy to back them.

The process took a while. I knew this from the start, but it certainly seemed to go on quite some time. They were good with updates to the process, but I quickly learned that "we think we'll be shipping it by {insert some point in the near future}" statements were not terribly likely. Eventually, I decided "okay, it'll happen at some point, and it'll be a pleasant surprise when it does". Finally, about a month ago I received an update message that said they'd be shipping out soon. It showed up on my porch one day, and I was pretty stoked!

Initial thoughts

• It's a clean design
  The final shipped design is awfully close to the initial designs, and is really clean. Non-cycling friends can (and have) made jokes about the new sex toy, but aside from that it's a pretty cool looking gadget.
  
  
• No documentation at all in the box?
  The box looks pretty good, but one thing I noticed right away is there's no documentation either in the box or on it. If you're going to ship a device with no form of instructions included, you'd better make damn sure it's super intuitive to use and has no gotchas. Turns out, this isn't the case.
  
  There was, however, a nice thank-you card which lists the names of all the initial supporters. Yep, I'm on there, along with two friends that I know supported it. Cool.
  
  The only instructions that I received with the unit came in the shipping email:
  
  "Once you have unboxed your Hammerhead we suggest you connect it to the app and update the Firmware immediately: This video will show you how to update the firmware, and here is an initial turn instruction guide."
  
  As this was the shipping email, I initially missed it, and as we'll see, that turns out to be not quite enough.
  
  
• Reusing the Garmin mount is a clever approach
  The mount on the Hammerhead uses a standard Garmin bike computer half-turn mount. It's simple, it works, and opens up the ability to use a bunch of other mounts.
  
  
• Sparse documentation online
  After some initial setup issues, I hit the "Help" link in the app which leads to their online FAQ. They've bolstered it quite a bit since I got mine, but at the time, it was really sparse. The only other thing I managed to find were the videos which we've already discussed.
  
  
• Setup video says iOS, no separate video for Android
  Although the app looks almost exactly the same between the two platforms, the setup video that they linked to in the shipping email clearly says "iOS" in the title. So I look for the Android version, and I don't find it. Good thing I know Android and iOS well enough to be able to translate what they're trying to do in the video. It's not hugely different (beyond it actually working in iOS - but more on that in the next section) but it's still different.
  
  
• No GPX import?
  Playing around with the app, it looks like a fairly basic navigation app. I find I get the best results planning rides using a computer and web-based tools instead of an app on the phone - and then being able to import that route into an app on the phone when it comes time to follow it. This doesn't appear to be an option, and it doesn't even look like I can use another tool and then import that path. I understand that this could lead to issues - if I give it a route that's not on its map, how will it know where to turn, and if I go off-route, how will it figure out how to re-route me? It's probably not a trivial solution, but I sure hope that they figure it out.
  
  

Android problems

I have two phones - my own Android (first gen Moto X) and an iPhone 6 from work. This turns out to be a good thing, because about two weeks into having my Hammerhead, I've still yet to get it working with the Android phone. I've discovered a bunch of fun things, and have been seriously frustrated up to this point, but so far their customer support has been pretty good. Here's a rundown of the problems I've discovered and not yet surmounted:

• You don't pair it with your phone like a normal Bluetooth device.
  If there were instructions, I might have known that before I started using it. Having missed the one paragraph of instructions in the shipping email, I figured "Okay, it's bluetooth. Let's get it paired up and see what this thing can do." So, I went to the phone's Bluetooth setup menu, just like I've done for all the other Bluetooth things that I have, and tried to set it up. This failed with an "invalid PIN" error. I checked the instructions I received for what to do in that situation and oh wait - I didn't get any. Hah.
  
  Turns out you have to do the pairing in the app. Why? Fucked if I know. I've got theories.
  
  
• If you manage to lock it up, the only way to reset it is leave it alone and let the battery run out.
  In the process of trying to figure out how to get it to talk to the phone (remembering that I missed the one paragraph of instructions with links to videos for a mobile OS that I was not using) I managed to lock it up. The device has one button which is ringed by light when it's on, and at some point this went solid greenish-blue and the device stopped responding at all. The phone wasn't able to see it anymore - it was locked up. With no troubleshooting instructions and nothing of use I could find on the FAQ (which was much less populated than it is now and had almost nothing about connectivity issues) I was left to my own troubleshooting steps. I'm a computer guy, I've got decent troubleshooting skills. The first thing I tried was to press and hold the button, as many electronic devices honor that as a "turn off regardless" indicator. Holding the button down for well over a minute made me think that wasn't the case. Tapping the button did nothing. There are screws on the back of the unit and I considered opening it up - they're just T-6 Torx, which I have - but at this point the thing is brand new and I decided I didn't really want to do that.
  
  Ultimately, I left it alone and let the battery die off. Once that happened, I could start trying to use it again, until I locked it up again and had to let it die all over again. Speaking with support, I was told that I could reset the unit by "Plug in the USB cable and hold the main button for 6 seconds. Then remove the USB cable and hold the main button for 3 seconds." This procedure kinda sucks since I need to have a USB cable on hand and leaves a bunch of questions unanswered:
• Do I keep holding the button when I unplug the USB or do I let it go?
• Does the USB cable have to be plugged into the wall, or would a cable by itself do the trick?
• Most importantly, why didn't it work with any variation of the procedure that I could think of?
  
  
• Removing the charging port cover isn't intuitive or documented
  The charging port cover is easy to find, at the bottom of the unit on the back. Getting it off is another matter. It looks like it should just slide off away from the bottom of the unit, but trying to do that by hand without forcing it wasn't resulting in anything. There's a tab on the back of the device that looked like maybe it needed to be depressed in order to let the cover slide off, and I tried that. Turns out that's exactly what you don't want to do as it keeps the cover in place and pressing on it increases the lock, not decreases it. I see the FAQ entry has been updated to state this now - but that wasn't there the other day when I tried it. Also, the FAQ entry had one single photo with an arrow on it pointing to the charging port. The problem here is that the photo looks like a quick shot with a cell phone camera in crappy lighting so the arrow points to an area on the phone you could have found on your own (I did) and the relevant point on the unit is a featureless blob of black, so you really don't get any information from the photo which isn't already obvious. See what I mean?

  

  Crappy white balance and exposure make this photo useless.

  
  
  With a T-shirt providing a dark background so it doesn't throw off the auto exposure and sunlight from the window by my desk, I managed to get this photo:

  

  Less than a minute of work and a much more useful photo.

  I didn't include the cover because I took that off and just left it off.
  
  I eventually managed to get the cover off by sticking the point of a screwdriver in the space around the tab that holds it in place and pushing it away in the direction I guessed was right.
  
  
• The charging light is hard to see
  When I first let it die off because it was locked up, and then plugged it in, no lights came on. Considering the thing is covered with LEDs, I was kinda surprised about that. No form of indication if it's charging or done? Fail.
  
  Well, turns out I was wrong. There's a small green LED on the side of the unit which shows when it's plugged in. I had initially missed it. Let's see why:

  

  The charging light is on. Can you see it?

  

  See it now? The viewing angle is quite shallow.

  I also don't think the light changes based on the charge level. It's just an indication that it's plugged in. So, is it fully charged? Well, the app can tell you that, but a simple flashing during charge, solid when fully charged would remove the need for the app.
  
  
• The firmware process isn't well documented or intuitive
  The only instructions for upgrading the firmware are on the iOS video. It just shows the procedure happening once and leaves out pretty important details. I managed to assemble the proper procedure from the video, the light sequence demo video, and other information I managed to find online.
  
  
• Lack of information on firmware versions
  Since the only place you can update the firmware is through the phone app, you never have to manually download it, and that's nice. However, there's no way to see what the current released version of firmware might be - or changelogs, or anything like that. As a computer guy, I'm used to things like this. For the general user, not a huge problem, but since they recently uploaded a video mentioning firmware 1.5, and I'm at 1.3.x, I have to assume that it hasn't been released because "Update firmware" is greyed out in the app. Or maybe something's broken. I can't tell.
  
  
• The Android app won't actually talk to my phone
  After finally managing to update the firmware on my device, I tried to use it with my Android phone. I can create route instructions, but when I try to ride it, I get the following error:

  

  "wait for some time." ?? Dafug?

  Despite "waiting for some time" - it never sees my Hammerhead.
  
  
• The Android app crashes repeatedly
  Related to the above point, when I click "Skip" on the "Connecting to Hammerhead" prompt above, the app closes and I get this:

  

  Yay, crashed!

  
  
  
• All of this works on my iPhone
  I guess we know where they spent all their development effort and QA testing.

Test drive on my commute to work

So yes, I know that my first test with this thing should be on a bike, not driving in a car, but time constraints combined with curiosity/impatience led my first test to be my driving commute to work. It's actually not awful because I know the roads between home and work pretty well so should be able to follow pretty close to the route the app suggests, and it'd be interesting to see how it handles things. The key, however, with anything that gives you directions is you should get familiar with it on roads and paths that you _know_ so you learn its quirks - you don't want to find these out blindly following it where you have no idea where you _should_ be going.

For this test,  I had the hammerhead propped up in front of my speedometer so I could see the lights out of my peripheral vision, and the iPhone was in my phone holder so I could see the route it had planned out for me.

• It really prefers bike paths to streets
  This isn't too surprising, since it's designed first and foremost for giving directions to road bikers. Still, the roads around my house are quite nice and cyclist friendly. Here's the way it suggested I start my ride:

  

  It's pretty, but a circuitous 2.8 miles.

  
  

  

  Perfectly valid route that's a full mile shorter.

  While the route it suggested is pretty and almost completely avoids any roads, the way I usually go is perfectly fine for cyclists and takes 1 mile off the ride before I've even gotten to Route 202.
  
  
• It prefers a shared-use path to a marked bike lane.
  Similar to above, Route 202 has a shared-use path that runs along side the road, separated by a fence. It's a nice way to go - but 202 also has marked bike paths on the road. If you chose to do that (admittedly, few cyclists do, but I have) it will confuse the app, frequently telling you to turn around and head back when the shared use path goes away from the road too far.

  

  Route 202 has bike lanes and a separate shared-use path. gmaps

  
  If you don't already know where you're going, the indication for a U-turn while you're heading the right way on a marked bike lane could be confusing as hell.
  
  If you do already know where you're going, then you don't really need a blinky thing on your handlebars telling you where to go, do you?
  
  
• The routing was pretty good for a cyclist in the area
  Ignoring wanting to use bike paths over roads and insisting on a U-turn when you don't follow it exactly, the routing was pretty good. There are some tricky areas for bikes on my commute, and it managed to avoid those pretty effectively.
  
  
• It tried to direct me over a bridge that has been closed for a month or two
  I use the Waze app for driving. It's a community-supported app that allows you to report problems on the road, including road closures. One of the routes I take to work has a bridge which is currently closed for repairs. I was able to tag the bridge as unavailable in the Waze app so that other folks knew to not go that way.
  
  Unfortunately, Hammerhead's map doesn't know this, and tried to direct me over the same bridge. When I took my usual detour around the closed bridge, the Hammerhead was diligently instructing me to make a U-turn for well over a half mile before it finally figured out the way I was actually going.
  
  
• The amount of pre-turn warning that you get seems to be based on distance from the turn
  Okay, this is kinda a bullshit observation since I was in a car, going far faster than the app was designed for, but the turn notifications I was getting happened *very* close to the turn. At bike speed, that'd be just fine, but adjusting the amount of warning based on the speed doesn't seem like it'd be terribly difficult. More of an observation than a real issue.
  
  
• Several indicated turns that weren't actual turns.
  Driving down a section of road where I had well over a mile to the next turn, it kept indicating left turns. Sometimes those turns seemed to be nothing more than a bend in the road. Sometimes it indicated a left turn on a straight stretch of road where there was nothing beyond a driveway on the left. If I didn't know where I was going and didn't have the map up, that would have been confusing as HELL. Problem is, not knowing where I'm going and not having a map up is exactly the targeted use case for this device.
  
  I should note that these were indicated left turns - not the slight turns shown in the video. I did see one slight right on my route, which was accurate.
  
  

Conclusion - so far

I still think the Hammerhead is a great idea and a slick design. It shows real promise. However, I can't help but wonder what the hell they did with 20 months of development time. I can't imagine they offered these to too many folks for beta testing... or is that us, the initial backers? I can't imagine how they managed to go 20 months of development without writing any type of useful doc, or taking more than a single crappy cell phone camera when a simple lightbox setup with a good SLR would have been so much more effective. It's just been a really frustrating first experience with the device.

Given some time, I think that it still shows huge promise, and I'm not giving up on it yet, but I certainly don't think it's ready for the big time, and I sure won't be using it alone to figure out how to get somewhere. It needs a bunch of work before I'll be ready to trust it that far.

Chasing the Nox full lap KOM

Last night I went out with the specific goal of giving my best go at Bob's ownership of the full Nox loop.

I had no expectations of coming in sub 50, much less challenging his time of 49 minutes dead -- but I figured I could put in something in the low 50s.

I started off with a lap of the Cold Spot loop backwards, to warm up and to check out the downed tree that Bob had warned me about.  Returned to the parking lot, talked to some guys, then headed out for my loop.  The downed tree wasn't too bad, had to get off the bike, hop the tree, and get back on, but I don't think I lost too much time.  On the northern Hammer loop, my phone starts going off.  There was an upgrade happening at work, and the notifications of stuff being unavailable started rolling in.  No big deal except I have my phone set up to keep notifying me until I actually look at the stuff.  Super.  So, I had to pull off my full-fingered glove, dig out the phone, unlock it, view the messages, lock the phone, and stick it back in my jersey.  This happened probably four or five times on the Hammer loop, all while I'm trying to maintain a race pace.  Looking at the results, it did affect my time -- my best there is 7:15, and this lap went down in 7:42.

I kept a steady pace on the connector trail, then got to the south loop.  Was going pretty well until I cut it a little too close to a tree, caught my jersey on the remnants of a branch, and had it quite literally ripped off my back.

 

Click the photo for more pics of my wrecked jersey.

This wouldn't have been much of a problem (except for it being my favorite jersey and favorite base layer) except two of my rear pockets ceased to exist, causing my phone, keys, and multi-tool to fly all over the place.  Had to stop, pick the chunk of jersey off the tree (now hanging in my cubicle) and pick up my stuff.  Then, I had to figure out where to put all this stuff, since I now had significantly less room to put it.  So, I tried what seemed like the best idea... tucked the stuff into the legs of my knickers.  I spent a bit more time looking for my second set of keys, but couldn't remember if I left them behind at the car or not, so I gave up the search for them so I could keep riding.  (more on those keys later)

Well, the legs of my knickers wasn't such a good spot.  As I pedalled, the stuff would migrate down, eventually heading for the spot behind my knee.  I managed to get the phone stuffed into my last remaining pocket once I realized it was still usable, but fought the multi-tool and keys for the remainder of the south loop, all while trying to maintain a "race pace".

Got to the end of the south loop, and had to take a moment to relocate my keys and multi-tool to my already overstuffed seat bag (yes, the one that looks like a racoon) because I wanted a good run on the Eastern Woods northbound trail.  See, a couple days ago I made a run at that trail with two phones recording.  (I've had some issues with great rides getting "lost" due to the GPS getting mental, so now run a backup) At the end of the day, one recorded a time of 5:32, and the other recorded a time of 5:56.  So I was either well faster than Bob on that segment, or two seconds behind.  That's a pretty big gap, so I had to go back and do it again.  I figured if I could do at least a 5:4x time, then my 5:32 was legit. (that phone typically is far more accurate, too)  So, I wanted to have a good run on there.

Well, it was a little wet, but most of the trails were solid.  A handful of spots which were a little slick, but nothing too bad.  My time was slower, but not massively slower, so when I came in with a 6:04 time, I realized my 5:32 was bullshit. Too bad, but beating Bob by 20 seconds anywhere smelled far too much like bullshit, no matter how much I wanted to believe it.  On the upside, his 5:54 is only 2 seconds faster than I've gone, so I can get that.  Will it happen before he's in the 5:40s?  we'll see.

I finished up with the Haycock Run uphill, on which, only an hour or two before -- Bob set the new KOM... and came in only a little bit behind at 2:15 to his 2:09.  Weird that I run that section faster uphill than down.  I think a sub 2 is possible.

So, I was a little disappointed with a 57 minute time, but at least I came in sub 1 hour, and considering my two stops and having to check my phone, it's not too bad.  I figure it would have been a solid 54 minute run, maaaaybe 53 minutes.  Dry trails and luck, I might be able to drop it to 52 minutes.  So Bob's time is pretty much unchallenged, thanks in no small part to his phenomenal bike handling.  The one time I rode with him, I went from right on his wheel to 50-60 feet back in the span of a couple tight downhill S-turns.  That shit just adds up.

All in all, though, it was a fantastic ride.  It's not often I just focus on going hard for an entire MTB ride like that, and the challenge is so much fun.  Thanks to Bob for giving me something to shoot for!  I will get to a 49 minute lap, but I'm pretty sure Bob will be sub 45 by that point. :D

Oh, and I mentioned the second set of keys.  Got back to the car, gave a good search, and discovered that set of keys was not in the car.  So, that meant I did have them, and they were still laying trailside by that tree.  So, I loaded up the bike, and headed for South Park Rd, where you can park on the side of the road and access the trails.  As you can see here, the trail gets really close to South Park Rd, climbs up for a while, then drops back down, getting very close to the trail you just rode.  I took advantage of this, rode cross-country between the two chunks of trail, and got back to the scene of the crime.  Using the light on my phone (it's past sundown and I'm losing light fast) I managed to find my keys about six feet down the trail from the tree.