Latest Bluetooth with Gui Wizard and Applet

[Aung]

Another clean install, USB adapter and phone not seeing each other. Question, which dbus is to be loaded first, dbus or dbus-glib, and for bluez, bluez or bluez-gnome. Aung

./bluetooth
killall: bluetooth-applet: no process killed
./bluetooth: line 7: killlall: command not found
bluetoothd[11788]: Bluetooth daemon 4.55
bluetoothd[11788]: Starting SDP server
bluetoothd[11788]: opening L2CAP socket: Protocol not supported
bluetoothd[11788]: Server initialization failed
bluetoothd[11788]: Parsing /usr/etc/bluetooth/network.conf failed: No such file or directory
bluetoothd[11788]: Failed to open control socket: Protocol not supported (93)
bluetoothd[11788]: Can't init bnep module
bluetoothd[11788]: Failed to init network plugin
bluetoothd[11788]: Parsing /usr/etc/bluetooth/input.conf failed: No such file or directory
bluetoothd[11788]: Parsing /usr/etc/bluetooth/audio.conf failed: No such file or directory
bluetoothd[11788]: Unable to start SCO server socket
bluetoothd[11788]: Failed to init audio plugin
bluetoothd[11788]: HCI dev 0 registered
bluetoothd[11788]: HCI dev 0 up
bluetoothd[11788]: Starting security manager 0
# obexd[11798]: Bluetooth server register failed: socket(STREAM, RFCOMM): Protocol not supported (93)
obexd[11798]: Bluetooth server register failed: socket(STREAM, RFCOMM): Protocol not supported (93)
bluetoothd[11788]: Can't read address for hci0: Connection timed out (110)
bluetoothd[11788]: Failed to open RFKILL control device

(bluetooth-applet:11797): Gtk-WARNING **: Can't set a parent on widget which has a parent

bluetooth-agent.c:bluetooth_agent_class_init() class 0xb7fe7dd0
bluetooth-agent.c:bluetooth_agent_init() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_new() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_set_pincode_func() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_set_passkey_func() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_set_display_func() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_set_confirm_func() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_set_authorize_func() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_set_cancel_func() agent 0xb7f98960
bluetooth-agent.c:bluetooth_agent_register() agent 0xb7f98960
bluetoothd[11796]: Can't set link policy on hci0: Connection timed out (110)
bluetoothd[11788]: accept: Socket operation on non-socket (88)
#

[noabody]

I haven't used Bluetooth Dial-up Networking on Puppy Linux before. First I installed these packages.

I did the "hcitool scan" with my phone in discovery mode. Then "sdptool search dun" and made appropriate changes to /usr/etc/bluetooth/rfcomm.conf. Then "rfcomm connect 0". If I run the Internet Connection Wizard and select "Internet by dialup analog or wireless modem" /etc/wvdial.conf is created. I edited this file and changed Modem = /dev/rfcomm0.

Now I can use the "Internet by dialup analog or wireless modem" script to enter username/password and make a connection.

Every time I want to use BT DUN I have to open a console and run "rfcomm connect 0" and then use the connect button on the "Internet by dialup analog or wireless modem" script.

Like I said, this is the first time I've done this in Puppy Linux. Maybe there is a better way?

[jemimah]

Pri, I know that sending doesn't work. I'm not sure what the problem is. I may end up writing a new bluetooth send application, but this is still very low priority for me since I don't have any use for it. If anyone else wants to contribute a fix, feel free.

Aung, Dbus loads, then bluetoothd, then the applet. From your output, it looks to me as if it's working ok.

Noabody, You could write a script to accomplish both steps in 1 click.

Code: Select all

rfcomm connect 0
pupdial

Save it to a file and make it executable. I recommend grabbing gnome-ppp from the repository as it is much nicer than pupdial.

[pri]

owh... ... its bluetooth will end up here ?

well i am not progamer and learn linux in few month.... but it was still helpfull.

for reader.. iam removed all my lib... because latest bluetooth was succesfuly sending to puppy pc without it

sory for so long responding, i was busy make puppy for my internet cafe.

[jemimah]

I think I figured out the issue with sending. I need a few days to work on it, then I'll post a new version if I can get it working.

[pri]

hi jemimah......

today some one coming to me and want to print her photo on nokia phone, but it cant be receive with puppypc.

i think gnome-obex-server is needed for tranfer from phone devices.

so, now i am not using my libs for clean testing your bluetoth pet. waiting for improvemnet.

[jemimah]

Gnome-obex-server is no longer a part of gnome-bluetooth. I tried to see if the old version would build against the new bluetooth, but it has too many dependencies.

No progress on the Sendto issue either. I updated bluetooth to the latest version, and even built with all dependencies, sendto still does not work.

Pri, have you tried Dpup? It should make it easier to use debian packages.

[exProphecy]

I tried adding my Bluetooth Mouse and it said successful but it isn't working. I tried to set up the Bluetooth Mouse and it says Pairing unsuccessful.

[Max Headroom]

Help there Appears 2 be a Problem w/ bluez-gnome-1.8-i486.pet Package Crashing & Corrupting X in Both XOrg & XVesa maybe sumthing 2 do w/ ./xinitrc File, but I'm Not Really sure what 2 do 'bout it... All Other Pets install OK. BTW this happens w/ a Toshiba TE2100 Laptop Running grays NOP 4.3.1 ( Full install ) & a Generic USB BlueTooth Dongle, that is seen by the OS as proved lsmod & dmesg cmds.

[jemimah]

It doesn't modify the .xinitrc. I've only tested on 4.3.1 though. I'm not familiar enough with NOP to know what the issue might be.

