I seem to remember seeing a reference to a registry "fix" which allowed the voice instructions from Tomtom Navigator to be routed through a BT headset (on the Blue Angel).
Questions - has anyone managed to find the fix and try it out? Can this be done?
Such a fix would do away with the need for an amplified car cradle - and all the associated problems (radio interference, compatability, etc.)
Does anyone out there have the "Holy Grail" of fixes??
Update - Found this thread on another site:
http://www.modaco.com/I_have_found_the_Answer_play_music_through_your_BT_Headset-t116898.html
[email protected]
Related
:? :? :? Just a notification of some strange happenings with bluetooth handsfree -
I have been having problems with connecting the bluetooth handsfree Earpiece since installing TT6 - have tried uninstalling it, and then bluetooth handsfree works fine - it also works fine with TT5.21. - reinstalled TT6 and managed (with help) to get it all working from the 512MB SD card ( just 2 main folders on there:- GB plus Western Europe main roads map & Program Files with everything else in there),
everything was working Ok until I tried to connect to tomtom for a traffic update via GPRS, - I kept getting a message saying couldn't connect to server and to check GPRS settings on device or soft reset, which i did and re inserted all the GPRS settings.
Then I could connect via GPRS to get traffic updates - but it was impossible to connect the bluetooth handsfree again. Strange ain't it !!
I don't have any problems with the bluetooth GPS which is a Globalsat 339.
Apparently the version of TT6 that is available at the moment is only a pre-release and so has quite a few bugs in it - best to wait until the retail version is available. - when it is working I have found it to be really good - so without the bugs it should be great.
If anybody has any ideas on fixing this problem, let me have your input, i'm willing to give it a go, but i'm not very technical so need simple instructions. :wink: cheers all!
You may want to...
Uninstall your ILLEGAL copy of TomTom. That would solve your problem. Then you can go an PURCHASE a legitimate copy when its released and see how a LEGITIMATE copy works on your 2i instead of using a PIRATED beta version.
It's just a thought but I'm not too bright......
Why???
But the original TT5.21 was also an illegal - cracked copy and it worked on there!
Why pay for it when you can get it for free.
No you're not are you - maybe it's a culture thing!! :wink:
TOM TOM 6 - Bluetooth Headset Problems - SOLVED!!
Sorry to upset Weatheryoko :roll: but i think i've solved the connection problem(with help from anonymous) :wink: I Hope this helps someone else with similar problems. Downloaded Broadcom 3900 cab from wiki site/Blue Angel, to overwrite files already installed on my XDA11i - in case any were corrupt, this didn't make any difference. Then downloaded A2DP cab from Alpine Upgrading forum - put on to SD card - run it on XDA - soft reset - set up pairing with Headset - at first didn't seem to work but looked in active connections and icon was there tapped status and it was connected - icon showing on top bar, tried turning on and off few times - made phone call - started up tomtom 6 - all seems to be working ok. I haven't tried another soft reset yet as that was where the trouble started before - so far so good - I now have a fully working XDA11i with tomtom 6, all the maps and whistles and bells and connectivity to my BT Headset :lol: I hope this helps if you are having bluetooth headset problems, try A2DP. PLEASE DO NOT ASK ME FOR TOMTOM 6 LINKS THEY ARE OUT THERE - SEEK AND YOU SHALL FIND!
Cheers all - pistebeast
The various WM6 version threads have become cluttered so forgive me for starting a new thread. Does anyone know of a way to check bluetooth stack versions on these various builds of WM6? For the most part bluetooth in WM6 is an improvement over WM5 save for the use of my HF850 car kit by motorola....it'll bond, it'll trigger voice command (but only route it through the phone speaker, not the car kit), and wont carry audio inbound or outbound. It worked relatively properly with WM5, but would drop / reconnect randomly, and of course BT VC didnt work. Any ideas? Anyone else having the same problems with the Hf850 or other bluetooth peripherals? I've read some threads about some Parrot kits now working that didnt before. Any input is of course appreciated.
Hey all,
I've searched on Google & xda-developers forum for a while, but couldn't find anything on this. I've got an EGO Look carkit (http://www.egohandsfree.com/ego-look.html). This carkit has the ability to read messages from a phone over bluetooth, at least that what's stated in the specs of the carkit. I also see this option in the menu of the carkit, but its disabled. This leads me to the conclusion that the carkit thinks that my phone doesn't have the right bluetooth-options. I also tried it with a Samsung D600 & Samsung D900, but that didn't show the messages-option enabled either.
I updated the carkit to the most recent firmware, and am running RomeOS V3.1 (http://forum.xda-developers.com/showthread.php?t=406346) on radio 1.65.24.35. I have enabled Remote SIM Access in the bluetooth settings, but to no avail.
Is there anybody that has had a similar problem/feature in their carkit, that have this feature working? If not, can anybody tell me what bluetooth-profile is needed for this functionality?
Thanks in advance,
hawkeye
I have searched the net for a few days now and can't find anything about my
little problem.
I have as a carkit a VDO/DAYTON TR 7327B radio, when I pushed the phone button on this device it is connecting to my Kaiser and starts always dailing the last known number.
Every other bleutooth device is starting the voice dailing.
I have tried several changes in the registery, which I found on this forum but all with no success.
The Dayton has as sevices - Headphone and Stereo, the registery shows in the hardware status that a handsfree is connected and not a Headphone, could this be the problem?
It is not my intention to install another ROM.
Found the problem, the problem is the car radio.
VDO/DAYTON sels this car radio with on the box "handsfree" and yes they
are correct when you only want to answer calls and not when you want to make a call.
So I need a new carkit.
I'm having issues with a bluetooth conflict.
My set up is as follows:
- AT&T Tilt - WM 6.1 stock ROM
- 2009 Toyota Camry XLE V6 paired to the Tilt with Hands free profile
- Motorola S705 paired to the Tilt with Wireless Stereo profile ONLY -- I don't pair with Hands free profile. The S705 is connected to the Camry via an aux connection.
I also have GpsGate running in the tray with a bluetooth GPS receiver, but that seems immaterial to the issues I'm encountering.
When I pair the phone as above, the music from the car speakers skips to the point where it will be inaudible for 2 - 3 seconds per 30 seconds of music...no hissing or popping...just silence. The 2 - 3 second pauses are not regularly distributed.
In order to resolve the issue, I go to bluetooth setup on the Tilt and select the Camry Hands free and select 'Set as Hands Free', which, paradoxically, does exactly the opposite...it disables the pairing with the car (until I restart the car). However, once I do this the Wireless Stereo connection is rock solid. Alas, in this configuration, I can't get dial or hang up, hands free, via the steering wheel buttons.
I'm tending to believe the issue is the Toyota since I can connect a Scala 500 as Hands free without issue when playing music in the car (FYI, at no time do I have both the Toyota hands free connected and Scala 500 powered on at the same time).
I'd love to know:
- How I can confirm the problem is with the Toyota, since it is likely they will simply point to the Tilt or the S705 and claim that it is the culprit? I would like software output that demonstrates the Toyota's bluetooth implementation is ill-behaved.
- If the issue lies with the MS stack instead. My understanding from another site is that the MS stack was hacked to allow A2DP. I wonder if the MS stack is simply performing poorly and the Camry bluetooth setup is simply doing what it ought to do. If I could replace the MS stack with the Widcomm stack, this might allow me to test this premise.
In searching I've found some other threads which deal with Kenwood stereo systems and different symptoms (restarting), so I'm not sure the problem is related
http://forum.xda-developers.com/showthread.php?t=442370
I've also searched and found information on replacing the bluetooth stack. No confirmation in the thread whether this will work with the Tilt
http://forum.xda-developers.com/showthread.php?t=449775
Options i'm considering:
- replace BS stack with Widcomm -- no confirmation on whether it works on Tilt
- installing JETware -- mixed results in other threads, Tilt isn't listed as compatible
- reverting to 6.0 -- mixed results in other threads, don't relish the idea of going backwards (HTCHome via cab, etc.)
Edit: That would be the BT stack, not the BS stack (freudian slip)
Does anyone have any experience with the same problem, suggestions as to what options will likely bear fruit or if there is a simpler option? I'd prefer not to do a hard reset and re-install everything I have on this phone if I can get away with a simple fix.
Thanks.
Im having similar issue
I purchased a new headset for my motorcycle helmet.
I can not get the hands free working..
I have another headset that works with the phone, this ended costing me shipping charges thinking the helmet headset was bad.
I have searched many sites and have come to the conclusion it is the phone.
I have not seen anything that gives me an indication that we will find a fix..