Link: How to Emulate Google Chromecast on Windows, Mac and Linux Desktop

Google’s latest hardware offering, Chromecast was an instant hit as it promised a better way of beaming/ controlling  multimedia content from your mobile phone on to a TV than the current choices we have right now. Now when a popular company like Google is trying to solve an age old problem that haunted Android, with a less expensive ($35) hardware, we should expect it to run out of stock. That is what exactly happened to Chromecast as it ran out of stock on all popular online stores including Google’s own Play store. Now if you have already pre-ordered a Chromecast or is in queue, here is something for you impatient folks, ready to play with few command lines.

Github user (dz0ny) has developed a Python package called Leapcast that can emulate the Chromecast hardware in Chromium environment running on your Mac, Windows and Linux. In order to achieve this hack on your computer all you have to do is carefully follow the steps below.

Full article here:
How to Emulate Google Chromecast on Windows, Mac and Linux Desktop (Compixels)

Link: Say hello to PiCast, the open source solution to Chromecast using a Raspberry Pi

There is a lot to love about the Chromecast. It lets you stream your browser, your desktop, and a number of apps directly to your TV with little more than a $35 dongle that plugs into HDMI on your TV. However, lately, a few problems have arisen. For one, it’s really difficult to find one unless you’re willing to wait weeks for the next stock to come in. Additionally, the root method that was discovered over at XDA has since been patched. So Google isn’t letting everyone play fast and loose with their new dongle. It’s still a great device, but it’s not perfect and now there is an alternative called PiCast.

PiCast was started by a developer named Lance Seidman. The premise? To use a $25-$35 Raspberry Pi computer to do almost exactly what Chromecast can do. It’s an open source project that’s currently in development and it has a lot of promise.

Full article:
Say hello to PiCast, the open source solution to Chromecast using a Raspberry Pi (AndroidAuthority.com)

Link: Linux How-To: Use ANY IR Remote In The House to Control XBMC

Use Any IR Remote In The House

This tutorial will show you how to use ANY IR remote in your house to control XBMC.
I have used this method with COMPLETE success on many remotes. I have yet to find one that wont work.

To demonstrate this technique I will download and install the latest XBMCbuntu Live CD (Frodo 12.2) to verify it works “out of the box”
If you deviate from the Live CD XBMCbuntu install you are on your own installing and configuring LIRC.

Full post from the XBMC forum:
Linux How-To: Use ANY IR Remote In The House to Control XBMC

Link: Chromecast: Exploiting the Newest Device By Google

Chromecast-stockOn Wednesday, July 24th Google launched the Chromecast. As soon as the source code hit we began our audit. Within a short period of time we had multiple items to look at for when our devices arrived. Then we received our Chromecasts the following day and were able to confirm that one of the bugs existed in the build Chromecast shipped with. From that point on we began building what you are now seeing as our public release package.

Exploit Package:
Our Chromecast exploit package will modify the system to spawn a root shell on port 23. This will allow researchers to better investigate the environment as well as give developers a chance to build and test software on their Chromecasts. For the normal user this release will probably be of no use, for the rest of the community this is just the first step in opening up what has just been a mysterious stick up to this point. We hope that following this release the community will have the tools they need to improve on the shortfalls of this device and make better use of the hardware.

Full story here:
Chromecast: Exploiting the Newest Device By Google. (GTVHacker)

Additional comment: These devices might be a lot more useful to some of us if someone could figure out how to 1) Add a wired network connection, 2) Add an optical audio output for those of us with older receivers (that don’t have HDMI connections) and TVs (that don’t pass audio from a HDMI port back to the receiver). They’re obviously selling these to the low-income crowd, so why would they not assume that you might want to connect this to perfectly good but slightly dated equipment that requires optical audio, or maybe even to a large screen computer monitor that doesn’t have any audio capabilities?

Additional additional comment: If the XBMC developers could create an add-on that would emulate the Chromecast device and in effect turn XBMC into a Chromecast receiver WITHOUT the need for the Chromecast dongle, that would make us VERY happy!

 

Cubieboard2 open single board computer ships, Cubietruck model revealed

This comes to us from LinuxGizmos:

The forthcoming Cubietruck will have additional I/O ports
The forthcoming Cubietruck will have additional I/O ports

The Cubieboard open SBC project began shipping a faster Cubieboard2 version of its open source Linux and Android SBC, and revealed prototypes of a new, larger, enhanced Cubietruck model. Like the $59 Cubiboard2, the Cubietruck uses an Allwinner A20 dual-core Cortex-A7 SoC instead of the original’s single-core Allwinner A10, and adds a 2GB RAM option, WiFi, Bluetooth, gigabit Ethernet, VGA, and SPDIF ports.

