Use Skype on your Droid … with Wifi!

Posted in Geek Stuff, Ranting by dave on March 25, 2010 No Comments yet


This morning, the fine folks at Verizon and Skype unleashed their first attempt at an “official” joint-venture application for Skype on smartphones – including Verizon’s Android-powered offerings. Given the anticipation that’s been brewing, installing the newly-released app was the first thing I did after pulling my Droid from its cradle today.

Unfortunately, seeing the official Skype Mobile application waiting for me in the Android Market was where the positive experience ended. After installing, the app informed me that it wouldn’t work with the phone’s Wi-Fi connection enabled. Odd, I thought, considering that it’s already been well-publicized that Skype-on-Verizon will use the Verizon voice network to deliver calls, but without deducting any minutes from the user’s plan.

As it turns out, this new Skype app will only sign in if Wi-Fi is disabled on the handset – meaning that no other apps can use that Wi-Fi connection, either. Re-activating Wi-Fi causes an automatic log-out from Skype – so much for that “always on” connection that’s advertised in the app’s description!

Fortunately, there are a few ways to enjoy Skype connectivity on your Android-powered device. Rather than installing the Verizon Skype app, check out these alternatives:

Sipdroid

A decently well-integrated SIP client (that is, a soft-phone that can make and receive VoIP calls using the SIP protocol) that doubles as a Skype client.

Fring

A nice multi-protocol chat and VoIP client with a slick user interface; it’s gone through some revision lately, but gets better and better as its user base grows.

Truphone

While this one isn’t Droid-compatible, I tried out an early beta version and found it to be fairly workable. If you have an Eris or are saving your pennies for a Nexus One, HTC Incredible or Devour, this one might be worth a test-drive…

Springtime…

Posted in Random thoughts by dave on March 18, 2010 No Comments yet

image

…when RIT actually looks like a college campus!

(And for the record, “What’s Golden” by Jurassic 5 was playing on that jam box…)

Reasons to Ride: Springtime

Posted in Bike Stuff by dave on March 17, 2010 No Comments yet

Push. Push. Push. One. Foot. Down. Then. The. Other. Push. Harder. Slip. Spin. Slide. Turn the bars. The bike will follow.

Push. Push. Push. Gear up. Push. Push. Push. Gear up. Push. Push. Push. Climb. Down a range. Push. Push. Push. Brakes.


Brakes. Brakes. More brakes. Stand, turn, lean, roots. Brakes. Push. Push. Push. Push. Push. Trust the bike. The bike knows what to do.

Climb. Climb. Climb. Climb. Climb. Climb. Steeper. Climb. Climb. No gears left. Shit. Stall. Climb. Climb. Drop. Pedals out. Hike.

Saddle up. Coast. Roll. Brakes. Push. Brakes. Push. Brakes. Push. Spin. Descent. Range up. Gear up. Gear-gear-gear-gear up. Stand. Lean. Weight back. Weight up. Weight back. Brakes. Lean. Brakes. Push. Brakes.

Pause. Descent. Squint into the wind in your face. Wipe. Sweat. Wipe. Mud. Drink. Push. Brakes. Gear up. Gear down. Range up. Range down. Front brake. Rear brake. Pedals out. Clip in. Mud.

Enjoy. The. Ride.

Missed deadlines, trashed entries and new bicycles

Posted in Random thoughts by dave on March 14, 2010 No Comments yet

Hrmph. It appears I’ve missed a Project 52 deadline for the first time this year. Rest assured, fickle reader, that it was not for lack of trying. Actually, as I put the finishing touches on a thousand-word entry yesterday, I decided it just wasn’t worth bothering with. The post was more or less a rant about the similarities between Apple Computer’s business model (of late) and the health care legislation that’s currently looming over our country like the tidal wave at the end of The Abyss.

I wrote the post late Friday night, and read through it a few times yesterday, tweaking here and there. And then I read through it a couple more times. And then I asked myself, “why bother posting this?”. The answer wasn’t because I wanted to make a point, or share my conclusions, or push my point of view – it was because a new week was about to start, and I didn’t have anything else chambered up. So I flushed it. In the grand scheme of things, no one who reads this blog would have their mind changed by a bitchy post relating geek issues to Obamacare. And no one new would have visited the site just to see my rant. Why bother?

We had plenty of excitement in the afternoon, either way. After I nuked the rant, Kelly and I jumped in the car and headed out to Geneva Bike, in hopes of walking in with a gift certificate (a Christmas present from my parents) and leaving with a new pair of cycling shoes for me. Of course, you can’t go to a shop like this and not browse around a little – and that browsing landed us in front of a wall of ladies’ road bikes. As Kelly eyed one in particular – a Trek 2.1 left over from last year – I wandered off to play around on the 29′ers. A few minutes later, I found her (and the bike) bolted into a trainer, getting fitted! Long story short, after the bike was set up and we talked it over, it ended up coming home with us…

As much as I love mountain biking, I’m hoping that Kelly’s new wheels will give me a little more excuse to get out on the road with my trusty old Trek this season (after Craig tunes it up, of course). Stay tuned here; I’m sure we’ll have experiences to share!

