Samsung A950 Bluetooth Phone

Hey Erick!

So, do I have this correct, you spoke to the "Samsung Level 2 Tech" who stated you needed DUN to make this work?

Well, here's some additional information (ammo) for you (from the VZW web site):

What is the Bluetooth Dial-up Networking (DUN) profile?

The Bluetooth dial-up networking profile allows the use of the Bluetooth handset as a modem (please consult the Bluetooth functionality charts to see if a specific Verizon Wireless device supports Bluetooth DUN)...

Now check the following link (which is the functionality chart):

http://dts.vzw.com/pdf/bluetooth_chart_handsets.pdf


As you may notice, both Samsung models that VZW offers (A950 & A970) do NOT have DUN functionality. Thus, at first blush, what the Samsung tech said might make perfect sense. HOWEVER, take a peek at the profiles for the Motorola E815 and LG VX8100......NEITHER have DUN functionality BUT Prius owners of those handsets are still, according to a variety of reports, able to dial using the car. Note that DUN can be re-enabled on the E815 (maybe on the VX8100, not sure) BUT that requires going through a procedure which, I would be willing to bet, few E815 owners have bothered with.

I'll openly admit that I could be dead wrong on this but I tend to think, based on the foregoing information, that there's something else going on that has nothing to do with DUN functionality.

 

I have a Verizon e815 that I bought just in the last few weeks, and I can dial out no problem. I wonder if they disabled all dial-out on the Samsung just to disable DUN? That sure would make a lot of people with car kits upset!

 

I have an 04 Prius and a new Samsung a950 with Verizon service. I have been able to get basic operation to work (I can make and receive calls through the wheel buttons and screen). I am happy with the hands frree when it works, but it does not work consistently.

When I first pair the handset with the handsfree everthing seems fine. And during that use (i.e. as long as the car and phone both remain within range and/or turned on) I can receive and place multiple calls.

If I turn off the car and turn it back on, the phone automatically connects when it should, and evertying looks ok, but functionality is highly limited. If I try to place a call through the car, the phone dials but the darn hands-free is not on, the sound only comes through the handset. Similarly I cannot recieve calls through handsfree. The *only* way to get it working again is to disconnect from handsfree and completely erase the Prius connection from the registered list on the phone. Then you have to start all over by adding a new phone to the list.

This is more than I can take.

Is there a work around to make the re-connect good? I tried the same senario with a friends motorola and everythinng worked as expected. (For a short time today I though I had it working by changing the phone's answer protocol (fromm "flip" to "send") but I appear to have been only amusing myself.)

I am still in the 15 day prace period and can switch to either the VX8100 or Motorola (e815?).

Any input would be appreciated.

 

I think I'm starting to understand why the Samsungs were listed as testing "pending" on all the compatibility sheets... I've never seen that on other phones.

"Pending" better advice, I guess my advice would be to run, not walk, to the e815. :mellow:

 

Hey Tag,

I Agree with you 100%. I think something is rotten and it just may be this phone model (or maybe just my phone). Maybe I'll give the Level 2 techs a call tomorrow again to tell this info just so I can listen to their excuses...

Thanks for all the support and great info everyone!

I'll keep you posted if there are any updates...

 

Just got off the phone with the Level 2 tech again and basically he said that were SOL until the next software upgrade kicks in. I mentioned the other phones working with the Prius and he said that he's actually taken calls with outer Prius owners about this headset and they are trying to work out a fix. It just sounds like they aren't really sure why it isn't working but they will hopfully get it all worked out in the not too distant future... We'll see!

 

I just picked up a Samsung A950 today (Nov 25, 2005) and tried to link it to my 2005 Prius. First it appeared all was well - - - but it wasn't.
Even though the Prius indicated “Bluetooth connection successfulâ€, 1) the signal strength was very weak - No bars (Whereas my 2 cell phones had 4 bars each). I’m in a large metro area and signal strength has never been a problem on any cell phone I have had. 2) I could call in and call out, but the conversation would not come through the Prius speakers, and the Mike appeared not to work either (although the radio signal was silenced during the connection. 3) Connection never lasted more than 15 seconds. It was “disconnected by the networkâ€. 4) Bluetooth connection also continued to drop out so that I had to re-establish a new connection.
In the Prius Nav book, it says “This system supports HFP Ver 1.0 and OPP Ver 1.1. The Samsung A950 manual says the phone supports HSP and Bluetooth hands free kit support* (with the * referring me to www.verizonwireless.com/bluetoothchart which tells me everything is “pendingâ€). This manual also states it does not support OBEX (whatever that is!).
So, can anyone tell me where I could go or what I should try to get my Bluetooth up and running in my Prius?

Any suggestions would be appreciated.

D Angelo Q
(New member - 1st post)

 

OBEX = Object Exchange. That protocol is a prerequisite to transfer your contacts from the phone's address book to the car's phone book.

Sorry, I do not know enough about the other issues to offer any viable solutions.

 

A weak signal does not seem like a protocol problem.

Is the phone charged ?

Where do you place it in the car ?

You may wish to simply exchange the phone, in hopes it is a dud, and not a problem with the entire model line.

If you have a bluetooth computer, you could verify the viable connection distance before speaking with your phone CSR.

 

****
Thanks for the rapid response.

Yes, the phone was fully charged. Truth be known, I have 2 Samsung A950’s, one for my wife and one for my daughter. I tried both with no success.

