A little while ago, I sold my old Rogers HTC Magic(+) to my sister, as I had managed to procure a Google Nexus One. Upon receiving it, however, she had troubles getting ringtones to detect in Settings >> Sound and Display >> Ringtones. A little troubleshooting led to the first problem, which was a ringtone downloaded from Rogers that was in the form of a .DM file. Unfortunately, Android devices aren’t able to read these DRM-encrusted files. Even with that explained, though, there was another issue – the phone wasn’t detecting any MP3′s, either.

After remoting in to the computer and taking a look around, everything seemed normal. I had her mount the SD card, and after browsing around, everything looked alright. As instructed, she had created the correct folder structure on the SD card and placed the MP3 appropriately:

/Media/Audio/Ringtones

(relative to the root of the SD card)

I was a bit stumped, but then I had a brain wave, and renamed the folders as such:

/media/audio/ringtones

Sure enough, the phone then happily detected the MP3 as a ringtone.

The TL;DR version: Like most Linux-based operating systems, Android uses case-sensitive paths. Avoid the urge to properly capitalize your folder names!

07. February 2010 · Write a comment · Categories: Linux, Short · Tags: ,

Due to a failed kernel upgrade earlier today, I decided to wipe my MSI Wind and start over with the LXDE spin of Fedora 12. After the install, I went through installing my favourite packages, and notice the following while yum processed the dependencies for VLC:

schroedinger   i686   1.0.8-3.fc12   updates   208k

Closer inspection revealed the package to be a codec, but that only led to further questions. Does this package transport video, and then only determine whether it is encoded/decoded when your media player first tries to render it? Does the process involve acid, or radioactive material? Does it work with Boxee?

This has been your annual dose of quantum humour. I now return you to your Superbowl Sunday. Thank you.

Major Update (01/17/2011):

With the first few official Pre-Alpha builds of CyanogenMod 7 being released, it’s worth noting that a new feature has been included that allows you to change the hostname on your device from the Settings menu. If you have a supported device, you can get the nightly builds from the TeamDouche Mirror System. Once you’ve flashed (I take no responsibility if you break something – make sure to read up on issues/pitfalls/requirements before flashing), open the Settings menu, then choose Applications, then Development, and select Device Hostname at the bottom. This setting persists between reboots and ROM upgrades (unless you wipe).

Warning: I accept no responsibility if you brick your phone while doing this.

I ditched my iPhone due to problems my local provider was having and got an HTC Dream instead. I promptly rooted it using the Cyanogen Mod, but noticed that by default, Android reports the hostname as ‘localhost’. I don’t really like this, so I set about finding an easy way to change it.

First off, even rooted, the / partition is mounted read-only when you boot normally, so you need to boot to Recovery Mode (Home+Power). In the recovery menu, choose to boot to console. From there, browse to /system/etc/init.d.

IMPORTANT: Make a backup of ’05userinit’ before continuing! You can do this by simply running the following command – ‘cp 05userinit /05userinit’ (without quotes). This will create a copy of it in the / directory. If you screw up your editing, you can just rm the messed up version and cp the backup back in.

To add the command to set the host name, we’re simply going to echo in the following two lines:

echo  >> 05userinit

echo hostname NEWHOSTNAME >> 05userinit

Note that there are two spaces after the first ‘echo’ command. This creates a blank line at the end of the file. The second echo adds the hostname command. This way, whenever your phone boots, the hostname is set. Also, be sure to use two greater-than signs (>), as that appends – if you only use one, it overwrites the contents of the file.

Make sure the edits are correct by typing ‘tail 05userinit’ – as long as it isn’t blank, and there’s more than just the hostname line, you’re golden. Reboot the phone by typing ‘reboot’ at the prompt and hitting ‘Enter’, and you’re done.

Once you’ve booted back up, open up your terminal emulator of choice and type ‘hostname’ (by itself, no parameters) – it should echo out whatever hostname you specified.

Update (April 6th, 2010): To change your hostname on Cyanogen 5.x, add the following line to the bottom of /system/etc/init.d/01sysctl — and make sure you make a backup of 01sysctl before editing it!

echo NEWHOSTNAME > /proc/sys/kernel/hostname

05. December 2009 · 1 comment · Categories: Linux · Tags: , ,

My MSI Wind U123 has an 802.11n wifi card that uses the Ath9k driver. Although it’s technically supported by the 2.6.31 kernel used by Fedora 12, it constantly drops it’s signal and often refuses to connect to my access point.

I’m happy to report, however, that after I manually compiled the 2.6.32 kernel and booted with it, the wireless card works perfectly!

Unfortunately, it seems the 2.6.32 kernel also breaks a few things – booting takes 3 minutes, and the machine hard locks on with a black screen if you close the lid. I’m going to try to iron out those issues, but overall I’m pleased with the results.

Edit: I re-installed Fedora 12, then updated to the 2.6.32.1 kernel using the FC13 rpm’s from http://mirror.kernel.org – works like a charm now. I still can’t close the lid unless I have the action set to ‘do nothing’, but I can deal with that.

Additional Edit (02/15/2010): I’ve enabled the Rawhide repo and set it to only include kernel* and dependencies. The 2.6.33 RC chain works perfectly.

I have a love-hate relationship with NetworkManager on Fedora. I love it on my netbook for the ease it provides when trying to connect to wireless networks. However, I hate it on my dual-NIC workstation at work as it always mangles the connections and tries to route traffic through eth1 when eth0 is the primary network. As such, my favourite commands of the moment are:

chkconfig NetworkManager off

chkconfig network on

Then, a quick change to

