Yeah, the first post hasn't been updated since May- I've got the Touch listed in the spreadsheet in my sig, and so far we haven't seen any differences between the different carrier's versions. Most of the Windows Mobile phones are this way, thankfully

 

To follow up, yes the phone has 6.1, I also have bad echo through the speaker system. I do get phonebook integration but the other problems are too severe.

Thanks for offering a solution.

 

Is the list on page one still usable? I do not see any of the currently available Verizon phones on the list. I'm also wondering about the old post update date.

 

Scroll up two posts and hit the hyperlink in nicknbecka's signature line. That is assuming you haven't already. Lots of those phones are Verizon phones, even though they're not listed as such.

 

Nokia 6301 works (I presume the same for the 6300). Wifi calls work too... if I feel like sitting in my garage to talk.

 

Nicknbecka ; What is the color code legend for the R55 R56 (gen2) phone spread sheet. Sorry if I missed it in somewhere in the preceding pages. ajm

 

Thanks, I followed that link and found a few currently available Verizon devices. My bigger problem is that the phone has to iSync with my Mac 10.5.6 & iSync 3.0.2. There are only a very few that will work with both Mini and Mac iSync. I would do iPhone / ATT but their cell service is horrible in my area. Down to Blackberry Curve and MOTO Q9c. Neither implementation is clean. ajm

 

Good luck moe-jiller and keep us posted!

 

Apologies for the delayed response, I've been out of the loop for a few days. I've never really come up with a legend and you could be forgiven for not kicking back to read all 550ish posts to try and find one.

It boils down to:

• [*]
• [*]
• [*]

I also try to keep a comment with the URL to the most detailed report on each phone- cells in the spreadsheet with a comment should have a little orange box in the corner. Hovering the mouse pointer over these cells should bring up a tool-tip with the URL to the post.

 

Thanks! Does it sync the address book too? Any chance you've tried voice dialing with it?

For what it's worth, WiFi calls from the Blackberry Curve work too. I keep meaning to have my wife try a call while driving alongside one of the WiFi enabled buses, but it's hard to keep close in the traffic.

 

So, any word on this firmware update yet? I'm jonesing for one of these.

 

Blackberry 8900 (the new Curve) pairs with phonebook loaded easily. Phone officially released yesterday on Tmobile.

 

OK, so I got an LG ENV2 with firmware VX910V07, everything works fine except phonebook download, I suppose I can live with that, it's annoying though.

Is the phonebook profile a function of the firmware or the bluetooth driver?

Jeff

 

It is a function of the fact that LG WILL NOT implement the Bluetooth Standard as it is written.

What LG wants is to have their own (and only their own) accessories available for use with their phones. So what they do is implement a slightly different data stream for the transfer.

What this does is not allow the transfer of the phone book to many vehicle bluetooth systems. Some of the aftermarket systems such as Parrot do a better job with them but still do not work fully to the bluetooth standard because of the LG unwillingness to implement their software to the bluetooth standard.

The parrot and other aftermarket units are easier to implement changes to to make them work with a wider range of non compliant phones thru software upgrades etc.

I hope this helps you understand.

 

Thanks a bunch!

 

Hi Jeff- the phone's Bluetooth driver would be stored in the firmware, so you could say it's both. As Schatzy said, it's entirely up to LG/Verizon to get it fixed. There's a handful of LG phones that do work, but most of them are older or from outside the US.

 

Has anyone been successful in getting Verizon to flash their phone back to an earlier firmware, heck I'd do it myself if I could get the update.

Jeff

 

IIRC, Shatzy has tried this already, but the older firmware revisions don't include Bluetooth, leaving the newer versions still on the phone.

 

hmmmmm......... frustrating..........

 

Here's a phone update. Had to buy a new phone because my LG VX5300 bit the dust, unfortunately. It was a simple phone but worked perfectly with the MINI's bluetooth deal.

Using the spreadsheet, I thought that the Samsung Sway U650 would work, but it did not. The only thing that worked in the pairing was that if I wanted to dial the phone by hand, the sound would work through the radio with the bluetooth but the address book didn't load...so there goes the whole idea of hands free.

Just for "fun" I called MINI for "help" and all they did was tell me that the phones listed on that website http://wireless4mini.com were the only phones that would work. When I explained that the majority were out of date and not sold anymore (besides the iPhone and the Blackberries), they were of no help. Honestly, the guy sounded like an automaton. I really had to laugh because he said none of the other phones available would work!!!

Fortunately a Verizonwireless store not too far from where we live, had a real technical Manager who told me to come over and he was sure one of his techs could help me. And help me he did - we tried an LG...no go...and then the Motorola "Rapture" VU30 and it worked 100% perfectly!! So add that one to the list!

 

Sorry about that- there's another report on it that didn't have problems, but it's a few months old, so maybe there has been a firmware update that causes problems. I've updated the spreadsheet to 'conflicting reports' so that others in the future can be aware.

If you check the PDF's from wireless4mini.com, those won't even guarantee that the phones they have listed will work. Hopefully, as the Bluetooth option gets more common, they'll get their act together.

That's nice of them to do that, it sounds like 'officially' they have to have you buy the phone first and then return it. It's good to hear that there's some helpful people out there The VU30's now in the list- thanks again!

 

Well, the first Verizon store would not allow their tech to come out to try a phone in my car, so yes I did have to buy it. The second Verizon store, which was farther away where the tech came out to my car, etc., actually would not have made me buy a phone until they were sure it worked. That's where I'll go the next time around - which hopefully won't be for several years.

 

Excellent, thanks a mil!

 

We had trouble pairing our phone, Motorola V3, until we drove to a high hilltop. Have no idea why that did it or even if it did.

 

Some phones just take a while to load the first time. I had that problem with a friends phone in my car. It took about 3 hours to load while on a long trip. After that it made all the changes we could through at it very quickly, usually with in a 30 seconds or less.