You can delete /root/Startup/bluetooth to stop bluetooth from starting.

[Pro]

Hi,
Please recompile bluez-gnome with bluez-gnome-1.8-ODS-API.patch

the obex-data-server -0.4.5 is works only if this patch is established.
Sending of files should work.

sorry my english is bad

[trapster]

I also cannot get the bluetooth gui working for sending files so I found a way to "push" files to my phone from the laptop.
This is on a eeepc 1005HA using puppeee3.5.
Requires obex_test from the debian package openobex-apps_1.3. Download and extract. Get obex_test from /usr/bin of the extracted files and copy or link to /usr/bin or /usr/local/bin.

In a console, run:
hcitool scan
This finds and address of the phone and the channel required for Obex Push, ie:
Hardware address:

Code: Select all

05:50:37: ~ > hcitool scan
Scanning ...
        00:24:91:8A:B6:7F       Al's Phone
05:50:58: ~ > sdptool browse  00:24:91:8A:B6:7F
Browsing 00:24:91:8A:B6:7F ...
Service RecHandle: 0x10000
Service Class ID List:
  "PnP Information" (0x1200)

And the part for the Obex Push channel:

Code: Select all

Service Name: Object Exchange
Service RecHandle: 0x10005
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 5
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

In a console, connect to the phone:

Code: Select all

#rfcomm connect 0
Connected /dev/rfcomm0 to 00:24:91:8A:B6:7F on channel 1
Press CTRL-C for hangup

Then in a different console use obex_test with the phone hardware address and Obex Push Channel:

Code: Select all

#obex_test -b  00:24:91:8A:B6:7F 5
Using Bluetooth RFCOMM transport
OBEX Interactive test client/server.
>

Type "c" at the > prompt to connect:

Code: Select all

> c
Made some progress...
Server request finished!
server_done() Command (00) has now finished
Timeout waiting for data. Aborting
>

Type "p" at the > prompt to Push a file to the phone

Code: Select all

> p
PUT file (local, remote)>

Now enter /path/to/file/on/laptop <space> filename. ie:

Code: Select all

> p
PUT file (local, remote)> /usr/share/backgrounds/Penguin-Windows.jpg Penguin-Windows.jpg
name=/usr/share/backgrounds/Penguin-Windows.jpg, size=53741
Going to send 53741 bytes
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Made some progress...
Server request finished!
server_done() Command (02) has now finished
Timeout waiting for data. Aborting
>

File should now be on your phone!

[jemimah]

I'll try the patch Pro posted and see if that sorts it.

[jemimah]

Hmm, even the patched bluetooth-sendto still gives the same error about "signature ss".

Maybe if I can figure out how to talk to obex-data-server or obexd, I could make my own gui.

[Max Headroom]

OK Thanx jemimah 4 the Prompt Reply, indeed Removing BlueTooth from /Root/Startup Does Stop X Crashing @ Bootup, But then I Can Confirm Manually eXecuting that BlueTooth File Does Still Crash X. is there any info I can provide to trouble-shoot this bug? Also what is the ODS-API.patch? Will it Help Me? And How Do I Apply it?

[Pro]

Hmm, even the patched bluetooth-sendto still gives the same error about "signature ss".

Maybe if I can figure out how to talk to obex-data-server or obexd, I could make my own gui.

obex-data-server version 4.x or 3.x ?

In obex-data-server version 4.x new API

------- Comment #40 From Paul Philippov 2008-11-14 13:38:03 0000 [reply] -------
Created an attachment (id=171712) [details]
bluez-gnome/files/bluez-gnome-1.8-ODS-API.patch

Patch for bluez-gnome-1.8 to make it work with object-data-server 0.4 API
See http://wiki.muiline.com/obex-data-serve ... ing_to_0.4

Incorporates patches from Mario_Limonciello
(http://marc.info/?l=linux-bluetooth&m=122256527621027)

Now I can send files from Bluetooth applet without errors =)

From here http://bugs.gentoo.org/236357

[jemimah]

OK Thanx jemimah 4 the Prompt Reply, indeed Removing BlueTooth from /Root/Startup Does Stop X Crashing @ Bootup, But then I Can Confirm Manually eXecuting that BlueTooth File Does Still Crash X. is there any info I can provide to trouble-shoot this bug? Also what is the ODS-API.patch? Will it Help Me? And How Do I Apply it?

My guess is that NOP already has dbus installed, so installing a new dbus might cause issues. You can try running the bluetooth script from the command line to look for error messages, but if it crashes X, you probably won't have much time to see what the error message was. I don't think the patch would be much interest to you until you can get bluetooth to run.

--
Pro,

I tested with obex-data-server 0.4.5. I had tried older version in the past, but they all gave an error message of some sort.

[jemimah]

For obex, what you can try is

Code: Select all

mkdir /tmp/mnt
obexautofs /tmp/mnt

Do this after you pair your phone. Then go to /tmp/mnt in Rox and you should see your bluetooth devices. It doesn't work well at all (extremely slow!) when I test it with my Windows machine, but that might be specific to my device.

[Pro]

I tested with obex-data-server 0.4.5. I had tried older version in the past, but they all gave an error message of some sort.

OK, Please give to me recompiled bluez-gnome with patch (and ru.po please)
I test it on my system.

The obexd-0.21 in my system not work (obexd: obex_handle_input poll event HUP ERR)

[jemimah]

Here try this instead. This is from gnome-bluetooth (the rest of gnome-bluetooth won't build with Puppy's GTK version, but sendto does).

This one doesn't need obex-data-server (which is apparently deprecated anyway). On my system it starts obex-client, but no data is transfered. It just hangs. But it may work with another setup, I do not know.