• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Bluetooth can't connect after pairing

richjhart

Lurker
I have an issue with my Galaxy SIII connecting to several Bluetooth devices.

My car stereo is an audio and phone device. I can pair the devices fine, and it remains connected and works perfectly. But once disconnected it cannot automatically connect next time as it usually does (when the stereo is turned on). I can connect by disabling auto connect in the stereo, and manually connecting from the phone.

Note that there is some sort of connection - I have Tasker which responds based on connection to it, and it does respond. However neither the audio nor phone connection is completed, and if I try to connect manually from the phone at that point it just hangs until I switch Bluetooth off on the phone.

The other device is a headset (so just phone device). Again it pairs correctly, but then once I switch it off and turn it on again it does the same thing as the stereo. The difference here is that I cannot stop the headset trying to connect, meaning I can only reconnect by unpairing.

Has anyone experienced this?
 
Yes I too have the same issue. Coming from S2 with ICS which paired the device automatically once i enable the BT, this is a bit frustrating. I have to manually enable the BT, and then select the car stereo (under paired devices), which then connects to car audio and only then the handshake happens. ( please ensure that the car audio box is checked.
 
Same issue as both of you but only for my BT headset. It works fine for my car.
While I was pairing my headset the process stopped and I had to start again... I suspect I misconfigured something between both attempts whereas the pairing went fine for my first try with my car ...
 
For my bluetooth in the car to work,I have to have the phone active as I approach and enter the car. If it is in sleep mode, the connection doesn't happen. Looks like the phone is not discoverable while it is in the sleep mode, even though it is on. My current solution is to just click the phone on prior to getting into the car.
 
I also have a problem 7/6 I got my Galaxy SIII and everything was fine it Paired with my Motorola Sliver and worked fine for two days and then yesterday it paired/connected and seemed to work BUT would send BUT would show it didn't send, but it did. But now when you type in your text and send sometimes it sends and sometimes it doesn't. The problem started at work, so when I got home I tried to find a solution this problem with the use of texting my wifes Galaxy SII Skyrocket, and that is how I found all that was happening, Any suggestions, I will be getting a hold of BestBuy, At&t and Samsung --- I'm disappointed, didn't have this problem with my Captivate. Don't like the little Land Mines they call Smilies --- the original was much better.
 
Just purchased one of these and every time the phone goes into sleep mode it disconnects from the car bluetooth-called Samsung and they have just told me that all of these phones with ICS do the same thing as they shut down the processor in sleep mode thereby disconnecting the bluetooth on the phone. It is a big PAIN getting it connected again with having to turn on the phone, connecting to the car and Samsung recommends setting Sleep Mode to 10min rather than 1 minuteif you have ever heard anything so ridiculous. Anyway, the tech says there is NO FIX for this problem and you cannot go back and reinstall Gingerbread once ICS has been installed on the phone. They have no fix in sight at this time as I was informed. Looks like everybody is having this and/or similar problems so let's hope Samsung get's on this real quick as I have full intentions of contacting them again the first of the week and going higher up the ladder as this could be a potential serious driving hazard.
 
I had the problem where it would register my commands until it dialed and went back to radio. Well the service guy at my car dealer figured it out. Go to setting, your device, calls, making calls, and make sure it is set to make calls in lock mode. Wala it worked. Hope this helps.
 
Back
Top Bottom