I have a quesiton for those of you who know more about this stuff than I do. Ever since I have installed a custom FROYO rom on my aria, the wired headset will no longer open voice dial when I long press the button. It opens the music app instead. Not even my stock HTC headphones will open the voice dialer. IS this an issue with FROYO? was it created this way intentionally, or is there a way I can fix it? TIA for any help you can offer
utefan42 said:
I have a quesiton for those of you who know more about this stuff than I do. Ever since I have installed a custom FROYO rom on my aria, the wired headset will no longer open voice dial when I long press the button. It opens the music app instead. Not even my stock HTC headphones will open the voice dialer. IS this an issue with FROYO? was it created this way intentionally, or is there a way I can fix it? TIA for any help you can offer
Click to expand...
Click to collapse
I would think that this would be a configuration setting that can be modified. They may have changed the default setting to launch the music player instead of the voice dialer, but you may be able to change this via Settings.
I think I am getting to the bottom of this.......
From what I understand......the phone itself is choosing to prioritize mixzing over voice dial.......From what I understand you can use an app called autostarts to adjust the heirarchy within the phone...however, I am not brave enough to attempt it as i don't really have any script writing abilities, nor do I understand them. If anyone could talk me through it I would be grateful. I also downloaded choice dialer.....long press will open that, but it also still opens mixzing at the same time so it doesn't really run smoothly...why apps don't have options for button presses on single button remotes is beyond me...of course I have never created an app so I probably shouldn't be throwing around suggestions without first knowing the difficulty involved.
What ROM are you running? I have ran liberated and CM6 Roms and havent have this issue with either. It could be a bug, by now we would have heard this more often.
Except for my Supertooth, I use the OEM wired headset without any issues. Sorry.
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
Ok guys so the question has been asked a couple of times on XDA and there is still no viable solution. Maybe a Nexus section would be better to post and work on this.
I'm wondering if there is a solution or workaround to disable the built-in Google Voice Dialer that is launched from the lock screen when pressing the action button on a bluetooth.
When the phone is unlocked the action button on the Bluetooth typically launches Google Now, which is perfect. BUT I want to be able to Launch Google Now from the lock-screen using the Bluetooth action button, and NOT the crappy Google Voice Dialer.
The closest thing I've seen that allows this to be done so far is: Bluetooth Launch.apk from the PlayStore.
BUT this app has one major flaw.. when the headset button action is changed to com.google.android.googlequicksearchbox.VoiceSearchActivity, which is what is required to launch Google Now, the phone never sleeps/locks.
If this action>assign could be written and still allow the phone to sleep and lock, it would be ideal.
I was hoping that there would be an Xposed module to disable to Google Voice Dialer, but this has not been created as of yet.
Any help would be much appreciated and thanks will be given.
Get rom toolbox pro and take it out or freeze it. Simples
Ten min cutoff app.
I wish that when I click the green dial button in my car kit it will launch Google now.
Has anyone done that?
Is it possible?
eranyanay said:
I wish that when I click the green dial button in my car kit it will launch Google now.
Has anyone done that?
Is it possible?
Click to expand...
Click to collapse
I hope it will be possible... I tried "Ok Google" and then everything stopped... and the phone seemed to freeze (except for when I pressed the back button and everything resumed)
Just like you (yes it was me that also replied to your post on the Parrot UK forum ) I use the MKi9000... as you might have noticed, I wasn't very pleased with the (lack of) answer from Parrot... hope to hear from them soon.
Hi Mormel,
Yes I figured it out, yet since of the big lack of help in Parrot forums i didnt bothered to update there, as I dont do it now (doing it here instead)
anyway, Once your parrot has no contacts it will instantiate google now voice recog., so you need to erase them.
The quickest is just reset the parrot - do long press on both scroller wheel + End key, it will do it.
then, never sync contacts ever again
Now when you press the green dial button, it will be google now.
the annoying thing is, atleast on my phone (xiaomi mi2 running KK), that I need to manually quit the google now, as next clicks will open it with the state it was before, with the search inside and wont start the voice recog. again.
Seeing as the OK Google from any screen is not currently working I have been trying to find a way to wake the device using S voice and having Tasker kill S voice and open Voice Search. I am a Tasker novice and am looking to see if anyone has any ideas. I am currently unrooted which I think may be why it is so unreliable.
I have made a profile that when S voice opens it is killed and Voice Search is opened. I also tried it with the Voice Input service opened. It works occasionally, maybe 1/10 times.
Any input is welcomed.
atvman77 said:
Seeing as the OK Google from any screen is not currently working I have been trying to find a way to wake the device using S voice and having Tasker kill S voice and open Voice Search. I am a Tasker novice and am looking to see if anyone has any ideas. I am currently unrooted which I think may be why it is so unreliable.
I have made a profile that when S voice opens it is killed and Voice Search is opened. I also tried it with the Voice Input service opened. It works occasionally, maybe 1/10 times.
Any input is welcomed.
Click to expand...
Click to collapse
I got OK google back after disabling anything to do with S Voice. I put the Google search widget on the top of each screen and now get OK google from every screen
As said in another post you can start Google now with s-voice without the need of tasker.
As S-Voice allows you to say something without waiting for it to listen you can say "<wakeupcommand> Start Google". I'm for example using "Galaxy Start Google". According to someone else you can also say "Galaxy Voice Search".
Both are starting Google Now and will listen to your voice without any button presses and even when the phone is locked.
whitepaw said:
As said in another post you can start Google now with s-voice without the need of tasker.
As S-Voice allows you to say something without waiting for it to listen you can say "<wakeupcommand> Start Google". I'm for example using "Galaxy Start Google". According to someone else you can also say "Galaxy Voice Search".
Both are starting Google Now and will listen to your voice without any button presses and even when the phone is locked.
Click to expand...
Click to collapse
Confirmed the galaxy voice search command works.
This is a great alternative until okay Google gets fixed. thank you so much!