/etc/resolv.conf

/etc/sysconfig/network-scripts/ifcfg-eth0

/etc/sysconfig/network-scripts/ifcfg-eth1

in order to add the correct nameservers, gateway, and IP addresses, and life is good!

I like bleeding-edge technology. The newer, the better, as there are usually fun little things to discover and rarely does anything bleeding-edge actually work perfectly, giving me ample opportunity to mess around with things.

Enter Fedora 12. I’ve played with the initial Alpha release, several of the Snap releases, and as of this morning, the Beta release. So far, at least as far as my MSI Wind 123 goes, they’re all unusable.

The biggest problem so far is the display – as soon as GDM kicks in, prior to the login screen loading, the screen starts to ‘pulse’. To be more specific, if you were to tap the ‘Brightness Up’ and ‘Brightness Down’ keys fairly quickly between two different levels, you’d get the same effect. This continues incessantly, and makes it impossible to use the GUI. If I boot in runlevel 3 (direct-to-console), everything is fine, so the issue is restricted to Xorg.

As far as the beta goes, there’s been a little regression. In the Alpha and Snap releases, I was able to get all the way to the desktop, despite the pulsing display. Now, with the beta, it takes just over 2 minutes just to get past the boot animation, and then it stalls before the login screen loads. Whether or not this has anything to do with the fact this is a livecd on a USB stick (made with the Fedora live-usbcreator for Windows, with persistent overlay), I’m not sure. I’ll probably download another spin (maybe the KDE version) and see if I have any more luck.

Update: Progess! On a whim, I removed rhgb from the kernel line when booting (press Tab to cancel automatic boot, and then again to edit boot options) and was actually able to get to the desktop, albeit with no improvement to the speed of things. The screen still pulses, however I did notice something interesting: while the screen pulses (briefly before the login screen appears, then it stops until you choose a user, and then it starts again), if I switch to another terminal (CTRL+ALT+F2, for example), the login name starts to fill with “^@” repeated several times, and then stops. If I then switch back to the GDM terminal (CTRL+ALT+F1), the pulsing stops.

At least that gives me something to go on.

Further Update (Dec 12, 2010): The Wind U123 works perfectly on Fedora 14 with no additional hacks/changes needed.

Considering that this is my development VM at work, I usually wear pants while coding. Apparently CentOS couldn’t see them through my desk and decided I needed a pair.

CentOS decided that I needed pants, so it installed the Trousers package.

CentOS decided that I needed pants, so it installed the Trousers package.

(Note: More information on the trousers package is available here.)

And while it may be a step in the write direction, there are a few little things that just bug me about the current iteration of the Moblin netbook distribution.

  • Power Button – Where is it? The short answer is there isn’t one – your only option is to simply use the physical power button on your netbook. Also, the shutdown terminal command is strangely absent. Thankfully, though, the reboot command is still there. It would be excellent if Shutdown/Reboot/Sleep were included in the options presented when you click the battery status icon.
  • myzone – There’s no way to customize the myzone tab, which is the default location on start up. You get three columns, and no control of them or choice in adding other quick content. Not very handy for a start page, in my opinion.
  • Persistence – The detailed instructions page that tells you how to put Moblin on a flash drive/SD card/whatever doesn’t explain how to add a persistence layer so that your changes survive a reboot. All of the instructions/utilities supplied simply bite-copy the image to your device and that’s that. Supposedly you can use the Fedora LiveUSB Creator to do this, but I’ve yet to try it. Having an official utility would help, and something that I hope to see coming down the road.

So for the time being, Moblin is something that’s neat to play around in – it has an amazing interface that’s refreshing and definitely easy to use for Linux (or computer-in-general) newbies – but still has some growing to do before I’d use it in place of a full distribution.

With any luck, they’ll work on these things for the final version of Moblin 2, or if not that, than hopefully for Moblin 3.

Edit: Also useful information, the root password for Moblin 2 is ‘moblin’. And for some reason, although sudo is installed by default, the standard user (also ‘moblin’) isn’t in the /etc/sudoers file, so you can’t use sudo unless you manually add it. That needs to get fixed as well.

I recently picked up an MSI Wind U123, and have been doing my usual try-every-operating-system-I-can-find-and-see-what-happens tests. Along the way, I’ve tried Windows XP (was installed by MSI, lasted a few minutes before I got rid of it), Windows 7 (worked fine out-of-box, no extra drivers needed), Moblin v2 (not a big fan of the UI, but ran very well from an 8GB SDHC card), Fedora 12 (big issues with this one, but it’s only an Alpha release), and now I’m at Fedora 11.

I dumped the Live image of Fedora 11 (Gnome desktop manager) on to my SD card (the U123 supports booting from SD cards, something my old Acer AspireONE couldn’t do), and installed it in less than 10 minutes, boot times included. Almost everything works out-of-box, however the Gnome UI was horrifically huge. Most windows would fill the screen and beyond, making it impossible to see buttons, let alone click them.

The solution? Change the default DPI. To do this, login, then click the System menu, followed by Preferences and Appearance. In the resulting window, click the Fonts tab, then the Details button at the bottom. In the new window, change Resolution to 96 and hit Enter on your keyboard (as the Close button is just out-of-view). Everything should be back to normal.

In addition to this, I also changed all of the font sizes to 8, but that isn’t strictly necessary – I just like to get as much on the screen as I can.

Beyond that, everything else works perfectly, including sound, wireless, the SD card reader, and even the webcam.

Update (Dec 12, 2010): The Wind U123 works perfectly on Fedora 14 with no additional hacks/changes needed.