Bluetooth fails to connect

I have 2 hands free devices which both worked perfectly with my old 6630. Problem is that neither will pair with my new 6280? In fact it looks like the only thing it will pair with is another 6280 or my old 6630. I know the hands free are both OK as my old 6630 connects fine.
Any ideas?
TIA

Also just tried a GPS receiver and that connects fine so what's wrong with the other 2 devices? They are both fairly new but the phone doesn't see them at all!

Similar Messages

Bluetooth fails to connect headset

[bluetooth]# info 00:16:74:76:1F:61
Device 00:16:74:76:1F:61
Name: ST BUDDY R19
Alias: ST BUDDY R19
Class: 0x200404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
[bluetooth]# connect 00:16:74:76:1F:61
Attempting to connect to 00:16:74:76:1F:61
Failed to connect: org.bluez.Error.Failed
[bluetooth]#

I would imagine this is because you are trying to connect to a device that Bluez doesn't have a supported profile for.
Bluez5 removed support for HSP/HFP headsets.

Bluetooth fails to connect to mouse after reboot/sleep

My bluetooth mouse (an Arc Touch) fails to get connected when my MacBook Pro starts up or comes out of sleep mode.
So I reset the mouse and "pair" it again, removing the previous entry for it, and the mouse works again.
If I then power off and restart, it fails and shows up as "not connected".
Have to "pair" it again, every time.
This was working fine until I upgraded to OS X 10.2.2.
I've reset the SCM and PRAM with zero success.
Any further things to try?

Ok Rb621,
Follow the same procedure as you have done before. Exception - At the restart, boot into Safe Mode. You don't have to log in. Wait a while, have something else to do. During this time, OS X will clear some caches. Come back and restart normally and see what happened.
Have fun
Leo

Bluetooth fails to connect after 10.6.7 install

I recently upgraded from 10.5.8 to 10.6.7. Prior to upgrade, I had a Bose Soundlink bluetooth device which I used extensively and loved. After the upgrade, I could not connect to the device. It showed in the list of known bluetooth devices, but upon connection try, it connected only for a sub-second, then would disconnect. Thinking the config might have been munged, I deleted the Bose Soundlink bluetooth device, then used Bluetooth setup assistant to find it again. It will NOT find it.
My daughter's MacBook Pro running 10.6.6 also will NOT find the Bose Soundlink device, but our 2 MacBooks WILL discover each other.
Nothing has been done to Soundlink -- it worked perfectly before OS X upgrade.
Is this a known problem? How can I fix?
Many thanks for reading.

Hi markl_me
Thank you for the hint, it also OS 10.6.7 - I tried one evening in vain and its so easy, press the bluetooth button on the soundlink until the Macbook Pro has registered it.
Happy New Year.
G
P.S.: also works great with the ipad 2 OX 4.3.3

Lumia 620 fails to connect to car bluetooth - coll...

My lumia 620 did initially connect to my ford focus car audi/phone successfully. However after about a week it failed to connect and I haven't been able to connect since. Defeats the object of hands-free!
Steps taken (which work with previous phones of various makes/models):
Turn bluetooth on in car
Turn on phone bluetooth connectivity
Car display finds my phone successfully and provides a PIN to enter in the phone
Phone bluetooth status says 'unable to connect to ford audio system' and times-out.
I've noticed that the 'tap to pair' message doesn't appear as it previously did and I can't find anywhere else to look for bluetooth settings.
A colleague who has an identical phone can successfully connect - it does show the 'tap to pair' message.
I have updated the ford audio system software and checked the other phone connects ok. I have also tried removing the phone battery several times but still no joy.
Help please - thanks

Hi Roshanrims,
Thank you for reaching out to us. Let's go with the connectivity issue first. Are you getting the same issue when you connect your phone to another PC? To further isolate the issue, you can try other troubleshooting steps found on the below link:
• The cable connection to my computer does not work
Note: The link is intended for the Philippines. Let us know your location so we can give you the correct link.
As for the Project My Screen, see this: Project my phone screen to a TV or PC.
We look forward to your reply.

