Author Topic: Bluetooth Cellphone Modem (Read 7448 times)

walts · « **on:** September 11, 2007, 10:51:22 am »

I've gotten pdaXii13 running on my C3200 and everything is great! This is the best RO
M implementation I have seen on many Zaurii over the years!

Thanks to all who have helped me to get this installed and running.

Now I have a new challenge - I'd like to use my cell phone as a modem via Bluetooth. So far the only thing I can find on the subject is on Hluc's excellent page on pdaXii13:

Quote

GPRS network connection via Bluetooth also works. Make sure /etc/bluetooth/pin contains your PIN and then use the PPP config tool to configure the preconfigure GPRS profile to look for your phone. Then use the PPP dialer to connect to the phone to enable the GPRS connection.

I've done that, entering my Cingular information into the PPP config tool, and when I try to connect wiht the PPP dialer, it gives
"Failed to open /dev/rfcomm0: No such device"

/dev/rfcomm0 is specified as the device on the Modem tab of the PPP config tool, and was already filled in. It's just a plain text field, no other choices offered.

Based on some other threads (not for pdaXrom) it looks like hciconfig is to Bluetooth as ifconfig is to Wi-Fi, but when I run it it returns nothing.

The Bluetooth card is an AmbiCom BT2000-CF and cardctl ident says

product info: "Compact Flash", "Bluetooth Card", "", ""
manfid: 0x0319, 0x0000
function: 2 (serial)

I'm not sure where to go from here, I'd appreciate any help or advice.

TIA

Walt

andrewwoods · « **Reply #1 on:** September 11, 2007, 01:15:28 pm »

Quote

I've gotten pdaXii13 running on my C3200 and everything is great! This is the best RO
M implementation I have seen on many Zaurii over the years!

Thanks to all who have helped me to get this installed and running.

Now I have a new challenge - I'd like to use my cell phone as a modem via Bluetooth. So far the only thing I can find on the subject is on Hluc's excellent page on pdaXii13:
Quote
GPRS network connection via Bluetooth also works. Make sure /etc/bluetooth/pin contains your PIN and then use the PPP config tool to configure the preconfigure GPRS profile to look for your phone. Then use the PPP dialer to connect to the phone to enable the GPRS connection.

I've done that, entering my Cingular information into the PPP config tool, and when I try to connect wiht the PPP dialer, it gives
"Failed to open /dev/rfcomm0: No such device"

/dev/rfcomm0 is specified as the device on the Modem tab of the PPP config tool, and was already filled in. It's just a plain text field, no other choices offered.

Based on some other threads (not for pdaXrom) it looks like hciconfig is to Bluetooth as ifconfig is to Wi-Fi, but when I run it it returns nothing.

The Bluetooth card is an AmbiCom BT2000-CF and cardctl ident says

product info: "Compact Flash", "Bluetooth Card", "", ""
manfid: 0x0319, 0x0000
function: 2 (serial)

I'm not sure where to go from here, I'd appreciate any help or advice.

TIA

Walt
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167272\"][{POST_SNAPBACK}][/a][/div]

I have this working on Beta3, so I'm not sure how helpful my comments will be.

Firstly make sure you have searched for the phone using BT DUN on the PPP Modem dialog.

Then I found that at least one reboot of both the phone and the Zaurus was required.

HTH
Andrew

walts · « **Reply #2 on:** September 11, 2007, 02:18:00 pm »

Quote

I have this working on Beta3, so I'm not sure how helpful my comments will be.

Firstly make sure you have searched for the phone using BT DUN on the PPP Modem dialog.

Then I found that at least one reboot of both the phone and the Zaurus was required.

HTH
Andrew
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167274\"][{POST_SNAPBACK}][/a][/div]

Thanks, Andrew

Since pdaXii13 is derived from beta3, I think it would work.

That said, I think the issue is deeper than that. The search turns up "Can't get DUN info". The Zaurus is not discoverable either by the phone or my laptop, so I think I need a way to turn on the Bluetooth card. (The LED is blinking, which is how my Wi-Fi card behaves when it is first inserted, before it connects to the network).

I found a posting in another forum that looked like it would be helpful, but Google's Japanese translator leaves a bit to be desired -- "It is to think as the kana where is my report, my pdaXrom, (1.1rc8 deteriorates and) with can use that with the standard ...."

Amusing but not very useful

Walt

tesla_cubed · « **Reply #3 on:** September 11, 2007, 04:03:01 pm »

Using PadXii13 and Sprint fusic works great hope this is close enuff to help. It seems like your phone and Z aren't pared up so the phone is ignoring the Z. Here are the steps I took

