Saturday, November 16, 2013

Moving to Macintosh

I'm been using Linux as my primary operating system for more than 13 years, and on and off before then. However, some of the recent changes in the way the desktops are being designed and other factors got me thinking. If the Gnome Desktop is looking more and more like OSX, maybe I should look at OSX. So after 6 months of research, using the equipment in stores, and trying things out I decided that I would get a Mac as my next computer. I also think I was ready for a change in my personal computing.

So when the new Macbook Pro's were released in October I figured it was time to make the move. I ended up getting a MacBook Pro 13 with a 2.8Ghz i7, 16GB of RAM, and the 512GB SSD (yes, I am now broke for awhile). The hardware that Apple makes is really excellent, and I figured if I really hated OSX, I could always put Linux on the machine. So I have used the machine for a couple of weeks now. And I have to say that while I am not fond of a few things (the menu bar at the top and Spaces just don't work that well compared to virtual desktops), I am finding that I can just use the computer and I am getting used to these changes. It is also nice that when buying hardware and software, I now do not have to spend a few hours researching if it will work in Linux. I can usually just look at the box and know.

I am also having to get used to paying for software again. I have to admit that being able to install OpenOffice on the Mac was a big reason to consider it. I'm not sure I could fork out another $500 in software for the Mac, so that cost of buying into the Mac is pretty low after purchasing the hardware.

I also have to admit that this is one of the fastest machines I have ever used for day to day activities. Even faster than some of the massive servers I have used less than 3 years ago. I think the SSD is a big part of that as the CPU clock speed is not all that different.

Does this mean I have given up on Linux as an operating system, definitely not. I still use it as my primary OS on my work laptop (RHEL 6.3) and I think as a server OS there is nothing better at the moment. I will probably always have a Linux box somewhere in the house, unlike Windows 8. Also a side note here is that Windows 8 is probably one of the main reasons that I started looking at Mac. I know that I don't use Windows personally, but others in my house do and after having a loaner machine here it made us all think that Windows 8 was not for us, at least on the desktop.

So what does this mean, it means that I need to find someone to take over some of my Linux projects. Over the last year I have not had much time for them anyway due to my work schedule (I travel a lot more now). And it is time the projects had someone focusing on them.

Saturday, October 19, 2013

Preliminary gnome-mplayer and wayland testing

On my Fedora 19 machine wayland is available and so I thought it would examine what might be needed to make gnome-mplayer run in this configuration. GTK 3 will support wayland, but what I am not finding is a way to embed mplayer into a GTK window. The current code uses the GTKSocket and passes the XID of that window to mplayer for embedding. I am also not completely sure that the GTKPlug/Socket API is going to work on Wayland. According to the GTK 3 manual I see this note

The GtkPlug and GtkSocket widgets are only available when GTK+ is compiled for the X11 platform and GDK_WINDOWING_X11 is defined. They can only be used on a GdkX11Display. To use GtkPlug and GtkSocket, you need to include the gtk/gtkx.h header.

So the current method of embedding mplayer may be a no go on Wayland/GTK3.

However, I believe I may have a workaround for all this. I think if we compile gnome-mplayer in GTK2 mode and then use XWayland everything should "just work". It is also possible there will be a way that XWayland is launched for applications that are linked to Xlibs or we may just need to but a wrapper script around gnome-mplayer to ensure it is launched properly even in GTK3 mode. Not the cleanest solution, but better than nothing. Once Fedora 20 is released and Wayland and XWayland are available I will do some more testing and see what needs to happen.

Tuesday, October 30, 2012

gnome-mplayer 1.0.7 released


Announcing the release of gnome-mplayer 1.0.7

Due to a change in the logging of the application gmtk 1.0.7 is *required* for gnome-mplayer and gecko-mediaplayer

Notable changes:

gnome-mplayer now has MPRIS2 support, so as support is added to the applications gnome-mplayer should be able to be controlled from several panel applications. I have requested this support from several applications but as of yet support has yet to appear.

Added Anamorphic 2.39:1 as a preset screen ratio

Prevent crash message on shutdown.

GTK compatible logging system

Fix problem when controlling the playback of audio only files

Rework playlist handling in gecko-mediaplayer so that website playlists are handled in a sane manner and caching is done correctly.

And the normal stuff:
Several bug fixes
Additional keyboard shortcuts and fixes


Files:

http://gmtk.googlecode.com/files/gmtk-1.0.7.tar.gz

http://gnome-mplayer.googlecode.com/files/gnome-mplayer-1.0.7.tar.gz

http://gecko-mediaplayer.googlecode.com/files/gecko-mediaplayer-1.0.7.tar.gz

Enjoy!

Friday, August 10, 2012

Using a keyboard and mouse with the Kindle Fire

After installing CM9, with the 3.x kernel, on my Kindle Fire, I read about people connecting keyboards, mice and other USB devices to the Kindle Fire. In order to do this a USB cable referred to as a OTG cable is needed. I happened to order this one, but there were many options. After I got the cable, I plugged a USB 2.0 powered hub into the OTG cable which was then plugged into the Kindle Fire. A powered hub is essential as the Fire does not put out enough voltage to power most external devices. Also, on the Kindle Fire, you will want to install the applications "StickMount" and "File Expert" from the Google Play store.

