Related
Hello people,
Does anyone know if the Mda Compact is compatible with the Nokia CK1W Car Kit or if there is a bluetooth update to fix this problem. I have tried several times to connect both units, each time the phone recognizes the car kit and lets me connect but a few seconds after connecting it disconnects.
Any help would be much appreciated.
Thanks
Try upgrading the ROM of your MDAc.
I don't have any problems with my MDAc and the Nokia CK-1W (tested with 1.12 and 1.13 ROM).
Out of interest, does the remote end complain about copious amounts of feedback? My ck-1w connects fine, its the echo at the remote end thats awful. Ive seen a lot of other people with the same issue in forums on the net. Its not related to mic placement, just some incompatibility with the magician (ie. People can use Nokia mobiles fine with their car kits, only the magician has the feedback)
scenty said:
Out of interest, does the remote end complain about copious amounts of feedback? My ck-1w connects fine, its the echo at the remote end thats awful. Ive seen a lot of other people with the same issue in forums on the net. Its not related to mic placement, just some incompatibility with the magician (ie. People can use Nokia mobiles fine with their car kits, only the magician has the feedback)
Click to expand...
Click to collapse
Yes same problem with the nokia ck-7w car kit.
I was hopeing that after I upgraded my ROM that the reported remote end echo would disappear. Alas no. No problem with using Nokia phones via bluetooth to the car kit, or my Compact with a bluetooth headset.
Very very annoying :evil:
Oh, really?
Yes, there is a considerable amount of echo, I cannot deny. :wink:
Anyone know where I can download the updated ROM and Radio. I am on T-mobile so I am unable to register on imate jams website to get access to these files. I currently I have version:
ROM version 1.12.00 WWE
ROM DATE 05/28/05
RADIO VERSION 1.12.00
PROTOCOL VERSION 1337.42
EXT ROM VERSION 1.12.152 WWE
Thanks
Hey guys,
I have updated my ROM to
ROM version 1.13.00 wwe
RADIO VERSION 1.12.00
PROTOCOL VERSION 1337.42
EXT ROM VERSION 1.13.*** wwe
which also has the larger memory but my bluetooth is still refusing to connect to my nokia in car kit. I have noticed that after the upgrade my radio version has not updated. Could it be this that needs updating. If so,any one know where I can download from.
radio 1.13
Is to be found here http://forum.xda-developers.com/viewtopic.php?t=32274&start=0
Not sure that it is actually newer, you can always try
Regards, M
Dont bother. The nokia carkits (BT) are not usefull with Magicians. De receiver gets an echo of his own voice all the time. I have the CK7W and it is doing the same.
Hallo experts,
I am a newbie to this forum and a greenhorn concerning programming. But I bought the HTC Kaiser in order to get it running with my Mercedes Bluetooth SAP V2 Cradle (Article number Mercedes Benz: A204 820 0535). Unfortunately, the cradle does not work with the Kaiser. Do you know any solution (another ROM? for example) that may change the situation?
Thank you all very much for your appreciated help!
doc holiday
HTC Kaiser
Don't have a Merc....One day maybe. Had similar problems as you with a Parrot bluetooth car kit though.
Found that Dutty 29 Apr, and Laurentius' latest roms work completely with it though. Other roms may work too (don't want to tread on anybody's toes).
Some of the older cooked roms would either not route the audio properly, would only work for one call then stop routing, etc.
The latest rom I have tried is PDAViet'. Very fast in some aspects, Very slow at others. The Parrot car kit has real problems working with this rom.
Basically, try a Dutty (latest), or the latest Laurentius and I reckon everything will be fine.
Thank you very much Blartiartfast for you rapid and competent reply!
So I will try to change the Rom to the one's you mentioned and will report the result
Have a good time m8
doc holiday
HTC Kaiser
i've had problems with both a hermes and kaiser connecting up to the mercs bluetooth.
What i found i had to do was to get both the merc and the kaiser to search and connect to each other at exactly the same time. I found that if you made the merc search for the phone it wouldn't auth, and vice versa. But oddly making both connect at the same time worked.
Hope this helps.
carkit
hello,
i have a bmw , and with the Laurentius_26 rom (http://forum.xda-developers.com/showthread.php?t=389915) , my bluetooth connection works as a charm.
grtz
Thanks both of you ghostie and BeeCee
I will try it
doc holiday
HTC Kaiser
BeeeCeee said:
hello,
i have a bmw , and with the Laurentius_26 rom (http://forum.xda-developers.com/showthread.php?t=389915) , my bluetooth connection works as a charm.
grtz
Click to expand...
Click to collapse
Agreed! Laurentius_26's latest ROM works very with my ML63 AMG. Sometimes it randomly disconnects, but what Phone/Rom isnt going to?
ghostie said:
i've had problems with both a hermes and kaiser connecting up to the mercs bluetooth.
What i found i had to do was to get both the merc and the kaiser to search and connect to each other at exactly the same time. I found that if you made the merc search for the phone it wouldn't auth, and vice versa. But oddly making both connect at the same time worked.
Hope this helps.
Click to expand...
Click to collapse
This approach has worked for me several times as well. I use Dutty's April 29th ROM and have found stability to be fantastic. I haven't dropped a Bluetooth connection yet. Good luck.
T
Many thanks to all of you folks
doc holiday
HTC Kaiser
Problems always persist with HTC Kaiser and MB bluetooth SAP
As stated in the replies to my question (Thanks to all of those who answered), I tried the last Dutty ROM and the last Laurentius ROM - but in no way I have been able to establish an adequate bluetooth SAP connection between my Kaiser and the mercedes benz bluetooth sap v2 cradle (I provide the original art. no A204 820 0535 in order to be more precise about the item I use).
Does anybody have a step by step "cooking receipt" how I could establish the communication? I suppose that the MB bluetooth sap device uses A2DP, but nobody could confirm until now...
The Kaiser recognizes the MB bluetooth sap device on a regular basis as "UHI-SN3483" and sometimes as "MB-Phone". The MB device recognizes the Kaiser as "Pocket_PC" with the Laurentius ROM and as "TYTN II" with the Dutty ROM. Note that the "Remote SIM Access" was enabled in both ROM's.
I tried also to modify the registry entry
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys\COD from decimal 5898764 (Smartphone) to decimal 5374476. But no connection at all.
I didn't use JETware because I do not want an HFP but a SAP connection.
Another point I could not deal with is that the Dutty ROM features in Settings an item named "Bluetooth SIM Access". What does it is for and how to set it? pointing on it does not result in another effect than display in the header where was located Settings the term "BT Remote SIM Acce"
Sorry I have been that long, but I really need to get into this bluetooth SAP connection with my Kaiser
Thank you all
doc holiday
HTC Kaiser
hello guys... I've read in one of the threads for a diamond-rom-based rom that it includes "SIM Acess Version 3.0.xxx"... perhaps it will work with thsi new version... but until now I've not found any cooked, diamond-based rom, that includes SIM Access...
doc holiday said:
Does anybody have a step by step "cooking receipt" how I could establish the communication?
Click to expand...
Click to collapse
With every ROM that I have used before this one - it has been a rather hit and miss endeavor to link my Parrott bluetooth in my car with my phone. I USUALLY have to tell the PArrott that I want to link with a phone and step through things.
With the DEATH V3.5 ROM installed I got in my car and was in a hurry and thought I would sync them later.
After I started the car the phone indicated that the PARROTT wanted to connect and establish a connection - I indicated that it should be allowed - I was then asked for a key code on my phone- I looked at the PARROTT display device and had a 4 digit code there - keyed that into my phone and it paired easily.
Go figure...
Bill
I work for Mercedes and I paired my Kaiser 10s of times. I am guessing you are in the UK because we don't use the sim access cradles. I don't see why our technology would be better than yours. The cradle we sell that works is 6-7-87-5878 But I doubt it will work there.
I was trying to use a Nokia 616 car kit with T mobile sim in the UK, but T mobile does not support Sim acccess profile with their sims. I am about to try an o2 sim which hopefully will.
If the NB uses sim access profile and the provider does not support that use of its sim, then the Nokia will not even allow fallback to bluetooth car profile.
I hope you proble is not being caused by the above but thought you should be aware in case!
Regards
Chapelhill
It does works for MBZ. I am using it without any issue
Htc touch diamond and Mercedes SAP kit
i have a mercedes sap v2 car kit, i have the same problem being not able to pair with windows mobile based phones, the car can see the phone but phone cannot recieve the password confirm and so connection fails.
i tried many roms, added the SAP settings, and yesterday had the chance to try the new HTC touch DIAMOND on car, but same results.
i think that solving this problem is just a software issue, first in windows profiles, or as addition from Phone manufacturers (as HTC) ,because the car kit is already fixed to car and cannot be modified to use other profile.
but i still have hope that the professionals in this forum can help to solve this problem, before any of Microsoft or HTC. Please share any information to help
Thank you
Mercedes Benz makes five BlueTooth adapters that have five proprietary firmware that each adapts to a different type of phone. For example, a Vorizon CDMA BT adapter will not work with Sprint CDMA phone and vice versa. So in essence, if you have a AT&T service, and use a Motorola Phone, MBZ provides a specific BT adapter, that would be close to impossible to pair with an HTC device.
I would suggest going to an authorized Mercedes Benz parts department at their dealership and request to try all 5 adapters b4 you commit to buying one.
Only In the new 2008 and 2009 C-Class MBZ cars the BT adapter is universal and built in. In earlier models and other models (2008's), the BT adapters would need to be purchased independently; a 2X4 device that installs in the center glove box that works as a link between the media port of the car ( Hands Free) and the phone.
My 2 cents....
try the neon radio rom
i tried it in one of my friends car
if it did not work (change your car to fit your phone )
doc holiday said:
Hallo experts,
I am a newbie to this forum and a greenhorn concerning programming. But I bought the HTC Kaiser in order to get it running with my Mercedes Bluetooth SAP V2 Cradle (Article number Mercedes Benz: A204 820 0535). Unfortunately, the cradle does not work with the Kaiser. Do you know any solution (another ROM? for example) that may change the situation?
Thank you all very much for your appreciated help!
doc holiday
HTC Kaiser
Click to expand...
Click to collapse
Penske MB said:
It does works for MBZ. I am using it without any issue
Click to expand...
Click to collapse
which Penske Mercedes Benz do you work at?
doc holiday said:
Hallo experts,
I am a newbie to this forum and a greenhorn concerning programming. But I bought the HTC Kaiser in order to get it running with my Mercedes Bluetooth SAP V2 Cradle (Article number Mercedes Benz: A204 820 0535). Unfortunately, the cradle does not work with the Kaiser. Do you know any solution (another ROM? for example) that may change the situation?
Thank you all very much for your appreciated help!
doc holiday
HTC Kaiser
Click to expand...
Click to collapse
Try Htc shipped WM6.1
If not work.
Read this.
The Bluetooth® (HFP) telephone module, which is also suitable for Motorola PEBL U6, Nokia 6131, Nokia 6111, Nokia N70, Sony Ericsson K610i, Sony Ericsson W550i and BenQ-Siemens EF81 mobile phones, acts as an extension of the pre-installation for mobile phone with universal interface, a feature which is already present in many of the latest Mercedes-Benz models (optional extra Code 386). The module is simply inserted into this pre-installation in the centre armrest. The Mercedes-Benz Bluetooth® (HFP) telephone module, in independent-design closed-box format, will be available from Mercedes-Benz sales partners from March 2007, and is priced at EUR 250.00, including VAT (price applies to German market).
High-end telephony: the second generation of the Mercedes-Benz Bluetooth® (SAP) telephone module offers even more possibilities
I recently upgraded to a Touch Pro (Raphael), from the Dopod 838Pro (Hermes), and discovered that although I could pair the Raphael with my Kenwood DDX5032 car entertainment head unit via its KCA-BT200 bluetooth adaptor, attempts to make calls would result in 'error 68' displayed on the stereo's display, address book would not download to the Kenwood, and A2DP would not work. Basically none of the Bluetooth functionality worked, full stop.
Research revealed that there had been a firmware update for the KCA-BT200 which had added phone model support, specifically the HTC Diamond (running a French ROM no less, but any port in a storm I suppose).
The supported models under this new firmware are listed here. There's heaps of other useful info here.
The firmware, the tool required to flash it (a Bluetooth-equipped laptop is required), and the instructions are all found at the following page;
http://www.kenwood.com/bt/support/143to160/groupE/eng.html
I have saved a copy of this page and the firmware / flash tool should the above link go dead. Please PM me if you can't access it.
Regards,
Codenix.
There's a new upgrade for the BT200 available (now 1.7).
Go to http://www.kenwood.com/bt/support/groupF/eng.html for download and info.
The parent page which is updated when a new rom is released is at http://www.kenwood.com/bt/support/eng_model.html .
The 1.7 update seems to have resolved my intermittent issues. My HTC Touch Pro doesn't disconnect from my Kenwood DDX5032 for 10-20 seconds after hanging up any more, and A2DP connections aren't severed by phone calls anymore either.
Call logs still don't work (they worked fine with my Dopod 838Pro), but the battery status now works.
Kenwood are getting there - hopefully the next update will get us ALL the way there
Codenix.
1.70 did jack for my TP + BT-200 + DNX7100. I went through 2 units with the same flaky results. I've given up and went back to my trusty BT-100.
http://forum.xda-developers.com/showthread.php?p=3199533#post3199533
KCA-BT200 problem
I tried upgrading my bluetooth firmware to the version 1.7. My kenwood KVT-522DVD headunit froze on updating... and I reset the unit and now the bluetooth option has been disabled. Bluetooth firmware version is blank and the Start button for firmware update is disabled. Any help would be appreciated.
manga2 said:
I tried upgrading my bluetooth firmware to the version 1.7. My kenwood KVT-522DVD headunit froze on updating... and I reset the unit and now the bluetooth option has been disabled. Bluetooth firmware version is blank and the Start button for firmware update is disabled. Any help would be appreciated.
Click to expand...
Click to collapse
Ever figure out anything on that? I've run into the same problem.
XStylus said:
Ever figure out anything on that? I've run into the same problem.
Click to expand...
Click to collapse
I have this same problem... Did you find a solution? I called kenwood and no help. It's like I know more than the tech support guy.
Apparently this is a problem with many different car stereo head units/handsfree kits. I would like to get some info on who has it working and who doesn't. If you could provide the info as follows.
I will start,
-Phone: ATT Fuze
-Head unit: Kenwood DNX 8120
-Rom: Elite RC3
-Radio version: 1.02.25.32
-Specific problem:
1. After hanging up after a call the bluetooth connection drops. A call coming in causes the phone to reconnect to the headunit and handsfree works again until I hangup again. To make a call from the headunit I have to re-establish the bluetooth connection from the phone or headunit first.
2. SMS feature does not work.
3. Battery icon on headunit works when first paired but shows completely empty all times after that.
-Works with other phone?: Yes, ETEN x800 (No SMS), Eten X500 (no SMS)
-Ever worked with this phone in any configuration?: No
-Fixes tried: Jetware Bluetooth Handsfree Extension. Fixes the battery level icon, doesn't fix connection drop problem, or SMS.
I really hope someone can shed some light on this and some type of fix.
-Phone: HTC Raphael
-Head unit: JVC KD-BT1
-Rom: ROMeOS 1.70.1
-Radio version: 1.02.25.28
-Specific problem:
1. I seem to have the same problem with the connection drop you describe. Although I'm not sure it's always.
2. SMS feature does not work either
3. Sometimes I can't acces my phonebook through the headunit, a reconnect most of the times does the trick.
4. Disconnecting the headunit from the phone will give an error. I have to shut down BT on my phone to disconnect, so I can connect another phone.
-Works with other phone?: Yes, Nokia 6230i
-Ever worked with this phone in any configuration?: No
-Fixes tried: -
-Phone: touch pro
-carkit: parrot mk6100
-Rom: wwe 1.90.401.1
-Radio version: 1.02.25.19
-Specific problem:
1. had the exact same problem. solved by installing jetware 1.30. now it never disconnects.
2. SMS feature dunno (never tried)
3. battery icon fixed also by jetware
-Works with other phone?: Yes, qtek 8310 (wm6, also with jetware), se z520i
-Ever worked with this phone in any configuration?: yes
-Fixes tried: Jetware Bluetooth Handsfree Extension - for me this solved all problems, including syncing the phonebook on the older qtek 8310 which didn't sync at all.
-Phone: HTC Touch Pro
-BT System: Windows Blue&Me
-Specific problem:
1. sometimes connects automatically to car system (which it should do) and other times it doesnt. very annoying when driving and assumed it has connected.
Stupid Kenwood... not the phone i love my TP
-Phone: ATT Fuze
-Head unit: Kenwood DNX 6140
-Rom: EnergyRom 2.0 Series build 32609
-Radio version: 1.12.25.19
-Specific problem:
SMS not working
AD2P not connecting. Just getting "No Device"
I even try to connect Via USB... no love there either, and it locked up the Kenwood.
I am going to try a few A2DP programs i found. will report back when i have more answers.
Dolph
Update: So I did some messing around with the system settings on my phone and one the DNX 6140. I found that if i delete the bluetooth profile off of both the TP and the Kenwood, then pair via the kenwood not the Touch Pro, disable A2DP and grant access to my phonebook. They seem to "play well together". The moment I enable the A2DP on the Kenwood I get issues. I turn off A2DP and the Kenwood acts like everything is fine again. I am going to see if there are any other A2DP profiles that I can install on my TP, then do some messing around. I'll keep you guys posted.
Update #2: I have officially paired my TP to use the handsfree function, Phonebook download with voice dialing, and A2DP for the Kenwood DNX 6140. If you have any questions on how I did it I will create another post below. you can also PM me.
-Phone: ATT Fuze
-Head unit: Dual HD6425
-Rom: NATF 4.5
-Radio version: The ATT leaked one
-Specific problem:
1. When a call ends, the phone won't hang up. I have to turn the phone off manually. I can't seem to hang up the call from the radio like I'm supposed to.
2. I get this background hum sometimes.
3. If I try dialing before the phone connects it will only connect as a hands free device and not A2DP.
Did you find a way to prevent automatic contact download to the Kenwood with the HTC Touch Pro. I have too many contacts to transfer. (i.e more than the Kenwood can handle)
Thanks
Jeffrey
1st post yay, glad I can be of "some" help here as everyone else I've looked someone else has answered before I get a chance to respond lol...but..
-Phone: HTC Fuze
-Head unit: Pioneer 9800BT
-Rom: Stock
-Radio version: 1.02.25.32
-Specific problem:
1. Haven't had any problems with the unit dropping the connection. I can make and receive phone calls just fine. When I dial from the remote control on the unit and use the "Make Call" and "End Call" buttons they work flawlessly.
2. SMS feature on the phone works, but the sound doesn't play through he car speakers. Is that what you meant?
3. Battery icon shows empty on mine too...It never did this with my old Kaiser.
-Works with other phone?: HTC Kaiser (No SMS)
-Ever worked with this phone in any configuration?: No
-Fixes tried: None yet.
Anyone battling with the Kenwood 9140? I've got a call into Kenwood - they said it (touch pro) was tested with 1.90.xx... (FRE) ROM. Nice - the US model they're selling has been tested with only a French ROM. Got a second reply back to contact Parrott (the 9140 has Parrott BT). They forwarded my info on to their OEM division...we'll see.
Oddly, I never had an issue with the Parrott 3000 aftermarket BT unit when I had it installed with an Alpine (who's OEM BT didn't work, either) prior to installing the Kenwood. I figured if Parrott could do it right as a stand-alone, it should be a piece of cake for an embedded version. *shrug*
-Phone: ATT Fuze
-Head unit: Alpine Iva-w505 with kce-400bt (with firmware v 2.51)
-Rom: Latest EnergyRom (issue persists across every version i've used)
-Radio version: 1.14.25.35
-Specific problem:
1. sometimes connects automatically to car system (which it should do) and other times it doesn't.
2. Forcing a connection doesn't always work, but the it will connect when a call is made or received
3. Same issues above affect both phone and audio streaming
4. using MS voice command, it'll loose connection after accepting the command you want. will reconnect a few seconds after the other party picks up the phone.
phone : pro 2
head unit : Bolero 1Z0 035 156F
ROM ver : 1.86.415.2(67102)
Radio ver: 4.49.25.17
1- the pro2 pair with the Bolero nicely with full phone book access with no problem in call droping
2- the sms function is not working not show on car screan and not even a notification sound
hope there is a solution for the sms prob
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...