I am searching but have not lucked up on the correct search words for an answer...
New Verizon HTC6800 updated the 3.12 and radio 3.39. I noticed voice activation was not on the phone so I searched and found a thread that said add:
Cyberon_Voice_Speed_Dial_v1.2___BT_Fix.cab
So first was that correct? OK ,I did that and got voice command back to make calls holding the device. What I cannot do which I could do with the OEM was:
Turn on my Jaw Bone BT headset (phone BT is on)
Press the button on my BT set
(OEM setup) Would open the voice command box and I speak the name "wife"
Now on the new setup ROM 3.12 when I press the button it goes to the phone screen where I can dial a number which I do not want. I am sure there is a easy fix and hate to waste a post so can someone share that with me. I want to be able to press the button on BT set and hear the beep in my ear so I can speak a command to call a number?
Thx
Sounds like you want Microsoft Voice Command?? Not the Cyberon Voice Dialer. Cyberon requires self created voice tags if I remember correctly...MSVC just requires you to push your BT headset button and speak the command.
is that my only option....anyone else...vets???
What did you end up doing about this?
Is there any to get rid of the automated speach recogniztion other than building a custom rom without it? I really like using the cyberon voice speed dial but I can't. I installed it and made voice tags but everytime I press the button on my bluetooth the asr program starts intead. I have gone into the voice command setting and disabled it for contacts and phone but that didn't help.
Hello, I have a problem with my Voice Talk, normaly you open it by double tap the home button. But sometimes it's enough with just one click. I tried to update my phone and reset it but nothing seems to work. Does anyone know how "uninstall" Voice talk or something like that?
Hi,
As the title suggests, is there any way to disable the bluetooth last number redial functionlity.
I have a Xperia Mini Pro (SK17i, Bootloader unlocked, Rooted) with a Samsung HM1700 bluetooth headset. The headset has a button for answering / ending calls and this same button also has the last number redial functionality, ie when not in a call, pressing this button redials the last dialed number.
AFAIK, the headset just sends a signal to the mobile which then calls the last dialed number.
What I need, is to disable only the bluetooth redial functionality on my mobile.
[ BUMP]
Any suggestions anyone?
Sent from my SK17i
BUMP
Sent from my SK17i
You can try the app Smart Bluetooth Headset from the Play Store.You can not only disable it but also make it do something useful
Since the app "Smart Bluetooth Headset" does not work reliably for me (e.g. not activated by default after program start) I use this now: Go to Bluetooth settings and find your headset. Uncheck Phone to disable the headset from being used for voice calls.
Use an app on your smartphone to enable bluetooth on call and disable after call. There are many apps for this, for example bluetooth on call: https://www.addictivetips.com/mobil...ndroid-bluetooth-for-bt-headset-during-calls/
In addition to solving this problem your phone battery will last longer.
Regards Rob.
Necroing this thread to say that I tried "Headset Button Controller" and "Smart Bluetooth Headset" apps, both free versions, on my rooted HTC10 running Oreo 8.0 with a paired MPOW Crescent. Both apps worked, in slightly different ways.
Headset Button Controller places a dummy call on the call log. Activating the redial function on the headset (double click the answer/end call button on the MPOW Crescent) makes the phone call to the dummy thing, and a little window shows asking for a valid number. No call is actually made.
Problem is, if a valid call is made (for example, you call your boss or a friend), the dummy call setting must be reenabled again manually in the app - meaning that, if you make a valid call, the next time you activate the redial function on the headset, it will call the valid call.
Smart Bluetooth Headset works basically the same way, except that, instead, the redial attempts to call the * or *1 numbers. These attempts open the call window but close it right away, and immediately activate whatever you set the redial function to do. I set mine to run "Tasker 01", but didn't set what "Tasker 01" is. So, what my phone does when I (accidentally) activate the redial function on my headset is open and close the call window, and then return an onscreen self-fading error notification stating that Tasker 01 could not be found.
Best of all, the settings stick - meaning that, if you make a valid call, the redial function will still attempt to dial the * or *1 numbers, as long as the Smart Bluetooth Headset service is active.
So, in my experience, the Smart Bluetooth Headset app works the best.
Of course, I could just turn the headset on and off, whenever I need. It has a physical on/off switch, and immediately pairs with the phone (if previously paired) when turned on.
Awesome guys, thanks! Well written instructions Kam0laZ So nice when a solution presents itself effortlessly. Just turned on my new Bluetooth piece and INSTANTLY ( double tapping by mistake Just to get the damn thing in my ear hole) redialed my (dreaded) Ex BF..... TWICE! .... Noooooooo! Damn it! *Fists shaking furiously* And the ball was only in MY court but for a fleeting moment... wah wah
Could you share a link for these two apps? I've been trying to find them on the Google play store..
Unfortunately, redialing is no easy feat (like instead the stupid "media player opens" case).
https://github.com/LineageOS/android_system_bt/blob/lineage-17.1/bta/include/bta_ag_api.h#L319
https://github.com/LineageOS/android_system_bt/blob/lineage-17.1/btif/src/btif_hf.cc#L423
https://github.com/LineageOS/androi...e-17.1/jni/com_android_bluetooth_hfp.cpp#L194
https://github.com/LineageOS/androi...luetooth/hfp/HeadsetNativeInterface.java#L118
https://github.com/LineageOS/androi...ndroid/bluetooth/hfp/HeadsetStateMachine.java
https://github.com/LineageOS/androi...droid/bluetooth/hfp/HeadsetService.java#L1331
So, like, simply put.. You have a bluetooth HFP device that sends an AT+BLDN command to your phone.
The bluetooth stack runs DialCallCallback in the bluetooth package, which getLastDialledNumber from your phonebook, and then sends an ACTION_CALL_PRIVILEGED intent to the rest of the phone with the number to call.
Where could we act?
Perhaps if you could force some sort of HSP-only mode, you could avoid all the extra cruft but I'm not aware of any way to do so.
Similarly, there are plenty of ways to "directly hack the code", but I don't think anybody has got such a solution yet.
So my efforts have focused on disturbing the phone dialer from getting the action to call.
The problem is, "install-only" permissions aren't changeable. And without root you can't even hope to revoke android.permission.READ_CALL_LOG. And without xposed you can't even block intents.
(if you have either of these though, something could be done I guess?)
So long story short, well, Smart Bluetooth Headset still sounds like the best option.
It's no longer available in any official place as already stated.. But luckily enough it was open source!
We'll see.
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
kounelii said:
kounelii said:
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@kounelii how do you configure the macro so that it only applies to calls made from headphones when last number redial is executed?
kounelii said:
Hi,
Install macrodroid app from play store.
Create a macro as follows:
Trigger:
Call/sms -> call outgoing
(Select number(s) from the 3 bullet menu that appears, it is the 3rd)
Enter * (meaning all calls)
Action:
Phone -> call reject
Save the macro.
That's it !!!
Keep in mind to let the macrodroid app on the white list of any battery saver app you may have installed or is built in the android it self (eg xiaomi phones) easy to make it unrestricted to not be killed by any task manager.
Simple solution, minimal battery drain, no wake up the phone to check. The macro runs only on call intent
Thats's it.
Thanks
Click to expand...
Click to collapse
Prior to the latest update to Google Search 3.5.16.1262550 a couple weeks ago, I used to be able to do a long press on my BT headset to bring up Google Now, which let me say, "Call Joe Blow home" and it would make the call to his home number. Now it brings up Google Dial which tells me to say "Call someone" but pops up with a numbered list of the cell, home, and work numbers on the screen that I either have to touch to choose the one I want, or say, "Select Two" to dial his home number. This requires that I either touch or look at the screen to make a call, which totally defeats the purpose of "hands-free" calling.
I have switched back to S-Voice for now, which I hate because she talks too much before I can actually make a call, but at least I don't have to dig my phone out to push or see which phone I want to call. I hope someone can help us get back to BT dialing the way it used to be.
This is on a Sprint Galaxy Note 3 running KitKat, but I imagine this is affecting all phones.
Yes I have a note 3 kitkat and Google search issue is affecting my phone as well. Instead of Google now voice prompt when pressing headset hard button on my LG bluetooth headset....Goople dial is not default which sucks!
Bump! Surely someone must use Bluetooth dialing from a headset and noticed this major change besides the two of us. Please help if you have any ideas to revert Google Search to work the way it used to.
Bump again! Doesn't anyone else use their Bluetooth headset to initiate calls?
I think I have finally found an acceptable workaround using Bluetooth Launch from the Play Store. Install the app and follow the directions as described in this thread: http://forum.xda-developers.com/showthread.php?t=2794883
Step one shouldn't be needed as when you long press, it will detect the new app and let you select Bluetooth Launch as the default.