Connecting your Chromecast to wired networking – DIY

I’ve had a Google Chromecast (1st generation) for a while now, connected over WiFi. Works great, although sometimes the wireless reception cuts out, or the signal gets saturated. Since I’m mostly streaming from a device which sits less than 10 cm away, it is also rather stupid to have all those packets going back and forth to my router, causing unnecessary load.
Google has a nifty solution, the Ethernet Adapter for Chromecast, but it’s 1. rather expensive for what it is (in my opinion), and 2. difficult to get your hands on (in Belgium, where I live).

So, after some digging, enter a DYI solution that works ;) It costs about half, but requires more patience (for delivery).

I ordered following pieces of DealExtreme, and had them ship here:

To install it all: plug the mini-USB power supply (delivered with the Chromecast) into the blue plug, the network dongle into the normal USB plug, and the black connector into the Chromecast. (And an ethernet cable into the network dongle, duh). It should automatically pick up the fact that it’s now connected via ethernet, and other than that… it just works. Enjoy ;)

(Edit: I’ve noticed that this setup does cause plenty of electrical interference… so FM reception becomes nearly impossible. Have to figure out what is real cause)

LG Nexus 5

I’ve always been a fan of the “stock Google” look of android, also often referred to as AOSP (Android Open Source Project) – a clean look, no bells and whistles added by the vendor of the device in question.
The ‘vendor’ looks usually change the look of the Android OS, add (unneeded?) applications, and add their own launcher. There are several vendor skins, like Samsung’s TouchWiz (pictures), HTC’s Sense (pictures), Motorola’s MOTOBLUR, and numerous others.

I just don’t like them.

Don’t get me wrong – they have their good things too. Usually better integration of all the vendor apps, and a higher degree of userfriendlyness.

Since my old HTC Hero, I’ve been replacing the look set by the vendor by a more stock Google Android look. So it makes only sense that my last phone should be a Google-commissioned Nexus device, namely the LG Nexus 5. In black, ofcourse ;)

So, replacing the HTC One X, here’s my new daily use phone:

LG Nexus 5

(and, before you ask, ofcourse it’s been rooted.)

Android 2.1 (Eclair) on the HTC Hero…

I’ve bought an HTC Hero a while back. Rooted it too, so I could edit the sms database. Loving the phone.

Then HTC promised us (owners) an upgrade from Cupcake (Android 1.5) to Eclair (Android 2.1), scheduled for March 2010. Since Eclair has a ton of additional features and bugfixes, this was a biggy.

Then HTC postponed it to beginning of April. End of April. May. June.
On the 4th HTC started rolling out the update for Asia, and we still had to wait in Europe. That’s when I got fedup with waiting.

Thanks to the wonderful guys over at XDA-Developers and this Complete Newbie Guide to Install a Custom Rom, I now have VillainRom10 installed, which is basically a repackaged official 2.1 rom from HTC.

I had to use the GoldCard method to downgrade my Hero (specified in the Guide – worked perfectly with a Sandisk 2gb SD card), and install the drivers from this thread for the RUU (Rom Update Utility) to find the Hero in bootloader mode. Other than that, it’s a smooth sailing.

After using the phone now for two days, it feels mightily fast, snappy… it’s a total new phone.

Gigantic Android, Donut, Cupcake and Eclair at the GooglePlex

Goodie!