Free Space on Phone's SD Card Incorrect in Nautilus

Thanks for your bug report.

James: do you have an idea about that? Should I forward the bug to some place?

Daniel: I haven't yet set up a place to report bugs in gnome-vfs-obexftp. I should probably register it on Launchpad ...

The obexftp method is just using the free space number for the first memory type.

I notice the bug on my phone: it is returning the free space for the phone even though I have an MMC card. Looking at a directory listing ("obexftp --bluetooth ... --list"), I see that it does tell me the memory type for each item in the root directory:

  <?xml version="1.0"?>
  <!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd"
   [ <!ATTLIST folder mem-type CDATA #IMPLIED> ]>
  <folder-listing version="1.0">
      <folder name="Memory card" user-perm="RW" mem-type="MMC"/>
      <folder name="Images" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Video clips" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Music files" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Graphics" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Tones" created="19800101T000008" user-perm="R" mem-type="DEV"/>
      <folder name="Recordings" created="19800101T000008" user-perm="R" mem-type="DEV"/>
  </folder-listing>

So with this listing, I should be using the "DEV" free space value for "/Images", but the "MMC" free space value for "/Memory card". I've got no idea if there is a more direct way to work this out than listing the parent folder to find the memory type.

So the bug does look fixable, which is good. The alternative would have been to remove the free space calculation code ...

I just had a look at the OBEX spec, and it seems that this mem-type attribute is not part of the standard.

In fact, the inclusion of this attribute in folder listings is the subject of one of Nokia's patent applications (http://www.freepatentsonline.com/20060095537.html), so it is probably not found on other manufacturers phones.

I've made the above change, which seems to work at the GNOME-VFS level:

    >>> import gnomevfs
    >>> bda = '00:0E:ED:...'
    >>> def free_space(path):
    ... uri = gnomevfs.URI('obex://[%s]%s' % (bda, path))
    ... return gnomevfs.get_volume_free_space(uri)
    ...
    >>> free_space('/')
    4802560L
    >>> free_space('/Images/')
    4802560L
    >>> free_space('/Memory%20card/')
    26442752L

However, I am still seeing 4.6MB free space when browsing "Memory card" in Nautilus, so there is probably something else I need to do to get it working in Nautilus.

Just tried restarting Nautilus again, and things started working. Nautilus now shows 25.2MB free on the memory card, and it let me copy a file to the memory card that wouldn't fit on the phone's memory.

So this bug will be fixed for the 0.3 release (provided you have a Nokia phone, or one that provides the same data in folder listings).

Fixed in the 0.3 release.

gnome-vfs-obexftp (0.3-0ubuntu1) gutsy; urgency=low

  * New upstream release:
    - Sync osso-gwobex and osso-gnome-vfs-extras changes from Maemo
      Subversion.
    - Instead of asking hcid to set up the RFCOMM device for communication,
      use an RFCOMM socket directly. This is both faster and doesn't require
      enabling experimental hcid interfaces.
    - Improve free space calculation for Nokia phones with multiple memory
      types (e.g. phone memory and a memory card).
      Now the free space for the correct memory type for a given directory
      should be returned. This fixes various free-space dependent operations
      in Nautilus such as copying files. (LP: #116912)
    - debian/copyright: updated. (LP: #120146)
    - debian/control.in:
      - added libbluetooth-dev (>= 3.7) to Build-Depends.
      - changed Maintainer field.

 -- Daniel Holbach <email address hidden> Wed, 13 Jun 2007 09:00:05 +0200

I have tried both 0.2 and 0.3 with my SonyEriksson z710. Both versions report 0 bytes free space, so I can't copy anyting to the phone. I tried 0.2 with my old phone K610 and that worked, but that phone didn't have a memory card.

So in short... this bug still is valid for new SonyEricsson mobiles with memory cards

Did you try to restart nautilus? Did you pair the phone with your machine properly?

Just to be sure I tested again and restarted everyting (including phone, nautilus, bluez, gnome-vfs-daemon) and still not working.
The phone is paired, and I can access the phone and browse the content, copy from the phone to the desktop but not to the phone.

I don't know if it helps, but it seems that there are no mem-type specified on this phone....

obexftp --bluetooth 00:16:B8:75:7F:34 --list
Browsing 00:16:B8:75:7F:34 ...
Channel: 7
Connecting...done
Receiving "(null)"... <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<!--
 XML Coder, (C) 2001 Sony Ericsson Mobile Communications AB
-->
<folder-listing version="1.0"><folder name="Telefonminne"/>
<folder name="Memory Stick"/>
</folder-listing>
done
Disconnecting...done

Matthias: I don't think your problem is related to this bug report -- this one is about distinguishing what volume a particular directory resides on and returning the appropriate free space. Your one sounds more like faulty reporting of free space.

I've heard of a few other people having trouble with Sony phones, but don't have the hardware to debug it. If you would like to help me debug the problem, I suggest opening a new bug report. I've got a few commands you could run to collect data that would be useful in tracking down the problems.

Ok, opened the bug 120214

Closing the bug report.

I Had a similar problem with a Sony Ericsson W595 with a 2GB M2 memory card, and resorted to purchasing a external card reader for a few pounds. I do have to admit this was an easy way out and avoided correcting the real problem. :(