opensuse sees android system but nothing whats in it


when connecting android tablet opensuse sees device as camera, I can see folders but there is nothing in it. Can these be a issue with mounting point or am I missing something else?


What is you device ? Wich protocol does it use ? mtp or else ?

On Thu, 09 Jun 2011 19:06:03 +0000, loand wrote:

> hi
> when connecting android tablet opensuse sees device as camera, I can see
> folders but there is nothing in it. Can these be a issue with mounting
> point or am I missing something else? thanks

When I mount my Android phone on my Linux system, there’s an application
on the phone to tell the system to present itself as a USB storage device

  • you might need to do something similar with your tablet.


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at

its xoom,I maked folder ‘xoom’ then a xoom.rule, which is:

 # 70-motorola-xoom.rules
    # Put in this file in /etc/udev/rule.d/
    #ATTRS{idVendor}=="22b8" , ATTRS{idProduct}=="70a8" , ENV{ID_MEDIA_PLAYER}="motorola_xoom" , ENV{UDISKS_PRESENTATION_ICON_NAME}="tablet-motorola-xoom"
    #ATTRS{idVendor}=="22b8" , ATTRS{idProduct}=="70a9" , ENV{ID_MEDIA_PLAYER}="motorola_xoom" , ENV{UDISKS_PRESENTATION_ICON_NAME}="tablet-motorola-xoom"

    ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="70a8", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="proprietary", ENV{ID_MEDIA_PLAYER}="1", ENV{ID_MTP_DEVICE}="1", MODE="0664", GROUP="audio"

    ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="70a9", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="proprietary", ENV{ID_MEDIA_PLAYER}="1", ENV{ID_MTP_DEVICE}="1", MODE="0664", GROUP="audio"


    # Motorola Xoom (ID 1)

    #ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a8", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="proprietary", ENV{ID_MEDIA_PLAYER}="1", MODE="664", GROUP="audio"

    # Motorola Xoom (ID 2)


mounted with the mtpfs -o allow_other,
and when I plug in my tablet I can see device as “camera” in most recent devices.
I am not sure what is the proper name for that so I am providing screen-shot:

when I go to properites on any folder on my tablet (recognized as camera?) I can see that:
/MTP Device@usb:002,005/store_00010001 (camera)

is it bad mounting point?

I have the xoom working using the mtpfs -o allow_other /xoom, you need to create the directory
/xoom with primissions set for your user can rw. The rule file is used to access the xoom with programs like dolphin but all the directories are empty. Mounting with the mtpfs command I’m able to see the directories and files. Reading and writing work. The difference may be I’m using tumbleweed which may have a updated lib that works. Also, are you in the audio group? If you notice the end of the attrs lines group=audio.
I’m using the same rules file from the mot web site.

yes I am in audio group and the /xoom folder has 777 permissions.
when I connect the xoom new device pops up and I can browse the xoom folders but there is no data there and I can’t write any files there.
When I am mounting xoom with the mtpfs -s -o allow_other /xoom
I am getting that message:

linux-c6ea:/home/andre/Dokumenty # mtpfs -s -o allow_other /xoom
fuse: bad mount point `/xoom': Transport endpoint is not connected

mount point? maybe some other roules has effect on mounting xoom?
here is the ls /etc/udev/rules.d reuslt:

linux-c6ea:/home/andre/Dokumenty # ls /etc/udev/rules.d/
40-xend.rules     56-hpmud_support.rules             70-persistent-net.rules
40-xen.rules      56-sane-backends-autoconfig.rules  71-multipath.rules
51-android.rules  60-vboxdrv.rules                   77-network.rules
51-lirc.rules     60-vboxguest.rules                 81-mount.rules
52-irda.rules     70-kpartx.rules                    99-iwlwifi-led.rules
55-hpmud.rules    70-motorola-xoom.rules             kino.rules
55-libsane.rules  70-persistent-cd.rules             winetricks
linux-c6ea:/home/andre/Dokumenty # 

Hi Jim,

Android 3.0 doesn’t do USB mass storage any more like on the phones up till 2.3 at least (my phone also has Android), the tablets use MTP. I’ve got the same problem with my xoom. Do you use a specific app on your phone to mount it in Linux or do you use the normal USB mass storage that unmounts the SD card from the phone and mounts it onto the computer?

I reloaded OpenSuse 11.4 and was able to redo the configuration I used to access the Xoom.

  1. Installed 11.4 and fully updated to the current level.

  2. Installed fuse-devel

  3. Enabled the packman repo

  4. Installed mad and id3tags from the packman repo

  5. downloaded mtpfs_0.9.orig.tar.gz (google the source)

  6. Unpacked, configure and make install the mtpfs binary

  7. Ran mtpfs -o allow_other /xoom after mkdir /xoom

  8. The xoom was readable at this point.

This didn’t require tumbleweed or too many compiles to get it working.

I was able to copy the rules file into the /etc/udev/rulles.d/ directory, the device notifier sees the
device but only reads the root directory of the xoom, no subdirectories or files.
Once the device is mounted dolphin can be used to navigate to the /xoom directory.

Don’t forget to unmount the xoom when done.

fuermount -u /xoom

I did most of this with root but I don’t think it’s necessary.

I’ve got all of those things installed except for one: id3tags from Packman. I couldn’t find id3tags, but I did find id3tag. However, there was no Packman version. Where’d you get that version from? My Xoom is also not readable :frowning:

I note in this thread Difference Between Android 3.0 and 3.1 Honeycomb that for USB connectivity it is best to have Honeycomb (Android) version-3.1 :

Android 3.1 is the first revision to Android 3.0 (Honeycomb), the tablet optimized operating system. Google announced the update on 10 May 2011. The first major update to Honeycomb refines many of the features in the original Honeycomb version. The improvements are added on to the same UI and features in Android 3.0. The new features added on to Android 3.0 include refined UI, resizable home screen widgets, added support for many new input devices like any type of external keyboards, mouse, gamepads, game controllers and digital cameras, support USB connectivity for Android powered external hardware devices, attach one or more input devices simultaneously over USB and/or Bluetooth, improved multitasking with expandable recent apps list and robust Wi-Fi networking. The improvements are on Browser application, Gallery apps, Calendar,email and enterprise support[LEFT]

loand and erget, I think you both have xoom tablets ? I read here on itechreport on the xoom that it is being sold with android 3.0 and should have 3.1 later. I’m thinking not having Android 3.1 could be contributing to the difficulty you are having with your xoom.

hi oldcpu, it is 3.1 android.

hi dwellen,

I did all the same steps like you including fuse, man+id3tag mtpfs from source 70-motorola.rules from motorola website and still getting the same error :

fuse: bad mount point `/xoom': Transport endpoint is not connected

I think there is some problem with fuse and I think I am missing fuse.conf files so can you please show me result of whereis fuse command I will compare with my. I found that on ubuntu/redhat should be fuse group and /etc/fuse.conf which I am missing.
I will compare your result of whereis fuse with my when I get home.

erget, the id3tag can be installed from source just google it, sorry I am not writting from my laptop so can let you know later on.

I didn’t install the /etc.fuse.conf file. The rules file is needed only by udev and
controls the notifier. It isn’t needed for mtpfs. I didn’t have to add to the user
to any groups other then default. This can be ruled out using root to mount and

The whereis command’s output was exactly the same as your results. It just reports
the same two files.
Some people on the web have seen this error due to a defective usb cable. Motorola
however uses a special cable so it isn’t a easy option to try another.
Another option to rule out hardware is to boot a live-cd on a different distribution that
is known to work with the xoom.