Read the full article here.

Note that the abbreviation “SBC” in the above-linked article stands for “single board computer”. In our opinion, if the Cubietruck works reliably it could relegate the BeagleBoard Black to also-ran status, and could even give the Raspberry Pi a run for its money among those who’d like just a bit more power and a wider selection of outputs. For Home Theater PC builders, the inclusion of a SPDIF Toslink optical port is no small thing. We’ll definitely be keeping an eye on this one!

Link: How to watch Netflix (Watch Instantly) in Linux

EDIT: After publishing this article we learned of another article that gives additional information on what is probably the easiest method so far:

Yesterday, developer and programmer extraordinaire Erich Hoover and I spent several hours working out all of the Netflix Desktop kinks. Most users will have no problems with installation now.

Here is how to install the Netflix Desktop App on Ubuntu. …

Full details here:
PPA for Netflix Desktop App (iheartubuntu)

Should you have problems getting it to work, see:
Report Netflix App Bugs on Launchpad (iheartubuntu)

What follows is the original text of this post, which also mentions this method as one of the two choices:

Running Netflix is entirely possible in Ubuntu Linux 12.04 (and most likely any other modern distribution). See the section below “Running with Wine”.

Until recently there was no simple solution to watching streaming movies via Netflix (Watch Instantly) in Linux for any Linux distros besides Android based computers. Netflix has not released a player that will install natively in any of the others.

Read the full article here:
How to watch Netflix (Watch Instantly) in Linux (How To Wiki)

Notes on setting up Raspbmc on a Raspberry Pi

A couple of days ago we published Notes on setting up OpenELEC on a Raspberry Pi. One thing we found a bit frustrating about OpenELEC was touched upon in that article:

OpenELEC is very fast but much of the file system is read only, and even if you SSH in as root you cannot edit many of the configuration files as you could on a normal Linux system. Sometimes there are ways around that.

Now if you are setting up a system for your grandparents, maybe not having a writable file system, nor access to tools like apt-get for installing additional software won’t bother you. But we found it did bother us. For example, we missed having access to Midnight Commander. While there is an unofficial way to install it on on OpenELEC, the developers apparently would prefer you don’t do that. Well, sorry, but that kind of thinking is not acceptable to us. It’s our system, and we want to be able to control it. In fact, it kind of goes against the whole spirit in which the Raspberry Pi was created to make an “untinkerable” distribution, although we can certainly understand why some people like it. Different strokes for different folks*, and all that.

So we decided to again try Raspbmc. We had tried it once before, but found the interface a bit slow and clunky. However, just a few days ago a new version was released, and reports were that it was faster. So, we decided to give it another try. This time, we installed it using the instructions found here, which are for users that will be writing to the SD card using an OS X or Linux system. If you were using Windows for this task, you’d use these instructions instead. This only writes an installer to the card, and when you place the card into the Raspberry Pi and boot it up it will complete the installation. You must have an active Internet connection for the installation to complete.

The interface in the new version of Raspbmc does seem faster than in the previous version we’d tried. Some things may still be a bit slower than in OpenELEC – we particularly noticed that it took a bit longer for fanart to appear after we’d made a selection.

One thing that had bothered us about OpenELEC was that you could not change the Samba password. In Raspbmc it is easy, you simply SSH into the device (as user pi, default password raspberry) and enter:

sudo smbpasswd -a pi

Also if you want to change the SSH password, which we highly recommend, you simply do:

sudo passwd pi

In either case you will be prompted for the new password.

You can install Midnight Commander in the normal way, using apt-get install mc and it seems to work fine. Another thing we had an issue with in OpenELEC was changing the Samba share name. It’s easier to do this in Raspbmc, but still perhaps a bit non-obvious. The easiest way to do it is simply edit /etc/hostname and change name in that file – this is also picked up by Samba, though you may need to reboot and wait some time before the new share name appears and the old one disappears – it took about 20 minutes on our systems.

One thing we noticed about Raspbmc is that XBMC’s RSS feed is turned off by default. This was a major contributor to high CPU usage in OpenELEC. Not that higher CPU usage is really all that bad, but some people like to see a lower figure. Note that you cannot get an accurate reading from the XBMC GUI – to see an accurate representation of CPU usage you must SSH into the system and use the top command.

Speaking of SSH, one weird thing about RaspBMC is that the first time you SSH into the device, you’ll be asked to select a language and timezone. Always select at least the UTF-8 version of your preferred language – that is probably the only one you need. That’s the first time we’ve ever seen this information requested on an initial SSH login to a system.

