<!-- Hi -->

After installing iPodLinux, I found that Ubuntu Breezy would occasionally mount my ipodlinux partition before it mounted the actual ipod partition with my music. This completely confused programs like gtkpod, and generally was annoying. I don't pretend to know anything about HAL, but by reverse engineering what I could find (documentation on HAL is sparse and ugly) I came up with the file below.

If you place the below file in /etc/hal/fdi/policy/, and name it something like no-ipodlinux.fdi, iPodLinux will mount as /media/ipodlinux, and your ipod will always mount as /media/ipod. Hooray. Anybody who knows more about HAL than I, PLEASE feel free to correct me.

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
  <device>http://chrismurf.com/newsite/textpattern/txp_img/htmldown.gif
     <match key="block.is_volume" bool="true">
      <match key="volume.fsusage" string="filesystem">
        <match key="@block.storage_device:storage.no_partitions_hint" bool="false">

          <match key="@block.storage_device:portable_audio_player.type" string="ipod">
            <match key="volume.fstype" string="ext3">
              <!-- Attempt mount point 'ipodlinux' for iPodLinux, or any ext3 on an ipod -->

              <merge key="volume.policy.desired_mount_point" type="string">ipodlinux</merge>
            </match>
          </match>
        </match>
      </match>
    </match>
  </device>
</deviceinfo>

Warning – I take absolutely no responsibility if you hose / break your phone. The people at Verizon will probably laugh at you, so don’t expect any sympathy from them either. You’re on your own.

Installing BitPim

The first step is to install BitPim. The website documentation is relatively decent. I tried installing it for Windows, but had a hard time as I do not have access to the official v265 USB drivers necessary. If somebody could hook me up with those, I would much appreciate it. I got it working under linux without really any trouble by using the ACM kernel module. There is some documentation on the bitpim site about setting up hotplug appropriately. This part is the most obnoxious part. I can’t really help.

Ground Rules

Do not use any view other than filesystem. Do not change files if you don’t know what they do. I can’t help you – I am in no way a professional. If you get it hosed up, I don’t care. I would strongly suggest before you overwrite ANY files, you make a backup copy of the original by right clicking and selecting "Save…". This may help you later, or it may not.

Images

In the filesystem view, you can navigate to /motorola/shared/picture/. You will note there is a long list of pictures. Everytime you take a photo, it is added to this list as a .jpg file. You can rename the photos that you take through the phone interface, in the normal way. If you, for example, rename an image to Pretty Sunset in the phone, it will be named Pretty Sunset.jpg. You can then download the picture to your computer by right clicking and selecting "Save…".

At this time, it does not seem that BitPim supports adding files to the v265 filesystem. It does, however, support overwriting existing files. First, take a photo of something random. Next, find a photo on your host computer that you want to replace it with. It should be a jpg. You can then right click on the file on your phone, and select overwrite. After navigating to the new photo, BitPim will replace the picture on your phone with the photo from your computer. Thus, to add a picture you take a photo, and then rename it, and then overwrite it. I hope BitPim supports ‘adding’ sometime soon :-)

Ringers

In the filesystem view, you can navigate to /motorola/shared/audio/. You can use a similar strategy as above to overwrite existing ringers, with one catch. I have not yet found a way to ‘add’ a new sound. This means that you need to overwrite an existing ringer. Hopefully this will be rectified soon.