Related
Hi,
I've trawled the forum and I've followed all the TomTom setup procedures. The Problem is they seem to be for people who can't get TomTom working at all. I can get it working, just awkwardly.
Once I pair with my GPS receiver and go into TomTom i can get a connection. However when i quit TomTom and turn off the GPS it seems to forget. Next time I turn it on I don't get a connection.
The way I understand TomTom is that it seems to wait for the GPS receiver to contact the phone. This seems odd as I would have thought the phone would be the one to initiate contact.
Anyway my GPS receiver just seems to forget what phone it was connected to. TomTom obviously isn't forgetting the port, windows obviously isn't forgetting the pairing. But Every time I use it I have to re-pair the receiver (thus reminding the receiver of the phone it's supposed to be bonded to). It's beginning to drive me a bit insane.
Anyone else have this issue? Perhaps it's to do with my incoming and outcoming ports? Hopefully someone has already solved this? Not seen any references to it anywhere.
Lewis
Hello,
Which version of Tomtom are you using ? The last one (5.21) ? If not, try to upgrade and try again.
Yep 5.2 latest release.
I was hoping upgrade would fix it but alas no.
Lewis
BigDamHero said:
Yep 5.2 latest release.
I was hoping upgrade would fix it but alas no.
Lewis
Click to expand...
Click to collapse
Don't mean to be picky, but 5.2 or 5.21?
I've held off installing TTN on my Wizard, as it works fine on my iPAQ 4700, I have a cradle for that, and according to ttcode, my current device is actually my old 3970, not the current iPAQ... Last week, I had a couple of hour drive to do, so I thought I'd give it a whirl. After an email exchange with TomTom support (who were more helpful than I'd originally given them credit for), I had a new activation code for the Wizard. Here's what I did, from a fairly recent hard reset with no previous TTN install whatsoever. Skip the mail if it doesn't look helpful, but I'll detail my steps in case it helps anyone else...
Although I believe the PC install is mended in 5.21 I copied the map and voice cab files from the CD to my SD card and installed them from there. The GPS drivers and main app I installed from the download I got from the TomTom support site by running the setup util on my PC. Once everything was installed, I moved the maps which seemed to finish up in a sub-directory on the card to the root of the card.
I paired the GPS (my old Emtac BT one) and selected serial port profile. I tried all the offered serial ports in the "Other BT GPS" list in TTN but none worked. Then I went to 'COM Ports' in Comm Manager/Bluetooth Settings and selected "New Outgoing Port". I picked the GPS from the list of paired SPP devices, and it created a new BT COM port on COM6. That definately hadn't been in TTN's list of BT com ports before, but is now there in the list with about half a dozen others. I selected that in the "Other BT GPS" list of BT ports, and TTN connects to the GPS each time.
As I said, I'd recently hard reset the device to try and prove a problem with my BT car-kit soit's quite possible the clean install was the secret, but try creating a new outgoing COM port against the GPS and see if TT remembers that...
Dox
BigDamHero said:
Hi,
I've trawled the forum and I've followed all the TomTom setup procedures.
Click to expand...
Click to collapse
Which?
There are 2 general ways to set it up, 1 works 100% (i use it so know it does ) 1 i dont use and have never tried so may well work in the reverse direction and be causing you errors.
The way i set up tomtom; pair the BT GPS. Open an OUTGOING port to the BT GPS, set my GPS as OTHER (wired/cable) NEMA device (NOT bluetooth) in TTN5. now my tomtom connects to the bluetooth, not the otherway round. This method has thrown up no errors for me at all.
If you have followed the reg edit/hack to show the GPS page in connections then i dont know how the settings differ and the possible results this could have on connection issues.
Let us know which way you are going
I have the exact problem as BigDamHero. Each time I wanna use TTN, I need to delete the previously paired BT GPS and then pair it again, otherwise the TTN will just say No GPS Device. I use TTN v5.21 and Wizard with Windows Mobile 5. I tried my BT GPS device on my brother's PDA which runs on Windows Mobile 3, and it connects like a gem every time. I am also looking if anyone has solved this issue, cos it is tedious re-pairing every time.
Had the same problem until 5 mins ago! Found an explanation in another thread, but only in Dutch..
Here's how to do it:
Turn on GPS
Activate bluetooth on device, go to BT parameters, delete previous pairing like you're used to
Create new pairing, choose GPS, enter passkey, check Serial port in services, go to COM ports and add outgoing port (e.g. COM6) like you're still used to :roll:
Add an incoming port too (e.g. COM7) <-- Here's the trick!
Set your GPS apps to use COM6 (the outgoing one)... and here you are! This time it will work, you can turn off GPS and device bluetooth, turn on again and it will connect by itself.
If you want a bit more you can activate GPS panel, set program port to COM8 (then you will have to use this in your apps) and COM6 as hardware port.
Everything works fine now!
hey man, wot a coincidence....i also just read that post which had the dutch explanation.....BUT however, it's not working for me.
toneslee said:
hey man, wot a coincidence....i also just read that post which had the dutch explanation.....BUT however, it's not working for me.
Click to expand...
Click to collapse
I did everything in the list except for creating the incoming port and it still works everytime (I know that's no consellation to you). I wonder if something else you've installed, or the way you installed the app is causing the problem? Is it worth a hard reset and trying the entire install on a clean wizard?
Dox
A friend didn't need the incoming port either. I believe it has something to do with the GPS, as he has a different brand than me.
With mine, before adding the incoming port if I started an app without erasing/redoing the pairing before I would get a notification saying "Navman GPS wants to connect" and asking me to pair. It would keep coming every 10 seconds whatever I did.
BigDamHero, what brand / model of GPS is it?
Maybe we can see if anybody here, or over on pocketgpsworld has been able to make the same combination work and if so, what they had to do to get it to fly...
Dox.
well, tomtom was the very first thing I installed when I got my new vario. it was only after I got tomtom fully working (but still need to re-pair everytime), then I installed a couple of simple Card games.
toneslee said:
well, tomtom was the very first thing I installed when I got my new vario. it was only after I got tomtom fully working (but still need to re-pair everytime), then I installed a couple of simple Card games.
Click to expand...
Click to collapse
A quick glance at pocketgps suggests others are having similar issues. There's a thread here that suggests leaving it a while, and I seem to remember other GPS issue threads saying power up the GPS and let it get a fix before starting TTN. A more detailed probe round the forum will probably show more of the same.
Dox
I've just flashed my Qtek 9100 to a new ROM, (the O2 one), and since then I've been getting this same problem. With my previous ROM everything worked fine. I was able to turn of either my PDA or GPS, and they would always auto-reconnect in a few seconds. Looks to me like something broke during one of the ROM changes. Which ROM versions does everyone with/without this problem have?
By the way, I have a BT77 GPS.
Hey sorry for the total lack of reply. Been snowed under with exams.
Ok I tried most of what you guys said but didn`t work. BT ports aren't available to select as hardware ports.
However I have managed to solve it. The key was to pair the GPS, and create an UNENCRYPTED OUTGOING port. That's all. Previously I had encrypted ports outgoing and incoming. My GPS applet in control pannel is set to none so it,s nothing to do with that.
I don't know what my GPS is. Its unbranded. One of the cheap common ones.
Hope this helps some people with the same problem.
Lewis
After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht
Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?
Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.
Changed over to Tytn... works perfectly without any hacks
here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.
I searched and didn't find any previous postings regarding an issue with Parrot and Audi Hands Free (Bluetooth) car kits and the TyTn.
This issue is only with the TyTn and the Wizard devices work fine.
It seems to pair fine with the car kits but 5 minutes into usage...the TyTn turns the bluetooth off on the device.
Then about 1 min later, turns Bluetooth on again. The cycle then begins Off and then On ....
Here's a link on the Parrot forum.
http://www.parrot.biz/forums/english/viewtopic.php?id=2667
I've got the same problem with my Seat Leon (new model) bluetooth carkit !!!
I think it's the same module as in the Audi (all VAG related cars).
It's very irritating !
I hope they will fix it soon....
http://forum.xda-developers.com/viewtopic.php?t=58789&highlight=
:wink:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Pyranwolf said:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Click to expand...
Click to collapse
I'm going to try this !
I hope that it works.
Thanks anyway.
What kind of Leon do you have ?
I've got an A6 with BT kit and am having this problem. I cannot make/receive a call whilst running my BT GPS device & TomTom, although from reading this the issue may be the Audi kit anyhow.
Are there any fixes available - be it HTC or Audi? Or are there any work-arounds, such as add-on software for the TyTN??
Please help - it is driving me mad. Spoiling what is otherwise a great piece of kit.
I have been having this exact problem with my Audi A4 with Audi Bluetooth.
I did wonder if it was in some way connected with the phone going into sleepy mode as it is being powered by the phone battery.
Also, the bluetooth stops responding after 5-10 minutes, but if I am continously using the phone, it seems to be ok.
Therefore, I think I need to buy an in car charger, and see what happens...
Has anybody else tried this that can confirm it works?
Markee
Just a quick note to Paul_o
My Audi A4 / SPV M3100 / Tom Tom / Bluetooth GPS work fine together.
If I am in Tom Tom, and get an incoming call, the little call window pops up over Tom Tom, Tom Tom carries on and the phone audio is routed through the speakers - the only irritating thing is that the Tom Tom lady keeps interrupting... :wink:
Mark
Hi,
I'm using Vario 2 with Audi Bluetooth and also having the BT ON - BT OFF issues.
These are my findings.
- Without JETWARE software:
- BT goes ON and OFF in the car regardless of the VARIO 2 being on or stand-by, or the phone being battery powered or connected to the car.
- Once a conversation is started the BT connection seems to be remain ON.
- With JETWARE software
- If I leave the screen always on the BT connection stays always ON. Only backlight automatic switch-off is selected
- I have tried several screen toggle programs (which claim that they only power down the screen) but the BT goes OFF in the car after a few minutes.
I'm happy to test any other proposal.
Cheers,
C
What version of JetWare are you running, they have a beta which has settings for the Audi kit, this may help, there is also a registry setting that is meant to change the power settings when bt is connected. An extract from an email conversation with Jetware...
We have also addressed the power issue, but this fix requires a registry change. Please create a DWORD registry value in HKLM\Software\JETware\AGExt named InSessionPower with a value of 0 (valid values are 0-4, with lower values indicating greater power availability). This will tell the OS that the Bluetooth device should stay at full power while it is in a Hands-free session.
Not sure if this will help, my Hermes is ariving on Monday, I'm was hoping that all the problems i've had with my magicain and the audi kit would go away with the Hermes, but maybe not.
Give the key a go and let me know
Hi dh,
thanks for your reply.
I haven't installed the Beta version yet. However I have changed the registry setting and will test first thing tomorrow. If this doesn't fix the problem I will try the Beta version with the Audi setting.
I'll keep you posted.
Cheers,
Carles
Hi dh,
I have tested the two proposals (Change in the registry and the Beta version + Audi settings) without much luck. The BT connection with the car keeps going ON and OFF when the phone is running on battery.
Have you got your Hermes? any luck?
Thanks,
Carles
Got my Hermes (Orange M3100) a couple of days ago. I've installed the JetWare extention, and without the InSessionPower set the connection is dropped. So far with the setting applied it has stayed connected. I have had other problems like not being able to make calls etc, which is a bit of a issue. I need to do some more testing, as i've been messing with the phone a bit.
I'll update here in a couple of days
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Hi dh,
You will see from my previous postings I have had the same problems too.
It should be noted, though, that the Vario (wizard) worked flawlessly with the Audi A4 Bluetooth without Jetware software.
Has anybody been able to prove there is no problems if the phone (SPVM3100) is powered whilst in the car?
Cheers
Mark
I have a factory fitted hands free system in my Vauxhall. Every other phone you can think of works with it...EXCEPT my XDA mini. It seems to pair up, but there is no signal showing from the carkit. It might work for a minute and then it drops out. Is it the XDA or Vauxhall that's at fault? It seems that nobody knows the answer and I paid serious money for this bit of car kit. I like the phone, it really is annoying. I have tried another XDA mini as well and that doesn't work either. Does anybody else have a Vauxhall with the same built-in system and not connecting?
Markee
I've had the phone plugged in without the registry entry and it seemed to be ok. If I can get to a stage of a working solution i'll test again without the registry entry and with external power.
dh said:
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Click to expand...
Click to collapse
I'm guessing that since they went from BT1.1 to BT2.0 they had to make a new stack.
My Wizard worked PERFECTLY on my Parrot, my TyTN is almost useless on it.
you make a very good point ScottC, that'll be what it is.
Just driven home and could not make a single call with Jetware installed. Removed it and i could at least make a call, but i didn't get any status info or phone book. I didn't get a chance to leave it connected without Jetware for longer enough to see if it disconnected without external power, i imagine it will. I will test some more later/tomorrow. I'll also send an email to Jetware to see what there thoughts are regarding bt v2.0 and their product
Hello,
I have an Audi A3 with the factory fitted Phone kit but without the Audi Craddle so I'm using the Bluetooth connection.
I have tried the Vario (Wizard/QTEK 9100) and Vario 2 (Hermes/TyTN) and had similar problems with the two of them. Once the connection is stablished I can make and receive calls without problems. The issue is that the BT connection goes ON and OFF without an apparent reason.
The only thing I have seen is that when the Vario is kept on (only the backlight is off) the BT connection normally stays ON, regardless of the phone being powered or not.
I have tried Jetware, the Beta version, the registry entry, programs to switch off the screen...but haven't seen any real difference.
I have bought a bluetooth USB stick and will do some test at home to see if the problem is with the car or the phone.
I called T-mobile and they said it was a faulty phone, but I don't think so.
Keep the postings, we might end up finding a solution
Cheers
C
Try upgrade the BT software. I had the same problem after that i upgraded de Parrot software. Now i have the version 4.16
hi.. i hve a skoda, octavia 2, it has factory installed bluetooth car kit, i can easily connect my Herms , but it keeps disconnecting and reconnecting every few minutes, I tried to upgared to WM6 and its same, I cange my bluetooth control unit at Skoda , and its same. the car kit works fine on any other phones like Nokia or SE. the problem is only with HTC devices. any idea ?
not a single reply !!!
This is a common problem with the TyTn, there are plenty of other threads here with exactly the same problem. I have a Parrot C3000 Evolution car kit and am using a LVSW WM6 ROM (see sig) which works most of the time (better than other ROMs in my experience) - although I experience the following all the time;
Bluetooth turns itself off (on the TyTn)
Bluetooth is on, but the phone won't connect to the car kit
Connection to the car kit gets lost after making a call
Connection to the car kit gets lost when dialling a number
In most cases going to connection manager and turning bluetooth off then on usually works, sometimes (rarely) I have to soft reset the phone and once in a while I have to soft reset the phone and the car(!). When it does all connect it works very well, I also use MS Voice Command and with the various fixes applied I get announcements, voice dialing etc. all working perfectly.
My problems with bluetooth are limited to the car kit though, I also have a TomTom bluetooth GPS dongle which works perfect all the time.
thanks forza
thanks a lot, at least I don't feel lonley with my problem.
i found this, which works great with my car kit.
www.jetwaremobile.com it costs, but there is a 30 day trial to see if it will work with your car kit.
m15chief said:
i found this, which works great with my car kit.
www.jetwaremobile.com it costs, but there is a 30 day trial to see if it will work with your car kit.
Click to expand...
Click to collapse
can you please advise how to setup the jetware ??
forza said:
This is a common problem with the TyTn, there are plenty of other threads here with exactly the same problem. I have a Parrot C3000 Evolution car kit and am using a LVSW WM6 ROM (see sig) which works most of the time (better than other ROMs in my experience) - although I experience the following all the time;
Bluetooth turns itself off (on the TyTn)
Bluetooth is on, but the phone won't connect to the car kit
Connection to the car kit gets lost after making a call
Connection to the car kit gets lost when dialling a number
In most cases going to connection manager and turning bluetooth off then on usually works, sometimes (rarely) I have to soft reset the phone and once in a while I have to soft reset the phone and the car(!). When it does all connect it works very well, I also use MS Voice Command and with the various fixes applied I get announcements, voice dialing etc. all working perfectly.
My problems with bluetooth are limited to the car kit though, I also have a TomTom bluetooth GPS dongle which works perfect all the time.
Click to expand...
Click to collapse
I have found that my 3200LS Color works great as long as I have unlocked my phone BEFORE turning ignition on. Have you updated your Parot firmware to latest version?
timbouk said:
I have found that my 3200LS Color works great as long as I have unlocked my phone BEFORE turning ignition on. Have you updated your Parot firmware to latest version?
Click to expand...
Click to collapse
Firmware is the latest version for my device, but will try unlocking as you suggest and see how that goes, thanks for the tip.
parrot ck3100 and spv m3100 with wm6 dutty v2... it works perfect... i had black 3.0.1... it all went well untill a call in or out was made... but with dutty v2 it is al perfect... i am amezed myself when i see all the problems others have...
I have a problem where my HD2 does not work properly with my Land Rover Freelander 2 in-built bluetooth car kit.
The HD2 pairs with the car and I can search my phone book, see my last dialled number, I can even dial a number, BUT, the phone does not connect properly - the car radio should cut out and phone audio come through the car speakers, but instead the radio just continues to play. And shortly after the call is connected to the other party the line is terminated.
My Nokia phone works perfectly with my car, but this phone does not. Even my Sony Ericsson Xperia X1 did not for properly with the Freelander 2.
I did manage to make one successful call, but after I stopped and restarted the car, the problem returned!! Arghhhhhhhhhhhhhhh!
So, does any one know of a fix? Surely hands free/car kit is a standard?
Help!
same problem here. i have a bluetooth car stereo. Always worked fine with my previous HTC's. But now with the HD2 i get the exact same problems as you... I think it's software bug. i have rom version 1.43.404.1 NLD
i hope this gets sorted out cause i use bluetooth audio streaming a lot in the car....same for handsfree calling
Paired it with my Pioneer FH-P80BT on my way to sell my 3GS and recieved a call. Got the same issue as described above - just a bug i presume.
I'm experiancing similar problems. All works fine (incoming call's or outgoing call's) but they get disconnected randomly it seems. I'm using a JVX NX7000 by the way. No problem with my iPhone. Hope they fix it soon!
I tested it with my BMW Idrive last night which is notoriously difficult and it worked fine, I was really surprised tbh! But was able to recieve and make calls, the stereo cut out and could see the phone book too. With my N82 i was only ever able to make/receive calls.
Same problem - Jaguar XF - it docks ok but I have to initiate calls from car (vs phone). Just some weirdness going on...
glenner05 said:
same problem here. i have a bluetooth car stereo. Always worked fine with my previous HTC's. But now with the HD2 i get the exact same problems as you... I think it's software bug. i have rom version 1.43.404.1 NLD
i hope this gets sorted out cause i use bluetooth audio streaming a lot in the car....same for handsfree calling
Click to expand...
Click to collapse
Mercedes brutality
I have a new Mercedes C, and when the HD2 is connected over bluetooth I get an extremely loud, strange ringtone when receiving a call. It is so loud it could really make your shoes go off.
Also it is none of the ringtones available to choose from, inside the phone - it sounds more like a BIOS beep from a PC and hits me while the normal ringtone is playing as well.
It definitely comes from the phone, not from the car stereo. I have not figured out how to resolve this, I think it is outright dangerous for unprepared drivers.
I have a Nissan Pathfinder; it paired ok, and dials from the Pathy without probs. Ringtone is ok too. Sound quality seems better than my old Tytn so all in all v happy.
Doesn't stream music, but that's Nissan's fault, not HTC.
Works fine with the Ford BT system in the Ford Focus (2009).
HTC HD2 Pairing with a Freelander 2 - SUCESS!!!
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone.
Hope this helps everyone.
graemenwallace said:
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone.
Hope this helps everyone.
Click to expand...
Click to collapse
Hello i have same problem with my BMW X5. Can you explain better your steps ?
graemenwallace said:
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone.
Hope this helps everyone.
Click to expand...
Click to collapse
Interesting, I have a similar problem with my 2009 BMW 3 I explain here (sorry I posted before discovering this thread) and I'll try your registry tweak.
But you say that it is "a known change" to the HD2, could you tell us where you saw it ? Is there another discussion about the BT stack somewhere or more generaly about the Widcomm implementation in the HD2 ?
The HD2 being so recent and in short supply, I'm a bit surprised something like that is "well known"
Thanks for your help.
It works !
graemenwallace, I just tried after applying your tweak and... OMG, this is AWSOME man, it just WORKS !
I still just have one gripe though, it seems that the car doesn't always receive the RF level correctly at the first connection. Sometimes it sees the phone as having no carrier at all (no bars in the RX level display), preventing the car to make any calls, but as soon as I receive a call, the level resets to full bars and I can pick the call and make calls myself after that.
When the first call comes in, I can see the display with no bars and a "?" appearing on top of it for a short time before it becomes full bars.
So there is still some compatibility problems, but at least now I can pick-up incoming calls without risking my life.
So I suppose you are a potential life saver then
Thanks mate,
Yves.
Bluetooth is working YES with JVC KD-AVX44 ADV49
After the registry tweak from graemenwallace the bluetooth connection is working properly with my car radio (JVC KD-AVX44/KD-ADV49).
The phone functions ok now (incoming & outgoing calls) Also the AD2P connection is super (very good sound)
Also the ID3 tags are functioning (didn't function with the X1 Xperia)
I see the track title now into the JVC display
Skipping etc. all is functioning. I will tell HTC about it because I have a ticket running for this issue. I think they have to solve this issue
Big thanks for this trick
By doing a little search on the net, it seems like graemenwallace suggested that this problem is not new with smartphones that identify themselves as such.
The tweak above forces the BT stack of the phone to identify itself as a standard phone instead of a smartphone.
What's puzzling is that my BMW handsfree worked with other smartphones so far, including the iphone.
Anyway, it's ok now, but I wonder what bad press this will cause to HTC.
The majority of the users are unaware of this kind of wizardry and this justs adds up to the long list of bugs of the HD2.
When I first got the phone a few days ago I was rapidly convinced to return it immediatly as it's fancy interface wasn't enough to overcome all the shortcomings. It was plain unusable as a business phone.
Now after applying most of the tweaks, it begins to show potential, but HTC really has to work on the problems we can't fix by tweaking the registry.
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
jah said:
Works fine with the Ford BT system in the Ford Focus (2009).
Click to expand...
Click to collapse
Does your Ford system have the Bluetooth audio choice?
I get my Ford Focus changed every six months coz i'm a driving instructor and it comes as part of the deal.
On my last Ford Focus my htc tytn 2 connected ok and I could make and receive calls ok.
However, when the new car was delivered the Ford system had bluetooth audio choice and ipod integration which the other one didn't.
Now my htc tytn 2 didn't connect very well at all.
Now with my HD2 it does connect only if I have the bluetooth audio profile selected.
But now the music player keeps appearing and wants to play music all the time. If I pause the music on the phone it just starts replaying.
Anyway I will try the registry tweak in this thread and hopefully that will solve the problem.
Paul.
Jolig said:
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
Click to expand...
Click to collapse
I have the same problem. I`ll try to pair my HD2 with MB C-klass using SAP but i can`t get them connected it seems like a SAP adaptor can`t activate a PIN input window on HD2 (i guess). With other phones it works perfect (tryed with Nokia 5800, 6500).
Shark_Abuser said:
I have a new Mercedes C, and when the HD2 is connected over bluetooth I get an extremely loud, strange ringtone when receiving a call. It is so loud it could really make your shoes go off.
Also it is none of the ringtones available to choose from, inside the phone - it sounds more like a BIOS beep from a PC and hits me while the normal ringtone is playing as well.
It definitely comes from the phone, not from the car stereo. I have not figured out how to resolve this, I think it is outright dangerous for unprepared drivers.
Click to expand...
Click to collapse
could you pls describe, how did get them paired? when i try to pair them, i see the device`s id, try to "call" it, see pin code and after that i hear the descending tone. and it nothing occurs. SAP is enabled, device is discoverable, what else? Any idea?
Jolig said:
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
Click to expand...
Click to collapse
I feel your pain, my wife has a GolfPlus and the rSAP instalation is crap.
It's overly expensive and useless if you don't have one of the few phones compatible with it.
Unfortunately, many customers are falling in this trap, thinking it is a standard handsfree, but it is not, it is a full GSM build-in which only access your phone SIM card to log into the network and download your contacts.
In the case of my wife, the dealer was honest and clearly stated that it was a mistake to order this option.
The only problem is that he had no other alternative than proposing an Parrot retrofit which wasn't really an option for me as it wasn't integrated in the car and certainly not in the navigation system.
But internet is your friend and the solution is quite simple, the Kufatec kit.
This is brilliant, it is a small box that connects to the CAN bus of many german cars and integrates perfectly into existing navigators, it uses the steering wheels command buttons and so on.
It is much better (more functions) than original BT options, is tailored to each brand so that the displays are in the same style as the original ones etc.
More interesting, it is field upgradable (just a laptop with BT) so that it is potentialy compatible with anything existing or not yet.
And it only costs a fraction of this crappy rSAP option.
In your case, the good news is that it can simply replace your actual rSAP kit for a minimal installation fee. (the CAN bus has to be reprogramed however, so professional instalation needed)
There is another solution: to replace the unit you have (it is situated under the driver's seat) by a skoda unit. This unit has the same connector but is simple handsfree instead of rSAP.
Hope this helps.