* A line from “Everyday People” by Sly and the Family Stone (1968)

Notes on setting up OpenELEC on a Raspberry Pi

First, before you go out an buy a Raspberry Pi for this purpose, keep in mind that it does not have any type of digital audio output (such as a TOSLINK connector), other than the HDMI output – see discussion here. This may or may not be an issue in your installation, but you should be aware of that going into the project.

While you could use NOOBS to set up OpenELEC, you may not get the latest version. You are better off using these installation instructions and downloading the latest build.

OpenELEC is very fast but much of the file system is read only, and even if you SSH in as root you cannot edit many of the configuration files as you could on a normal Linux system. Sometimes there are ways around that. For example, Samba by default is controlled by the file /etc/samba/smb.conf. But you can’t edit that file. However, if you navigate to the /storage/.config directory you will find a file called samba.conf.sample. If you copy or rename that file to samba.conf in the same directory, then that becomes the file that controls Samba, and you can edit that file. For example, you can change the share name by editing the line server string = OpenELEC and changing OpenELEC to something else, and then find the line netbios name = %h and change the %h to the same thing you used as the value for the server string.

Also if you don’t want your Raspberry Pi acting as a Master Browser for your local network, you can comment out the following lines in samba.conf, as shown here:

# domain master = yes
# local master = yes
# preferred master = yes

When you are in XBMC you may notice that the CPU usage seems high. This is apparently because of two things. First, the act of measuring the usage in XBMC and drawing the usage bar on the GUI actually consumes significant CPU power. You can confirm this by using SSH and then the top command to view actual actual usage. When you are on screens that are completely static, with nothing being continually redrawn, the CPU usage will be lower. But also, if you go into XBMC’s settings (System | Appearance | Skins) and turn off the RSS feed, your CPU usage will drop considerably. Note that actually playing video content actually causes CPU usage to decrease since the work of drawing the screen is transferred to the GPU. On the other hand, leaving the XBMC GUI parked on certain pages may cause CPU usage to increase – for example, we found that if we went to a page that displayed large size thumbnails and fanart, the CPU usage shot up considerably.

To get a PVR plugin to work, you must first enable Live TV. Only then will you be given the option to pick a PVR frontend, But note that even if you set it up properly, you might get audio only and no video. As best I can determine, the reason is that neither the Raspberry Pi nor OpenELEC contains a license to play MPEG2 video. The Raspberry Pi folks will be happy to sell you a license, but we didn’t bite so have no idea if it works or not, and we have read where others have had mixed results. Keep in mind that MythTV, and probably other PVR backends, have the ability to transcode recorded programs to another format that does not require a license, so if all you want to do is watch previously recorded content and not actual live TV, you could just set up the backend to transcode everything to a format that the Raspberry Pi will play after it is recorded.

OpenELEC and the Raspberry Pi will output 1080p, however it appears that on some TV’s you need to go into XBMC’s setting and explicitly specify playback at 1080p, otherwise it will default to 720p. This happened for us on one TV set but not on another.

One question remains, some older TV’s need a “CVT reduced blank” signal before they will offer a Dot-by-Dot mode that has no overscan issues. In normal systems you can change this by using specific software, or in Linux, a specific ModeLine in the xorg.conf file. But it appears that OpenELEC has no support for this. This might make OpenELEC a poor choice for those users. Fortunately, you can also try other distributions for the Pi, such as Raspbmc, XBian, or GeeXboX.

Link: MythTV: Use All Buttons of Your Remote Control – Without LIRC

It can be really frustrating to get a remote control to work properly under Linux with LIRC and programs like MythTV, mplayer or XMBC. This article shows how to avoid using LIRC altogether: Treat the remote like any other keyboard, then change the keyboard mapping to use the application’s key shortcuts. Because we do this before the keypresses reach X11, it avoids the dreaded problem of keys with codes >255 not working.

Full article here:
Link: MythTV: Use All Buttons of Your Remote Control – Without LIRC (Richard Atterer)

Link: TheLittleBlackBox: An ARM-based, open source XBMC media center

XBMC is a media center application that started its life as a project to turn the first-generation Xbox into an audio and video powerhouse. The project has since been ported to run on Windows, Mac, Linux, Android, and other platforms, and we’ve even seen it running on low-power devices with ARM processors such as the Pivos XIOS DS Media Play.

Now there’s a new XBMC box on the way, and it’s designed specifically for running XBMC. It doesn’t run Android apps at all, just an embedded operating system to support XBMC.

Full article here:
TheLittleBlackBox: An ARM-based, open source XBMC media center (liliputing)