Hi
I just got my new BMW 330 (E90) with Navigation and Bluetooth. I can pair my MDAc but that's it.
When a call comes in, My BMW signals it. Sometimes I can get the call with the button in the steering wheel. Sometimes not. Sometimes I can but the connection breaks down in the middle of the call.
I see the reception of my MDAc in the display and when a call comes I also see the number of the caller.
I cannot make a call (dial out).
I read a lot but did not find a solution yet. Has anyone experience with BMW carkits or any advice what to change in order to get it going. I sort of refuse to have another handy...
BTW I have the latest T-Mobile Update (1.12) but I did not install everything from the extended ROM.
I have exactly the same problem with Audi bluetooth, with my Nokia 6230 works perfectly, with my S100 I have the same problems you have experienced. I have an old ROM 1.06, but I see that even with 1.12 the problems are not solved.
I tell what I tried: I've installed various BT stacks (Toshiba, Widcomm, Bluesoleil also with crack). Toshiba pairs but does not find any service, Widcomm does not run, Bluesoleil does not have the needed profiles.
I have installed the CAB from VCABT project (see the thread in this forum), I can answer from the car I can call using the car voice command but I can't use the S100 buttons.
Hope that somebody could help us.
dgv
fdigianv, have you tried the new A2DP Stereo BT Tool to see if it works better with your Audi.
I just upgraded my JAM to 1.12 and have yet to try it with my Audi A6 4.2 2005 MMI BT System.
I'm tired of waiting for Audi to fix anything. It seems like the only fixes or upgrades they offer come in the form of a new car release.
I like you can call out from the Audi, but those on thger other end of the call complain about sound quality.
I'm getting ready to make a move to the new Treo MS Mobile device, or a smartphone that works better with my Audi.
I spoke to BMW this morning and they claim has more to do with the version of Bluetooth installed on the phone than BMW's implementation of Bluetooth.
BMW supports Bluetooth verson 2 and up.
Related
I have purchased an O2 XDAII in Oz which is loaded with the 1.66 ROM. I have tried connecting two headsets to the phone over bluetooth with many problems.
Both seem to bond ok and work initially but later they fail - the XDAII doesn't respond to anything I press on the headset. Or the XDAII does respond (answer or end call) but no-one can hear me either through the headset or the phone.
Deleting and re-bonding seems to temporarily solve the matter. But if the XDAII goes to sleep and comes back on it stops working. Will also just stop working for no reason after a call or two is made or received.
I have tried installing the bluetooth tools which is cool because the XDAII can recognise some of those extra headset profile functions (like redial) but I still get the same problems as above.
Tried Plantronics M3000 and Motorola HS801
What can I do? Is it this Bluetooth stack problem from MS I have read about? Do I need a ROM upgrade? Do I need Widcomm something installed on the XDA II? I don't know how to do any of these myself. Any kind advice from a pro is appreciated in advance.
When you installed bluetooth tools did you delete any bonding and pairing of devices beforehand? it can make a difference if you havent done this.
Yes. I tried it twice thinking that maybe I might guess a way to make it work.
First I deleted the bonds after installing BT Tools and then rebonded.
Then I deleted the bonds before installing BT Tools and then rebonded.
I spoke to my Telstra dealer again today and they received a list from Brightpoint (a distributor) that matches various headsets against various PDA's available in Oz.
Not all BT headsets will work competently with all PDA's. The M3000 is marked as NOT compatible with the O2 XDA II available in OZ. So was the Motorola too.
I am now using a Hello II headset which so far is fantastic (very small and comfortable to wear) and is working with no modifications to the XDA. I will post back in a week with a fuller review. I'm going to re-install BT tools and see if that make a difference with the available functions.
Anyone else wanting to test these out in Perth, WA, (Australia) - they are available from Communications Plus.
Help
I can stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
Help
how can I stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
I had a problem with my Plantronics M3000 too so I called Plantronics themselves who said that the problem is with the phone, not the headset. It's a compatibility issue with the software.
Unlikely to be any fix, at least not in the near future.
Hi. I have a MDA Vario, ALK Co-Pilot with Bluetooth GPS & a Pama "Plug'n'Go 4" Bluetooth Car kit.
I can use the Vario and the Car Kit together with out a problem and I can use the Vario and the Sat Nav with out a problem, but I cannot use them both together. When you run the Co-Pilot software on the phone with the car kit paired it disconnects the car kit, then the car kit re-connects itself, then it disconnects etc.......
I have looked in the bluetooth pairng for the Car kit and their are no settings I can change, and the Co-Pilot software talks directly to the Bluetooth GPS receiver and thir are no settings that can be changed in that either. I am stuck. Co-Pilot say its the Car kit and Pama say it is the Sat Nav, and the guy in the T-Mobile shop says it could be the Windows Mobile 5.
Does anyone know if TomTom or any other Sat Nav vendor do a demo version for Windows Mobile 5. That way I can see if it is a Co-Pilot issue or not, I know people with Sat Nav systems but none of them are for Windows Mobile. I also know a couple of people who use bluetooth headsets but not car kits, I cannot get on with headsets, after about half an hour I want to throw it out of the car window. I have asked if I could borrow a car kit from the T-Mobile shop, but they said no!!
I downloaded and installed the latest rom from T-Mobile last night, it was only released on the 19/06/2006, but it did not fix any thing.
Regards
Andrew
Hi sysmanuk i have got copilot and vario and hve used it fine on a parrot 3100 i also used tomtom again no problems this was on the old tmobile rom not used it on new rom but it sounds like it is the pama device causing the problem can you upgrade its firmware if so try that
Hi ya,
I can confirm that i use tomtom, a parrot ck3000 and a holox bt-321 with no problems. They all stay paired.
I can either turn the BT on before i get in the car and thus just have the ck3000 pair, or i can have BT turned on paired up with the ck3000 then start Tomtom and have no issues. Or i can just start tomtom with turns the BT on and then this auto pairs with the GPS unit and the ck3000.
I hope this givess you some help in to finding out what is causing the issue.
I had this issue, using the T-mobile MDA Vario release rom, a Parrot ck3100 & tomtom5.21 with a bluetooth rikaline gps.
If both used together, the car kit would randomly disconnect bluetooth, and the gps would also randomly diconnect.
Used seperately they were fine.
I went back to using the Vario with the Parrot, and my old Ipaq for Tomtom/GPS.
I have now updated to the Mr Clean rom, and plan on retesting once I reload all the software.
I've just got a Orange SPV M3100 and paired it with my BMW OEM bluetooth carkit, all goes fine and paired no problems.
It manages to connect to the phone and display contact details on the radio display and make calls.
But leaving it a couple of hours and coming back, the phone will not reconnect back to the car. I've tried resetting the phone without success.
The only way to get the connection back is to re-pair the devices.
I had a Imate Jamin before and it worked without a problem, connects every time.
Is anyone else experiencing problems with their carkits?
Do you think the problem is specific to the Orange ROM, would flashing it to a Imate or TyTN ROM help or resolve the problem?
Any advice would be greatly appricated.
Hi, I got a problem similar like yours...
I´m from Spain and I have an ´06 Opel Astra(Vauxhall in UK) with the BT handsfree carkit from factory.
If I make a hard reset to my Vodafone S200 (Orange SPV M600) and leave the machine with the factory settings it works fine with the carkit, but it recognice the carkit like a headset handsfree. But if i restore a back up with the TomTom 6 installed... wow, then start the problems... the handsfree conect with the S200 but after a few seconds the connection is over...
I don´t know if have you got some kind of navigation system, but in my case the problems starts when I install the TomTom... I´m sure it changes some drivers of the BT and this makes the don´t works propertly.
I don´t know what to do...
PArrot Car Kit
I have the same problem with Parrot Car Kit and I have the latest TYTYN ROM
2006 BMW 3-Series Bluetooth
My car doesn't have bluetooth, but I had a loaner car while my car was under the knife. The loaner car was a 2006 3-series w/ Bluetooth. The first pair was perfect, but after a few hours.. What a POS.
I have the latest ROM on my phone, and that didn't make a difference.
No issues on my 5 series, but I have one of the first ULF modules in mine.
From reading TyTN Bluetooth issues around the net and on this forum, it seems to be an issue with the TyTN having some kind of power save mode which turns the bluetooth off after some time.
Kinda stupid, anyone know some registry crack to turn any power saving off?
I have a Parrot CK3100 in a BMW and a brand new SPV M3100. All was working well with my M600 but as soon as I swapped the phone for the M3100 last week I've had problems as described by the OP. Bluetooth keeps switching itself off on the SPV. It works well enough to start with and then suddenly it disconnects. Re-pairing works and it's worth going to bluetooth settings and turning it back on again before you try re-pairing.
Surely there must be an easy fix for this problem - I'm just really pleased I'm not the only one with this fault.
............
Your all quite lucky it works at all..mine doesn't do anything
My Ford Fiesta has been waiting for an 'software upgrade' since October !!
Promised it would be available before Xmas but nothing happened.
lifterus said:
Try and replicate the problem with a different phone if possible. One that BMW supports. If can replicate it, then they'll update the firmware on the BT unit in the car. This happened to me. But I had to prove my case using my girlfriend's RAZR before they'd listen and stop blaming my phone as the cause.
Click to expand...
Click to collapse
I dont think it is a problem with the BMW carkit as it worked fine with my SPV M600 (Prophet)
I got my S200 back from a repair and it was also upgraded form G3 to G4.
Everything seems to work fine, except my Jabra BT500 head set. After pairing with my S200 I got a very cracking sound.
So I checked my Jabra with another mobile phone and it worked very well. I checked another head set with my S200 and again a cracking sound.
Does anybody knows how to solve this or do I have to return my S200 again for repair?
Hi, I have excatly the same problem, it also occurs with the bluetoothof my car...anyone can help us?
I have returned my S200 to QTEK today in order to have it repaired (again).
I have tested it (in my car) with 2 other Bluetooth headsets and there was no problem. There was also no problem when I tested my own headset on another phone. So this proves that my S200 has some kind of defect.
The sound is very crappy ?
Or is the soud quite ok, but experiencing high frequency glitches, kind of metallic parasits?
Because in that case, there is nothing to do, It's due to the MS bleutooth stack which has a very poor encoding librairy... and since there is no widcomm stack for S200 (and some other qtek too, a lot of people is yet trying to malke it work), then evey bleutooth headset will have bad sound in A2DP with the S200 :'(
One of the main reasons why I want to change for a widcomm stacked pocketPC (shame on MS!!!!!!!!!!)
For me, the quality is very bad. At the beginig I use it only on my car and it was working perfectly, since I try to connect to the bluetooth headset or to my computer the sounds became very very crappy. I have Dopo ROM, which rom do you have? what ROM do you advise? Thank you
I have tried the LVSW, Jester and shipped ROMS and all these ROMS have the same problem. So I think that it is not related to the ROM but due to bad hardware components.
it's strange because it was working for me before I use other bluetooth device. I will try to upgrade the rom to the official QTEK ROM
I have the same problem. As if the bluetooth signal were cut per moment.
it's not linked to roms, but to bluetooth stack, so since the bt stack is updated (but I doubt it), changing roms won't help
I could fix it, I update the ROM, delete all pairaing on my cars... I change the "hsotname" of my QTEK on "settings - Owner information" I recreate the pair and it works fine on my car, now crappy sound anymore. Just to test it again, I try to pair my "fujitsu laptop" to my qtek, since I did it, the sound is again very crappy. So I will flash again and pair it only with my car. If I return it to Qtek it takes 1 months... If someone can fix this that would be great.
I'm hoping someone is having the same experiences or can help recommend a solution.
I have trinity (Obviosuly) with the latest WM6 rom from the Manufacturer, with Radio 1.50.
I use a TomTom One v2 (with bluetooth), and a Parrot 3200ls.
The TomTom has the latest firmware, as does the Parrot.
When trying to get traffic updates to the tomtom thorugh my trinity, the connction works the first time, but switch off both the tomtom and the trinity, the connection never works again and has to be re-setup.
The Parrot will connect to the phone, but sometimes will not connect at all until i reset the trinity, when it does connect sometimes the sound and mic wont be routed to the car kit and you have top physically pick up the phone , not a good idea in communist Great Britain when your driving!
Ive tried different ROMS, I even tried downgrading my radio to 1.45 with no success.
The trinity is a great device but not being able to use the bluetooth car kit safely, and the tomtom plus services, is seriously making me consider going back to my SE k610, which I really dont want to do but I know works flawlessly.
Thanks in advance.
Craig f said:
I'm hoping someone is having the same experiences or can help recommend a solution.
I have trinity (Obviosuly) with the latest WM6 rom from the Manufacturer, with Radio 1.50.
I use a TomTom One v2 (with bluetooth), and a Parrot 3200ls.
The TomTom has the latest firmware, as does the Parrot.
When trying to get traffic updates to the tomtom thorugh my trinity, the connction works the first time, but switch off both the tomtom and the trinity, the connection never works again and has to be re-setup.
The Parrot will connect to the phone, but sometimes will not connect at all until i reset the trinity, when it does connect sometimes the sound and mic wont be routed to the car kit and you have top physically pick up the phone , not a good idea in communist Great Britain when your driving!
Ive tried different ROMS, I even tried downgrading my radio to 1.45 with no success.
The trinity is a great device but not being able to use the bluetooth car kit safely, and the tomtom plus services, is seriously making me consider going back to my SE k610, which I really dont want to do but I know works flawlessly.
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
I havebeen struggling with issues on my P3600i (trinity) and Parrot 3200 LS. It seems parrot have issues with WM6. The problems I was facing was reset of parrot during call, random divert of calls through handset, I answr sometimes and have to turn off handsfree on the call menu on my phone so I can hear the caller through my handset.
Today I downloaded the latest software for the parrot and uploaded it to the car kit via bluetooth on my laptop. There is a new feature in the paired devices list of "Forced Connection". I used that and low and behold my issues apparently have stopped. I noticed that my phone book isnt synchronising but the fact that I can actually use the car kit is fantastic!!!! I have been dealing with these issues for over 7 months!
Update to the latest version and see if this fixes it.!.!.!