My Galaxy s II keeps going into voice command when I pressed the home button to exit my program and access my home screen. I know that one can access voice command by pressing the home button twice but this is different. But I'm very sure that I only pressed my home button once and it goes into voice command. I want to do some troubleshooting. anyone knows how to disable quick acccess into my voice command?? Many Thanks!!
mix1987 said:
My Galaxy s II keeps going into voice command when I pressed the home button to exit my program and access my home screen. I know that one can access voice command by pressing the home button twice but this is different. But I'm very sure that I only pressed my home button once and it goes into voice command. I want to do some troubleshooting. anyone knows how to disable quick acccess into my voice command?? Many Thanks!!
Click to expand...
Click to collapse
Hey,
I experienced exactly the same thing... Sometimes I even wondered if the first press was not recognized, and then the 2nd, even being seconds later, was regarded as double-press.
Anyway, I did not succeed in breaking down the issue the right way. The only solution I found was disabling Voice Command using Titanium Backup (freezing the app). This effectively prevents it from loading...
See my post here for how to: http://forum.xda-developers.com/showthread.php?t=1161333
even I have faced this... Seems like a code bug
Galaxy Nexus
Android Version: 4.2.2
Steps to reproduce the problem:
- plug in headset
- lock screen
- press headset button for several seconds
What happened:
- No reaction, Google Now / Voice Actions not launched
- Manually unlock screen
- Long press with unlocked screen correctly launches Voice Search
What you think the correct behaviour should be:
Long press of headset button should launch Google Now / Voice Actions even with locked screen. Having to dig the phone out of your pocket in order to launch Voice Actions with a headset e.g. to place a call kinda defeats the purpose of using Voice Actions in the first place.
Adding insult to injury: long press is not broadcast to other applications because of Google Now, so it can't even be put to good use e.g. as volume control.
This was open and ignored by code.google.com Issue 48616
I also have the same problem. The restriction is not due to the lockscreen, apparently. If you disable the option "Power button immediately locks screen" and set "Automatically lock screen after sleep" time to a long enough time, still the long press doesn't work.
It works fine only when screen is on and unlocked. Weird. There is no point of this shortcut if our phone is unlocked and on, because in such a scenario, if headset is connected and phone is awake and unlocked, it means the phone is in our hands. And if it is in our hands, we can just press the button on the Search widget instead of long pressing the headset button. This is pathetic.
rhoadster91 said:
I also have the same problem. The restriction is not due to the lockscreen, apparently. If you disable the option "Power button immediately locks screen" and set "Automatically lock screen after sleep" time to a long enough time, still the long press doesn't work.
It works fine only when screen is on and unlocked. Weird. There is no point of this shortcut if our phone is unlocked and on, because in such a scenario, if headset is connected and phone is awake and unlocked, it means the phone is in our hands. And if it is in our hands, we can just press the button on the Search widget instead of long pressing the headset button. This is pathetic.
Click to expand...
Click to collapse
I'm affected by this as well.. I love calling upon Google Now from the headset, but sucks that I have to first unlock the screen on the Nexus 4 to do this. I'm OK with this being off by default, but users should be offered an option to turn this on while screen is locked.
Levistras said:
I'm affected by this as well.. I love calling upon Google Now from the headset, but sucks that I have to first unlock the screen on the Nexus 4 to do this. I'm OK with this being off by default, but users should be offered an option to turn this on while screen is locked.
Click to expand...
Click to collapse
Android apparently wants you looking at the screen so you can see the advertisements, so much for being the "open" OS.
So, guys, still no solution to fix this???
Darksydecad said:
Galaxy Nexus
Android Version: 4.2.2
Steps to reproduce the problem:
- plug in headset
- lock screen
- press headset button for several seconds
What happened:
- No reaction, Google Now / Voice Actions not launched
- Manually unlock screen
- Long press with unlocked screen correctly launches Voice Search
What you think the correct behaviour should be:
Long press of headset button should launch Google Now / Voice Actions even with locked screen. Having to dig the phone out of your pocket in order to launch Voice Actions with a headset e.g. to place a call kinda defeats the purpose of using Voice Actions in the first place.
Adding insult to injury: long press is not broadcast to other applications because of Google Now, so it can't even be put to good use e.g. as volume control.
This was open and ignored by code.google.com Issue 48616
Click to expand...
Click to collapse
Levistras said:
I'm affected by this as well.. I love calling upon Google Now from the headset, but sucks that I have to first unlock the screen on the Nexus 4 to do this. I'm OK with this being off by default, but users should be offered an option to turn this on while screen is locked.
Click to expand...
Click to collapse
vivekiny2k said:
Android apparently wants you looking at the screen so you can see the advertisements, so much for being the "open" OS.
Click to expand...
Click to collapse
Elastep said:
So, guys, still no solution to fix this???
Click to expand...
Click to collapse
Please check this link
rhoadster91 said:
Please check this link
Click to expand...
Click to collapse
I got so fed up I wrote my own app. If you have s voice, the phone wakes up on long press and My app takes over. I an releasing another version tomorrow. I still have to update the video demo.
http://forum.xda-developers.com/showthread.php?t=2289104
There's a solution
Darksydecad said:
Galaxy Nexus
Android Version: 4.2.2
Steps to reproduce the problem:
- plug in headset
- lock screen
- press headset button for several seconds
What happened:
- No reaction, Google Now / Voice Actions not launched
- Manually unlock screen
- Long press with unlocked screen correctly launches Voice Search
What you think the correct behaviour should be:
Long press of headset button should launch Google Now / Voice Actions even with locked screen. Having to dig the phone out of your pocket in order to launch Voice Actions with a headset e.g. to place a call kinda defeats the purpose of using Voice Actions in the first place.
Adding insult to injury: long press is not broadcast to other applications because of Google Now, so it can't even be put to good use e.g. as volume control.
This was open and ignored by code.google.com Issue 48616
Click to expand...
Click to collapse
You can enable it by, either
1) setting the unlock pattern to none(that will completely disable locksreen, and you can use the google now feature even in screen off)
2) setting the unlock to any pattern and uncheck the "power button instantly locks screen" - in this way you can use the the feature withing the time you specify in the lock screen
CellSmart! said:
You can enable it by, either
1) setting the unlock pattern to none(that will completely disable locksreen, and you can use the google now feature even in screen off)
2) setting the unlock to any pattern and uncheck the "power button instantly locks screen" - in this way you can use the the feature withing the time you specify in the lock screen
Click to expand...
Click to collapse
Sorry, I have the same problem, I tried this, but this doesn't work...
Any ideas?
Cheers,
--
Steph
Me too
I'm also in the boat of wanting to access Google now while the phone sits in my pocket and I'm wearing headphones. I can kinda understand why they disallow this (so a thief can't make calls on your dime), but it'd be very nice to at least launch apps.
Even xposed's app settings, with Google search allowed to show on the lock screen, doesn't make it happen. I just get a message saying I need to unlock my phone.
The only idea I currently have to launch it over the lock screen is to use auto voice with Tasker. Perhaps I could get it to launch/listen with a triple tap (because long press is locked up by Google now) via degauss. I just hope it all works over the lock screen. I'll update if/when it happens.
tcg-2 said:
I'm also in the boat of wanting to access Google now while the phone sits in my pocket and I'm wearing headphones. I can kinda understand why they disallow this (so a thief can't make calls on your dime), but it'd be very nice to at least launch apps.
Even xposed's app settings, with Google search allowed to show on the lock screen, doesn't make it happen. I just get a message saying I need to unlock my phone.
The only idea I currently have to launch it over the lock screen is to use auto voice with Tasker. Perhaps I could get it to launch/listen with a triple tap (because long press is locked up by Google now) via degauss. I just hope it all works over the lock screen. I'll update if/when it happens.
Click to expand...
Click to collapse
I found a fix for this (yes I know this is old but anyway). You have to install the xposed module "xposed additions" and set the long press headset button to unlock the phone. when the phone is unlocked you can simply long press the button again and google voice search will come up. this way you have to long press the button twice but at least it works
spiderflash said:
I found a fix for this (yes I know this is old but anyway). You have to install the xposed module "xposed additions" and set the long press headset button to unlock the phone. when the phone is unlocked you can simply long press the button again and google voice search will come up. this way you have to long press the button twice but at least it works
Click to expand...
Click to collapse
thanks spiderflash, this would work but fully unlocks the phone instead of just the Google now search, guess we have to wait for google to fix it.
I've got it
I've developed a good way to do this now. I've had it for the past 2 months or so, but I was waiting until I could go 2 weeks without a hitch.
You need 4 apps: tasker, secure settings, headset button controller and (if you don't for some reason have it) Google Now.
1. Tell hbc to perform a Tasker task (whatever you want to name it, e.g. 'launch voice search') for 3 clicks
2. Task should do the following: turn screen on, keep screen on at least 15 seconds, launch Google voice search [this is where you say your command, e.g. 'play some music'], lock screen, turn screen off.*
If you want to make this slightly less complex, you can simply have it turn the screen on, then you have to manually say 'OK Google,' then say your voice command (as long as you have Google Now available from the lock screen), but I'm trying to get directly to voice search, which won't launch directly if the screen is locked.
For some reason clicking the headset button 3 times sometimes doesn't trigger the first time after you plug in your headset (but works fine once it's triggered the first time until you unplug and re plug). Sometimes you need to do it twice if you don't hear the little Google Now voice beep.
So I hope this helps, but if you develop a better way to do this, please let me know.
* This is because, before I added this, motion in my pocket with the screen on caused it to swipe to the camera, where it will not turn off by itself. It stayed on for a good half hour in my pocket that day.
I have found the solution.
I had three Assist Apps . When I long pressed headset button while screen unlocked, it asked me to choose between Google, Autovoice and Tasker Secondary. I chose Google. From there on Assistant wakes up on long press headset button when screen is on.
When the screen is off, and you long press the headset button the same options popup but you don't see because screen is locked. Now Assistant can't run untill you set the default assist app on lockscreen.
Solution:
Lock your screen.
Long press headset button.
Within 3 sec pressing quickly unlock the phone.
You will see the dialogue asking to choose assist app.
Choose google.
Solved.
I'm looking for the simplest 'eyes-free' way to perform a voice command with the phone asleep. So my basic question is: can you execute a voice command, e.g: "Send message to Chris", without having to turn on the screen, unlock the phone, and double tapping the "Home" icon and then clicking the google-now mic?
I want to be able to perform a voice command without having to really look at the device. On the Iphone 4s, I can send a message or call a contact relatively eyes free by just holding down the home button and saying the command. This ability is a big convenience when you're on the road a lot and I can't figure out how to do this relatively simple action on the One.
If there's no default action, is there an app that accomplishes this and maybe lets you map the soft keys? Or put a widget on the lock screen to this?
Thanks for any tips or comments!
PS- since the Samsung SIV has a physical home button, is it doable on that phone?
I've got a rooted Android 7.1 device (with LineageOS).
I want to use Termux to force the screen to immediately turn off and lock, in such a way that I can usually keep the setting "Power button instantly locks" set to false so that pressing the hardware power button will turn off the screen but not lock (except for the "Automatically lock" after 30 seconds etc).
I know there is the Device Manager API that would let an app do this - but I'd like to do it from Termux if possible (so that I don't need to make an app).
I can run this in Termux:
Code:
su -c "/system/bin/input keyevent 26
and get the screen to turn off, but since this is exactly like pressing the hardware button it will not lock unless I have the "Power button instantly locks" setting enabled.
What I'm thinking is, could I manually change the settings database to briefly enable the instant lock, then fire the key event, then turn the setting off again? Any other suggestions?
I found a reference ( groups.google.com/d/msg/android-porting/9aDv9MPWx4M/KxPHoglH7EUJ ) for changing the settings using an sqlite3 command, but I don't know which setting is instant lock would be (or if this is safe to do in newer Android versions).
Partial workaround
It doesn't solve the problem entirely, but I've found that using the "Smart Lock" feature sort of does what I want - keeping the phone unlocked when pressing the lock button.
I have set Smart Lock to enabled "On-body detection", so now while I'm holding the phone or have it on my person it won't lock when I press the lock button. I can force it to lock (and require the PIN) by first locking, then unlocking and pressing the padlock icon at the bottom of the lock screen.
This isn't quite what I wanted but comes pretty close, basically I can use the lock button to turn the screen off and can then also make my phone secure if I need it to be.
Is there anyway to disable apps? I remember on my note 9 being able to. Also is there anyway to change the bixby key to another action ?
Disabling apps - If they can be disabled normally then find the app under settings > apps and then click on the disable button. If you can't disable them normally either a 3rd party app can do it for you or else use ADB to disable the app. With the ADB method you need to have it installed on your computer, your phone setup and connected to the computer by USB cable, and the application package name you wish to disable.
The command you use in ADB would be along the following:
Code:
pm disable-user --user 0 {enter package name here}
So to disable the bixby wakeup service you enter:
Code:
pm disable-user --user 0 com.samsung.android.bixby.wakeup
I would suggest you disable apps using a 3rd party app to make things easier and simpler. I would suggest not uninstalling/removing apps via adb. If you remove the wrong thing you could end up creating more problems then solutions.
Remapping bixby key - You can also use 3rd party apps to do this. With the latest release of Bixby you can do this easily.
Open Settings > Advanced features > Bixby Key
Select single press or double press
If it isn't toggled already toggle the option under the single or double press selection you made. Then proceed to tap on the option you just toggled to open a new menu.
You can choose to open an app or run a quick command. Tap the gear icon to make the applicable selection(s)
Alternatively the website below can be used as a tutorial with pictures:
https://www.digitaltrends.com/mobile/how-to-remap-the-bixby-button/
Notes: There is a restriction with this option. While it does not actually disable bixby it does allow you to map it to either a single or double press.
Also you can not use a competing voice app when using this method of remapping the bixby key. That being said you can work around this by using an app like tasker which has a "Tasker Secondary" app feature. You create a task in tasker to open Google Assistant (for example) and set this to trigger when the Tasker Secondary app is opened.
I personally use that option with Google assistant since I run tasker for other things as well. I have bixby set for double press, but I rarely if ever use it. Single press launches the tasker secondary app, and holding the bixby button in lets me use bixby voice commands.