I have a strange Bluetooth issue: I can't even find my Bluetooth headset with my HTC One X.
But the Bluetooth headset works perfectly - I can easily find it with my HTC Desire or any other phone.
The headset itself of-course is in pairing-state.
Might this be due to only Bluetooth 2.0 capability of my headset?
As you know HTC One X has Bluetooth V 4.0. Is this backwards compatible to Bluetooth 2.0?
Anyone else experiencing such issues?
theliquid said:
As you know HTC One X has Bluetooth V 4.0. Is this backwards compatible to Bluetooth 2.0?
Click to expand...
Click to collapse
It's supposed to be. But as we all have experienced at one time or another BT is an imperfect technology. I've been lucky. All my BT devices work fine. The One X actually connects much faster to previously connected devices than my i9100 did. I have a BlueAnt Q2 and confirm it works fine.
Once you do get a headset connected you'll find HTC didn't include a native ICS voice dialer. All the APK's I've found don't work. The only way I've found so far to initiate a BT call from the headset is to use Vlingo in In Car mode. Hopefully a dev will come up with a working BT dialer.
Good luck.
Argh, my Bluetooth headset was quite cheap (~30 €), and is a no-name brand (bought about 2 years ago)
Bluetooth connection from One X to Desire works flawless.
Maybe I'll buy a new headset from a well-known brand ...
Or any other ideas?
try a reset of the phone? that seems to help in a lot of cases. also, any other bluetooth connections already in place? may want to try removing them before doing the reset. i have a much older bluetooth headset that will pair with my one x. and a newer one that pairs. both useless for voice dialing without an intermediary app, but the newer one seems to work well with a paid app (enhanced sms and caller id) that will identify callers and also read sms messages. getting there.
Hmm, reset is just my 'ultima ratio' ...
Will only try it, when I get not other solution ...
Any other ideas?
Related
Hi all,
I just bought the Parrot minikit Hands Free car kit.
I am facing allot of problems with this device:
1. The main one is that when I am issuing a call from the TOUCH, the sound remains in the TOUCH and is not routed to the car kit.
2. When someone calls me most of the times I can answer the call and it works fine, but sometimes the phone rings and the car kit not.
I read in the trinity accessories forums that people faced the same problems with other Parrot car kits when they upgraded their roms to WM6.
I opened a SUPPORT case to Parrot and they are saying:
"We have fully tested the HTC Touch in France with our Minikit and we did not see any impediments. "
So I emailed them back with allot of links describing the problem.
Did anyone faced problems with the Parrot Mnikit or any other Parrot car kit with the Touch?
Thanks,
Carmi
Carkit problem
Hi,
I have a similar problem. I have my HTC touch paired with a Nokia Bluetooth carkit. I get incomming calls over the speaker but when I answer the call I first have to go to the menu and select "enable handsfree calling".
I can make outgoing calls directly via the carkit whitout selecting an option in the menu. Furthermore the volume is very low compared to my prvious PD (MDA Vario).
Has anyone a fix for this?
Gus
I have The same problem
I have an HTC Touch with a Parrot CK3100 freehand car Kit and have the same problem.
Often, when I receive a call the car kit show the call in display but when I pick up the CK shows an icon (like a musical note) and the audio is not transferred.
When I call from the HTC, some times works fine and some times no.
A partner of my company with the same car kit and a HTC Touch dual, has the same problem too.
With WM5 works fine (I test it with HP6515).
did you set the "services to use from this device" to "Hands Free" ?
This is a known issue with Parrot devices and WM6. I've had the same problem with a couple of different HTC WM6 devices. The problem is specifically related to Parrot, not WM6 in general. I've used the Tytn II with Motorola and BlueAnt BT devices without any problems. I upgraded my minikit from v1.02 software to v1.03, but that hasnt fixed the symptoms which we are all complaining of.
ARE YOU LISTENING PARROT?! Ive had the minikit for 6 months and I'm getting tired of waiting for a version of software that will fix all our problems.
I have the exact same issue with my Parrot 3200. I'm also waiting for a solution from Parrot!
Parrot MINIKIT and Touch problems
I've similar problem.
paired the two devices, sometimes I can start a call from my Touch and the sound is on the MINIKIT speaker, but most of the times the is still on the phone and I have to press the green button to switch the call on the parrot speaker.
I've upgraded the firmware from 1.02 to 1.03.
Another information: I've tested the MINIKIT with my blackberry 8100 and works perfectly, when paired and connected every calls is routed to the parrot speaker, so I think It's an issue between the parrot and WM6.
Any news?
thank you
Besides my Touch I also use my BlackBerry 8800 and that also works fine. With htc it's not working as it should be.
HTC Touch Parrot mk6100 PROBLEM!
With the Parrot mk6100 I have all the problems possible.
This Parrot is supposed to play properly the mp3 files that I have in the touch, but everything is a dissaster. Very long to write. The thouch gets hunged every time.
The worst problem is that the Parrot can't read the contacts in the Touch.
I have spoken with Parrot and Htc here in Spain and both say that the problem is Windows mobile 6.
I don't know what to do...
ive got the dual w mk6100
after having a lot of issues i found out i had to pair it both ways and the mk6100 got to say "bye". then everything worked fine. well almost. but pretty good indeed.
i posted in niki accesories.
it takes time to sync the contacts, true, but it finally does.
as far as i know, touch and touch dual is not that different , except for the mhz.
let me know what you think
Touch cruise and Parrot Minikit
I have the similar problems too. Sometimes the sound cannot be routed to the car kit. There is no way to understand the reason why one time it works fine and another time it cannot move the sound via blue tooth. Sometimes pressing the green button of the parrot minikit is possible to move the sound to the car kit, sometimes it doesn't help - the sounds remains in the HTC. I tested the Parrot minikit paired with Nokia E70 - I haven't seen any problems. Also I have tested the HTC paired with another blue tooth car kit - BHF-200 and all was OK.
I wonder ... if someone knows ... if the WM6.1 (by Bepe) will fix the problem!
Thanks in advance !
Parrot Minikit just tested with QTEK 900, WM6.1-Ranju
The Parrot minikit was tested with my other PPC - QTEK 9000 (HTC Universal) and I didn't see any problems. The QTEK works under WM6.1 (Ranju pack).
So I really wonder ... to upload WM6.1 to my HTC touch cruise ...
Any comments and opinions are welcome.
Thanks in advance !
p.p. My HTC touch cruise is still with its original WM6.0 ...
Bluetooth Hotfixes
Has any of you guys or girls tried any of the "Bluetooth Hotfixes", that are available for HTC branded devices on the HTC e-Club site.
It seems to fix dropped calls and connection probs. (and it seems to work)
The hotfix is available for several HTC devices.
You just have to register your HTC branded phone to get to the download portion of the site for your model, and see if it's available.
It's definitely there for the Elf, Tytn II and S710 (i'm not sure if it's there for the Touch cruise)
I recently purchased an AT&T Tilt (TYTN II phone) with Windows 6.1 Dutty Series... since my motorola KRZR took a dump on me....Quite an upgrade...I am trying to use the Motorola H700 Headset from my KRZR on to my HTC, I can get the headset located in the device menu but I cant get the HTC to pair up with the headset on a continual basis. I am also having an issue connecting to a Bluetooth GPS Antenna. I can locate it it just the same as the headset but it wont pair to the HTC nor ask an authorization code.
Is this a bluetooth glitch? Can I somehow reload the driver for the bluetooth? Perhaps I am doing something wrong but I never had a problem linking bluetooth devices before.....
On a separate note....I tried doing an activesync via bluetooth on my Dell Laptop and it again can be located on both ends but I can get any services to work on either side...
Help?
I have just received a new HTC TyTN II on Orange that has the same problem. My old one (windows mobile 6.0) had no problem with my Motorola H12, but the new one (Windows Mobile 6.1) can't keep the pairing, and I have to turn Bluetooth on an off to get the connection. Always have to enter the passcode.
Version data is:
CE OS 5.2.19212 (Build 19212.1.0.3)
Processor: MSM7200-400MHz
ROM version 1.65.16.25
G 25.83.40.02H
D 3.28.00.00
Any help /advice much appreciated!
O.
Pyper,
i don't know how it is on the H700, but on the BlueAnt Z9, you have to hold down the power switch until the LED on the headset blinks red very rapidly, when it does this, the headset is in pairing mode. then you can pair the phone with the headset. try something like this with the H700. if you can, find out how to get the H700 into pairing mode before you try to pair it up.
hope that helps!
Pyper70 said:
I recently purchased an AT&T Tilt (TYTN II phone) with Windows 6.1 Dutty Series... since my motorola KRZR took a dump on me....Quite an upgrade...I am trying to use the Motorola H700 Headset from my KRZR on to my HTC, I can get the headset located in the device menu but I cant get the HTC to pair up with the headset on a continual basis. I am also having an issue connecting to a Bluetooth GPS Antenna. I can locate it it just the same as the headset but it wont pair to the HTC nor ask an authorization code.
Is this a bluetooth glitch? Can I somehow reload the driver for the bluetooth? Perhaps I am doing something wrong but I never had a problem linking bluetooth devices before.....
On a separate note....I tried doing an activesync via bluetooth on my Dell Laptop and it again can be located on both ends but I can get any services to work on either side...
Help?
Click to expand...
Click to collapse
I've been having issues with my HTC TyTNII with the official 6.1 ROM and the Jabra BT500V headset. The pairing is automatic in WM6.1. The bluetooth causes the phone to be sluggish and causes call drops if the call's picked up within 3 rings or the call's picked up before it rings on the phone (Yes, Jabra rings first before the phone does). I've escalated this issue to HTC SEA Support and they've advised me to disable Bluetooth and test which I did for the past 3 months :|
I have 3 Jabra headsets (BT250, BT500, BT500V) and all are having the same issue with this ROM. I'm quite skeptical to buy another brand just for testing purposes. Do anyone else face the same issue? HTC SEA has fixes available specific for Jabra / Samsung headsets on Touch Cruise but strangely not on TyTN II
Finds BlueAnt S3 but won't pair
My BlueAnt ST3 pairs fast with a Motorola Razr V3xx but the HTC with WM6 Professional, finds the ST3, prompts for the password (0000) but always fails. On the Razr, I touched the enter key but on the HTC it only beeps. I tried the O.K. key too. The message I am getting after touching "Next" says invalid password or connection. Yes, Bluetooth is turned on and the ST3 as well.
Any ideas anyone?
Hello:
Some time ago I bought an unbranded HTC KAISER with WM6.1:
rom version: 3.29.422.1 WWE
rom date: 05/20/08
radio version: 1.65.20.29
protocal version: 25.88.40.04H
BT VERSION: 2.0/2.0+EDR
BT ADDRESS: 00:17:E8:2E:9F:A1
Anyway, I'm still having bluetooth issues with the unit. The BT works great with BlueAnt Z5i on streaming and music listening but I can't get it to work on phone calls, incoming or outgoing. No sound in the headset nor out of the Mic. Same problem with new Jawbone on calls and a Motorola HS860. Before I waste any more money I thought I'd ask about possile regedits etc. to correct this problem? Or perhaps I should consider new Roms?
Ben lurking here and reading and re-reading and getting more confused..anyone have suggestions or can point me to a probable solution?
Thanks for Listening
I finally got it to pair with BlueAnt ST3 and Motorola T305
BlueAnt ST3: I had to delete the ST3 connection, and get the ST3 in "pairing mode" then have the phone search for bluetooth devices. Doing this I got the password screen and entered the 0000. Driving around testing this, it was not as good as the Motorola Razr V3xx. Not always answering, dropped calls ect.
Motorola BT Speaker: I just received a Motorola T305 BT speaker, same process to get it paired. No voice activated call function yet. Just the two beeps, one indicating it is ready for a command and then it beeps again, and clicks out. The ST3 would talk to you and ask for confirmation.
What I have learned so far, the trick is to get the speaker phone in the pairing mode, so the Kaiser phone will prompt for password.
I am going to sell the Kaiser and buy the HTC touch HD and hope for better bluetooth functionality and reliability.
Hmmm... Actually I have no problem pairing any of the BT items I mentioned, just the handsfree doesn't work in all. Thanks for the reply...
Need a help to make T7373RUS works with bluetooth mono handsfree.
Actually it works with, but does not the whole functionality, one thing is missing - it's a voice dialing via pressing call button on BT handsfree. OK, I know T7373 (non USA) does not have any voice dialing, but this is a WM, well I set up VITO VoiceDialer and it works perfect. But there is a problem - my bluetooth handsfree don't launch it. I've tryed to use wired handsfree it works perfect. What is a point, why such perfect phone cannot does that any nokia or SE phone does like a piece of cake.
Please help, this is really sad thing need to be fixed, can some one to figure out how to solve this?
May be anyone know USA version of Tp2 uses the same bluetooth stack?
May be some parts of USA version software is possible to integrate into my TP2?
Does anybody use Bluetooth handsfree with HTC TouchPro2????
Hello,
I've had my Tilt2 for 2 months now and am ready to get a headset. After many searches I can't find a definitive list of headsets that are working/ not working correctly.
I'm using a stock ROM and have the Tilt2 2 tweaked to 43% memory usage on boot-up. The phone is fast and everything works correctly. Also using SPB mobile Shell.
Has anyone tied in the Bluetooth 2.1 vs 2.0 headsets with correct operation? I want the voice command, audio passthrough, and buttons to work correctly.
Maybe we can start a list of Phone - ROM version - Headset - Whats working/not working.
I'm mainly concerned with the stock ROM but any info may assist others.
Thanks
Jim O
Well, I have the Jawbone Prime & Motorola HX-1 and both work fine.
Motorola H710 works fine as well.
Thanks for the info. Does the voice command work for making calls and you can also hear music files and audio from websites?
Thanks Jim O
Surely more folks can contribute to a good list. Lets get some more response going. This could be of great benefit to one and all.
Thanks!!!!!
Samsung WEP 850 with voice command works just fine.
The Sony DRBT100CX stereo bluetooth earbuds also work very well with the Tilt 2. All A2DP/AVRC audio and handsfree calling functions are supported. Nice bargain at $50 as well.
Yes, but...
... has anyone found a BT headset that announces the incoming caller ID over it instead of the phone's speaker?
I've tried a couple of older as well as one new BT headset. All pair and work flawlessly with my Tilt 2, but none of them will announce the incoming caller ID over the headset as it did with my original Tilt.
Yeh, I'm pretty sure this was a screwup in the Widcomm BT stack but just want to make sure. FYI, HTC tech support states that none of their phones do this! When I asked 'em why the old Tilts did, I didn't get any more response.
Well, I picked up a new Motorola H17 12/30/09. Everything works as advertised, except the incoming caller announcement (on phone announcement only). This headset was released only a couple months ago with the latest Bluetooth 2.1 and all the other amenities so this problem does seem to be a problem with the stack.
On a side note, this headset works great. Get ALL phone sounds transferred and also volume control on both the phone and headset. Works great with streaming video/audio. And it is loud, usually have it set to mid volume. Also, I bought it from an AT&T store ($80) and he stated that if anything goes wrong with it for 1 year just bring it in and he will replacement.
Jim O
I have the Jabra HALO and works wonderfully well with my TP2, running Win6.5
jlmwrite said:
... has anyone found a BT headset that announces the incoming caller ID over it instead of the phone's speaker?
I've tried a couple of older as well as one new BT headset. All pair and work flawlessly with my Tilt 2, but none of them will announce the incoming caller ID over the headset as it did with my original Tilt.
Yeh, I'm pretty sure this was a screwup in the Widcomm BT stack but just want to make sure. FYI, HTC tech support states that none of their phones do this! When I asked 'em why the old Tilts did, I didn't get any more response.
Click to expand...
Click to collapse
The manager @ my local AT&T store has a Tilt 2 using a Blue Ant Q1 bluetooth & he says that his BT does all these things. I just ordered one so I will let you know when I get it. FYI he was using a Jawbone prior to the Q1.
Montea said:
The manager @ my local AT&T store has a Tilt 2 using a Blue Ant Q1 bluetooth & he says that his BT does all these things. I just ordered one so I will let you know when I get it. FYI he was using a Jawbone prior to the Q1.
Click to expand...
Click to collapse
I got my Blue Ant Q1 and it does announce the incoming calls over the blue tooth & your text messages, e-mail, reminders, your music- I like it. If you turn "announce incoming call off" in voice command it will not announce them over the speaker on the phone. I bought mine off e-bay for $48.99.
Hi all,
Anyone can confirm that Desire has a rSAP (remote Sim access)?
Some people are saying it doesn't work with their Nav, some say it is working.
Any one got it hooked up to their Vw/Audi/Skoda RNS Nav?
Looking to change from my TouchHD.
Cheers,
Android does not support the SAP/rSAP protocol. It may be that some people have it working on cars that use the HFP or HSP profiles.
Thanks mate, not good at all!!!
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
swissman said:
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
Click to expand...
Click to collapse
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Maybe you could check if it has another setting to retrieve data from the phone.
From what i know the new modules used in audi/vw/skoda are Novero modules (part of the nokia business) which only supports rsap.
The older modules are from harman/Becker and do support al the possible connectiontypes.
You can check which type you have under the passengers frontseat, the modules are build in under the seat, not in the radio.
If you have a Novero, tough luck. But you can always check on the local car junkyard if you can find an old car which does have a harman/becker, and build that one in
salahag said:
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Click to expand...
Click to collapse
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
salahag said:
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
Click to expand...
Click to collapse
Exactly... you can even read/send sms directly through the display and through your car multimedia system.
Ford
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Tirinoarim said:
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Click to expand...
Click to collapse
I got the stock Android and it's showing Android 2.1 update 1.... but not working ;-)
Hmm - well I'm trying to use my HTC Desire with a 2010 Audi A3 with BT and not having any luck so far. Although it paired and transferred the phonebook (took quite a few minutes with a couple of hundred contacts), it's now being really flaky and sometimes just refusing to connect at all. I tried un-pairing/re-pairing but to no avail. It just seems to work sometimes for a bit then stop again. By comparison pairing my Desire with a Jabra BT headset worked fine.
Anyone else having these problems? Anyone know of any updates for the Audi software? (if not I suppose I'll just need to wait for Froyo and hope that it fixes things )
my desire works well with my VW golf.
phone book, calls (dialing and receiving) and status dispay working. not working is SMS
Hey Folks,
there is room for some BT "education", because most people don't know the difference between rSAP and Handsfree.
Handsfree is working like a BT headset - most disadvantage - you are using the phoneunit of your mobile.
rSAP is using BT protocoll to get only the SIM card of your mobile and work together with the phoneunit of your car.
For Audi you can see on which mode your are conntected at the MMI-Display => "SIM card icon" stands for rSAP while "Mobilephone icon" represents handsfree mode.
no rSAP
I could be wrong, but I was of the impression that Nokia had patented the RSAP protocol, so you're not going to see it on non-Nokia phones. Irritating, really. Some car users have retrofitted their handsfree kits with a module that uses handsfree profile with some success but it's not going to use the car antennae etc in this case.
rSAP is a "STANDARD" for bluetooth protocoll in general.
Nokia was one of the first, thatswhy the Nokia unit has some "problems" in early releases....
Well I picked up my Skoda Superb last week, dealer told me they were fitting the new GSM 3 units that had just recently changed, not that it meant much to me.
Anyways it did work fine first couple days then started playing up with not connecting, I went into the options because I found it was connecting to media, but not phone, so I disabled the media option on the phone for the bluetooth connections and its been fine ever since.
Desire running Modaco R4, R5 & R6 now also ok.
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Will take a look though see if its connecting with a phone or sim card, I had noticed the signal always seemed really good even if the phone was berried in the car somewhere so maybe the rSAP explains it.
Tinyk said:
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Click to expand...
Click to collapse
Do you have a link to the thread that includes this file by any chance?
Do not mix up android 2.1 and 2.2.
AFAIK the modaco roms are froyo which should have a better bluetooth stack than eclair.
Well some good news! The FroYo/2.2 update on the Desire seemed to do the trick for me and I now seem to be able to get a stable BT connection with my A3. Phonebook transfer working fine too and it's reacquiring the connection when getting back into the car.
Any hope for Android 2.1?
Alanjrobertson: did you say you got your HTC Desire Android v2.1 phone working with your Audi, albeit a bit flaky? I cant get my HTC Desire Android v2.1 phone working with my VW EOS working at all.
What was the process you followed? The process I went through was to turn on phone’s bluetooth and make my phone discoverable. I then initiated a search from the car. It found my phone and displayed the correct name. However, when I chose the “connect” option on the car, it gave the error message: "mobile telephone phone is not compatible" on the car’s MFD.
Is this what you did? Is there a better way of connecting?
The car’s entertainment system is RNS510. I’m not sure if this is associated with Bluetooth or not.
My previous phone (Nokia 5800) worked OK, but my Desire doesn’t.
I am hoping that the Android v2.2 upgrade will fix my problems, but I’m still waiting for the update from Orange. It could take a while by the sounds of things.
I contacted HTC and they told me “The HTC Desire does not have the remote sim access profile. we currently have no plans to update the Bluetooth profiles on the device.” This makes me worried that when I eventually do get the Android v2.2 upgrade it will not work.
Any ideas other than waiting for the Android v2.2 upgrade?