1st on phone set bluetooth to on
2nd set phone to be visiable on a bluetooth scan
3rd on Z in PPP settings Click the serch button
4th the phone shows a paring request tell it OK and give it the pin "1234" unless you edited the pin to something else [the file is /etc/bluetooth/pin I think]
5th on phone set the Z as a "trusted device" then you don't have to par every time
They will the rember each other now
6ht setup PPP for yor provider
7th enjoy

Its a different provider so but i thing bluetooth paring is the same all around ymmv

PS: oops I didnt see that the Z wasn't showing up my BT card is a diffrent brand (blekin) so I don't know if thats normal or not mine blinks when paring the light is on when in standby and off when working the exact inverse of my WiFi Card

walts · « **Reply #4 on:** September 12, 2007, 06:59:56 am »

Quote

Using PadXii13 and Sprint fusic works great hope this is close enuff to help. It seems like your phone and Z aren't pared up so the phone is ignoring the Z. Here are the steps I took

1st on phone set bluetooth to on
2nd set phone to be visiable on a bluetooth scan
3rd on Z in PPP settings Click the serch button
4th the phone shows a paring request tell it OK and give it the pin "1234" unless you edited the pin to something else [the file is /etc/bluetooth/pin I think]
5th on phone set the Z as a "trusted device" then you don't have to par every time
They will the rember each other now
6ht setup PPP for yor provider
7th enjoy

Its a different provider so but i thing bluetooth paring is the same all around ymmv

PS: oops I didnt see that the Z wasn't showing up my BT card is a diffrent brand (blekin) so I don't know if thats normal or not mine blinks when paring the light is on when in standby and off when working the exact inverse of my WiFi Card
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167283\"][{POST_SNAPBACK}][/a][/div]

Thanks, I'll try that again in the morning.

The problem I had is that at step 3, I get the message , "Can't get DUN info".

It seems like the card is not getting turned on. The hciconfig command just comes back with a shell prompt, as if there was no card in the slot, but cardctl ident gives correct results.

I'm pretty sure the hardware is OK, it worked with Cacko.

thanks for the help

Walt

jpmatrix · « **Reply #5 on:** September 12, 2007, 09:34:21 am »

Quote

Quote
Using PadXii13 and Sprint fusic works great hope this is close enuff to help. It seems like your phone and Z aren't pared up so the phone is ignoring the Z. Here are the steps I took

1st on phone set bluetooth to on
2nd set phone to be visiable on a bluetooth scan
3rd on Z in PPP settings Click the serch button
4th the phone shows a paring request tell it OK and give it the pin "1234" unless you edited the pin to something else [the file is /etc/bluetooth/pin I think]
5th on phone set the Z as a "trusted device" then you don't have to par every time
They will the rember each other now
6ht setup PPP for yor provider
7th enjoy

Its a different provider so but i thing bluetooth paring is the same all around ymmv

PS: oops I didnt see that the Z wasn't showing up my BT card is a diffrent brand (blekin) so I don't know if thats normal or not mine blinks when paring the light is on when in standby and off when working the exact inverse of my WiFi Card
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167283\"][{POST_SNAPBACK}][/a][/div]

Thanks, I'll try that again in the morning.

The problem I had is that at step 3, I get the message , "Can't get DUN info".

It seems like the card is not getting turned on. The hciconfig command just comes back with a shell prompt, as if there was no card in the slot, but cardctl ident gives correct results.

I'm pretty sure the hardware is OK, it worked with Cacko.

thanks for the help

Walt
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167317\"][{POST_SNAPBACK}][/a][/div]

type: sdptool browse
to have all bluetooth services available. you'll have dialup networking channel.

are you sure of your rfcomm.conf setup ?

did you type ?
rfcomm bind rfcomm0

what does rfcomm gives you ?

louigi600 · « **Reply #6 on:** September 12, 2007, 09:45:19 am »

I posted on some bluetooth thread here ... and I have some guides on ppp over bluetooth on my home page. Hope these can be helpfull.

walts · « **Reply #7 on:** September 12, 2007, 11:01:16 am »

Quote

type: sdptool browse
to have all bluetooth services available. you'll have dialup networking channel.

are you sure of your rfcomm.conf setup ?

did you type ?
rfcomm bind rfcomm0

what does rfcomm gives you ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167322\"][{POST_SNAPBACK}][/a][/div]

Thanks!

From another thread I learned to do:
#setserial /dev/ttyS3 baud-base 921600
#hciattach -s 921600 /dev/ttyS3 bcsp

That seems to have activated the card.

Now, to your comments:

