... 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 plans to use cable connection, be sure the cable is plugged-in :)).
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.
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 will You phone works with anyRemote at all. Cell phones known to work:
Some phone-specific details described here.
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.
You have to test, does the phone supports Event Reporting feature. See details here. If phone does not support Event Reporting then it could not be managed by anyRemote in AT mode.
You have to test, does the phone supports keypad emulation events. See details here. If phone does not support eypad emulation events then it still can be managed by anyRemote in AT mode, but SendCKPD(...) command will not work.