Looks like there's a similar list out there for all you BMW drivers...

 

does anyone know if the Samsung MM A920 works???? My current contract with sprint ends in Feb..I will be getting the iPhone at that time..but for now (my Cooper is expected to arrive week 28 so sometime at the end of August I think) Im stuck with my current phone.

 

I haven't seen anything, but it seems closely related to the MM A900, and it's been reported to work. The Samsung phones are hit or miss, but it's probably a safe bet.

 

Hi... I've been following this thread because I just ordered a 2008 mini cooper s scheduled to arrive by end of July. I just picked up an Env2 with the same s/w and bluetooth version. (VX910V03 and bluetooth v1.2) I guess I need to know whether or not to keep the phone or not so updates are much appreciated. I picked up my phone in santa monica, ca at a verizon dealer on wilshire. I'm hoping the combo will work. i'm seriously considering switching to at&t and getting the new iPhone though.

 

The post that you quoted says that your firmware will work, and is the only one known to work. Just don't upgrade your phone's firmware

 

thanks NICKNBECKA. My issue now is... Are the 2008 MCS the same as the 2007 that CARJOY has? I'm afraid that it's a car issue now. LOISLANE had a problem with her 2008 with many LG phones. Just need to know if anyone has tried that phone (with that build) on a 2008. Thanks~

 

Specifics on the hardware versions of the Bluetooth module are hard for us to come by, but so far as we know all 2007-2008 R56s are currently the same. The env2's firmware versions ending in 05 and 07 are known to be broken- schatzy62's car is a 2008 and he's tested those.

 

Forgive me if redundant, but I searched the threads and the spreadsheet and found nothing on the Motorola V360. It works flawlessly so far, making and receiving calls, and interacting with the voice activation. Not too surprising, since I think it's the same software as the RAZR V3 in a clunkier piece o' plastic.

 

I've found two cradle part numbers for the Nokia 6310i phone in this thread. Is one 'righter' than the other, for use in the US spec center armrest?
84210304651
84216930108

Also, a related question. My 6310i cradle I use in my C43 is tiny, and would fit into the center armrest nicely. When using bluetooth I don't think I need the antena hook-up on the back of the phone or other wiring to the car's system... I'd think I'm really just using the cradle as a place to house it and provide the phone power. Is this correct? So would/could I use the MB part number'ed cradle in the center armrest? I'm sure I could hook up to the phone's antenna with a little splicing too if that is used in the Mini.

thanx for reading... hope some know.

 

Great news! Thanks for the post, I'd rather have a dupe than miss out on a new phone. It's new to me and added.

It should be the difference between IBUS cars and MOST cars.

The R56 is MOST-based so 84 21 0 304 651 should be the correct part number for the R56, but you'd probably want to double check when you placed your order, most of my snap-in info comes from a German BMW PDF I stumbled onto, so I wouldn't consider it infallible as it didn't apply directly to MINIs. I list both part numbers in my spreadsheet, just in case.

The snap-in for the R56 provides power and some sort of connection with the antenna. For most phones, the antenna connection is indirect- a wire loop built into the bottom of the snap-in is connected to the car's outer antenna.

This antenna is for cell reception, not Bluetooth. The area near my house is at the very fringe of cell reception for me, and even without the snap-in, just keeping my old RAZR in the armrest improves the signal reception enough that I can use the phone in the car where I couldn't before.

I was looking into hard-wiring the antenna connector myself, without buying the snap-in (the antenna connector appears to be an MCX connector) but I think it's more hassle than it's probably worth now that I've switched to a Blackberry that doesn't have an external antenna connector.

 

Thanx very much, whichever, Nick or Becka! Awesome spreadsheet shared on Google. I hadn't caught that in your sig before this post of yours.

I guess the only outstanding question for me to search-on and find is that the snap-ins are the same dimension and plug-compatible in both the US and European center armrests. Everyone I encountered using the 6310i has been in Europe, and I have recently come to understand they have a different center arm-rest... so therein lies my hesitancy that all things are equal.

 