Now for the big test. The first thing I did was plug in a USB mouse into the powered USB 2.0 hub.  Much to my surprise a mouse cursor appeared on the screen and I was able to move the mouse around and click a few things. I was wondering if the mouse cursor would appear as the Kindle Fire is a touch screen device. Both the touch screen and the mouse worked at the same time, so nothing was lost. So far so good. I then plugged in my USB keyboard and then I opened a browser window and was able to type in the url on the physical keyboard. So now things are looking pretty promising. The next step was to plug in a USB flash drive. Within a second StickMount popped up a prompt asking me to allow it SuperUser access and then informing me that the USB device had been mounted in /sdcard/usbStorage/sda1. I then used File Expert to navigate to that directory and view the files on the flash drive. Everything seemed to be there and I was able to open and interact with files just like files found on the Kindle internal storage. Perhaps with the right USB flash drive, very low power requirements, the USB hub would not be needed and then you would have a solution to the limited space on the Fire. One of my sticks, a 4GB one, almost worked, but the 32GB one definitely would not.

Now for the things that didn't work. I tried to plug in my 1TB External USB harddrive and while the OS knew something was there, I do not believe the file system drivers were present. I also did not have much luck with my USB Bluetooth adapter. Also while these devices where plugged in I could not charge the Kindle Fire, so I was limited on how long the device would run. This adapter from Amazon may allow you to work around that issue.

So all in all the Fire with the OTG cable, a powered USB 2.0 hub, a USB keyboard and mouse can actually function as a basic computer. Now I would not recommend this setup for full time usage, but if you want something for some basic work that requires a lot of typing on the cheap, this would be one option. I also see no reason why this setup would not work with other Android devices. So if you decide to try this, I would appreciate some feedback.

Thursday, July 19, 2012

Upgrading the OS for Android 4.0.4 on the Kindle Fire

I have a Kindle Fire and it is a pretty nice piece of hardware. I use it for reading and watching videos while I travel weekly. But lately I saw that the new Android OS 4.1 (Jelly Bean) was available for it so I wanted to try it out. Needless to say it was an interesting experiment and I thought at one point that I had broken it forever. Luckily, I did not. In the end I decided to not use the Android 4.1, but to drop back to 4.0.4 because it was a little more polished and all my applications worked on it. After the upgrade the Kindle Fire feels like a new device. It responds better, does things I never expected it to do and still does all the great Kindle things I wanted it originally for.

Tools you Need:

On Windows use Kindle File Utility, I would recommend that you not run this in a VM and connect the Fire directly to a motherboard USB port. I had better luck running this tool on Windows .

Run the "install permanent root" part of the setup and that should install FireFireFire (bootloader) and TWRP (recovery tool)

On Linux use FireKit and run the install_fff_twrp_from_stock script as root (this is the actual method I used)

Once FireFireFire and TWRP are installed you now have complete control of what OS to put on the device.

So what I did next is to copy a ROM to a folder on the Kindle, doesn't matter where as TWRP will be able to navigate to it.

I got the Android 4.0.4 ROM (CM9 based) from here: http://rombot.droidhive.com/ROMs/otter/cm9/
I also got the Google apps from here: http://goo.im/gapps make sure to use the 20120429 version of them for CM9.

After the files are copied on to the Kindle, disconnection the Kindle and power it off.

Boot the Kindle (the logo should be blue now, from FireFireFire) and press the power button to boot it into "recovery" mode. This will start TWRP. First thing you should do is make a backup. This will take about 1GB of space on the Kindle so make sure you have room. After the backup is done, wipe the device including data, cache, dalvik (this will not wipe the SD card). After the wipe is done, install the ROM you just downloaded from the directory on the Kindle. Then install the gapps file you downloaded. I would recommend not flashing them at the same time, but to do one at a time.

After that you should be able to reboot your Kindle Fire and have a working Android 4.0.4 system after a few minutes of bootup.

You may also want to install the Amazon Market from here: https://www.amazon.com/app-email so that you can redownload and install the apps you have purchased before.

To enable USB storage access go to Settings -> (Device) Storage and in the top right click on the three dots and select USB Mass Storage


Desktop:








Apps:

Kindle for Android - Book reading
Next Issue - for reading my Entertainment Weekly subscription
MX Player - for playing videos, works great with subtitled .mkv files
Netflix and HBO Go work fine

Enjoy

Friday, May 18, 2012

mplayer-video-thumbnailer aka nailer update

I hadn't really noticed that my mplayer-video-thumbnailer had not been working properly in under Gnome3. Some thumbnails were getting updated and others were not. So I finally tracked down the problem and was able to solve it in about 20 mins. It turned out that nautilus had changed its configuration for thumbnails from a gconf entry to something similar to how Thunar does it.

So I made some changed and bumped the version

You can download it from here:

http://mplayer-video-thumbnailer.googlecode.com/files/nailer-0.4.6.tar.gz

Thursday, May 17, 2012

MPRIS2 support in GNOME MPlayer

MPRIS2is becoming the standard way of controlling media players over DBUS. Since GNOME MPlayer already had much of this capability built in due to the usage of DBUS to communicate with gecko-mediaplayer I decided to add MPRIS support in to the upcoming 1.0.7 release of gnome-mplayer.

After a few days of work, much of the MPRIS specification has been implemented. Really not that hard except for having to figure out how to implement some of the more unusual types. The mpristester application was a huge help in debugging and ensuring that the implementation went correctly.

After initial support was working I began testing the code with a few of the gnome-shell extensions that use MPRIS to control several media players. I had to make a few modifications to them, mainly just adding "gnome-mplayer" to the list of supported players and after that they just started working.

So if you use one of these extensions, tell them to add support for gnome-mplayer to there application. And as always if they have issues, I should be able to fix the problems within a short period.

The code is in SVN now, and I recommend that you get gmtk and gnome-mplayer from SVN for the best support.