I have NO idea how to set up rfcomm.conf.
right now it has

Code: [Select]

rfcomm0 {
   bind yes;
   device {null};
   channel {null};
   comment "Generated by BT dial-up network applet"
}

Based on that last line, I have refrained from fiddling with it, although, honestly, I'm more at home with the command line than with some of the GUI front-ends.

#sdptool browse
appears to find my phone - it gives a lot of information, but the Service Name is Bluetooth-PDA-Sync. (That's not what I want to do, I want to use the PDA/Phone as a modem.)

Code: [Select]

#rfcomm bind rfcomm0
parse error line 3
Can't find a config entry for rfcomm0

and
#rfcomm
just returns immediately to the command prompt.

Walt

jpmatrix · « **Reply #8 on:** September 12, 2007, 11:38:32 am »

well,

i don't know if latest distros don't use it (or fill it themselves) but i alway do that :

1) rfcomm.conf should contain :
bind yes;
device xx:xx:xx:xx:xx:xx;
channel 1;
comment "gsm";

instead of xx:xx.. put the mac address of your gsm
you can have it with:
hcitool scan

2a) rfcomm bind rfcomm0 should now work

2b) rfcomm shoud say something like:
rfcomm0: xx:xx:xx:xx:xx:xx channel 1 clean

3) sdptool browse|more should give you a service called Dial-Up Networking (it is called like that with my Nokia...). i don't think it is the same than pda-sync. on previous bluez i had to manually fill rfcomm.conf with the same channel but i think it is not necessary now.

anyway now,
pppd call provider should now work

walts · « **Reply #9 on:** September 12, 2007, 04:30:33 pm »

That's a big help, especially the information about rfcomm.conf. Apparantly that file is written by the PPP Modem applet in system tools. Once I edited it by hand it was fine.

After following your instructions I was able to "wake up" my PDA, but not connect to the network. The problems from here out appeat to be on the PDA, not the Zaurus.

Thanks for the help

Walt

louigi600 · « **Reply #10 on:** September 16, 2007, 04:40:37 pm »

If you still have'nt got it working you could have a peep on my home page ... I've tcp and ppp over bluetooth guides (that should be applicable to any flavour distro) on the Zaurus Documentation section.

ratki · « **Reply #11 on:** October 20, 2007, 05:06:41 pm »

Hi,

I had a similar 3 week long "project". I couldn't connect my new Nokia 6120 Classic to my Z.

The problem was, that all earlier used phones had the DUN (dial-up network) channel on the 1st rfcomm channel.

Quote from: jpmatrix

well,

i don't know if latest distros don't use it (or fill it themselves) but i alway do that :

1) rfcomm.conf should contain :
bind yes;
device xx:xx:xx:xx:xx:xx;
channel 1;
comment "gsm";
...

Please check it with
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']sdptool search DUN[/div]

It was in my case channel 4.

BTW: May be the graphical PPP setup program makes so, but I tried to set up manually, because this program deletes the other rfcomm entries. Like my GPS.

Best wishes,

Tamas

mrmg · « **Reply #12 on:** November 19, 2007, 11:47:27 am »

Hi guys, hope I'm not hijacking a thread as I seem to have a very similar issue to this.

I got my Z (3100) on Friday and have been having a good play with it over the weekend. I've settled on PdaXrom as this gives a nice desktop experience and quite a bit of speed from what I've seen so far.

I managed to get DUN working fine under Cacko with very little configuration. So far in pdaxrom I've tried pairing using the gui's (PPP Modem) but the search fails with my phone (nokia e65), however I am able to pair it by using sdptool and rfcomm mentioned above and editing the files by hand.

The issue I currently have is that when using PPP Dialer the Z connects to my phone but never seems to make an actually connection out. I'm using all the defaults but have set the user/pass in PPP Modem and have set the number in the same app. The output is:

Code: [Select]

abort on (NO CARRIER)
abort on (NO DIALTONE)
abort on (BUSY)
send (^M)
expect (OK)
/* PAUSES HERE FOR A WHILE */
alarm
Failed
Connect script failed

Does anyone have any idea about how I might fix this as I'm so close to getting the bluetooth connection to work, it just doesn't seem to want to dial after connecting!

Thanks,

--
mg

mrmg · « **Reply #13 on:** November 19, 2007, 12:36:05 pm »

Ok, solved my own problem! I'm sure I tried this a million times yesterday. I reinstalled everything today, edited rfcomm by hand, had the problem above. I went just needed to at "ATZ" as the dial prefix and now all is working. Looking forward to installing some apps now!

News:

Author Topic: Bluetooth Cellphone Modem (Read 7448 times)