• SCMxx - Play with Siemens from linux.
  SCMxx allows you to exchange certain types of data with mobile phones made by Siemens. It works with the S25, S35i, M35i, C35i, SL45, S45 and ME45 and probably others.
• Connect mobile phone via infrared with Linux box

OpenOBEX - Free open source implementation of the Object Exchange (OBEX) protocol.

OpenOBEX Home

Open OBEX SourceForge

# bez šī obexftp-0.20 nekompileesies (jāsak viss no sākuma arii cp...):
yum -y install bluez-libs-devel bluez-hcidump
# Priekš obexfs vajag:
yum -y install fuse fuse-libs fuse-devel fuse-convmvfs fuse-encfs fuse-smb fuse-sshfs

# openobex:
./configure; make; make install
cp openobex.pc /usr/lib/pkgconfig/ # (bez šī nekonfigurējas obexftp)

# obexftp:
./configure; make; make install

# obexfs
# tam vajag fuse

Tested versions: openobex-1.3 obexftp-0.20 obexfs-0.8

ObexTool

yum install tk tk-devel tcl-devel

• BWidget Toolkit
• Tablelist
• te tas viss aprakstīts: obextool Installation

# tam jāizskatās šādi:
/usr/share/tcl8.4/BWidget-1.8.0
/usr/share/tcl8.4/tablelist4.6

tar -C /usr/local/ -xzvf obextool-0.33.tar.gz

Usage

/usr/local/obextool-0.33/obextool.tk
# or try using a commandline like this:
obextool.tk --obexcmd "obexftp -t /dev/modem"

# You may also create a symlink in the binary directory:
ln -s /usr/local/obextool/obextool.tk /usr/bin/obextool

# Note: You must set the environment value OBEXTOOL to the 
#  installation dir if using a file link to obextool.tk.

#!/bin/sh
# ralfs
# ObexTool startup shell

# IrDA:
# --obexcmd "obexftp -t /dev/ircomm0"
# USB:
# --obexcmd "obexftp -u 0"

OBEXDIR=/usr/local/obextool-0.33
OBEXTOOL_CFG=/usr/local/obextool-0.33/etc
# ralfs
# NEVIENS NEDER :(
# OBEXTCMD="$OBEXDIR/contrib/obexftp/obexftp.static -t /dev/ircomm0"
# OBEXTCMD="$OBEXDIR/contrib/obexftp/obexftp.static -u"
OBEXTCMD="/usr/local/bin/obexftp -u"
export OBEXDIR OBEXTOOL_CFG OBEXTCMD
#
# Let's start the ObexTool without memory status
# feature (if no Siemens), using Tk version 8.4 and
# a specific configuration directory /etc/obextool
# and the contributed static compiled obexftp version.
# wish8.4 $OBEXDIR/obextool.tk --memstat 0

# tas par maz:
# exec $OBEXDIR/obextool.tk --memstat 0
exec $OBEXDIR/obextool.tk --memstat 0 --obexcmd "obexftp -u 0"

Var ņmt te: /usr/local/obextool-0.33/contrib/startup/obextool

!!! Atkarībā no pieslēguma SALABOT /dev/ircomm0:
/usr/local/obextool-0.33/etc/obexwrap.sh

### Tested versions:
obextool-0.33.tar.gz
BWidget ToolKit 1.8.0 October 2006
Tablelist 4.6

Links

FUSE - Filesystem in Userspace

FUSE Homepage and Wiki about FUSE

Fedora Core 6 Extras repo have:
# fuse-2.6.3-2.fc6: File System in Userspace (FUSE) utilities
# fuse-convmvfs-0.2.3-2.fc6: FUSE-Filesystem to convert filesystem encodings
# fuse-devel-2.6.3-2.fc6: File System in Userspace (FUSE) devel files
# fuse-emulator-0.7.0-6.fc6: The Free UNIX Spectrum Emulator
# fuse-emulator-utils-0.7.0-5.fc6: The Free UNIX Spectrum Emulator
# fuse-encfs-1.3.1-3.fc6: Encrypted pass-thru filesystem in userspace
# fuse-libs-2.6.3-2.fc6: File System in Userspace (FUSE) libraries
# fuse-smb-0.8.5-5.fc6: FUSE-Filesystem to fast and easy access remote resources via SMB
# fuse-sshfs-1.7-2.fc6: FUSE-Filesystem to access remote filesystems via SSH

The phone should be useable then, but most probably, it will be accessible only as root user, as udev creates the corresponding devices with basic (root) permissions by default. We'll try to adapt this so that it can be accessed by any user in the dialout group.

Next, let's try and check the phone's characteristics in udev (you will need to adapt the path given bellow to the USB device numbers seen in lsusb above) :

# udevinfo -a -p /class/usb_device/usbdev2.8

  looking at device '/class/usb_device/usbdev2.8':
    KERNEL=="usbdev2.8"
    SUBSYSTEM=="usb_device"
    DRIVER==""
    ATTR{dev}=="189:135"

  looking at parent device '/devices/pci0000:00/0000:00:03.0/usb2/2-2':
    KERNELS=="2-2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{configuration}=="WMC Device"
    ATTRS{serial}=="3517090195964940"
    ATTRS{product}=="Sony Ericsson K610"
    ATTRS{manufacturer}=="Sony Ericsson"
    ATTRS{maxchild}=="0"
    ATTRS{version}==" 2.00"
    ATTRS{devnum}=="8"
    ATTRS{speed}=="12"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceClass}=="02"
    ATTRS{bcdDevice}=="0000"
    ATTRS{idProduct}=="d046"
    ATTRS{idVendor}=="0fce"
    ATTRS{bMaxPower}=="500mA"
    ATTRS{bmAttributes}=="80"
    ATTRS{bConfigurationValue}=="3"
    ATTRS{bNumInterfaces}=="10"

This suggests that this phone obeys the WMC Device specification (WMC : Wireless Mobile Communication : http://www.usb.org/developers/devclass_docs/cdc_wmc10.zip), which means it understands OBEX commands.

Based on the above informations, it's safe to think that the phone can be configured in UDEV like the following.

SUBSYSTEM=="usb_device",                        GROUP="dialout", \
        ATTRS{configuration}=="WMC Device"

SUBSYSTEM=="usb_device",                        GROUP="dialout", \
        ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="d046"

I suspect the first one to be more generic, but I'm not so completely sure... any reports on your side may be helpfull.

Now, if you issue the following command, then unplug the phone and plug it again, you should be able to access it if your user is in the dialout group :

udevcontrol reload_rules

Now, we will try and access the contents of the phone through OpenOBEX tools. Thanks to http://dburr.veritel.com.au/nokia/ for useful commands.

$ obexftp -u 0 -l