I've lost the functions of my home and search buttons . . . I thought I remembered testing long press voice search with long press when I was setting things up and it worked and the short presses of both buttons worked. I don't remember using a long press on the home button. As it is now a short or long press on home doesn't go to the home screen or bring up recently used apps. The search short and long presses doesn't bring up general search or voice search. I've tried clearing the data/cache for cyanogenmod settings and I've tried resetting ADW launcher to see if either of those were the culprits.
Any solutions?
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.
Hello. On every phone, if i hold the powrr button long inought, it will pop up a power menu. But on meizu, there is only 2 options (power off, reatart) and i found app, that have more options (recovery, turn off sounds, etc). So is possible to somehowe stop the menu function and replace it with open app function? I know that it sounds like an idiot idea, but for me it would be great. Thanks for your time and answers.
P.S.: i was thinnking about macrodroid, but it have only power button toggle (3-5 times) but every device i know lock screen after 1 time pushing power button. Sr for my english
Hi community, i'm looking a way to activate the long press functionality using the task button (the one next to home that is not back button). I just update my phone Xiaomi to android 8.1, i use a few aplications (critical for me) that require a long press on that button, i imagine that is some config missing on build.prop
Remember, always attack ideas, never people.