Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm quite new to using bluetooth in Linux and need some help.
My problem is, I can send image files to my old phones (Sony, Nokia) using ussp-push from the CLI without being prompted for a pin, but not my Samsung SGH-D840. It wants to pair with a pin before the copy can take place. I'm not able to pair even after following all the advice of others with a similar problem. Because I'm scripting this, I want to be able to do this from the CLI rather than from an X desktop.
I've had a good look around the phone config and it seems its not possible to turn this pairing request off. It does have a 'secure mode' option, but it doesn't actually change anything if its off or not, even after a phone power cycle.
OK, so this is what I've doing...
# sdptool search --bdaddr 00:11:12:13:14:15 OPUSH
Searching for OPUSH on 00:11:12:13:14:15 ...
Service Name: OPP
Service RecHandle: 0x10007
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
Profile Descriptor List:
"OBEX Object Push" (0x1105)
So the Samsung's OBEX channel is 3.
I run the following ussp-push command to push the file, shortly after running it the Samsung asks for a pin to pair with the PC. I enter 0000 and nothing else happens apart from the phone returning 'Invalid pin. Unable to connect'.
pushing file ../data/test1.gif
__obex_connect: client_context_t = 0x99584a8
Set user data
Created new objext
Local device 00:16:15:14:13:12
Remote device 00:11:12:13:14:15 (3)
Write error: Connection refused
obex_event: client_context_t = 0x99584a8
Started a new request
Unable to connect to the server
As you can see from the /var/log/messages file below, I don't get past the 'pin_code_request'.
Jan 18 23:53:53 dora hcid: Bluetooth HCI daemon
Jan 18 23:53:53 dora hcid: Register path:/org/bluez fallback:1
Jan 18 23:53:53 dora hcid: HCI dev 0 registered
Jan 18 23:53:53 dora hcid: Register path:/org/bluez/hci0 fallback:0
Jan 18 23:53:53 dora hcid: HCI dev 0 already up
Jan 18 23:53:53 dora hcid: Device hci0 has been added
Jan 18 23:53:53 dora sdpd: Bluetooth SDP daemon
Jan 18 23:53:53 dora hcid: Starting security manager 0
Jan 18 23:53:53 dora hcid: Device hci0 has been activated
Jan 18 23:54:48 dora hcid: pin_code_request (sba=00:16:15:14:13:12, dba=00:11:12:13:14:15)