Android fitness apps: CardioTrainer vs. Buddy Runner

Posted in Geek Stuff by dave on March 4, 2010 4 Comments

Sometime in 2006, some co-workers and I tried our hands at running. We’re not all that fast, and our endurance isn’t all that great, but we enjoy hitting the pavement together, and we’ve all reaped some big-time fitness benefits from the hundreds of miles of ground we’ve covered in our four years of ground-pounding. What we lack in performance, we make up for in dedication – we run right through the bitter Upstate-NY winters – but none of us has ever felt dedicated enough to drop several hundred clams on a dedicated GPS training device.

But then, at long last, the Droid came to Verizon, and I finally entered the world of Android users. Not long after me, one of my running buddies traded in his Blackberry Storm for a Droid as well. Since then, I’ve tried out a couple of apps for runners, and thought I’d share a few observations here…

CardioTrainer

The first app to join me on my runs was CardioTrainer, from Android app house Work Smart Labs. I tried the free app on a couple of trail runs during a visit to California, and it did a great job. Given the unfamiliar surroundings, it was nice to have a little insight into how far I’d gone. CardioTrainer measures distance, time, pace and calories burned in real time using your handset’s GPS receiver, and automatically – and anonymously – uploads completed workouts to the Work Smart servers. There, you can view additional details about your performance, as well as check out your route on a larger map.

After returning home, I tried CardioTrainer on several routes that I had previously mapped using online tools such as MapMyRun or the GMap Pedometer. The app’s distance measurement is very accurate, and receiving spoken pace and time information proved helpful in regulating my speed and achieving a more balanced effort. Still, it’s is not without its annoyances – despite the formidable processing power of the Droid, CardioTrainer takes noticeably longer to register screen taps than other apps, especially when it’s using the GPS. During some runs, while the overall distance and time numbers are correct, large portions of the track are mysteriously missing from the track display. I suspect this has something to do with the autopause feature.

Checking in on the CardioTrainer web site, users can view their training history and data logged for each workout. Oddly, each workout’s elevation graph is accessible on the web site but not via the handset interface, while a pace graph is available on the handset but not on the web site.

Pros

  • Many configuration options
  • Live map display – very helpful to check for dead-end roads when running in an unfamiliar place!
  • Automatic track upload to CardioTrainer web site
  • Can track several different activities – running, walking, biking, etc.
  • Ability to manually add workouts (such as for indoor activities, swimming, etc.)
  • Configurable auto-pause stops timer and pace calculations if you stop moving

Cons

  • Pace graphs only show miles/hour, not minutes/mile (which would be preferable)
  • Voice guidance configuration could be improved
  • Autopause can disrupt track logging
  • Can export KML and GPX files, but not import

Buddy Runner

After experiencing a few quirks with CardioTrainer, I took a look in the Android Market for other options. Buddy Runner seemed to have a strong rating and a friendly pricetag (it’s also free), so I gave it a shot during today’s run. While the interface is far more sparse than that of CardioTrainer, BuddyRunner does allow customization in one area that its competition does not: specifically what data is read aloud to you during voice guidance. Rather than CardioTrainer’s pre-defined content – which alternates depending on whether you’re at a milepost or mid-mile interval – users can choose exactly which data points they want to hear.

In use, Buddy Runner is simple – the main screen provides “Start / Pause” and “End” buttons, as well as tickers displaying time, distance and pace. A map view is also provided, though I’ve never looked to see if it’s updated in real-time. I particularly like the fact that Buddy Runner gives you an option to select how your voice-output pace is calculated – it will read out either the “live” pace from your last few seconds of running, the average pace for your last mile, or your overall average pace for the entire run. Based on my usage of CardioTrainer, I’ve surmised that the only pace it reads to you is the “live” pace, which is what I prefer to hear anyway.

Pros

  • Better voice guidance configuration
  • Simple interface, easy to use while running
  • So far, no corrupted tracks
  • Configurable pace calculation (last few seconds, last interval, entire run average)

Cons

  • Only tracks running – no other activities
  • Autopause is either “on” or “off” – the stop interval isn’t configurable
  • Requires e-mail address to enable uploading of tracks to the web, but does upload automatically
  • No visible feedback on button-presses, such as highlighting – a complaint common to many Android apps

Conclusion

With both CardioTrainer and Buddy Runner on my phone, I’m hard pressed to choose a winner – neither is head-and-shoulders above the other, at least when it comes to running. I’m inclined to look past CardioTrainer’s occasional quirks, given that it has the capacity to track other forms of exercise, as well as input indoor workouts manually – we all know I enjoy my time on two wheels. Which will I use going forward? For day-to-day runs, Buddy Runner wins, since I can choose what I want read aloud to me while running. If both apps were to slap on a $5 price tag tomorrow, however, my money would go to CardioTrainer – it simply delivers more functionality and a smoother user interface. They’re both great apps – and I would encourage any Android-toting runner to give each a try.