OVI fails to connect to Nokia N8-00 on "Checking t...

Hi All,
I'm having problems connecting OVI to a Nokia N8-00 handset via Bluetooth.
The Add New Device wizard is able to detect the phone but when selecting it from the list and proceeding it stays on "Checking the Bluetooth capabilities of your device." for some 20 seconds after which it eventually fails with the error of "Failed to connect to your device. Problems occured while authorising the Bluetooth connection between your device and computer."
I've verified that both devices are configured as authorised by their respective counterpart.
Also tried to remove the pairing from both the laptop and phone and re-pair them again - same problem.
I am able to sync the phone with OVI via USB no problem.
I am also able to use my OVI with another Nokia phone (E72) via Bluetooth without any issues.
This points me to a possible problem with Bluetooth on the N8 phone itself but I don't have any way to prove it.
I wonder if anybody else has experienced the same issue?
OVI version 3.0.0.290
N8-00 version 013.016
Thanks, Jan

OVI is A BUG! I'm using PC suite with an old version 7.1.40.6 (still compatible with the N8) which wor'ks great with my N8 for more than a year. Time to time I update OVI to check if the known bugs are fixed but since new are coming it is a no end situation. I have had a N95 and a N97 before which never either worked properly with OVI and Outlook 97, 2003 & 2010.
How CAN THAT BE Mr NOKIA?
Because of this, I'm closed to give up with this good phone supplier offering a VERY WEAK software support to its clients!
Good luck to all of you still patient ...

OVI fails to connect to Nokia N8 on "Checking the ...

Hi All,
I'm having problems connecting OVI to a Nokia N8-00 handset via Bluetooth.
The Add New Device wizard is able to detect the phone but when selecting it from the list and proceeding it stays on "Checking the Bluetooth capabilities of your device." for some 20 seconds after which it eventually fails with the error of "Failed to connect to your device. Problems occured while authorising the Bluetooth connection between your device and computer."
I've verified that both devices are configured as authorised by their respective counterpart.
Also tried to remove the pairing from both the laptop and phone and re-pair them again - same problem.
I am able to sync the phone with OVI via USB no problem.
I am also able to use my OVI with another Nokia phone (E72) via Bluetooth without any issues.
This points me to a possible problem with Bluetooth on the N8 phone itself but I don't have any way to prove it.
I wonder if anybody else has experienced the same issue?
OVI version 3.0.0.290
N8-00 version 013.016
Thanks, Jan

All bluetooths stack versions, OVI versions, PC Suite versions are same as those of another laptop which connects well over bluetooth.
By the way still, my Win7 Home Premium's OVI's system info tells that it is using Microsoft Bluetooth Stack Version 6.1.7600 build 16385 (Active & In Use).
PLS DO HELP. OTHERWISE I'VE NO OPTION BUT TO LOOK FOR ANOTHER SYMBIAN 3 DEVICE. I DON'T WANT TO PART WITH MY N8 OR MY ACER ICONIA TABLET.
Note: This problem seems only with N8 because I've tried other nokia models. They all connect well. But I've also tried another N8, that also DIDN'T CONNECT. What the heck problem is with N8.
Wish#1: MP3 Tag Editor capable of editing ratings.
Wish#2: Android type Video player, highly efficient player capable of playing all formats.
Wish#3: Without Google Maps (and products), no gadget is worth keeping.
Attachments:
Ovi system info.png ‏19 KB

IMac fails to connect automatically to WiFi network

This is a re-submission of this request for help because I got no response the first time around.
The trouble began after upgrading to Snow Leopard. Prior to the upgrade I was running 10.5.8 and the airport wireless card would reconnect perfectly every time the computer woke up. After the change to 10.6, it's hit and miss. Sometimes after waking up, the computer will find my wireless router and connect with no problem. On other occasions it will not. Here's what I've observed:
When it fails to connect, if I immediately click on the wireless icon on the menu bar it will show no wireless networks at all, not mine, not any of my three neighbors, none. If I wait a few seconds (less than a minute) they will suddenly be detected. At that point clicking on my network will result in an immediate connection. I do not know why it takes so long for the Airport card to detect the networks, but that's not the issue. It eventually does. The problem is that the iMac has stopped trying to connect by then.
How can I get the computer to keep trying to log on (at least periodically) until it succeeds?
Any help will be greatly appreciated.
-John

