[Q] Bluetooth Voice Dialling, BT Phone Book Access (PBAP) - Fascinate Q&A, Help & Troubleshooting

I'm running DL09 Super Clean 0.4/EB01 2.4 on a Fascinate. Kernel is EB01-based Voodoo.
I took the plunge and got a Motorola Roadster bluetooth car kit, preferring a car kit to an earpiece. With my Froyo based Fascinate, I was eagerly anticipating voice dial, etc. No such luck.
Car kit pairs and requests phone book access. Grant privilege (always). Great!
But... Car kit does not announce caller name, even though it is a contact in the phone. Seems like although the rights are granted for PBA, the request for an phone book entry by the car kit fails.
Also, no bluetooth voice dial
Pressing the command button on the car kit returns and annoying "not supported by phone" message.
Is the BT stack still under development, or do I need to configure something? (seems unlikely).
Thank you in anticipation.

I don't know anything about phone book access, but to use voice dialing on Super Clean, you need to flash the Nuance zip in that thread. Nuance is the stock app that handles bluetooth voice dialing.

Thank you for the tip. Installed Nuance. Useless. My accent is South African / Oz / USA. Voice commands deliver some interesting response. Even after adaptation, recognition (in a quite environment) is no better than 10%. Too bad.

And just a heads up...post questions in the General section

I pulled out my bt headset the other day and was disappointed to discover the same thing. I agree that Nuance is trash (and is why my bt has been in storage for a while). I haven't done so yet, but have you tried Vlingo?
Sent from my SCH-I500 using XDA App

Installed Vlingo and have been using it for a few days. Recognition is great, but does not cut media sound when waiting for command and does not handle car noise well. Maybe my car more noisy than average... I'm going to keep it and watch for updates.

In my opinion there is most definitely an issue with the Bluetooth stack in EB01. I just had a head unit installed in my car that is capable of streaming music and phone calls. Whenever I make or receive a call through the unit, it force closes upon hanging up, with both devices indicating they still have a connection (and they definitely do not). I have to power down the stereo and turn bluetooth off and back on the phone.
It is extremely aggravating. I feel like this phone has been one huge repeat of "one step forward, two steps back".
I love Froyo except this bluetooth issue is a major disappointment. That, and I've tried everything posted and still have lousy battery compared to DL09. But that's another thread.

Anyone know if this is any better in ED01? Im running SC2.9.2 and see no reason to go back to stock or even an ED01 ROM -- unless the BT voice dial is working...

Related

Sony MEX-BT2500 review

