On my bluetooth earpiece, tapping the button on it brings up the music player instead of voice dialing. Is there any way to fix/override this behavior (yes, I am rooted)?
thats weird cuz when i press the pause button on my ipod headphones it brings up dialer lol. i think htc got something backwards...
In my case it did the same thing on my old Env3, but I was hoping that there was some way to configure it on the Thunderbolt (even if it requires root).
It is setup for multi button-multi function not single,not sure how to change it on the custom roms but htc tech support will walk you thru it
Posted from my Nokia V560
I have a Motorola Roadster bluetooth car speaker.
It works fine for incoming calls and plays music over FM.
Can I setup things so I can make hands free outgoing calls,
just push a button on the Roadster and say call home, etc ?
Seems to work at times but once the Note's screen locks, it stops working...
I've noticed the same problem with my Jawbone ERA. Actually, the ERA keeps disconnecting and later reconnecting itself while in use. It doesn't do that with any of my other devices. :/
But as for your problem...if you charge your phone while it's in the car, and set the Note to open Voice Talk when a Bluetooth device is detected, as soon as you turn on your Bluetooth, VT will stay open and give you instant access to a variety of voice commands. If you enable driving mode, it will read incoming messages to you, and then allow you to reply hands-free. You can also make outgoing calls. If you want, you can also enable a mode so that it will listen for a keyword and you don't have to press a button at all, but that would add to the battery drain a bit.
I know that's not what you wanted necessarily, I'd also like the same thing...mostly so I can keep the phone in my pocket and operate it remotely via headset. But I have yet to get that to work reliably.
EDIT: Okay, I just did some testing and actually fixed my ERA's disconnection issue by doing a factory reset. But the phone WILL NOT take voice commands when the screen is off, or when it is at the lock screen. And for some odd reason, if I have Voice Talk open and I press the button on my headset, it beeps and the phone closes Voice Talk. Every time. If Voice Talk isn't open, when I press the button on my headset it opens Voice Talk and responds to my commands as it should. Very strange.
Thanks for the reply.
Does yours work with a Pin lock?
When I have a pin protected lock screen,
Voice Talk works with the Roadster button but only when the Note is unlocked.
Once the lock screen times on
it does not detect the voice command button press on the Roadster.
If I remove the pin on the lock screen it works all the time but my phone is unprotected.
I'd like the voice button on the Roadster to work even when the pin lock is used and active, does yours?
Oh! I didn't even think of that...I do have the PIN lock activated. You are correct, it works just like it should when there is no PIN code on the device. I suppose it's by design, but it sure would be nice if they had an exception one could enable for voice input. Well at least I know now, haha.
I picked up an HBS-730. It sounds good, the Call button works fine for picking up a call or last number redial (by two short presses of Call) but when I long press it I don't get the voice dialer (or any other voice app).
Is there a file in System that I need to edit or run? I do have the LG and Google voice components installed. I've also tried unpairing and repairing the headset.
On a long press I end up with a roughly half second "beep" in the headset.
Alternately, anyone know of an app that captures a BT Call longpress, that you can then assign an app to?
(It sounds like trapping a longpress is something done in a .jar file, not a case of just touching the .kl files)
Thanks!
Hmmm....
Check your BT volume.
Volume is fine on calls, and playing music.
Headset Mic also works fine on calls and for voice commands if I manually launch voice dialer or Google search.
It just seems that a long press of the Call button isn't properly launching voice dialer, that's why I'm looking for an apk or a setting to edit.
markfm said:
Volume is fine on calls, and playing music.
Headset Mic also works fine on calls and for voice commands if I manually launch voice dialer or Google search.
It just seems that a long press of the Call button isn't properly launching voice dialer, that's why I'm looking for an apk or a setting to edit.
Click to expand...
Click to collapse
The LG voice dialer is bland, try this. I know it works.
https://play.google.com/store/apps/details?id=de.itdevcrowd.voicecommand&hl=en
I tried the VoiceCommand app from Play Store, unfortunately same problem. I don't get a voice ommand prompt, on either a single short press or a long press of the Call button on my BT headset.
A single short press does work to connect an incoming call, or disconnect, any a double short press does activate last number redial, so I believe my headset is overall working okay, but I am not hooking a voice command app at all. On a single short press nothing happens, and on a longpress I get a beep, but that is all.
Headset volume works fine, the mic works fine (if I manually launch VoiceCommand, whether the LG app or Google, it picks up fine), just that my phone isn't linking the Call button to launch any VoiceCommand app, on either a single press or a long press.
I disabled the lg voice command and use Google and it works for me
markfm said:
I picked up an HBS-730. It sounds good, the Call button works fine for picking up a call or last number redial (by two short presses of Call) but when I long press it I don't get the voice dialer (or any other voice app).
Is there a file in System that I need to edit or run? I do have the LG and Google voice components installed. I've also tried unpairing and repairing the headset.
On a long press I end up with a roughly half second "beep" in the headset.
Alternately, anyone know of an app that captures a BT Call longpress, that you can then assign an app to?
(It sounds like trapping a longpress is something done in a .jar file, not a case of just touching the .kl files)
Thanks!
Click to expand...
Click to collapse
markfm said:
I tried the VoiceCommand app from Play Store, unfortunately same problem. I don't get a voice ommand prompt, on either a single short press or a long press of the Call button on my BT headset.
A single short press does work to connect an incoming call, or disconnect, any a double short press does activate last number redial, so I believe my headset is overall working okay, but I am not hooking a voice command app at all. On a single short press nothing happens, and on a longpress I get a beep, but that is all.
Headset volume works fine, the mic works fine (if I manually launch VoiceCommand, whether the LG app or Google, it picks up fine), just that my phone isn't linking the Call button to launch any VoiceCommand app, on either a single press or a long press.
Click to expand...
Click to collapse
Did you ever get to the bottom of this as I am having the same issue. On my Xperia Z2 I can choose what I want to activate when I press the call button on my car kit but on the G3 it mutes my radio but never brings anything up on the phone.
I have also tested it with a different bluetooth kit and it still doesn't do anything so it is definitely a phone issue.
I froze some files and maybe froze something I shouldn't have, but factory resets are not doing any good for me as they seem to only partially reset my phone (Frozen apps still do not appear even after factory resetting and also flashing a totally new firmware!)
My G3 will not allow me to Voicedial and I was hoping someone with an operative G3 on their car kit could download a program called Clear Defaults or Default App Manager Lite and advise me what program they have as Default for Voice Dialing (I am not too sure what the heading is exactly as my G3 doesn't show it at all)
Clear Defaults
https://play.google.com/store/apps/details?id=com.zealdroid.cleardefaults&hl=en
Default App Manager
https://play.google.com/store/apps/details?id=com.appiator.defaultappmanager&hl=en
I am trying to get troubleshoot this issue instead of returning it as I bought mine from eBay.
Is there actually someone who has the voice-dialing in his G3 working? I'm waiting also for a solution.
Voice dialing with Google works fine on the phone for me. Via Bluetooth in my car is also fine. nothing in default apps mentions voice dialing.
Oooooo, the voice dialer in the phone.... mine does not work either.
Does there happen anything when long-pressing the button in your car/on your Bluetooth headset?
Long pressing the button does nothing in the car or not.
I am trying to use the voice command feature w/my Galaxy S4 w/4.4.2 (KitKat, NK1).
Voyager and Edge headsets have a feature where a 2 second press on the Mute button when not in a call will launch Voice Search on the phone so you can use voice commands from the headset (e.g., "Call xyx on mobile") to make calls.
While connected to my phone but not in a call I press the Mute button for two seconds. I hear a brief low tone (from the headset) and then nothing - I never hear the Google Voice search tone/prompt coming from the phone through the headset.
Everything is configured properly as far as I can tell:
1. Audio over Bluetooth and requests over Bluetooth are enabled in Google Search.
2. Bluetooth commands are enabled in S4 settings when the phone screen is locked.
3. Phone is connected via BT to headset.
4. Legend has been granted access to contacts and call history. (Not sure this even matters for this issue.)
5. Firmware has been updated on the Legend to the latest and rebooted the headset and unpaired and paired it again.
I tried disabling S Voice (I never use it, but went ahead and turned it off) and that didn't help.
FWIW, I get the same results with the Edge headset as well. (Also updated to current firmware.) Since both fail I'm thinking that this is a Samsung issue.
Help! Any known work-around to get this to work. This makes the headset useless to make calls w/the phone in my pocket - I have to take my phone out, wake it up, enter my pin, and hit Home to go to the Google voice search prompt and then talk via the headset. Not exactly convenient.
Help! (And thanks!)
Holy Buttons, Batman. Figured it out.
<gulp> Operator error.
Was hitting the wrong button. Call button for 2 secs, not mute/voice command button.
Crawling back under my rock now.
Hi all,
Looking to see if its possible to set up either a N5 or G3 so that when it is unlocked the LED flash comes on automatically and the phone/app switches direct to the rear facing camera. I do not need the ability to use any other apps or take a video or picture - in fact it would be preferably if this is the only thing the phone could do when unlocked it with absolutely everything else disabled on the phone - maybe even with the touch screen disabled and it's woken and unlocked automatically by a press of the power button.
I will be recording the output via slimport/hdmi so all i really need the phone for is as a webcam / so the person viewing it can see what the camera is looking at.
Any help appreciated.