Test after taking each of the following steps. Back up all data before making any changes.
1. Make sure the network is on the preferred list by following these instructions. It's important to read the article carefully, as it's the starting point for any further efforts to solve the problem. If you skip any of the steps, the problem may not be solved.
2. Follow the instructions in this support article under the heading "Symptom: The network connection drops unexpectedly."
3. Make a note of all your settings for Wi-Fi in the Network preference pane, then delete the connection from the connection list and recreate it with the same settings. You do this by clicking the plus-sign icon below the connection list, and selecting Wi-Fi as the interface in the sheet that opens. Select Join other network from the Network Name menu, then select your network. Enter the password when prompted and save it in the keychain.
4. From the Location menu at the top of the Network preference pane, select Edit Locations. A sheet will drop down. Click the plus-sign button to create a new location. Give it any name you want. In the new location, set up the Wi-Fi service with the same settings you used before. Click Apply and test.
5. Launch the Keychain Access application. Search for and delete all AirPort network password items that refer to the network. Make a note of the password first.
6. Repair permissions on the startup volume.
7. Turn off Bluetooth and test.
8. Reset the System Management Controller.
9. Reset the PRAM.
10. Reinstall OS X.

Wifi scans but fails to connect on Thinkpad W520

Running Network Manager on a Lenovo Thinkpad W520 and able to scan but unable to connect to wifi. Wifi works fine in dualboot on Windows, and ethernet works fine in both.
$ lspci -vv
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 35
Region 0: Memory at d5300000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
$ sudo systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2014-12-21 22:58:55 EST; 12min ago
Main PID: 500 (code=exited, status=1/FAILURE)
Dec 21 22:58:55 Defiant systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE
Dec 21 22:58:55 Defiant systemd[1]: Failed to start Network Manager Wait Online.
Dec 21 22:58:55 Defiant systemd[1]: Unit NetworkManager-wait-online.service entered failed state.
Dec 21 22:58:55 Defiant systemd[1]: NetworkManager-wait-online.service failed.
$ sudo systemctl status NetworkManager-dispatcher.service
● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled; vendor preset: disabled)
Active: inactive (dead)
$ sudo systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2014-12-21 22:58:23 EST; 13min ago
Main PID: 341 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─341 /usr/bin/NetworkManager --no-daemon
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Disabling autoconnect for connection 'Bifröst'.
Dec 21 23:10:12 Defiant NetworkManager[341]: <warn> Activation (wlp3s0) failed for connection 'Bifröst'
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): deactivating device (reason 'none') [0]
Dec 21 23:10:12 Defiant NetworkManager[341]: <warn> Connection disconnected (reason -3)
Dec 21 23:10:12 Defiant NetworkManager[341]: <info> (wlp3s0): supplicant interface state: completed -> disconnected
Dec 21 23:10:15 Defiant NetworkManager[341]: <warn> Could not get scan request result: Scan request rejected
Additionally, after stopping NetworkManager and trying wifi-menu, it scans correctly but fails to connect, never even prompting for a passphrase.
So I tried wpa_supplicant on its own:
$ sudo wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "Bifr\xc3\xb6st" "mypassword")
Successfully initialized wpa_supplicant
wlp3s0: failed to initialize driver interface
For good measure:
$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f0:de:f1:62:13:b8 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.11/24 brd 10.0.0.255 scope global enp0s25
valid_lft forever preferred_lft forever
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:24:d7:c6:ab:48 brd ff:ff:ff:ff:ff:ff
I'm at a loss. and I've googled my little heart out. Any help would be appreciated.

