I have a Verizon TP2 and a 2009.5 Pontiac G8 with built in bluetooth...
I previously had a T-Mobile Shadow and the bluetooth worked flawlessly on this car. Now that I have hooked up my TP2, it seems that everything works with the exception of the hangup function. When I press the button on my car to hangup, the car disconnects properly and switches back to the radio, but the TP2 still stays connected.
Any thoughts or suggestions?
Related
I am having some issues w/ WM6 and my Plantronics 640 headset. After a call or two, when I go to initiate a call from the telephone (with handsfree on), the call immediately connects and disconnects right away.
If I disable bluetooth, it works fine using the phone.. If I re-enable bluetooth, I will get one or two calls and then the same behavior comes back.
BT
Try to leave the unit on while calling.
So, go into setting, power and take out the tickmarks for 'switch off after xx'.
There's something flaky on the BT implementation and the unit going auto-off. No expert, but it worked for me on my BT carkit.
Hello all. I'm new to windows mobile but not to smartphones. For some reason my bluetooth headset is not working. I have not installed TomTom or had any error messages, basically I turn on the bluetooth function on my TP2, then turn on my headset, it goes to search and never finds my headset. It finds everything else, my blackberry, another cell phone, but not my headset. Any ideas?
Headset not in pairing mode or not visible? If you have another bt device, use that to test.
I thought I had it in pairing mode but apparently I didn't lol. Problem solved, thanks!
I'm trying to connect my Sprint TP2 to my car stereo's bluetooth.
It works great for streaming audio from my phone, but when I try to make or receive a call, it's as if it's not even connected. If I call from the phone, and then click the connect button on the stereo a few times, it will connect, but then only for a second or 2 before it drops off again. The phone call never gets lost, it just doesn't work like a hands-free headset should.
What is interesting though, is if I'm playing a song from my phone, then the head set portion works exactly as it should.
I tried another phone, a Treo800, and it works as is should; you can make and receive calls as you would w/ any headset, and doesn't have to be connected via the audio profile first.
Any suggestions?
batpot said:
I'm trying to connect my Sprint TP2 to my car stereo's bluetooth.
It works great for streaming audio from my phone, but when I try to make or receive a call, it's as if it's not even connected. If I call from the phone, and then click the connect button on the stereo a few times, it will connect, but then only for a second or 2 before it drops off again. The phone call never gets lost, it just doesn't work like a hands-free headset should.
What is interesting though, is if I'm playing a song from my phone, then the head set portion works exactly as it should.
I tried another phone, a Treo800, and it works as is should; you can make and receive calls as you would w/ any headset, and doesn't have to be connected via the audio profile first.
Any suggestions?
Click to expand...
Click to collapse
Check this thread out: http://forum.xda-developers.com/showthread.php?t=591322
The TP2 can have some weird behavior with bluetooth car kits due to the Widcomm bluetooth stack. I applied the fix in thread linked above and haven't had any problems since with the Tilt 2 and my Acura's bluetooth system.
thanks, I'll give that a shot tonight.
didn't work for me; exactly the same behavior as before.
Additionally, the BDAddr key in HKLM\Software\WIDCOMM\BtConfig\General always resets itself when i reboot my phone (the instructions say to set the value to "no value").
I even tried changing the key type, and it reverted to binary upon reset.
I'll keep searching, but in the meantime, any other suggestions?
Hello guys,
I just got a Sony bluetooth headset and I am trying to use it with my HTC TYTN II. At first I paired the phone and the headset and I was able to listen to music and talk through the headset, all perfect. When I was listening to music, the bluetooth icon on my phone represented a music note and a headset over it.
When I turn the headset off once and then on again, it connects automatically with the phone but in some other mode. The bluetooth icon now represents the bluetooth sign with a headset over it. Now when I listen to some music, it comes from the speaker of the phone, not from the bluetooth headset. Talking through it is not a problem.
If I pair the phone and the headset again, it works just fine (showing again the music note) but once I turn the headset off and on again, I lose the music mode.
Does anyone know how to fix that? Thanks in advance.
I fixed the issue by installing AutoA2DP (found in this forum).
I've had a similar problem on my Tilt. I originally posted the following on the ROM thread. Since then, I have found that the AutoA2DP has not fixed the problem. I still have this issue about 70% of the time, and sometimes I can't get the bluetooth to work at all, not even after a soft reset. Sometimes it seems as if the bluetooth has no power, the phone can't communicate with the headset except when within a few inches of one another. Then it magically seems to resolve itself. Anyway here's my original post from the ROM thread.
The other day I installed an app on my phone called Schaps Network Plugin, which allows you to map network drives to the phone the same way you can do with a desktop. It allows me to access the home network directly via my wifi. It was something I needed and it seemed to work great, for a day. The next day my bluetooth headset would not connect. Long story only slightly shorter, it seems the problem was with the headset connecting via A2DP and doing so automatically. This always worked just fine in the past. Suddenly it wouldn't work. I tried a ton of things including a "fresh" install of everything and formatting my memory card to start with nothing on it. I flashed the original rom and then flashed this rom. I did hard resets each time. Did this twice. Even tried the bluetooth in the oem rom to see if I still got the problem. I did, and it is still with me. I can manually get the headset to connect via A2DP using the bluetooth settings, though even then it may take reconnecting several times to get it to work. However, when I turn the headset off and then on again, the A2DP does not reconnect, just the hands free. But the sound is not routed through the phone's speaker either, at that point. In fact you often get no sound at all, nothing via the headset or the speaker. OTOH, if you activate Voice Command, the headset does work while Voice command is running. After it shuts off, you are back to no sound. It seems as if the hands free works fine, but the audio gets partly routed to A2DP but does not connect to the headset. If I reset the phone, the headset connects correctly and efverything works until I turn the headset off again. Also if I pair the headset again, everything works correctly until I turn the headset off. Though pairing is not as trouble free as it used to be either. Sometimes it will not pair up wihtout repeated attempts. I did find this program, AutoA2DP which has patched the problem. It detects when a paired bluetooth device connects, and forces a connection via A2DP as well. But I never had this issue in the past, and my wife's phone still has no problem. I am not sure the Schaps Network plugin had anything to do with it, other than the timing. Seems odd to me that the bluetooth stack would suddenly develop issues that persist even after two fresh flashes of the rom. Any ideas, suggesitons, etc.? This is really bugging me, and although the patch seems to be working, the phone is still not acting "right." In the past, and on my wife's phone, if a bluetooth headset is turned on, it automatically connects, and all sounds, including the system sounds, are routed through the headset. Now, sometimes they are, and sometimes they aren't.
Has anyone else paired a headset to their slide and had media audio come through it?
I paired my old jawbone2 to my slide and when I was playing a game, game audio came through the ear piece. It only happened ONCE and now everything (except calls and the genius button) is back to the phone speaker.
Is that normal? Should audio be routed through my BT Headset like that? I was pretty certain only calls should go through to a non a2dp device.
I don't know anything about the jawbone2, but I have no problems. For regular phone use, I have a Motorola H500 and I always play Pandora in the car, and have never had music come through the H500, just voice like it should be. (I've used the H500 on the G1 I ordered on launch day, on a Motorola Droid, a Sprint EVO 4G, and the 3G Slide on a variety of stock and non-stock ROMs.) I also have a Motorola S9 A2DP headset, and the audio works as you would expect on it also on all of those devices. Maybe the Slide detects the Jawbone2 in a funky way somehow. What does it say when you go to Settings->Wireless & Networks->Bluetooth Settings->Jawbone2 (press & hold then select options.) If it's not a A2DP headset, it should just say "Phone, Use for phone audio." An A2DP headset will also say "Media, use for media audio." If you are lucky, the phone is just detecting it wrong and you can uncheck the Media option.
It only did it once and then went back to acting like a normal BT headset.
I am going to chalk it up as a fluke from initial pairing.
And under options it says phone audio only which is ok.
I'm replacing it with a Jawbone Icon tomorrow which supports a2dp and a whole slew of other nifty features for a single ear headset.
Don't deal with much bluetooth headsets but i do hook it up to my car stereo and i know there are settings in the bluetooth of that specific device. have you had a chance to look in there?
Bluetooth Pairing problems
I have similar problems when pairing to my truck stereo. It auto pairs when I get into the truck and works perfectly well the first time I make a call. But after that it doesnt disconnect properly AND it will disconnect but will stay paired.
I am able to go into BT setting and have it reconnect.
Works once then bam not connected again.
I have Android version 2.3.3
Baseband 47.3201.35.06U_7.07.35.025
Kernel 2.6.32.17 -Cyanogenmod-g501281a
Mem Info
183MB /418MB
Build GRI40
Connecting to a Kenwood Receiver
DNX9140
It worked fine for my Nexus Not sure why this is happening.
Thanks