News
Downloads
Screenshots
Support
LiveMobileTools
Help Us
About KMobileTools
SubVersion howto
Links
Thanks- KMobileTools 0.5Same Bluetooth phone displayed twice + others problemsremi.chateauneu
- KMobileTools 0.5Blocks the UO when configuring a second phoneremi.chateauneu
- KMobileTools 0.5Hangs when reading .DCOPserver_DuoLnx__0remi.chateauneu
- KMobileTools 0.5Unable to use th KMobile toolsjaspreetsunnydeol
- KMobileTools 0.5support for tmobile dashslipin3
[ENGLISH] KMobileTools and Bluetooth Phones
Installation of the tools necessary to use Bluetooth phones with KMobileTools.
In the lastest 2.4.x and 2.6.x kernels Bluetooth support is already included, so we don't have to patch anything.
You only need to install some packages.
From the website www.bluez.org, Downloads section, get all the avaliable archives and install them in this order:
bluez-libs-2.9.tar.gz
bluez-utils-2.9.tar.gz
bluez-pin-0.23.tar.gz
bluez-firmware-1.0.tar.gz
bluez-hcidump-1.10.tar.gz
bluez-hciemu-1.0.tar.gz
in the usual way:
./configure
make
(this as root) make install
or you can go to http://www.bluez.org/packages.html to find some precompiled deb e rpm packages.
Now we need to launch two little daemons:
hcid
sdpd
>
When connecting our USB Bluetooth key, or any other adapter, check dmesg output to verify if your device is recognized.
The next step is to view your phone address.
Open bluetooth connection on your phone and type on your terminal:
hcitool scan
>
after a bit you'll read something similar to:
00:0E:07:CF:C2:C9 iManc T630
The first string is the phone address (depending from your model), the second is his name.
Now we need to create a device /dev/rfcomm0 that will associate with that address.
With:
mknod /dev/rfcomm0 c 216 0
create /dev/rfcomm0 if it's not present, and with:
rfcomm bind 0
associate it with your phone address..
To use qtmobiletools you should now only link /dev/mobile to /dev/rfcomm0:
ln -s /dev/rfcomm0 /dev/mobile
Or you can overwrite /dev/mobile if it exists with:
ln -sf /dev/rfcomm0 /dev/mobile
That's all, now your BlueTooth phone and KMobileTools can communicate!
kmobiletools w/ Nokia 6630 and 7650
Well, you can get those working as far as they work (Even Nokia PC Suite cannot access SMS of those phones if I remember correcly...)
First, I have udev, so I don't have to make /dev/rfcomm[x] by myself.
1. Check you phones BT address: *#2820#, and you can see your BT address. 'hcitool scan' gives other address, that doesn't work.
2. Bind your phone: 'rfcomm bind [channel] [address] 1' where [channel] is just one of the available channels and [address] is your phones BT address. For example: 'rfcomm bind 4 00:02:EE:46:6F:50 1'. This creates (if you use udev) necessary /dev/rfcomm.
3. Start kmobiletool and configure it to use /dev/rfcomm[x], for example /dev/rfcomm4.
If you don't have udev, just make that device by yourself. For example: 'mknod /dev/rfcomm4 c 216 4' and then bind it like mentioned above.
For these two Nokia models at least, proper channel is 1.
And for quick notice, you can send SMS, but you cannot read them, nor cannot you browse your SMS's or phonebook.