Welcome to the forums - and thanks for a great initial post, all the needed information seems to be here.
Specifically, the following error from wpa_supplicant will most likely be best to dig into:
wlp3s0: failed to initialize driver interface
I see several results of this error in a google search, but none of them quickly translated into solutions yet. To get some more information on it, could you run the same wpa_supplicant command, but with the verbose debugging flag "-dd" and post the ouput here?
I don't have a intel wireless card, so I don't know what the diagnostic signs are for the problem addressed in the wiki, but you may want to try the modprobe options shown in this section of the wiki.
EDIT: there is a similar but unresolved thread on these forums here which points to using the -D flag for wpa_supplicant to specify other drivers. I was thinking this too upon my first reading, but I don't fully understand what these are so I was reluctant to suggest it. It certainly can't hurt anything to use the command in the wiki to see which drivers are available, then try each one.
EDIT 2: and this thread seems to indicate that the -D flag driver specification is the right solution. So start here with the -D flag and only if that fails follow up with my initial debugging suggestions.
Last edited by Trilby (2014-12-22 12:52:13)

Bluetooth failed after last OS Update

After the last OS update 10.7.3 on my Powerbook Pro, bluetooth failed on both Trackpad and Apple Mouse. It connects and then disconnects. Anysolutions out there?

catnfran,
I'm sorry to hear that you have been experiencing this issue with your Bluetooth feature! Updates are meant to offer enhancements.
Based on our findings, with the new update, making this change manually would be the recommend option. If needed, we can attempt to master reset the device http://vz.to/1d1KPN1 to see if this helps resolve this particular concern.
EfrainM_VZW
Follow us on Twitter @VZWSupport

Unreliable / slow bluetooth under E66 - connect wi...

I recently changed from an N70 to an E66. I've been trying to connect to my E66 with bluetooth to use it as a GPRS modem which was no problem with the N70. I've finally managed, but I found it a real problem and had to use several tricks. It seems the bluetooth in the phone just doesn't work reliably and stably.
Problem 1) the channel keeps changing.
The phone DUN doesn't stay stable. If I do
sdptool search --bdaddr xx:xx:xx:xx:xx:xx dun
(xx is the bluetooth address you can find with "hcitool scan" )
I sometimes find it's on channel 2 and sometimes 4.
Problem 2) the phone only works on some connections
The phone regularly refuses connections. It looks as if it needs some time to recover after one thing is done.
Using sdptool (as above) I get messages like:
Failed to connect to SDP server on xx:xx:xx:xx:xx:xx: Software caused connection abort
Failed to connect to SDP server on xx:xx:xx:xx:xx:xx: Connection reset by peer
Trying to connect with dial up networking I get messages like
Cannot open /dev/rfcomm0: No such file or directory
Often it seems that waiting a few seconds or trying again gives the phone time to recover and it works.
I've managed to get it to work more or less reliably with the script below; however, does anyone have a suggestion what is wrong with my phone and what I can do to fix it?
#!/bin/bash -x
#put your bluetooth address here.
BT=xx:xx:xx:xx:xx:xx
if test "$(id -u)" -ne 0 ; then
exec sudo $0
fi
RESULT=255
while [ 255 = "$RESULT" ]
do
OUT=`sdptool search --bdaddr $BT DUN`
RESULT=$?
if ( echo "$OUT" | grep "Host is down" )
then
echo bluetooth device down: $OUT
exit 255
fi
done
CHAN=$(echo "$OUT" | awk '/Channel/ { print $2}')
rfcomm release 0
rfcomm bind 0 "$BT" "$CHAN"
rfcomm
#sleep seems to allow phone to recover??
sleep 2
wvdial gprs

I'm afraid it is not the Linux problem only, bluetooth modem is also unreliable under windows XP. I never had internet connection over bluetooth modem running more than 15 minutes, and reconnecting was equally problematic as it obviously requires some time to "recuperate". Sometimes restarting the phone is the only solution if I want to reconnect again. Cable connection via USB seem to work much better, however, it is not convenient as the bluetooth connection I got used to on my previous phone 6233

