TP2 is paired c Garmin 660. Incoming calls ring once then dumped. Happens occasionally on Pioneer GPS/radio. Is there a fix for this? Thanks
you need to update to the stock 6.5 rom which has bluetooth stackup changes
I have the latest stock rom. ????? next
Thanks
You are out of luck then more than likely. Some hardware seem to only work well with the microsoft bluetooth stackup while the tp2 using the widcomm. You might be able to create a custom rom with the microsoft stackup and see if that helps.
Related
I've got a Bluetooth Car audio in my Toyota from Toyota. But I cannot establish a connection between my PDA (BA) and the car.
I Know there are not all bluetooth profiles installed on the BA.
I'm using WM2003 SE and the Widcomm Stack 1.0.3900.
How can I change/enhance the Bluetooth stack?
Is it working with WM5?
greets
JEKAL
I've the same problems with Ford.
I 've already posted this problem in every forum I know - but hadn't got any answer yet.
Now shouting loud
HI FOLKS, WHO CAN HELP ???? :lol:
Dieter
@dieterpapa
I have a solution which is working for me since last night :!:
I reinstalled the MDA3 from scratch with the latest ROM version (from march this year) and applied the audio gateway patch. :!: :!: :!: Do not restore any Backup made before.
Now it is working :!::!::!:
regards
jekal
Hi jekal,
thanks for the info. Which ROM version are you using ?
To my best knowledge I believe to have the latest version, too.
I did reinstall from scratch in April with the ROM mentioned below.
What's the difference to your version ?
What type of a Ford handsfree device are you using ?
Dieter
Hi dieterpapa
I'm using the same ROM version mentioned in your signature.
Did you apply the audio gateway patch?
Well I am using a Toyota Blutooth car kit, not a Ford.
Regards
Jens
jekal said:
Hi dieterpapa
Did you apply the audio gateway patch?
Click to expand...
Click to collapse
Audio Gateway patch ?
What I still have to apply is: BA_OEM_AudioGW.CAB
Is this the correct patch ?
Dieter
PS: Jens seems quite German/Austrian/Swiss.....
Yup, it is german, but I think we should keep our english for the others.
My patch is called Version 1.33g. Latest file in Cab is from Jan 27th 2005.
If you have this applied I probably cannot be of any further help.
Regards
Jens
did try with ford - doesn`t work. Ford only supports a "handsfree" bluetooth profile - the BA only has "headset".
I`m still trying to get an information how to upgfrade the BA to "handsfree" BT profile.
dieter
Bluetooth & Toyota Prius
I have an XDA 2 (UK - marketed by O2) & have (after 5 months) discovered that Toyota admit to having a problem with bluetooth connectivity for "some models" (three newer phones belonging to garage employees also failed to bond when I took it back after trying to create a bond for a week& these were not PDA phones!).
They tell me that if the bluetooth version I have has two specific files, it SHOULD be possible to connect - the files are HFPv1 M3 Profile & OPP v 1.1 The problem I have is finding out whether I have these files - I have an e-mail in to O2 at the moment & will be happy to let you know what they come up with - from Toyota's guarded reaction the XDA is clearly a "problem" model & what I do not know is what happens if I prove I DO have these files & still can't make a bond!
Toyota say they can't supply a list of compatible phones because "it would soon become obsolete" but technically minded folks might like to know that they say you need Bluetooth 1.1, Hands Free Profile 1.0 & Object Push 1.1
As I could grow old waiting for O2 to get back to me I'm afraid I gave up - if you want the PDA function of the Xda2 & a phone which will bond with the Toyota system, the Orange SPV M600 bonded instantly & seems to work well even near my home where the signal is pretty poor!
dieterpapa said:
Ford only supports a "handsfree" bluetooth profile - the BA only has "headset".
I`m still trying to get an information how to upgfrade the BA to "handsfree" BT profile.
Click to expand...
Click to collapse
Having a similar problem with a US 2006 Acura TL and a Cingular 3125. The phonoe pairs, but only has limited features. Call waiting drops the call and routes the waiting call to voice mail. Most annoying.
I understand that the Cingular ROM build I have *should* be able to support the HFP, but it was not included in the build for some reason.
Looking for a way to push address book, handle call waiting correctly, display battery life and signal strength on car dash display. As far as I can tell, HFP should handle some or all of those.
Any thoughts??
TVBanks98 said:
Having a similar problem with a US 2006 Acura TL and a Cingular 3125. The phonoe pairs, but only has limited features. Call waiting drops the call and routes the waiting call to voice mail. Most annoying.
Click to expand...
Click to collapse
I'm considering purchasing either a 3125 or 8525, but I am very concerned about losing the ability to accept a second call via my Acura TL handsfree system. Almost all of my calling takes place in my car, and this feature is critical to me. Does anyone know if the released Cingular 8525 works with the TL?
Third party fix for some cars
Guys
I came across the following after much searching. It certainly works for me, you may wish to take a closer look at it.
http://www.jetwaremobile.com/bthfx/support.htm
Hello guys,
I am experiencing huge problems with my current ROM and these WM bulides (eg. the Ranju's - v7.4) here.
With my BT software, I am not able to use the "Service discovery" feature on my Qtek without pairing the devices.
Unsless I have with different ROMS, but not with a WM6 Smartphone (Samsung Blackjak) it seams to be a problem with WM Cores.
Can anybody help me out?
johnripper1 said:
Hello guys,
I am experiencing huge problems with my current ROM and these WM bulides (eg. the Ranju's - v7.4) here.
With my BT software, I am not able to use the "Service discovery" feature on my Qtek without pairing the devices.
Unsless I have with different ROMS, but not with a WM6 Smartphone (Samsung Blackjak) it seams to be a problem with WM Cores.
Can anybody help me out?
Click to expand...
Click to collapse
This is an interesting request. I have tried to make my universal work with A2DP using various registry hacks, but I can only get a couple of seconds of sound and then it cuts off. I swear it used to work last summer on a different ROM.
My guess is that changing the core might help.
Anyone can help?
I am not quite sure what my last rom was, but i think it was a 6 Pro Rom and I had the same problems.
YES,have Different Rom
Hi brother there's is a WM6 Roms of UNI with different BT stack,it is use Broadcomm bluetooth stack and work fine on my used,but in first you should know there have some bugs while you are picking up and ending the call with your BT headset's button,you should learn how to use it ,the roms link is
http://forum.xda-developers.com/showthread.php?t=291875 ,it made from helmi_C ,I am very glad to use these rom since i used HP 4150 before and the HP use broadcomm stack,it have great a2DP quailty and can use avrcp profiles. Think it can help you !!
Okay thank you so long.
This BT Stack is avaiable for seperate download as well, but I not sure it if works...
http://forum.xda-developers.com/showthread.php?t=342039
This works flawlessly with 6.0 based ROMs, but with any of the 6.1 flavored ROMs I have tried, the pairing process fails. Is there something fundamentally different between 6.0 and 6.1 in the BT stack that would explain this? Any tweaks you might know of that could fix the problem? Basically, while pairing, the car system sends a "Authorization Unsuccesful" message and the phone rejects the pairing. Because of that I am stuck with 6.0.
I am using my bluetooth car cd player with my Tytn using a 6.1 Dutty's rom. Works perfectly. Try using the april 29 rom just for testing.
i use the rom and radio in my signature and have no problem pairing with car's BT.
No such problem w/ stock 6.1 or Dutty's rom w/ my Jvc BT-1 or Sony Ds-220
No problems with Jabra SP5050 and rom in signature.
ok. it might souns weird but:
I found that paring while your phone is in call (call in progress) will give you better results.
Also, i have seen reports that while phone is in call paring with TomTOM GO will ofer even DUN option while it does not normally offered on majority of WM6.x handsets. (DUN is available on Diamond phones).
I cannot confirm the DUN phenomenon, but paring works def better for me while in call.
I have no logical expanation to this.
Hi,
When using the Polaris with standard Dutch ROM in a Renault Laguna with built-in carkit system, the sound is very crappy. The paring goes fine, but the sound in the car is crap. Moreover, the other side cannot even hear my voice at all. I apllied the 2 hotfixes from HTC e-club, but that didn't help. Is it possible to change the bluetooth stack from MS to Widcomm or something, or is there any other solution?
Any help is surely appreciated!
Wouter
I had the same problem with my Mondeo (2008). I changed rom to WWE 6.1 (PdaViet V23 - at this moment) and problems disappeared. Perfect reception (both ways) and also all contacts visble through car touch screen..
Thanks a lot for your reply. Good to know that that's an option. I'll keep it in mind. However, I'm kind of hoping for a solution that doesn't require using another ROM, for warranty reasons...
The problem was finally solved by a software update on the car, done by the local renault dealer.
Whenever I sync my Touch Cruise in the car (BMW) the interface lags! For example pressing the phone button on the steering wheel takes forever to pull up the phone menu on the car display. Also during a call if I press the hang up button on the steering wheel, it doesn't hang up right away. I have to keep pressing it multiple times. The actual sound quality through the car speakers is fine and the pairing is very quick so no problems there.
Is this a specific problem between the car and the phone? The car handles other bluetooth phones very well, such as the ahem..iPhone. The response when hitting the steering wheel buttons is instantaneous.
I currently have udk Syrius R8 Beta2 with radio 1.59.46.12. I read in one of the other forums on xda that it has something to do with TouchFLO. I disabled the Manila TouchFLO, turned off S2U2, still no luck. Any ideas?
I have similar problems with my XDA Orbit2 with WM6.1 and with my Ignito/Diamond with WM6.1 both with my Peugeot car BT and with Motorola BT headset.
An incoming call sometimes takes 10secs for the audio to be re-routed, PITA
I also found that if I'm running Navigon 6 and an incoming call gets picked up by the car BT then Navigon (or any other GPS app like GPSCycleComputer) gets screwed, the internal GPS gets disconnected.
I'm suspicious that the problem is due to the on chip BT and GPS.
My XDA Orbit (1) with WM6.0 doesn't have the same problem but of course it also has a seperate SirfstarIII GPS.
So, who knows, it could be WM6.1 or it could be the Qualcomm integrated chipset?
I'd like to re-install the original Orbit2 WM6.0 to see if that makes a difference but that's not completely simple as there is no full (official) O2 WM6 file available (AFAIK)
Yeah it's pretty annoying. I assume the udk ROM that I have has all the bluetooth patches, etc. I know other phones don't have this issue, so I'm hesitant to say it's the BMW bluetooth firmware. Something is laggy about the device when paired. I must say though I've never tried pairing it to a BT headset so I wonder what that will be like.
No one else having bluetooth performance issues with their car's built in Bluetooth system?
I have carkit trouble, but don't know why.
My problem is as followed:
I Drive a Renault Scenic with a Carminat Navigation System including Bluetooth Carkit
When I connect my HTC TC Everybody complains that quality is poor. Reception is louzy etc.
When I connect my HTC TD2 the problem dowsn't exist.
When I connect my Samsung Omnia the problem doens't exist ( but other problems in the phone appear)
When I connect my Nokia N73 with the current software I have a lot of problems ( even other then with the HTC )
When I connect my Nokia N73 with an old version of the software I have no problems...
All phones run the stock ROMS ( Windows Mobile 6.1 Pro ) / original Software. I first thought It might be a carkit problem, but as some phones work and others don't I tent to believe that it is a ROM problem (Maybe radio not good)
Is it possible to update the bluetooth driver / firmware?
Problem with HTC TC could be in radio driver.
But since there are problems with other devices, it could be problem with Carminat. You should check with Renault is there software update for it.
But first check if those phones are on Carminat's compatibility list...
The strange thing is that I have the problem with the nokia N73 when the software of the phone is higher then 2.69
According to Renault all Windows Mobile devices are supported / compatible.
I think it is the BT driver or Firmware. But don't know if it is possible to upgrade this to a newer version. Or to test this?
Yes,
My Parrot Mki 9100 works perfectly for phone calls, but doesn't play GPS navigation audio instructions.
Anyone know waht is wrong?
speedyb said:
The strange thing is that I have the problem with the nokia N73 when the software of the phone is higher then 2.69
According to Renault all Windows Mobile devices are supported / compatible.
I think it is the BT driver or Firmware. But don't know if it is possible to upgrade this to a newer version. Or to test this?
Click to expand...
Click to collapse
Have an appointment at the car deakership on Tuesday to see if there is an update or quickfix...
I still suspect the TC though
BT, GPS and GSM are controlled by radio driver.
Please check version, since even stock ROMs use different drivers.
So far, my version is flawless...
Polaris WM 6.1 WWE official (3.13.405.0 WWE 2008-08-21; Radio 1.59.42.15; Protocol 25.85.30.07H)
Click to expand...
Click to collapse
This is the same version I am using....
hi,
I have have quite some problems with BT connection with same radio driver see
http://forum.xda-developers.com/showthread.php?t=570153
I sent it for fixing to the dealer.
Hope a solution.
Went to the car dealer today. They updated the software and modified the microphone volume (lowered it) and the sound quality is improved.
At the car dealer they told me that they have a lot of issues with HTC phones in combination with the different carkits, although the newer phones have less problems. There is a new software upcoming before the end of the year which should solve more problems. but for now the problem is less....
I figured out why (but not the underlying cause) of the sluggishness when the phone is paired to the car. My phone shows very high CPU usage (90%) with services.exe when I look in task manager when the phone is paired. I noticed that using the actual device is sluggish, even just typing up a text. I don't know why that is. The moment I turned off bluetooth, it was back to normal.
Any idea what could be causing that?
Maybe radio driver...
I had such problem when I was on WM 6.0, but it was caused by failing radio chip...