Writing on Tablets Tech stuff from @yeltzland

Sky Anytime, Routers and 3 Home Signal

Still been busy prototyping with NodeJS and MongoDB (nothing too interesting to show yet), but had a couple of things happen in my home network that I’d thought I’d share in case they help anyone suffering with the same issues.

Problems with Sky Anytime and my Netgear Router

I’d bought a wireless connector for my Sky box so I could use the on-demand services of Sky Anytime, but whatever I tried it wouldn’t connect to my home network - which made it worse than useless.

I’ve got a fairly old Netgear DG834GT router that has always worked fine for me with my BT Broadband connection without any issues, so thought it was unlikely there was a problem there.

I spoke with the usually very helpful and knowledgeable Sky support, but other than saying a few people had also reported similar issues, they had no idea what to do.

I’d almost given up on finding a solution, but then I happened upon a support forum where someone mentioned they’d changed their ADSL multiplexing method to “LLC-based” rather than “VC-based” and that had managed to fix the connection issue.

I was very doubtful that could be the problem, but after I switched I immediately made a connection, and can now use BBC iPlayer, 4OD and other services direct from my Sky box.

To be honest it still doesn’t make sense how the ADSL connection type can affect how the wireless network connects to the box, but hey, it worked for me!

3 Home Signal

I’ve been very happy with my iPhone since I got it a few months ago, and reasonably happy being on the 3 network except for one thing - the phone signal in our house was very patchy and much worse than I used to get on Orange.

Now living in a small town (Hexham) in a valley in the country means it’s not totally unexpected we get a weak signal - we only just about get free-to-air digital TV - and our house has pretty thick stone walls. However it’s still not exactly the middle of nowhere, so pretty disappointing to only get a connection in the house about 50% of the time.

However, I’d read that 3 have a solution called Home Signal that they will ship for free if you qualify. It’s basically a Femtocell connector that gives you a private phone network to connect your calls via your broadband router.

The tip I found online - which I will share here - is not to ask 3 directly for a Home Signal box, but simply tell technical support you are having problems, let them test the signal and then they will suggest Home Signal if you qualify for one.

It has definitely worked for me, and now I get at least 3 bars everywhere in the house and don’t miss any calls any more.

Sky Anytime Netgear 3 Home Signal

Developing for Heroku and Node.js on Windows

So I’ve been playing about with some hopefully interesting ideas I’ve been having for a new app - more soon when we have a bit more traction - and have been hacking about using Node.js and MongoDB on Heroku.

It’s been great fun learning some new things, but as ever things have been slightly harder because I’m developing on Windows rather than on a Mac or Linux laptop. Anyway, I thought I’d capture a few things I had to figure out along the way (mainly via Stack Overflow) here, both so I don’t forget them and in case they come in useful to someone else.

Installing MongoDB drivers for node.js

This stumped me for a while. In theory, it should be as simple as running:

npm install mongodb

However, the module has a dependency on the bson module, which will compile itself on install. In theory this shouldn’t be a problem, but out of the box npm is looking for the Visual Studio 2010 C++ compiler, and I only have Visual Studio 2012 installed - and definitely don’t want to install an earlier version as well.

After much searching, I found that there is an option to use VS2012 by using the command:

npm install mongodb --msvs_version=2012

… and everything installed and worked like a dream.

Running Heroku’s Foreman on Windows

I’ve been pretty impressed with the Heroku stack so far. It’s really easy both to deploy your changes by a Git push, and the command-line tools you get make it easy both to configure and monitor what’s going on.

One of the tools was slightly problematic, as Foreman - basically an easy way of running your apps locally - didn’t actually work properly.

Thankfully this was a known issue in version 0.62.0, and the solution was to use 0.61.0 instead which can be installed using:

gem install foreman -v 0.61

… making sure you’ve uninstalled it fully first (using the uninstall command)

Heroku NodeJS Windows Development

Bedside Clock code now on GitHub

A few weeks in with my iPhone and I’m very happy with my choice.

The iOS interface is fine, and although I do miss the “Metro” interface of my Windows Phone, having a massive choice of good and interesting apps makes up for that by far.

A perfect example is being able to use Instagram. I’ve really enjoyed taking some gratuitous photos and sharing them with the community there. Nothing unusual there for most people, it’s just it’s still not available as an app for Windows Phone.

Anyway, that means I’m definitely not going to be developing my Bedside Clock any more, so I thought I’d share the code on Github so if anyone does want to extend the app they can do.

This was originally a project just for me to learn about developing for Windows Phone, and to replace the better built-in clock I was missing from my Android phone. You can probably tell this with some of the slightly gratuitous features I added (phase of the moon calculations anyone?)

It’s done reasonably well at the App Store with around 14,000 downloads as of April 2013 - which is far more than I ever dreamed of! I learnt a lot building it, and I used it every night when working away in London, so it definitely had at least one satisfied user.

If any of you are interested in forking the code, extending the app or fixing any bugs you spot, I’d be very happy to help get them merged into the code base and releasing the out into the wild.

Bedside Clock App Windows Phone GitHub

And the winner is ... iPhone

So after my earlier post when I said I was going to get a Nexus 4, after a lot more pondering I’ve actually ended up buying an iPhone.

So what made me change my mind?

The main reason was I just wanted the phone with the best set of apps. The longer I prevaricated, the more I realised the interesting apps mentioned in the tech press are almost always iPhone first - and I didn’t want to miss out any more.

From a dev point of view, I am also thinking of getting a Mac Mini anyway for working on my own stuff, which will solve the ability to make my own apps.

I find it really interesting how the Mac has morphed into a dev machine - I guess the UNIX underpinnings means server-side technologies work more naturally there. For example, I was trying to get Ruby on Rails working on my Windows laptop, and it was just painful. However all the install instructions were Mac friendly, which makes a lot of sense.

Anyway, I hope I don’t regret my decision. One day in it’s been great to try out a whole load of interesting and experimental apps that are nowhere near being released on Windows Phone.

It’s also very interesting the reaction you can get when you tell some people what you’ve done - sometimes it’s almost like I’ve commited the heinous crime of changing which football team I support, rather than just getting a new phone!

Personal Phone

Final version of my Bedside Clock app shipped for Windows Phone 8

It’s been a great learning exercise, but I think I’m finally done with my Bedside Clock app for Windows Phone.

This was originally a project just for me to learn about developing for Windows Phone, and to replace the better built-in clock I was missing from my Android phone. You can probably tell this with some of the slightly gratuitous features I added (phase of the moon calculations anyone?)

However I’m almost certainly moving off Windows Phone very soon - and to be fair there isn’t much of interest left to do in the app - so other than fixing any serious bugs that are found I think I’ve finished working on the app.

The new version ( is just for Windows Phone 8, although there are no new features compared to the earlier versions. I’ve just refactored the code a little to work with the new SDK, and added support for the new icon sizess and different screen resolutions supported by WP8.

As ever, it took a couple of attempts to ship the app. The Store test team seem pretty thorough in their testing, and they found a minor logic bug in the back button logic which had changed in WP8. This was easy to fix, but it is very irritating that you have to re-enter all of the store details and screenshots everytime, even when it’s just a minor changed to the XAP executable file.

If you haven’t already got my app and want to give it a try, click on the Windows Phone icon below to install it from the Windows Store, and let me know what you think!

Go to Windows Phone Store

Bedside Clock App Windows Phone