Where should I place the phone in the car? I just set it on the console between the two front seats. I also tried it on the floor where my wife would keep her purse.

I also purchased the hands free bluetooth headset from verizon, and it pairs fine and works well, so I tend to think the phone is o.k.

I appreciate your thoughts.

Thanks again Eric,


D Angelo Q
D (for Dennis) Angelo (my middle name) and Q (for my last name of Quatrine)

 

I hate to repeat what I already posted in #24 above, but Erick and gracieguy have already run into similar problems, and Erick said there will little possibility of fixing them until the next Samsung software upgrade (if then).

So, if you are still within your 15-day window, consider exchanging these for Verizon phones that do work, like the e815...

As far as where to place the phones in the car, it really isn't that important. I can get a Bluetooth connection to a phone in my house from my car in my garage...

 

actually this would be correct if you program the contact with 10 digit info (area code included). realize that not all switches are compatible with caller ID so if you get "unavailable" that means there is nothing you can do...at least until the switch is upgraded.

another thing, if anyone is interested in the A950. it is on sale right now you can get an additional $100 off if eligible for an upgrade and the offer expires tomorrow.

 

you have 15 days... exchange it. sounds like you have a defective unit.

 

***
Just came back from Verizon. Had their Techie in the Prius. First he did everything I did yesterday with no success. Then he removed the A950 and paired his LG VX8100 into the car. It worked fine through the car speaker and mike and all. Then he tried to pair the A950 again and it worked completely with speakers and mike, then it disconnect and would not reconnect. He tried his LG VX8100 a second time and could not get it to work. Next he reset his LG VX8100 by removing the battery and reinstalling, and got it to pair and work correctly with the Prius. Then he removed the battery on the Samsung A950, removed the LG from the Prius system, and paired the A950. It showed pairing and the Prius indicated a successful bluetooth connecting, but speakers and mike did not function. He suggest I could either 1) wait for a software upgrade for the A950 (no telling how long of a wait), or 2) upgrade (cost wise another $100) to the LG VX8100.

But wait - there’s more!
Thought I’d wait a few days and see what might come from this forum, and headed home. On the way home I saw that the Prius had a bluetooth connection to the A950. Using my other phone (PDA), I called the A950. It worked fine! Not being able to hear too well with the echo, I called my wife at home and had her call me at the A950 number. She called, I answered by using the button on the steering wheel, the radio muted, I heard her fine through the car speakers, she heard me fine via the car mike. All is fine (at least for now) in Prius Bluetooth Land. One of those mysteries of Electronics! FYI - phone was in the cup holder - & still no bars on the antenna symbol (although we did see 3 bars when the techie was using his LG 8100). Bottom line, looks like a cold reset (R & R the battery) may be a solution to try with the A950.

If anyone cares, I’ll report back in a week or so and let you know how it’s going.

D Angelo Q

 

We are quite interested in how both your A950 does if you fix it (I suspect it will continue to be intermittent) or how the LG VX8100 does, should you switch to it. Please continue to post any experiences.

I hate to sound like a Motorola e815 cheerleader, but that phone has been proven to work with the Prius, which is why I selected it for myself. Please consider it as well.

One good test is to call your work or home voicemail/answering machine from your phone (unpaired), then call it again through the car kit. Then compare both incoming and outgoing audio using these messages.

I'm surprised the tech saw 3 bars when he connected his VX8100 to the Prius. According to the last info we had from Verizon, the 8100 wouldn't send battery meter, signal strength, or roaming status to the Prius. Maybe they've updated their software? The e815 will send all of these, so no worries there. However, the 8100 will additionally send caller ID, the minus being you can only see the information when you are stopped.

The next problem you are likely to encounter is all Verizon phones have trouble sending the phonebook to the car. Fortunately, there are workarounds for this.

Here are two posts made about experiences with the VX8100. BTW, when people talk about how poor the Prius Bluetooth audio implementation is, they are often talking about their phone, not the Prius:

http://priuschat.com/index.php?showtopic=6...12&#entry154612
http://priuschat.com/index.php?showtopic=1...89&#entry110289

 

All of my contacts have 10-digit info (area code included). Maybe it's possible to place cellular calls using only 7 numbers within certain area codes but not mine. I need to use the area code to place calls, cellular or landline, even if I'm calling my next door neighbor.

 

most areas can dial 7 digits and get away with it. but for areas that have area code overlays (two different area codes in same geographic area) that is not possible even if calling your landline from your living room.

 

I've been bit by the 7-digit phone number in the past, so now all mine are 10-digit numbers as well. I live in Indiana, had a local number entered in my phone book as a 7-digit number, then when I was in Florida I selected that phone book entry and got a "sorry, this number can not be completed as dialed". So from then on I put the area code in front of all my entries... Much more universal.

Also, from what you and tag said above, a nice addition to the MFD when it recognizes the incoming call as one that's in your phone book, and adds a name to the incoming phone number.

 

i rather it ask if i want to add ANY new incoming number to my phonebook like my old cellphone did. now that was cool. only asked once though so if you said no the first time and wanted to add it later, you had to do it manually

 

To all who are trying to get verizon+phone to work in the Prius, I can only wish you good luck.

If you have a choice of carrier however -- I switched to t-mobile, bought a moto 330, and have been a happy camper since with ZERO problems. AND, I send a few dollars to a company that supports the TDFrance, and has the guts to put their guys in pink.