Interesting Issue

[sarroj]

Hi All,Ok, here's a head scratcher: I have the original Q (just recently got it), and when my Bluetooth earpiece (Jabra BT250) is connected, the phone rings on both the phone & the earpiece (which is what I want), but when I get a text, I only hear the notification on the earpiece and not the phone (I want to hear it on both). This happens in all profiles (except Silent & Meeting). When the earpiece is disconnected, the phone operates normally. All the settings are correct as far as I can tell, and I have the most recent software update for the phone (which I did yesterday). Motorola can't figure it out, and neither can Verizon. I tried another BT250, with the same results. For the first few days, (I believe) the when I got a text, I heard the notification on both the phone & the earpiece. If anyone has any ideas, I'd really love to hear them. Thanks !

[n99hockey]

--moved to Bluetooth Forum--

[larsdennert]

You're just hearing things.

[firecracker37]

How long is your text sound? I had the same problem with my motorola bt headset, and when I changed my text sound to something about three seconds long it strated working on the headset as well.

[sarroj]

Originally Posted by firecracker37

How long is your text sound? I had the same problem with my motorola bt headset, and when I changed my text sound to something about three seconds long it strated working on the headset as well.

I'm using "free" which is about 10 seconds or so.

[troutseth]

Same thing happens to me and I have three different BT headsets . . all the same. Rings on both, all other sounds headset only.

[thewizardatst24]

Try going to Profiles, highlight Headset, Menu, Edit and change as necessary.
FYI, the profiles can be found in the registry HCKU\ControlPanel\Profiles.

[PBCliberal]

Originally Posted by sarroj

Hi All,Ok, here's a head scratcher:
...Motorola can't figure it out, and neither can Verizon.

There are serious Bluetooth problems in the original Q. Some of these have been acknowledged here: http://onemanshouting.com/tech/Comme...725227f3a.aspx

Its pretty hard to hide those BT functions that they've simply turned off. But there are some BT functions that they can't turn off. Nobody wants a phone that doesn't support hands free, and now that some municipalities require hands free, not supporting BT for hands free makes that phone worthless.

Verizon has already had one taste of consumers not getting what was advertised. They had to let those customers out of their contracts and buy back their phones and accessories:

http://www.verizonwireless.com/b2c/f...tices/v710.jsp

So it seems Verizon's answer has been to simply deny that there are any problems whatsoever.

We have been experiencing BT problems with headsets from the first day we received our MotoQ. Verizon started out very nice but has been unceasingly ineffectual at solving our problems. We've been told that its the headset. We bought 5 more. They all experience varying problems, as does the Toyota Prius, though the Prius' difficulties arise primarily from Verizon's suppression of Address Book and enhanced calling services.

We reached a flash-point, however, when our sales rep advised us--after the phones were out of warranty and there was an heir-apparent--that the solution was for us to pay for new phones like a new customer, and accept a 2-year extension on our contract.

We have, since then, been seeking an answer from Verizon about what they knew and when they knew it. Verizon's customer service/technical support department has retreated to the position that there is nothing wrong with the phone.

One of the two directors of customer service that handle Verizon's technical support department advises me that neither his subordinates nor he himself could find any entry in their knowledge base that deals with bluetooth problems in the Motorola Q. He also advises me that his company hasn't retained any of the records of our contact to technical support beyond the last few weeks.

How is it that their knowledge base shows no information about bluetooth problems with this phone when we know we've made scores of calls ourselves, and a simple web search reveals records just like yours describing all the head scratching going on and the problem is clearly documented. Take a look at question #3 on the jawbone FAQ:

3. Is the Jawbone compatible with the Motorola Q?

Although Bluetooth is a standard, not all Bluetooth is uniformly configured, causing potential compatibility issues between some phones and Bluetooth headsets. Currently, the Bluetooth on the Motorola Q is configured differently than on most phones resulting in compatibility issues with the Jawbone. While we have seen a few encouraging posts on forums regarding the new Q9m, until the Q Bluetooth configuration is closer to other phones on the market, we are unable to recommend our headset for use with it at this time.

It gets better. Jawbone's BT headset is sold in Verizon stores, but the technical support person I talked with at Jawbone indicated that his company has never advised Verizon that there is a problem with the headset when used with the Q. They did, however, pay an independent research firm to determine if the jawbone would work with the newer Q, and that company reports that it does work.

So the picture we're seeing appear is one of plausible deniability. If you keep the data out of the records, and never either volunteer information or ask the tough questions, you get to scratch your head to customer after customer and never have to deal with the problem, which is that the phone, as configured by Verizon, is defective with respect to this feature.

Who pays the price? We do, because we get to tell them and tell them and tell them again. Verizon asserts that the phone works and assures us they will make us happy by working with us to make its BT headset capability stable. We'll let you know how it comes out. At least until then, and probably until Verizon changes these business pratices, be very skeptical when told that they've never heard of anything like this and can't imagine why it is happening to you.

[larsdennert]

After a dozen paragraphs, I'm getting the impression that there is an issue with your Jawbone and the Q.

I use a MOTO HS850 headset and it works flawlessly. I also have the MOL3 firmware update for my Q. Might be an option for your unspecified issue.

[PBCliberal]

Originally Posted by larsdennert

After a dozen paragraphs, I'm getting the impression that there is an issue with your Jawbone and the Q.

I use a MOTO HS850 headset and it works flawlessly. I also have the MOL3 firmware update for my Q. Might be an option for your unspecified issue.

There definitely is an issue with the Jawbone, as I indicated in the quote from the jawbone website. But the situation I was trying to highlight was Verizon's 18 months of denial--the "scratching their heads" question that started this thread. There is also an issue with the Motorola H700, the Scala 700, an IOgear product, and the Plantronics Voyager 510. But not according to Verizon. Everything is beautiful at "can you hear me now."