Bluetooth problem - Cannot Connect to Device that is not copyright protected SCMS-T Method

I have a Qosmio X875-5280 which has a bluetooth adapter. I also have a bluetooth device which is an adapter for a Bose Sounddock such that the device allows the Sounddock to receive the bluetooth audio stream from the laptop -- at least that is how it worked until recently. Diagnostics show that both the bluetooth adapter and the bluetooth device are working. When trying to connect to the device, I now get "connection failed" message or the message "You cannot connect to a device that is not copyright protected by SCMS-T method." It seems the Toshiba bluetooth stack is responsible for this, however, I fail to see why a device which is acting like headphones fails to connect now. I have Windows 7 64 installed. I have uninstalled all of the bluetooth drivers and re-installed them several times. Attached is a pdf file which shows all messages and settings relevant to the issue.
Attachments:
bluetooth messages.pdf ‏158 KB

See the solution I proposed some time ago here.
-Jerry

Logitech V470 Cordless fails to connect in Boot Camp

After installing MS XP SP3, my Logitech V470 Cordless fails to connect in Boot Camp. The Logitech Bluetooth Connection Assistant does not recognize the mouse. In MS Control Panel, Bluetooth the mouse is recognized, without a password, but does not work. I have had not luck with Logitech or Microsoft. Any suggestions.

After Vista installed, did you insert the Mac drivers CD (if you're running the beta Boot Camp) or the Installation DVD (if you're running Leopard)? Without the Apple-supplied drivers you probably won't have a lot of things working right.
Doug

Nokia N78 fails to connect to PC via CA-101 USB ca...

Hi everybody.....
Please let me tell the story from the begining..Recently I purchased a China made N78 phone
with firmware ver. 12.046 / custom ver. 12.046.051.1 .When I tried to connect it to
PC via CA-101 USB cable & Nokia PC Suite ver. 6.9 (both are contained in the retail box)
it failed to connect.Although the phone does recognise the connection as a connection
icon appears on the left upper corner of the phone screen and the phone asks me to set
the connection profile e.g. PC Suite to use , while the PC tells me that a problem occured
during installation of a new hardware (the phone) and it cannot be used properly hence no
connection occures. First I factory resetted the phone , then did hardware format by
keys: (* + 3 + m.media key + power on ),then updated the Nokia PC Suite programme to
ver. 7.1 and I updated cable drivers from Nokia website and reinstalled them ,then I
updated the phone fimware using phone device manager to ver. 21.002 / custom ver. 21.002.051.1
and lastly reinstalled the Win.XP on my PC BUT THE PROBLEM IS SAME AND NO CONNCTION in every single step done respectively.On the other side the Bluetooth connection with the PC and Nokia PC Suite
works very fine. I think I checked and fixed every possible issue I could ,and the phone package is brand new and made under the authority of Nokia corp. hence its genuine one and purchased from a registered Nokia distributor in Middle East.So why this problem happens ?! I DONT KNOW , SO PLEASE HELP..HELP...

Did You install PC suite to your computer before connecting? Which mode are you using to connec PC Suite or data transfer? Data transfer shouldn't require drivers but you can get the cable driver just in case. It should be on the disk that came in the box with your phone. If you have installed PC suite make sure it's running when you plug the phone in
Show your appreciation. Hit that kudos button real hard

Nokia 6102i fails to connect to iSync unless I restart the phone

My Nokia 6102i frequently fails to connect through bluetooth to iSync. iSync prompts me to restart my phone, and doing so always does the trick. However, I don't want to restart my phone whenever I want to sync it up. Do any of you know what the problem is?
Incidentally, this problem has cropped up only recently; my phone use to sync without any problems. If I had to target an instigating incident, it would be uninstalling Markspace for Palm, but that might have been coincidental.
I have the following software running with iSync:
-Novamedia for Nokia 6102i
-Palm
Todd

Try deleting and reinstalling the phone plug-in on your Mac. Then, restart both Mac and Phone.

Bluetooth fails to connect

Similar Messages

Maybe you are looking for