You are not logged in.
Pages: 1
Hi there
I tried the last few hours to make a pair out of my pc and my mobile via bluetooth. I installed bluez-libs and utils and did hcitool scan. my mobile was found, so i tried hcitool cc address, but nothing happened. I also tried to make a PIN entry field pop up, as shown in many how-tos across the net, but none helped. Can anyone help me setting up bluetooth? here is my hcid.conf
# HCI daemon configuration file.
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# PIN helper
pin_helper /etc/bluetooth/givepin;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
passkey "1337";
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "KiWi";
# Local device class
class 0x3e0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}
Offline
In hcid.conf set :
security auto;
and restart bluetooth (/etc/rc.d/bluetooth restart).
Then try to pair from mobile. When mobile ask for PIN type 1337 (or whatever you set as "passkey" in hcid.conf).
If you have problems with finding PC from mobile try:
# hciconfig hci0 piscan
Offline
Then try to pair from mobile. When mobile ask for PIN type 1337 (or whatever you set as "passkey" in hcid.conf).
That is outdated. The PIN is now obtained via dbus. You can either use "bluetooth-applet" from the bluez-gnome package or enter "passkey --default 1337" before trying to pair with the device.
Offline
You can either use "bluetooth-applet" from the bluez-gnome package or enter "passkey --default 1337" before trying to pair with the device.
Of course you're right, but
I also tried to make a PIN entry field pop up, as shown in many how-tos across the net, but none helped.
So I thought this old method could work.
Offline
mhh now i got it running, but i cant access my filesystem on the mobile. its an nokia 6233. i am trying with wammu/gammu
Offline
mhh now i got it running, but i cant access my filesystem on the mobile. its an nokia 6233. i am trying with wammu/gammu
Are you just wanting to copy stuff from, say, your gallery? Obexftp is better for that kind of thing. I've had it working with a 6234, which is basically the 6233.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
that is exactly what i want
i am now trying obexftp, is there probably a GUI for it?
Offline
configuring obexftp confused me. I gave up after about 10 minutes of messing with it, but at least i got my devices to show up (I needed an hciconfig hci0 down && hciconfig hci0 up) and all that jazz...
Bluetooth is a bit confusing still. The dependency on dbus even more so.
Offline
Offline
configuring obexftp confused me. I gave up after about 10 minutes of messing with it, but at least i got my devices to show up (I needed an hciconfig hci0 down && hciconfig hci0 up) and all that jazz...
Bluetooth is a bit confusing still. The dependency on dbus even more so.
obexftp is not that confusing so far. actually you got nearly nothing to configure. The only thing is to type obexftp -b -l and your directories are listed. then download them via obexftp -g
but a gui would be nice anyway. looking at the obex page right now...
Offline
For all you KDE users, kdebluetooth uses openobex as a backend, so you can use konqueror as a GUI.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
bluetooth:/ /
Mr Green
Offline
Pages: 1