Johnny Cakes

I have paired the Moment with my car and have been able to make/receive calls. Sometimes it takes five or ten minutes to connect. Lately, it hasn't connected at all. I tried deleting the phone and re-pairing it, but that did not help. Yes, Bluetooth is ON. The car is listed on the Moment, stating "Paired but not Connected." Any ideas?

Last edited by Johnny Cakes; November 15th, 2009 at 04:09 PM. Reason: Bad spelling

deadsoccer

I had this issue too with my cars hands free system. When setting it up my phone said paired but not connected and I had to make it discoverable to make it connect again. After giving up the next day I noticed it connected. The only change I had made was I turned off the phone overnight.

Maybe a simple power cycle would work? I also manage my bluetooth connection with ToogleBlu from the app market. Hope this helps.

RacerNine

I found that if you click and hold the device you are paired with but not connected you can choose to unpair, then click it again and it connects.

danooooo

I've got the same issue with a Motorola T505. I've got a shortcut to get into the wireless setting to quickly enable the connection, but do you have an even quicker way?

TheEsupremacy

It's a bug that will be addressed by Sprint/Samsung in the next (first) firmware update. You can manually go into your bluetooth devices and reconnect it when it doesn't connect. Even if it says it says it IS connected, just click on it again. It should work for sure. There is also a bluetooth memory leak being worked on.
Be patient. We know.

surfereddie

how the freak can this be so difficult. bluetooth just sucks!!!

MikeS

Is there an ETA for this first update? Any idea if it will also have a battery indicator fix?

Anybody know if there a process we could kill that would automatically restart to free up the memory leak?

Last edited by MikeS; December 2nd, 2009 at 08:24 PM.

chixdigit

I've had this problem several times with my phone and although it is somewhat of a pain (and I should not have to do this), I have been able to easily resolve it by:
1) turn off bluetooth.
2) turn the phone off then back on
3) turn the bluetooth back on, then
4) turn on your bluetooth headset or turn on your car.

MikeS

chixdigit, I have been playing with this for a few days. Seems all you need to do is power cycle your phone in the morning before you leave for the day and bluetooth seems to work ok. Doesn't seem that turning bluetooth off and back on does anything it is the reboot. I haven't had it not work today and have tried it several different times hours apart.

Last edited by MikeS; December 3rd, 2009 at 04:11 PM.

Jim W

Mine stays paired fine until I turn the headset off, then turn it on later and I need to use the options on the phone to pair it up again. Not a big deal I guess, it's not like it drops out on me.

MikeS

Jim that is the problem. You shouldn't have to re-pair. A quick power off and on while walking to the car in the morning prevents that. I think after it is repaired it must restart whatever is having the memory issue.

paul3263

My Alpine system in my car will only Automatically connect with the 1st phone it is paired to. If you had other phones paired with the system you may have to clear them off of the car system. Then Pair-it your primary phone. You can then pair other phones but they will not automatically connect, you have to manually connect from the phone.

evilbeef54

Power cycleing and unpairing are not fixing this with my wife's moment and her garmin in the car

Johnny Cakes

I have not been able to determine a pattern for this. Sometimes it doesn't pair at all, other times it pairs after 15 minutes. If it doesn't pair at all, then I can get another shot by power cycling.

evilbeef54, when you say its not pairing, has it ever paired? Have you waited a really long time to see whether it will pair? As I said, sometimes 15 minutes after drivinging, I'll suddenly get "BLUETOOTH CONNECTION SUCCESSFUL" on my car's nav screen.

LastError

Mine Moment has been having BT issues as well with a BlueAnt headset. I think I have found a solution that for me at least works every time now:

First turn on the headset or BT device.
Second, go into the Moment's Wireless screen and turn on Bluetooth (if it's already on, skip this step)
Third, tap Bluetooth Settings and enter that menu. Your device should say "paired but not connected" Tap the device name then IMMEDIATELY tap "Scan for Devices"

It should immediately pair up and say something like "connected to phone audio"

An alternate thing to try is tapping the "Scan for Devices" first and then IMMEDIATELY tapping the device name.

For me, this is working 100% of the time and it takes a lot longer to explain how to do it than to actually do it, so it's not that big of a deal for me. What matters to me as that this works.

Is it as easy as it should be? No. I guess it still needs to be fixed.

Hope this helps someone. YMMV and all that.

Last edited by LastError; January 6th, 2010 at 09:57 PM. Reason: extra sentence removed

danooooo

--------------
I'm trying to figure this out too. Interesting that for the last few weeks mine was connecting on it's own (like is should)....then a few days ago I was playing around in the GPS area trying to figure out why it says I'm not in the US, and now the bluetooth isn't connecting like it was. Coincidence? I don't think so! I was turning off and on the network/gps satellites check boxes.

Last edited by danooooo; January 7th, 2010 at 04:55 AM. Reason: forgot the quote

Johnny Cakes

