Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
By Hammett at 2004-06-08 05:18
After many many months of trying almost everything, finally I managed to get file transfers between my Linux box and my mobile phone (Nokia 3650), although it will work also on other mobile phones with bluetooth. Take a look at p3nfs for all compatible mobiles. Here are the steps:
The things you're gonna need are: bluez, bluez libs, bluez apps, and p3nfs.
First of all, load rfcomm module, and run it. If you get an error such as "rfcomm: can"t get device list: operation not supported" you need to do the following:
Go to the kernel source directory and do "make menuconfig", save the config to a file, after that, edit that file and look for CONFIG_BLUEZ_RFCOMM_TTY=m and substitute the "m" for a "y", so you end up with CONFIG_BLUEZ_RFCOMM_TTY=y. This is a kernel bug, as this cannot be build up as a module, but in the config appears as, that's why you get the error.
This error has been seen in kernels 2.4.22 to 2.4.25 (the ones I tried). Seems that with kernel 2.6 the bug has been fixed (at least in 2.6.6).
Once changed this, save the file, run kernel configuration and load the new config. Now compile it.
OK, now is time to pair the mobile with the dongle:
First of all, activate the dongle by doing "hciconfig up"
In your mobile, enable bluetooth and make it discoverable to all devices, once that is done, run "hcitool scan", for seeing your mobile
Keep that address (your mobile phone), as you will need it later on.
OK, now ping you phone to see that there's connection, for doing that type:
[root][/etc/bluetooth]$ l2ping 00:60:57:75:7C:36 (Mobile's address)
Ping: 00:60:57:75:7C:36 from 00:01:53:00:0D:08 (data size 20) ...
0 bytes from 00:60:57:75:7C:36 id 200 time 27.89ms
0 bytes from 00:60:57:75:7C:36 id 201 time 29.96ms
0 bytes from 00:60:57:75:7C:36 id 202 time 16.25ms
0 bytes from 00:60:57:75:7C:36 id 203 time 16.18ms
0 bytes from 00:60:57:75:7C:36 id 204 time 15.80ms
5 sent, 5 received, 0% loss
(Note that lower L, not 1 in l2ping). You should get something like that.
So far so good. Now it's time to configure RFCOMM. If you don't have a rfcomm0 device (most probably you won't), do:
cd /dev && mknod --mode 666 /dev/rfcomm0 c 216 0
Now, go to /etc/bluetooth directory, there are 3 files: hci.config, pin and rfcomm.config
Edit pin file and enter there the pin code you wish.
In your mobile phone, try to discover the PC, when PIN code is prompted, put the same PIN as in the file, you should pair the phone.
Edit rfcomm.config file and put the relevant information there (basically phone's address and port to use, which p3nfs use is port 4).
After that, you must bind /dev/rfcomm to that service, for doing that:
rfcomm bind /dev/rfcomm0 00:60:57:75:7C:36 4
(Substitute address by your's and note the 4 at the end, is the port we use). It is also advisable that you put this line also in a rc.d file, so you will bind the device at boot time.
Now is time to configure p3nfs. It is very easy to compile and install. What does p3nfs is to mount mobile's filesystem in the PC, so you can browse it as it was another part of your Linux box, so:
1.- create a mount point for the mobile
2.- Download the client p3nfs for the mobile at http://www.daimi.au.dk/~kbn/nfsapp-2.7-series60.sis , the only problem here is that you must install that SIS file on the phone by uploading it from windows (for example).
3.- Once client is installed on the phone, run it, and within 30seconds you must run:
Where /mnt/mobil is the mount point we created before (make any changes you need)
If you are using other mobile that is not Nokia, or compatible with series60, you have to change that as well. In p3nfs website you have a description of each "series" and which mobiles work with them.
And woot!! Now you can go to the mobile's mount point and start browsing.
For transferring pictures from the phone to the mobile, just copy them!! Like if it was another HDD, the other way round also works (Transfers from PC to MOBILE).
I suggest you to make a script to connect to the phone, it's more easy than writing all this command.
Well, that's how i managed to get working File transfers between Linux and Nokia 3650. I don't know how to make it for calendar synchronization or anything else, this is just file transfer (pictures and tunes basically).
Hope this will be useful to somebody, if so, please let me know. Also if there's any mistake or something is not working, I'll try to manage what's wrong.
I apologize in advance if there's any errors on the process, but I don't think i missed any part.