Mercedes Bluetooth (AWS) Phone Compatibility List
http://www.wireless4mb.com
only Motorola RAZR's and L7 SLVR are compatible. However, people have gotten this puck to work with other phones. I can only guess that your V551 isn't a compatible phone. You can get Motorola Razr V3 phones pretty cheap off eBay though.
I *think* you would be able to use the V60 puck, but not sure if it supports your phone. Go to this site:
http://www.wireless4mb.com
and click the "Vehicle Phone Compatibility" button. From there you can select the year of your vehicle, and see what options you have, and for what cellular provider.
I *think* you would be able to use the V60 puck, but not sure if it supports your phone. Go to this site:
http://www.wireless4mb.com
and click the "Vehicle Phone Compatibility" button. From there you can select the year of your vehicle, and see what options you have, and for what cellular provider.
And my Cingular (now AT&T) Razr V3 works perfectly, and downloaded the phonebook entries as well.But I've since updated my cell phonebook and would like to reload the entries into car's phonebook, but I can't figure out how to delete the existing phonebook and have the entires my cell reloaded into the car - any ideas from anyone? It seems I can't even manually delete the entries from the car's phonebook.
Any help would be much appreciated.Ron
The Best of Mercedes & AMG
I never could get the phone to pair properly on mine, until I figured out that by erasing the entire address book, then pairing, then adding the addresses back to the phone, it would work okay because it only tries the address book sync the first time (which evidently is what made it fail). Of course if I accidentally hit the button, it stops working again.
Strangely enough... I borrowed a friend's V60 puck he has for an '04 SL500 to try and it failed it my car, but it failed in a totally different way than my puck. His would pair quickly with the phone and download the address book just fine, but any call you try showed on the the phone & command as having connected, but I had no sound or mic (tested leaving a myself a voicemail and got nothing). Odd.




I got to thinking about why this might happen and supsect that it has to do with the way the phone handles the status of the handsfree/headset profiles. Motorola phones keept the headset connection both "connected" and "active" whereas the SE phones keep it "connected" but only make it "active" when a call is actually taking place. It seems that the Bluetooth module is looking for this status before it attempts to download the phonebook (via the OBEX profile). If this is the case this is a really stupid programming error, but then this system seems to have a lot of those.
I'd be curious to see if anyone who has a phone that pairs but does not download the phonebook could try this (e.g., place a call as soon as the phone becomes available on the MB system and then stay on the call for a few mintues while the phonebook downloads) and post what happens.
Thanks,
- FD
windows mobile pda smartphone does not work very well.
I get a real bad feed back constant tone. I am able to make calls and they can hear me fine but I get a feedback tone, that goes away when I accelerate. 2004 S600.
no phone book, no call waiting, no caller ID.
I will prob try some other phones, and then maybe switch my main phone.
"As to equipment and firmware, AWS [MB's handsfree partner] said that the principal factor in success in communicating between the phone and the Bluetooth equipment in the car is the compatibility of the cell provider’s firmware. AWS stated that it tests both phones and firmware for 3 months before approving it; and the firmware is tested for consistency of result and noninterference with the firmware of COMAND and MHI. Approved firmware will connect to the car, provide good voice transmission and reception, download what it is designed to download, and not fail to download those items over time; and will not freeze or otherwise interfere with the MHI system or COMAND. AWS was emphatic that a) approved phones using approved firmware will perform as they are supposed to, absent an equipment malfunction; b) some persons who are using unapproved firmware and equipment may have success because their firmware is in fact compatible, but has not been tested yet; and c) some persons using unapproved equipment or firmware may have brief success with downloads but downloads that worked initially may cease over time as firmware corruption occurs; and in the worst case, the MHI or COMAND may freeze altogether. AWS was emphatic that most voice quality problems occur with use of unapproved and incompatible firmware or equipment, with the principal variable being the firmware compatibility. With respect to equipment, the better its quality, the better the results would be."
AWS has not been successful with, or certified, any Treo. With respect the the MB Bluetooth equipment, Treos have equipment compatibility problems, and with many carriers, firmware problems as well. I don't know if the newest version of the MB Bluetooth puck (https://mbworld.org/forums/audio-electronics/191734-new-bluetooth-module.html) will provide better compatibility with the Treo.
Last edited by Skylaw; Jun 14, 2007 at 11:43 PM.
.With all my tests done, I came to conclusion that the problem is that Comand system is recognised by my phone as an headset and not as an handsfree, in fact, each time they're linked I get the headset profile instead of the carkit profile, even if the latter is the default one
.I think that "alewifebp" is 100% right, it's a shame that manufacturers like MB & Nokia (as well as many many others), keeps advertising a STANDARD which in fact is just their vision of the standard.
Keep in mind that we're talking about the "top class" products of their relevant markets..., unbelievable.

.With all my tests done, I came to conclusion that the problem is that Comand system is recognised by my phone as an headset and not as an handsfree, in fact, each time they're linked I get the headset profile instead of the carkit profile, even if the latter is the default one
.I think that "alewifebp" is 100% right, it's a shame that manufacturers like MB & Nokia (as well as many many others), keeps advertising a STANDARD which in fact is just their vision of the standard.
Keep in mind that we're talking about the "top class" products of their relevant markets..., unbelievable.
Anyway, the N95 behaviour was odd. I've used N95 in my car with the BT SAP puck with a privacy cradle, the first version and it worked OK, including phone book download. Would you have an older SW for the puck or the phone, or do you have the SLR-like puck?
The Bluetooth puck is the latest one available with part no. B67875877 (the black one), the N95 has been firmware updated to the latest version V 11.0.026
.

On the other hand since my BT puck is older than yours, I would have expected it to have better functionality with different phones, like the SAP puck V2 supporting more phones (address book download) than V1.
Is there a reason you chose the HF puck by the way?
It paired okay, but only connects sometimes, other times it stays on the "activating phone" screen for several minutes then switches to "phone off" even though the phone shows an active bluetooth connection and the puck has the solid blue light. Other times, it will work fine for a while, but after driving for a few minutes, just randomly switch to "phone not connected."
Anyone else had problems like this?
Any advice where I should start troubleshooting? I'm not sure if it's my phone, the puck, or the cradle.
I'm pairing it with a Moto V3xx.
I'm pairing it with a Moto V3xx.