You may be on to something. Sometimes my Moment thinks I'm in Sweden. I'm not sure what I'm doing which causes this.

dbpaddler

When I can't connect, I just go into the BT settings (via Curvefish's BT Widget) and click on the BT device, and while it's trying to connect I click the connect/disconnect button on the BT device and it has worked every time. It is an annoying glitch. My boss constantly has to re-pair to his Audi, and I get to hear the complaints.

On a device note...I've been having great results with the Jabra SP700 speakerphone. Less than $40 new on ebay. No complaints from people on the other end, and the speaker is pretty loud. Plus I won't lose it like I have headsets. Though my Discovery 975 is works well when I need privacy or am walking around.

__________________
I can save you at least 10% on ProClip vehicle mounts and cradles. Send me a PM for more info. Check them out at www.proclipusa.com.

Evilrat

what I've found to work, is turn on the BT setting on the phone, then turn on the BT device, & they automatically connect. (Haven't had to re-sync since I figured that out in Dec) When you want to turn off the BT device, turn off the BT setting on the phone 1st, then the BT device.

danooooo

Since mine was connecting, I thought another app might be causing it to not connect properly. I uninstalled "QuickSettings" but that wasn't the issue so I'm downloading it again. IMHO, it's the easiest way to enable BT and also pick the device to connect.
It's Free!

@JohnnyCakes There's quite a bit of info re the GPS not showing correct location. From what I understand, it's a software issue on the phone. Once you find the correct combination of GPS & Wireless Network & Wifi buttons (off and on), it'll show the correct location for you. I don't think it's affecting the bluetooth connection, but I'm still testing.

electricsheep

I was having a connection issue with my car's bluetooth system, but it wound up the car's bluetooth module could only store 2 devices at a time and I hadn't deleted my last two phones.

Now my issue is the Moment only reads my KCA-BT100 as a headset and won't let me transfer the contacts to it. Anyone else encounter an issue like this in dealing with in-car bluetooth and the Moment?

-Eli

Johnny Cakes

I think that is a KCA-BT100 issue. The KCA-BT100 requires you to "send a business card" for each contact entry; not sure whether the Moment can do that. But if you can use your old phone to send the contacts, then they should be available for use regardless which phone is paired.

almahix

I am having the same problem on my Droid with Android 2.01. The phone is paired with my BMW. It used to connect as soon as I started it up, but nowadays it often doesn't connect at all unless I power cycle the phone. I downloaded a widget that turns BT on and off, and if I toggle it, it will usually connect.

One day I was on a long drive and I was wondering if maybe it was just taking a long time, so I left it alone, and once a call came in it finally connected.

NewAndroidUser

The bluetooth implementation sucks!!!! I can't believe that if I leave my phone on the desk & walk away & it unpairs, I simply can't push the button on the earpiece & reconnect. I literally have to go into the settings menu & reconnect. Simply garbage.

dj928

I have this problem with my phone and computer. I cannot transfer files from the phone to my computer and it says "paired but not connected." Not solved when turning things off and on again.

Also can't get pics to email from my phone to my computer either. Comes through as 0 bytes every time.

Never had this problem with my voyager so I know it's not my computer.

n9ssham

I solved this problem with my new bluetooth headset that I got for Christmas. When I firt got it every thoig worked great... just turn on the BT headset whenever I needed it and it wud connect automatically right away. Then I broke it by making some unsuceesful pairings while trying to do BT file transfers which apparently u can't do on a Moment....after that I had to manually connect my BT headset by going into the BT menu.... rediculous! I fixed it by deleting the other pairings so that only my Bt headset remained on the list. With only one BTdevice on the list every thing connects and disconnects automaticly wit a simple pust of the button on my BT headset... life is gud again!

NewAndroidUser

I honestly think that this phone should be smart enough to recognize the difference between my Plantronics Pro earpiece & my Motorola S9 stereo headset....just plain ridiculous if it can't. I may try you solution however.

9Nails

I'm also a T505 user. I am in the habit of turning the T505 off after driving to somewhere. What I've noticed is that when I connect my Moment to the T505 and turn off the T505, the Moment will reconnect itself the next time that I turn on the T505.

But if at any point after connecting to the T505, I turn off the Momen't Bluetooth radio it won't reconnect itself. The Moment will just show that it's "Paired but not connected" - which I have to pres the T505 and reconnect it again. Just to make matters worse, it will sometimes not connect at all. As if it crashed. Then I just have to turn the phone off then back on and try it all over again.

So, long story short, after connecting to a Bluetooth device, I'm leaving the Moment's Bluetooth radio on (even if I turn off the Bluetooth device) and the Moment will reconnect on it's own.

If I ever turn the Moment off, I have to reconnect to my Bluetooth devices again, but then follow the same pattern in the paragraph above and it is less of a nuisance.

CriticalCritic

I am having the same issue with my bluetooth. It's paired and not connected. I had the problem before the update... and I am still having the problem after the update. This needs to be fixed.

Johnny Cakes

