Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

tried rfcomm 2?

hrmf, as i look into it more, rfcomm can vary from phone to phone, as they are logical "ports" more then real channels...

that is, phone A may have dial-up connected to rfcomm 1, while another may have it on 8...

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

I've tred rfcomm all the way through 17, when I get up to 13/14 it just starts timing out. None of the rfcomm ports worked at all, except 3 and 4 showed the audio disconnected on my phone "Unknown error better than nothing" and 8 "works". 8 looks like it's using DUN (I do have my phone set to tether with my n810 for internet but it was NOT connected for that when I was trying PhoneLink)., as it brings up a data call.

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

that just about confirmes my fear, as checking a list i ones made on a older phone of mine shows rfcomm 8 as being for obex irmc sync...

ugh, if only the maemo bluez-utils included sdptool...

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

you can install bluez-utils-test with apt-get from extras-devel and then :

"hcitool scan" gives you phone BT Mac Address

"sdptool browse <phone BT Mac Address> | more" and search for service name "Serial Port" to read the RFCOMM channel

then try this channel with gnokii-gconf

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

ah, so bluez-utils-test holdes the secret sauce...

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

"Failed to connect to SDP server on <MAC I entered here>: Host is down"

Yes my bluetooth is turned on, yes the MAC I entered matches my phone's MAC.

Also, I tried this with my phone in discovery mode as well, even though I have successfully paired the two in the past, and often tether for internet access.

hcitool found my phone, but only when the phone was in discovery mode.

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

Any ideas?

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

your phone has to be bluetooth visible for the scan
but I suppose not for the browse ...
I suppose it's the "sdptool browse" that gives you this error ?
you should try and do it from a linux PC ...
You may get help from more knowledgeable people on the full linux forums ...

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

Wow, I would really like to say thank you. I did a bit more research and I used "sdptool browse" instead of with my bt mac and " | more" And it seems that I don't have a service name "serial port". I might show you what the terminal output to me and maybe I'm missing something.

I do have a "Service Class ID List" that says "Serial Port" however it says for "Phonebook Sync" and whenever I use PhoneLink to make a call it still shows up as a data call. It turned out that channel 8 was for DUN.

Here is what sdptool shows me:

Service Name: BPP sender
Service RecHandle: 0x10000
Service Class ID List:
"Direct Printing Ref. Object" (0x1120)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 16
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Basic Printing" (0x1122)
Version: 0x0100

Service Name: Voice Gateway
Service RecHandle: 0x10001
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100

Service Name: Voice Gateway
Service RecHandle: 0x10002
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105

Service Name: A2DP Source
Service RecHandle: 0x10003
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x100
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0100

Service Name: AVRCP Target
Service RecHandle: 0x10004
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100

Service Name: OPP server
Service RecHandle: 0x10005
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 17
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100

Service Name: PBAP server
Service RecHandle: 0x10006
Service Class ID List:
"Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 18
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Phonebook Access - PSE" (0x112f)
Version: 0x0100

Service Name: Dial-up Networking
Service RecHandle: 0x10007
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 8
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100

Service Name: Phonebook Sync
Service RecHandle: 0x10008
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 19
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Serial Port" (0x1101)

In my "Supported Profiles" part of my phone I see "Serial Port" as a listed profile. Any other way I could see what rfcomm channel this uses?

Edit: I cross referenced all those profiles with Google. It seems that channel 19 would be the port I should use (If for serial port) but it seems to be used as phonebook sync. Can this actually be controlled by the phone of is that just the service name? I know that the PBAP is for phonebook access as well, so I'm a bit confused. When I use channel 19, it still shows up as a data call when I make a phone call and it still doesn't send my text :/

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

I must say I always stayed far from Samsung phone : they are great phones for the UI and user interaction but I have heard a lot of problem when using them as modem or to dial up / send sms ...

Sorry

Keep us posted if you find a way to unlock a serial profile ...

Re: [ANNOUNCE] phonelink 1.4 : Dial Pad
 

*sigh* Such a shame. I really thought I was going to like the phone, then they stopped production not even a month after I purchased my phone, that was quite a let down. Since I'm using an N810 now, I will probably end up getting a nokia phone later on down the road sometime. Any suggestions as I am using Verizon? I wish VZW had sim cards so I could use one phone just for bluetoothing capabilities, then the other for the actual phone portion.

I could always just keep my phone tethered and send text messages via email or something else. This is a GOOD reason I wish I had a GrandCentral / Google Voice account!

I will look into making that serial port service work though, would be nice!