Skip to content

# anyRemote

# Setup anyRemote to work in AT mode

## Be sure that ...

- ... bluetooth subsystem is working. Your bluetooth phone should be paired already.
- If You use IR connection, IrDA service should be configured and the phone should be visible in output of irdadump utility.
- If You plan to use cable connection, be sure the cable is plugged-in :).

## Definition

Mobile Equipment Event Reporting functionality means what cell phone is able to send the unsolicited result codes for key presses, display changes, and indicator state changes.

- AT+CKPD command: AT command which emulate presing on phone keypad
- AT+CMER command: AT command which enables/disables event reporting feature
- CKPD key: CKPD command has the following format AT+CKPD="X", where "X" is key-kode for button to emulate. So, CKPD key is "X"
- CKPD sequence - sequence of CKPD keys.

## Supported hardware

anyRemote will try to determine phone model automatically, so just try any of configurational file from cfg-data/AT-mode directory. It should works out-of-the box for Motorola, Siemens and SE users. If You was not lucky please read further.

Firstly it needs to verify if your phone will work with anyRemote at all. Cell phones known to work:

- Benq-Siemens EL71, S68
- Motorola L6, V3i, V500 (Bluetoon and Cable), seems all Motorola V*** phones
- Sagem-my700Xi, Sagem-my6X-2
- SE-K700, K750 (Bluetooth and IR), it should works with T610/T630 and all modern non Symbian-based SE phones
- Siemens S55, S65, CX75

Cell phones known not to work:

- Nokia 6310i, 6021 (6021 supported in Server mode)
- Samsung S300
- Siemens ME45

Some phone-specific details described here.

## Bluetooth connection: /dev/rfcommX setup

Switch on bluetooth on cell phone and set it in discoverable mode. Run `hcitool scan` command. You will see somthing like:

    hcitool scan
    Scanning ...
    		00:07:3A:08:EE:74       Nokia

Then run `sdptool browse XX:XX:XX:XX`, where XX:XX:XX:XX is bluetooth address found at the previous step. You will see something like:

    sdptool browse 00:07:3A:08:EE:74
    Browsing 00:07:3A:08:EE:74 ...
    Service Name: Dial-up networking
    Service RecHandle: 0x10000
    Service Class ID List:
      "Dialup Networking" (0x1103)
      "Generic Networking" (0x1201)
    Protocol Descriptor List:
      "L2CAP" (0x0100)
      "RFCOMM" (0x0003)
        Channel: 1
    ...
    Service Name: COM 1
    Service RecHandle: 0x10002
    Service Class ID List:
      "Serial Port" (0x1101)
    Protocol Descriptor List:
      "L2CAP" (0x0100)
      "RFCOMM" (0x0003)
        Channel: 3
    ...

Search for "Serial Port" or "Dialup Networking" services and their channel numbers.

To setup /dev/rfcommX, execute: `su -c "rfcomm bind XX:XX:XX:XX Y"` where Y is channel number obtained from sdptool output. Alternatively You can edit /etc/bluetooth/rfcomm.conf file.

To connect anyRemote to /dev/rfcommX it needs to run anyRemote with `-s /dev/rfcommX` command line parameter or specify it in configuration file directly.

## Does the phone support Event Reporting?

You have to test, if the phone supports Event Reporting feature. See details here. If phone does not support Event Reporting then it cannot be managed by anyRemote in AT mode.

## Does the phone support keypad emulation events?

You have to test, if the phone supports keypad emulation events. See details here. If phone does not support keypad emulation events then it still can be managed by anyRemote in AT mode, but SendCKPD(...) command will not work.

Maintained by anyRemote. Website by m.lettner.