Dear Wiki user, You have subscribed to a wiki page or wiki category on "Freevo Wiki" for change notification.
The following page has been changed by 62.127.14.162: http://freevo.sourceforge.net/cgi-bin/moin.cgi/DocumentationPage ------------------------------------------------------------------------------ @@ -346,47 +346,60 @@ the file consists of many of the above sections seperated by a blank line. For a listing of all available commands and how they are mapped within the different events (Playing Audio, Video, TV, etc...) look at freevo/src/event.py . -=== Bluetooth Remote Control deamon === +=== Bluetooth Remote Control helper === This is a small deamon that let's you control Freevo with your cellphone. Tested with a Sony Ericsson T68, and in theory it works with Nokia telephones too. It should work with ALL cellphones that have event reporting and bluetooth. -You start it with "freevo bluetooth". It's placed somewhere under helpers, I think it is in src/helper/bluetooth. +You can find it in src/helpers/bluetooth.py -If you got a Ericsson T68 you should be happy with the current settings. (It's a bit akward but it works, the phone it was tested with had some semi-operational buttons; they only worked from time to time.) -It's fairly easy to change the button bindings, but beware that some buttons DO NOT WORK, i.e joystick up on the SE T68. -Just use a texteditor to edit bluetooth.py. If you got another phone, a Nokia or something else, you might want to check out what the buttons are called. Get a program called minicom and start it with "minicom -s", enter "Serial port setup" and set it to your bluetooth device. (/dev/rfcomm1, /dev/bluetooth/rfcomm1, /dev/bluetooth/rfcomm/1) As you already guessed it changes from system to system and the ending number, 1, is set by rfcomm. More about this later. +* NEW VERSION * +This version is untested (more or less) and is poorly written but it should work much better then the old. +You can find it at: -Example: -kp2direction = {"u":"VOL+", "d":"VOL-"} If you press the button called "u" (UP, the volume slider on the side of a T68) the remote will send "VOL+" to the network remote. This isn't a thing you might want to change, but I hope you understand how it works. +http://asm.meeep.net/ikea/bluetooth.py + +http://asm.meeep.net/ikea/local_conf.py.bluetooth <- Config example, you gotta get it too. + +New features: + + * Button exploring ("bluetooth.py --configure" Press a button on the phone and see what it's called. Used for buttonconfiguration.) + * Keylock feature ("bluetooth.py --ericsson" Makes it send commands only if the keypad lock is on. Ericsson only, so far.) + * Sleeping (Don't chew all CPU power, check the config) + * Keep alive (Fixes the disconnection problem by sending "ATI" once in a while, check the config. Untested) Requirements: - * A Bluetooth phone, a Bluetooth dongle. The phone should be able to receive AT (Hayes) commands, and it must have a certain command that sends all keypad events to the computer. (It's "AT+CMER=3,2,0,0,0", if you send it to your phone with minicom it should say "OK" back.) + * A Bluetooth phone, a Bluetooth dongle. The phone should be able to receive AT (Hayes) commands, and it must have a certain command + that sends all keypad events to the computer. (It's "AT+CMER=3,2,0,0,0", if you send it to your phone with minicom it should say + "OK" back.) * The Bluetooth Subsystem (kernel) * Bluez-utils (and it's deps, http://bluez.sf.net) -The bluetooth subsystem was tricky with a patched kernel so I recommend the 2.4.21 kernel, which has the bluetooth subsystem by default. When you are sure you got that working (test by running "dmesg | less" and look for bluetooth driver messages) you may want to create a bluetooth device in /dev/ if bluetooth doesn't make one for you. Google for it, I don't know how you do that (makedev 43 115 or similiar, but that aren't the right numbers though). +The bluetooth subsystem was tricky with a patched kernel so I recommend the 2.4.21 kernel or newer, which has the bluetooth subsystem by default. When you are sure you got that working (test by running "dmesg | less" and look for bluetooth driver messages) you may want to create a bluetooth device in /dev/ if bluetooth doesn't make one for you. Google for it, I don't know how you do that (makedev 43 115 or similiar, but that aren't the right numbers though). + When you got your device set up you run some bluez command to look for your phone. -"hciconfig hci0 up" Set your bluetooth interface. -"hcitool scan" Look for your bluetooth phone. On my T68 you must set the phone to "Searchable", item number one in the bluetooth menu. (Then the phone says "You may find me for 3 minutes" or something like that) + +"hciconfig hci0 up" +Set your bluetooth interface. + +"hcitool scan" +Look for your bluetooth phone. On my T68 you must set the phone to "Searchable", item number one in the bluetooth menu. (Then the phone says "You may find me for 3 minutes" or something like that) + hcitool then reports the bluetooth adress for your phone. Remember it. You will use it later on. Now you need to find out on which port the serial interface is on. (On the phone that is.) On my phone it's port number 6. -"hcitool info bluetooth adress" -> hcitool info and the adress that hcitool scan gave you. Look for "Serial" somewhere in there. (And the port/channel that represents it) +"hcitool info bluetooth adress" +hcitool info and the adress that hcitool scan gave you. Look for "Serial" somewhere in there. (And the port/channel that represents it) -then you bind that port/channel on the phone to a device in /dev/. -"rfcomm bind 1 bluetooth adress channel" -> rfcomm bind 1 00:11:22:33:44:55:66 6. THAT IS AN EXAMPLE ONLY! :) -Check if it's working with "rfcomm". +Then you bind that port/channel on the phone to a device in /dev/. +"rfcomm bind 1 bluetooth adress channel" +(rfcomm bind 1 00:11:22:33:44:55:66 6. THAT IS AN EXAMPLE ONLY! :)) -Make sure you enable support for the network control in local_conf.py("ENABLE_NETWORK_REMOTE = 1"), otherwise Freevo won't receive any commands and you should get an error from the deamon. - -IMPORTANT! -The port is changed to 35000 in the deamon which isn't the default port for the network remote function. +Check if it's working with "rfcomm". -I made an init-script to start the bluetooth interface (hciconfig) and rfcomm. This script also starts the deamon, which I also recommend you to do. -The deamon seem to disconnect after a while, a solution to that is welcome. (bluetooth disconnects after 20 minutes of inactivity.) +I made an init-script to start the bluetooth interface (hciconfig) and rfcomm. This script also starts the deamon, which I also recommend you to do. It must be started after freevo (untested, but I think so). If you need any help you can find my email adress in the deamon source. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Freevo-wikilog mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-wikilog