I just bought an MEX-BT2500 and had it installed - all at Circuit City, for the Americans on this forum.
Since I literally *just* got it, I will give an initial impression and then update this in a few days probably with some more info.
INITIAL IMPRESSION
Well, it looks nice. The buttons have blue LEDs. But that's not very important. Pairing it with the Hermes was pretty painless, you just turn it off and then hold the Equalizer/Bluetooth button >7 seconds. The passcode is, of course, 0000. It has three separate Bluetooth icons - one for it being off/on/discoverable, one for hands-free being connected, and one for A2DP being connected.
When re-pairing after turning it off or something, the A2DP mode does not reconnect automatically. I've tried pressing 6 (Pause) and that made it reconnect. Maybe there are other ways of doing it, I don't know.
I am still experimenting with the A2DP settings to figure out what sounds best - I am using the Microsoft stack, so I'm not expecting miracles here - so far, it sounds OK at BitPool/MaxBitPool = 58 and Joint Stereo = 1. Contrary to popular belief, Joint Stereo is NOT mono, but I have yet to determine whether the Microsoft stack thinks that. I just need to play the right song. I read somewhere on this forum that increasing BitPool/MaxBitPool to 72 while keeping Joint Stereo on sounds good, so I'll try that later.
I will try the hands-free mode later on as well. Updates to follow.
UPDATE 1: More on A2DP (and a bit of hands-free)
I set both of the BitPool values to 72 and enabled Joint Stereo. It works well. The sound is most definitely stereo, and the quality is a lot better than what it was with a lower BitPool and Joint Stereo off. I've never tried the Widcomm stack, so I can't compare it to that. I also tried hands-free calling, but it did not work at all. That turned out to be an issue with the ROM (because it no longer worked with my HT820 either), which has since been resolved by flashing a different ROM. One extremely disappointing thing is that it looks like, for making calls, you can only initiate a redial from the device. I haven't looked into that too much yet.
UPDATE 2: Hands-free
I still haven't been able to make it do anything but redial for initiating calls, but the call quality appears to be quite good, both for the person on the other end and for me. I have to say, I'm impressed by that, especially since the Parrot MK6000 apparently has a huge separate dual microphone that you have to mount in order to get clarity.
One thing that has started to annoy me is the beeping when I turn off my car. Apparently it's to remind me to take off the faceplate, but I don't always want to do that and it pretty damn annoying. I don't believe there is a way to turn that off. You can turn off other beeps, but not that one.
UPDATE 3: A2DP again
The wireless stereo really does work well! The Hermes is able to handle receiving Internet radio streams (www.di.fm in my case) and piping them through A2DP just fine using MortPlayer. Speaking of which, AVRCP works well. Play/pause, previous, and next buttons all work, but with a slight (<1 sec) delay, which is caused by something other than the BT2500 because the same delay occurs with the Motorola HT820. It's either an issue with MortPlayer or the Microsoft stack - I don't know which one since that is the only combination I've used that supports AVRCP.
One thing I have yet to try is receiving a call while listening to music. I will try to do it tomorrow and see what happens.
I've had the MEX-BT5000 (the BT2500's predecessor) since January & use it with my Wizard. I haven't had any issues with A2DP connections -- I've paired it only once when I installed the headunit.
The only time I have to reconnect is if the Sony powers up without my Wizard in range -- the next time I power up the Sony, it'll connect to the Wizard's hands-free profile, but not in A2DP. To reconnect A2DP, open up the Wizard's BT connections screen, select the MEX-BT5000 device, and right-click "Set as Wireless Stereo".
3waygeek said:
I've had the MEX-BT5000 (the BT2500's predecessor) since January & use it with my Wizard. I haven't had any issues with A2DP connections -- I've paired it only once when I installed the headunit.
The only time I have to reconnect is if the Sony powers up without my Wizard in range -- the next time I power up the Sony, it'll connect to the Wizard's hands-free profile, but not in A2DP. To reconnect A2DP, open up the Wizard's BT connections screen, select the MEX-BT5000 device, and right-click "Set as Wireless Stereo".
Click to expand...
Click to collapse
Im fitting a BT5000 today in my new car. What car did you install yours in?
Ive fitted a new head unit to a vauxhall corsa before but never needed to use the smart cable for steering whell controls...is it dead easy?
P.S: the new car is a 2003 vauxhall astra
Does the BT5000 let you do voice dial through the Hermes/Wizard, or does it also just support last number redial? So far, I haven't been able to get it to do anything but redial for call initiation.
mrvanx said:
Im fitting a BT5000 today in my new car. What car did you install yours in?
Ive fitted a new head unit to a vauxhall corsa before but never needed to use the smart cable for steering whell controls...is it dead easy?
P.S: the new car is a 2003 vauxhall astra
Click to expand...
Click to collapse
Mine is a 2002 Mitsubishi Diamante -- I had to get a $60 translation unit to interface the steering wheel controls to the headunit. Installing the translation unit took some doing -- they're a bit tricky to program.
Trancecoder said:
Does the BT5000 let you do voice dial through the Hermes/Wizard, or does it also just support last number redial? So far, I haven't been able to get it to do anything but redial for call initiation.
Click to expand...
Click to collapse
Haven't tried voicedial -- I've got Voice Command 1.6 installed on the Wizard, so I think it'd work. I'll give it a try tomorrow.
Quick report back, had a right bastard of a time installing it LOL!
Vauxhall cables are deliberatly CRAPPY, i had to swap over two of the wires because the unit was not keeping the time or radio stations when i switched off the ignition. I also purchased a smart lead to enable the steering wheel controls.
Finally got it working, works an absolute DREAM with both A2DP and handsfree.
I am also thinking of getting the BT2500, but my big problem with it is the 'redial' problem. Apparently the BT5000 can download and store 50 numbers but doesn't allow for voicedial, (I've heard anyways)...
Trancecoder: Did you ever find something to trick the phone into launching voicedialing when a bluetooth redial was activated? What about the 1-6 buttons, can they be programmed for speeddials like the BT5000 ??
JamesManios - I don't believe the BT2500 downloads any contact info whatsoever, so those keys won't be able to be programmed. As for the redial vs voice dial issue, I haven't experimented much with it, so if there is a way to make it speed dial, I haven't found it yet.
Trancecoder: Thanks for the reply, how are you liking the unit now that you've had it for a while.
As an idea for dialing I was thinking of making an app to maybe accomplish it, but some of it I don't know how to do yet...
My idea was, have the app pole every 200msec or so and see if the phone has started dialing (that I pretty much know how to do), then see if you are connected to the bluetooth handsfree (don't know how to do that just yet)... then the program can assume that if you are dialing AND in the car (because you are connected), then you must be using the redial... STOP the redial and launch the VoiceDialing app...
It leads to some questions, like would the Stereo drop the BT connection and therefore the voice prompt would be from the phone speaker and using the phone mic and NOT the stereo...
I currently have this (which works very well), but not as clean as the stereo ... but I'm not sure I want to lose CallID and VoiceDial... to buy this unit.
http://www.vitebo.com/ny00050/produ...betiew&MenuID=28&BClassID=9&SClassID=0&PID=13
ive had a bmw m3 and the bluetooth sucks in it my infiniti much better. i always use my jawbone though. I may need to pick this one up.
JamesManios said:
Trancecoder: Thanks for the reply, how are you liking the unit now that you've had it for a while.
As an idea for dialing I was thinking of making an app to maybe accomplish it, but some of it I don't know how to do yet...
My idea was, have the app pole every 200msec or so and see if the phone has started dialing (that I pretty much know how to do), then see if you are connected to the bluetooth handsfree (don't know how to do that just yet)... then the program can assume that if you are dialing AND in the car (because you are connected), then you must be using the redial... STOP the redial and launch the VoiceDialing app...
It leads to some questions, like would the Stereo drop the BT connection and therefore the voice prompt would be from the phone speaker and using the phone mic and NOT the stereo...
I currently have this (which works very well), but not as clean as the stereo ... but I'm not sure I want to lose CallID and VoiceDial... to buy this unit.
http://www.vitebo.com/ny00050/produ...betiew&MenuID=28&BClassID=9&SClassID=0&PID=13
Click to expand...
Click to collapse
The unit's pros outweigh its cons, at least for me personally. I receive a lot more calls than I make while driving, so the dialing issue is not a big deal for me. The person on the other end can definitely hear background noise, but they can still hear me pretty well when I have my windows open and driving ~50MPH. The unit also plays MP3 CDs, which is nice because I have some from when I was using my old MP3 CD player. A2DP quality is good, although occasionally there is a drop out for about half a second. Sometimes it happens 20 minutes into driving, sometimes not at all, so I have no idea what's causing it. Overall, I'm satisfied with it.
One thing I noticed is that when I press the Hermes button 5 (mapped to Cyberon Voice Commander) while fully connected to the BT2500, the "Say command" prompt goes out through the Hermes' speaker and not the BT2500. That may cause additional problems if you want to try and create a software fix for the auto-redial.
That Vitebo website is full of Engrish! "THE FRESH PET OF CAR ARTICLE" - what does that mean?
Ya, that website is pretty brutal, unfortunately the manual is similar but I got it finally figured it out (I hope)
I decided against the Sony and bought a none BT headunit, thanks for all the info though.
Had mine for 8 months now...
Excellent unit. I had BMW factory fit bluetooth in my old car, this is much clearer (VW Passat).
I used mune with an Artemis, and now an Elf/Touch...
It doesn't download a phonebook, so the only dialing it can do is redial last number - but just use PocketCm and dial with your finger!
Quality is good - I have found, however, that A2DP streaming breaks up unless I use Coreplayer, which is 100% perfect... and yes, pressing '6' a coupl eof times toggles on the bluetooth stereo on the device, which is good, because otherwise, I wouldn't be able to hear tomtom instructions if I had the radio on!
Sound quality all round is excellent - just a shame it dosn't have a steering-wheel mounted remote instead of the useless IR one...

[Q] Incoming text messages sent through Bluetooth?

This is a question I've had since owning the G1. Can we make it so that our incoming text messages get pushed through Bluetooth? I know the functionality is not there with the stock messaging app, but does there exist one that does? Or can one be programmed to do so?
This would be helpful to handful of people (like me) that have Microsoft Sync systems in their Ford/Lincoln/Mercury cars. Sync is able to read you your text messages while driving, and allows you to reply with your voice or call the sender, but only if the handset supports sending texts through Bluetooth.
I would imagine that since we have the latest version of BT, it could at least be programmed into a third-party messaging app, by someone with more knowledge than I. The only handsets to support this feature out of the box are some candybar Nokia and Motorola featurephones, so it wouldn't be too far fetched to get Android to support this.
Any thoughts?
This is the only thing i've been able to find that looks anything remotely close to what your asking for...
http://www.myblueant.com/android/index.php
Hope this helps
I believe I saw on the official Sync website that one of the Android phones was working with the text part of Sync. Posted by a Android user. You might look into that and see if it leads anyplace.
Sent from my SAMSUNG-SGH-I897 using XDA App
Try out the vlingo app in the market. It has something called Safe reader. It will read your sms out loud. When I'm driving and have my phone hooked up to my stereo, through bluetooth, it plays the message through my speakers. Not sure about standard bluetooth headsets but its worth a shot.
DriveSafe.ly will read your incoming messages to you via BlueTooth, and can be configured to autoreply, if you wish.
I looked through the syncmyride website and several people are reporting the Droid X works with the text messaging part of the Ford Sync system. Maybe there is hope for a direct connection. Although they also talk about Samsung phones in particular having issues with the Sync.
I'm trying to get this working as well. Stock EVO
Thanks for the suggestions of DriveSafe.ly and Vlingo. This is a great alternative, however in my case they would only work if I had the car stereo connected through Bluetooth (the Sync system allows you to do a Bluetooth media stream).
The issue, however, is that most of the time I have either my Zune or my Toshbia media player playing through a USB connection in the car. Say I get a phone call, Sync knows to pause the music in the USB connection, alert me to the phone call, talk on the phone through the car speakers, and then when the call is disconnected it will resume playing the music from the USB. Since the USB is selected and not the Bluetooth stream however, DriveSafe.ly and Vlingo won't automatically notify Sync of the text (it does work if I'm using the Bluetooth streaming option though, since Android is handling the streaming).
After rummaging through some posts, it seems that Syncs ability to communicate with your texts stems from a Bluetooth profile known as MAP (Messaging Access Profile), and while Bluetooth 2.0 and higher support this feature, only some handsets have that Bluetooth profile supported. How hard would it be to add a Bluetooth profile to the Android core through, say, a custom ROM? Or would the Kernel have to be modified?
Looking at the compatibility list it seems that the Motorola phones work with the text messaging system. All ( or most) of them, not just the Android phones. So it may be deeper than ripping the BT control scheme out.
But it would be great if someone could figure it out. I don't think many people care though, if you search here for Ford Sync you don't get many hits.
Blue control
search blue control on the marketplace or appbrain. this app allows sms to be played (and responded to) through a bluetooth headset!
Vibrant reads text out loud stock.
Settings>Voice Input and Output>Text-To-Speech Settings> Check Driving Mode...though..be warned. This will read ALL incoming texts out loud, and when you get a call, it will say Call from (caller or number if it's not in your contacts)
Don't have a BT headset..well I do..just can't find the charger. lol, so can't test it. And I'm not rich enough to have a BT enabled car.
Bumpity bump
gahockey05 said:
search blue control on the marketplace or appbrain. this app allows sms to be played (and responded to) through a bluetooth headset!
Click to expand...
Click to collapse
In the app description, it says it does not work with in-car bluetooth "at this time". So we can keep our fingers crossed.
Sent from my ADR6300 using XDA App
I have found, that to get messages read to me and be able to reply, I had to install a custom rom (CyanogenMod 9-20120710-nightly), it works great! I hope this helps.

[Q] Why can’t I place calls from a Bluetooth device when the phone is locked??

I'm hoping someone here has some *real* ideas or answers regarding this issue.
I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS “locked” I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system… are we back in the smartphone dark ages?? I might as well take up texting and driving while I’m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is “locked” it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don’t need these draconian measures this is just plain stupid and potentially unsafe.
I've already rooted my phone. I've tried other ROMs like the latest builds of UnNamed, ICS'd Out, and CyanogenMod. None of these allow Bluetooth operation while the phone is locked (and in fact all of them introduced other issues). I've searched the forums but most similar posts go unanswered or contain nonconstructive replies (flames, unrealistic answers, etc).
I can't and won't disable ALL security. I won't give up making phone calls while driving - I'm on the road a decent amount and need to use that time productively. What are my other choices? Go buy an iPhone or a Windows Mobile unit which work "right"?? Seems like a crazy oversight by Google/Samsung/AT&T if those are my only options!
I would suggest using the official samsung Car dock, as the USB port on there has a special impedance that tells the phone to go into driving mode, which once you unlock the phone, it stays unlocked until you either lock it, or take it off the dock. It also charges your phone at the same time. However if you have a case, this will not work for you. You would need to solder up your own usb plug that has a certain impedance over some pins (theres a thread somewhere about that, its like a jig, but with different impedance) and just plug that in when you're driving, but you still have to unlock the phone at least once with it plugged in.
My clarion cz500 car stereo has no issues making or receiving calls via Bluetooth while my phone is locked.
Sent from my GT-I9100 using xda premium
My biggest gripe with Android is that BT calling does not work as well as it did with WinMo's Voice Command (which works really well considering how poorly much of WinMo worked). Initiating calls via BT is my main gripe with Android. I wish Google would get it right already. That said, I have no problems answering calls via BT even when the phone is locked.
My phone is paired with the built-in BT in my car and I have no issue with making/taking calls while the phone is locked. Maybe its a compatibility issue with your particular hands-free device?
I also have no BT problem when locked, using the standard BT in my Toyota Avalon, 2011. Running rooted, UnNamed ROM, Entropy's DD 120811 kernel.
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Miami_Son said:
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Click to expand...
Click to collapse
Sgs2 does this stock with no problems via samsung/vlingo voice command app. Seems hit or miss on some custom roms. As long as device has bt turned on and had been prior paired with a headset, just have to turn headset on then hit the button on the headset. Voice prompts over headset ensue
Sent from my SGH-I777 using XDA App
I'm headed into the AT&T store tomorrow to do some definitive tests but so far I'm skeptical people who say it's working for them truly have their phone locked. The Bluetooth unit in question is a Parrot CK3100 LCD - a bit dated (3 years old) but it works flawlessly with several WinMo phones, several non smartphones (mostly Nokia's), and we just tried a friend's iPhone 3GS and iPhone 4. In all cases phonebook and voice dialing not only worked excellently it worked when the phones were truly locked and the screen off.
On the other hand the 3 Android devices I've tried all have the same problem - they won't dial out either by phone book entry or voice recognition unless you unlock the device first. The 3 devices are: Samsung Galaxy S II (AT&T), Samsung Galaxy S (Verizon), and EVO 3D (T-Mobile).
Unfortunately I don't have any other Bluetooth headsets to try out, hence my planned trip to AT&T. I plan on walking out of their either with a Bluetooth device that works or an iPhone Thanks for the replies.
I hear you. I have a Motorola FINITI bluetooth headset and it will not voice dial with the screen locked on my AT&T Galaxy SII.
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Some roms give you a quick toggle in your status bar called secure mode, this should do it.
I'm on villain rom with jaykay mod quick toggles and i have that options.
Sent from my GT-I9100 using xda premium
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
GeorgeP said:
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
Click to expand...
Click to collapse
Are you using a pattern/pin lock? Or just the slide to unlock.
Just slide to unlock.
It works very well and very straightforward. I just press and hold the call button on my headset (while the phone is locked), and then after the tone say, "call John Doe on mobile" and it works.
Something for OP to consider in troubleshooting why he is unable get this work:
The BT voice dial works through the older pre-installed Vlingo (version 2.x). Even though I have the newer version (3) of Vlingo installed, the phone still launches the older preinstalled version of Vlingo for BT voice dial. So it seems the BT voice dial function is in some way hardcoded to that version of Vlingo.
Perhaps OP is using a custom ROM in which the older pre-installed Vlingo is removed(?). I know that is the case with some of the custom ROMs for the Int'l SGS2.
If I were to freeze or remove the older version of Vlingo, that might impact BT voice dial. Although I wouldn't expect it to affect the use of my phone through my car's build in BT.
Try it with a pattern lock or some kind, I believe that is what the OP has and its what "locks" the phone from using BT dialing, whether its voice based, or address book based from a headunit.
OK, if OP means that type of lock, then, no you cannot make a call when locked.
Although, it is not clear to me why one would want BT to bypass the lock in this manner. It seems the PIN or pattern lock would be pointless. If the phone is stolen (or lost) the person who stole it (or found it) could have access to your phone's contents through bluetooth. Am I missing something?
Definitely missing something. He wants the phone to be able to make calls while the phone is locked which is why i suggested to keep it unlocked by enabling driving mode through the mount.
My point was that allowing bypassing the lock through BT creates a exposure many would not want. The simplest solution might be keeping it unlocked either using a mount as you suggest, or using one of the profile apps that lets you create a profile to keep the phone unlocked when plugged in. He could then plug it into the car power adapter.
I use a pattern lock, and can make calls through the built-in BT in my car when the phone is locked. I can dial on the car's touch screen (disabled when the car is in motion, except for pre-set speed dials), or tell it to call someone by pressing a button on the steering wheel and saying the name. The car BT compares the spoken name with the list of contacts from my phone that have been BT-loaded into the car's contact list. Nevertheless,the call is made though the phone, since the vehicle BT is not itself a phone. Has anyone noticed that we have not heard again from Rajah, the originator of this thread? Rajah, are you there? Were your issues resolved?

Can anyone verify this problem on your HTC ONE (M7)

This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Have you been able to use any other bluetooth device successfully? And have you checked the compatibility of that device with your phone? From what you're telling me, it seems very much like a bluetooth device compatibility problem, which is the same issue I had when I had a custom ROM flashed with my old HTC Rezound
nrkid9 said:
Have you been able to use any other bluetooth device successfully? And have you checked the compatibility of that device with your phone? From what you're telling me, it seems very much like a bluetooth device compatibility problem, which is the same issue I had when I had a custom ROM flashed with my old HTC Rezound
Click to expand...
Click to collapse
Absolutely not a bluetooth device incompatibility.
All bluetooth devices I have tested (3 different models total: 1 car stereo and 2 different earpieces) work just fine when NOT in CAR mode.
The HTC One (M7) treats a bluetooth button press the same as any other android phone when NOT in CAR mode.
It will bring up a different dialer which uses voice commands and this works fine.
Answering phone calls and dialing out via bluetooth work on both earpieces when not in CAR mode.
The car stereo also starts the voice dialer when NOT in CAR mode, same as the 2 earpieces that were tested.
ONLY CAR mode will start SPEAK when pressing the same bluetooth button.
However as I described above, You can successfully use all 3 bluetooth devices (audio is routed through all 3 devices' microphones and speakers) if you press the SPEAK icon in CAR mode.
Pressing the bluetooth button to start SPEAK causes the fail on all 3. Sounds like the SPEAK app to me but I/we won't know without more feedback.
Thanks for the suggestion but I have now successfully tested 3 different devices that can START and HANGUP and REDIAL calls but the same 3 fail when pressing the bluetooth button in CAR mode hence I am trying to verify if others experience the same results.
Do you have a bluetooth earpiece or car stereo with bluetooth to test yours with?
I sadly don't have a device that I can test with my phone at the moment. I will see if I can dig one up and test it on my own. Have you tried going to your carrier and resolving the issue with them? I'm sure they'll be happy to replace the phone if it's still under warranty (seeing as it just came out, it should be) and the issue is legitimate.
nrkid9 said:
I sadly don't have a device that I can test with my phone at the moment. I will see if I can dig one up and test it on my own. Have you tried going to your carrier and resolving the issue with them? I'm sure they'll be happy to replace the phone if it's still under warranty (seeing as it just came out, it should be) and the issue is legitimate.
Click to expand...
Click to collapse
Replacing a phone with a design flaw just gets me another phone with a design flaw. That is why we need to test it here and verify what results we all get.
I have the EXACT same problem using Bose 2 Bluetooth headset!
IIHomieII said:
This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Click to expand...
Click to collapse
Voice dialing does not work on my T-mobile HTC one with my JVC stereo either. I have exactly the same symptoms you describe. My nexus one with CM 7.1 works perfectly and has for the last two years - so I know the issues I have are not related to my stereo.
Other things that work perfectly on my nexus one but are broken on the HTC one include:
AVRCP play / pause commands in music
AVRCP play / pause command in beyond pod
Wifi tethering
Notification light (HTC one light only flashes for five minutes, or not at all if connected to power)
Google voice (resets to T-mobile voicemail every few days)
Does not seem to get push notifications (have to wake the phone to check email, etc – presumably this is for power savings, but despite this nexus one has better battery life)
I think I am going to return the HTC one and wait for the next nexus device. The camera, speakers and screen are great on the HTC one, but every one of the above issues is a deal breaker for me (I use car mode / AVRCP a LOT). I’d consider cyanogen mod, but the lack of native camera support (optical image stabilization, low light performance, etc) due to no HTC camera driver source code / reliance on sense UI removes one of the biggest advantages this phone has over a nexus phone. I think I could stay with sense and root / hack a fix to all of the above problems except for voice commands in car mode (the original topic of this post) – I have no faith HTC will ever fix this. I tried using google search / voice commands as a replacement, but could not get that to work either. If anyone has a workaround for this issue please let me know, as that would be the difference between me keeping and retuning this phone. I have spent a month trying to like this phone, but it has too many software issues (above plus no recent apps button, menu overflow button). My nexus one just works – no need to research hacks on XDA to fix HTC and T-mobile limitations.
IIHomieII said:
This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Click to expand...
Click to collapse
The Renovate ROM is fantastic you should really give it a try, the only thing that still does not work is the HTC speak app, but everything else you mentioned above I have not seen any problems with my mine.
They have updated the Renovate rom to 2.0 but I'm still running 1.0 with no issues at all.
I love the rom, the phone is fantastic except for the one issue with the voice dialer which eventually they will release an update for. You need to change the play/pause button when rooted to be the same key (key 200) if thats the problem.
I also set my forward track button to bring up Google search when long pressed, its great for driving to be able to long press a button on the stereo that I don't really use in that way already to do a Google voice search. I then use llama to return back to car dock mode after 20 seconds so that way I can get my results read to me from Google through the JVC so then it automatically goes back to car dock mode after long pressing the foward track key.
I can verify the same behavior. I came in looking for a MacGyver fix for the dock slipping and found this. When just connected to my headset no issues, but also add the car stereo in the mix and even with my headset I get the endless delay. I have always flashed my phones as soon as possible but with this I think I am going to wait and see what ROMS the senseless edition might bring that sounds imminent. Although I think I may be the only one who LIKES blinkfeed.
I like blinkfeed too.. I know some people complain about it, it's a sweet feature if you ask me but can't please all the people all the time..
I've now also an issue with my dock in that when I dock the phone it goes in to car mode, but then straight away opens up "Display Settings" even if i go "home", a few seconds later it opens it back up. Annoying, don't want to do a factory reset just yet.
Hi, I've got this issue too on my European HTC One with plantronic Discovery 975 headset

S-Voice and Bluetooth (on but not connected)

Hey All,
So, I've been searching all over for an answer to this, I've found a lot of information about S-Voice's problems being used over a bluetooth device but I haven't been able to find any direct discussion of the issue I'm experiencing.
What I've found is that when I have S-Voice's voice wake-up feature enabled, it'll work totally fine with bluetooth off. However, as soon as I toggle bluetooth on the wake-up feature just completely stops working. I don't even need to be connected to a device, as long as bluetooth is on S-Voice Wake-Up does not work. I can manually launch S-Voice and it will hear me just fine, but saying the wake-up command does nothing. As soon as I toggle bluetooth back off, it'll wake up again just fine. I do get that with a bluetooth device connected the microphone on the device needs to be active, so I could understand if this was happening while I was paired with a headset or something, but it seems really odd to me that just having bluetooth on at all would disable the wake-up command feature.
I did try Ok Google and found that it works whether bluetooth is on or off, but I really like the increased functionality that S-Voice offers and I think that for the most part the updates Samsung has done on it are great, so I'd like to get this working if possible.
Has anyone else experienced this, either on the Note 4 or on any of the other Galaxy devices? Anyone have any ideas or solutions?
Thanks!
I'm having the same issue with svoice, thought it was just the bluetooth in the car at first til I red your post
Widespread
I've got exactly the same problem.... Lovely new note 4 which is forcing me to use my hands on the phone whilst driving... Samsung need to think about this.
Apparently an issue for a few years due to Bluetooth /svoice conflicts, but not acceptable to leave it unaddressed.
I can still use my car system to skip music tracks on the phone, or dial numbers from the car stereo touch screen, but surely this is one of the most valuable areas for voice control?!
Bluetooth off then everything works fine, but Bluetooth on and svoice just fails. No wake up or voice recognition.
I don't use a headset, and the car doesn't have an inbuilt mic, so phone mic is used for calls (which is still fine incidentally.. Only svoice which is screwed.)
Looking forward to someone finding a simple solution to this, as I have spent hours in the menus trying to make a difference but Samsung might have just let us down I'm afraid... And if that's the case then I look forward to hearing them fix it, and update our ware to get everyone on track again.
Resolved and simple
After much fckin about I managed to get this sorted and the answer is simple..... You can't have both apps always trying to recognise the voice all the time.
Go to the settings for ok Google and voice detection then always on... Uncheck it and suddenly svoice is working again... On my way to the car for final checking now,but preliminary checking says all should be good.
Nope
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
When driving, set to hands free mode, this allows use of svoice on bluetooth
Ooof said:
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
Click to expand...
Click to collapse
Note 4 and above have it listed as car mode.
svoice works perfectly with blue tooth when car mode is enabled.
Set it up at home before you use it the first time.

Categories

Resources