It seems a little better to me but is still very probematic. I have discovered that the "workaroung" mentioned in an earlier post works for me -- going to settings, wirless, bluetooth, scan for devices, make discoverable.

We need an app which will execute this sequence with a single click on the home screen until it is hpoefully fixed. Does anyone know a programmer?

protivakid

I agree completely! I have the same problem with my motorola H375. I have to go into settings each time to re-connect to the phone because it won't auto connect. Not to mention the screen stays on during a voice call killing the battery. If the bluetooth libraries were included in 1.6 (which to my knowledge they are not) I would try to make an app.

NewAndroidUser

Strangely enough, the bluetooth issue seems to have worked itself out somehow. I have 2 pairings (Moto S9 & Plantronics PRO) & for the past few days it has been acting right. I turn on the earpiece & it connects right up. I walk away & it unpairs, but I come back & it syncs right back up. Weird.....I don't have the cl14 update yet so I really don't know what happened.....but I like it.

flu13

I've been experiencing this same problem. I didn't find this thread at first, so I started another. In that thread, someone asked me what happened if I paired my headset with something else. I paired my headset with my Blackberry, and it connected right up. I then paired my Moment with my Blackberry, and it shows as "Paired but not connected." I've tried rebooting, taking the battery out, repairing, rescanning, everything that I can possibly think of or read to try, and it still won't connect to anything.

4theMoment

My issue is that when i connect my Moto Rokr S9-HD head phones to my Moment, it connects. But it cuts out all the time, the phone is only about 1 foot maybe 1.5 from the headset sitting in my coat while outside. Now, when im in the house i have my same headset that I can connect to my laptop which is upstairs, and walk to the basement and not have a issue...I have tried it all...

SoulTerror

I have the same issue as the OP but with a Jabra headset. I was trying to figure out how to make the device forget it. After reading this thread I found out. Hope it works, I hate not having my BlueTooth.

pastafarian

For anyone using any of the "hacked" kernels out there (Zephie's, Johns, etc). My Samsung WEP870 connected without a problem with both cj05 and cl14 (Odin installed). When I went to Zephie's 10.3, I had to manually connect the headset every time. I tried about all the major "hacked" kernels out and all had the same issue. Re flashing to stock cl14 fixed the issue and my headset auto connects just fine again.

__________________
The RULES, follow them and prosper!

Did you forget to kiss a Mod today?

flu13

If you found a solution in this thread, you must have read more closely than I did, because I still have the problem.

SoulTerror

I found out how to atleast unpair the headset, still need to repair it. It was dead when I got home, must of forgot to turn it off last time I was playing with it.

duratime

Does everyone have this problem? Should I return the phone for a new one? I just got this phone last week?

SoulTerror

I still have to manually connect mine each time I want to use my BT.

duratime

I funny thing is I switched to the Moment from the Pre because there was no voice dialing on the Pre, which I felt was unsafe while driving. Now I have voice dial, but no auto connect! I'm not sure what to do next. I cannot switch providers. Is there an widget that can get me to the "bluetooth settings" with one click?

jmdenver

I shut down Incredible then re-paired again, and solved problem.

SoulTerror

2.1 fixed this issue on the Moment.

Johnny Cakes

I wish you hadn't revived this old thread. It brings back some really bad memories!

jstraw

Day three with my EV0..day one with my EVO and my Alpine-equipped car out of the body shop. Having this issue with Froyo. Will try deleting all other device parings from both the Alpine and EVO and go from there.

charliec

Let us know what happens. I cannot get the pairing to stay with EVO/Froyo and new Toyota Tundra (that worked perfectly with Treo Pro, by the way - so it is not the vehicle)

txag08

Has anyone found a fix for this yet? I have a Samsung Intercept and the same problem with not being able to connect. It pairs with my car, but does not connect. Sometimes, after I do a factory reset of the phone, it will connect, but only just that one time and never again until it's reset. Highly inconvenient.

I'm pretty sure it's the phone and not the car, because my old Nokia connected just fine every time without me doing anything. All I had to do was turn the car on and it would connect.

TimCastle

Bluetooth car kit connection problems with Hero Android 2.1

HeinG

My Desire's bluetooth allways worked like a charme untill rooting REDUX 1,2
Connecting to any previously known device, or any new once for that matter, did not work.
Some grey hairs, upgrading to Redux 2.0 and many tries later I concluded some data must be corrupted somewhere.
Deleting the content, not the files, just the content of the following files did the trick, much to my relief.

here's what you do:
(SU rights required)

edit the file:
/data/misc/bluetoothd/{some number}/names
and delete all data in it
save it

edit the file:
/data/misc/bluetoothd/(some number}/linkkeys
and delete all data in it
save it

{some number} is (I think) your device BT id

ready
I think linkkeys was corrupt, I deleted the first file content (names) to make sure no inconsistancies between the two remained.

Hope it works for you guys too

HeinG

ohh yeah... don't forget to reboot after this.