I haven't seen anyone mention that they're different, and everybody that's commented on the box says that there's no English instructions included. Still, I'd bet that a Service Adviser could tell you if it's a non-US part with a quick check when you order it. Chances are they'd have a cross-ref to the correct one if there were any problems.

 

Ok, I chickened out and bought a phone that is listed on the wirelessmini.com page. I guess I'm not so adventurous anymore.

FWIW, I bought the Verizon MOTO RAZR2 v9m. Setting up the Bluetooth was smooth. All my phone contacts transfered to the MINI. Voice works also.

The only problem I have with my phone book is that the MINI phonebook does not identify whether the numbers entered in the phone are cell, home, work, etc. Verizon uses an icon to ID each entry under each phonebook name, but these did not transfer.

Any ideas how to correct this in the MINI? I can't tell these numbers apart and I can't figure out how to modify the names in the MINI directory. I tried to modify the numbers in the phone, but the RAZR does not allow you add any letters after the number (and that would probably mess up the dial-out anyway)

Thanks, Rich

 

I picked up my Clubman on Friday. My Treo 700p (Sprint) does better than I thought it would after reading the horror stories here.

Odd: The phone book syncs IF you created a speed dial for the entry. Which is actually great, because I only want the most important numbers to sync.

Everything seems to work quite well. I'm running this through the Navi, so I'm not sure if that makes a difference.

I also only tried this on my first outing, so I'm not sure if it's going to lose pairing. More on that later.

 

Whoops- I accidentally had the 700p marked with the problems from the 755p in my spreadsheet. Also the R53's bluetooth system had a few reports of problems with the 700p too, but pairing with the R56 and later hasn't seemed to be a problem. The 700p and the 755p are close enough model numbers that you may want to be aware of past problems with the 755p. (EDIT: I haven't seen any problems reported yet, but the number of Treo users here seems to be pretty small... )

You might also have a firmware update available, depending on how long ago you got your phone.

Yep, it's a Treo thing. For whatever reason they all seem to work that way.

 

Thanks for the update Rich!

We had this problem with the RAZR too- we eventually just learned to remember the differences between the numbers. I considered switching the contact management back to single numbers and just adding 'Work' or 'Home' to the end of each contact's name. It seemed like more work than just leaving it be though.

 

I don't know if this one has been added but th Verizon Samsung SCH-U740 pairs and works. Phoe book does not dl.

 

Treo's bluetooth stacks are not very good. Always had issues with my old 650 and my wifes 755, on all types of bluetooth intergration.

My BB Curve hooked up flawlessly. I have full phonebook and hooks up everytime with clear sound.

 

Hey Des... Which Curve is that? Any chance its the 8330 from Verizon? Am considering getting one soon.

 

Hello Reyd1,

We've had reports on the SCH-u740 before, but they mentioned that their phone book did transfer. We've heard that some phones need a call in the received and missed calls log before the phone will sync, but haven't had any reports of that making a difference yet. It's something to try anyways.

 

Yeah, in case you haven't seen, it's probably best not to try with the 755p- it's caused serious issues for others in the past.

 

AT&T 8310 I believe. But I don't think you should have a problem with the Verizon version. If I were you, I would tested out at a store to see if it pairs.

 

Thanks Des, As far as I can tell from searching the Curve most have 8310. No one has reported on the 8330 specifically. Plan to try pairing before buying. I figure it's a pretty sure bet.

 

Anyone try the LG Dare from Verizon yet? Looks way too cool to pass up! Was all set to go with the Curve but since the Dare came out last week have been seriously temped to get it instead..

According to Verizon's bluetooth capability list it works with ULF 6934552. Does anyone know what gen that is? Shatzy? Nicknbecka?

 

I don't know of a report on the Dare, but I'm checking around in the usual places to see what I can find.

The ULF 3934552 looks like a model/part number for a BMW handsfree kit for an E39- not the same as the R56 MINI. Most of the phones between the two cross over, so that's a good sign, but no guarantee.