[Q] Long press headset does not start Google Now when screen locked - Android Q&A, Help & Troubleshooting

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.

Related

Challange! Lock Device On Power Off/screen Off.

I have been trying to Find a Macro Mapper or some kind of 3rd party ap to lock my device when i press the power button. The only work around at this time is to use Lock Device with 4 number pin and 0min lock setting. however i am tired of constantly pressing digits and would rather use native Lock Function that requires bottom left tap to unlock than middle right side tap to confirm unlock. However, it is only initiated from a Lock on screen tap.
IF anyone knows how to enable this lock by pressing the power button which is in my case on the right side of my mogul(PPC6800) that shuts off the screen and powers down to standby i would greatly appreciate it. this is also a replacement for S2U which has a few bugs with slide out keyboard and memory leaks.
Try this...
http://www.vijay555.com/?Releases:VJDeviceLock
there is a program by spb that has this funtion... I don't know the name of it but i will look around. I don't remember the specifics of it, but there was a check box that says to lock teh device when you hit the powerbutton (or anytime the display turns off)
i believe it is SPB mobile shell
"Device Lock
Spb Mobile Shell 1.5 improves usability of device locking. Now you can lock your device using a hardware key, soft key on Today or a shortcut. You can also unlock the device using only soft keys. When your device is locked the Now Screen shows you the most important information, so in most cases you don't even need to unlock the device. "
http://www.spbsoftwarehouse.com/about/pressreleases/2007/jun19.html?en
you can at least try it out and see if it does what you want.
damn i apparently didn't didn't read all of your post... so you don't want to use slide2unlock.. hmm i guess your best bet is to try spb mobile shell and play with the options to see if you can get it to do what you want -- unless of course someone wiser than me knows of something else.
::ignore below:::
it turns out that what i was really was thinking of was slide2unlock
http://ac.xenpage.eu/S2U2-0.99c-WM5.rar
(from http://forum.xda-developers.com/showthread.php?t=353008)
options:
lock when device wakes up --- on/off
lock when backlight turns off ---on/off
power off in --- (time in S)
but blank screen only -- on/off
blank screen on talk -- on/off
then it has some other options for how it looks -- but if you don't mind doing the slide bar to unlock the phone it will do what you want.

We Never Need Power Button power ON/OFF

Works for my MOTOROLA DEFY AND DEFY PLUS
Device admin tick the light lock apps
settings
lock setting
long press to lock set 2sec
unlock setting
1.enable the unlock function
2.press period for unlock set 0.5sec
3.screen on period 10sec
disable pocket mode period (it does not work)
working wiui,miui ,cm7,
LightLock apps
https://play.google.com/store/apps/d...senslock&hl=en
please press thanks button
ela1103 said:
Works for my MOTOROLA DEFY AND DEFY PLUS
Device admin tick the light lock apps
settings
lock setting
long press to lock set 2sec
unlock setting
1.enable the unlock function
2.press period for unlock set 0.5sec
3.screen on period 10sec
disable pocket mode period (it does not work)
working wiui,miui ,cm7,
LightLock apps
https://play.google.com/store/apps/d...senslock&hl=en
please press thanks button
Click to expand...
Click to collapse
I didn't understand a word. What exactly is this?
not working in my defy plus
i dont know why
can you make video to show us how it works
ela1103 said:
Works for my MOTOROLA DEFY AND DEFY PLUS
Device admin tick the light lock apps
settings
lock setting
long press to lock set 2sec
unlock setting
1.enable the unlock function
2.press period for unlock set 0.5sec
3.screen on period 10sec
disable pocket mode period (it does not work)
working wiui,miui ,cm7,
LightLock apps
https://play.google.com/store/apps/d...senslock&hl=en
please press thanks button
Click to expand...
Click to collapse
I'll be glad to press the thanks button(even if it doesn't work) only if I could understand what it meant.
From Google Play:
Description
This background service allows you to light on or off your device by proximity sensor. You just cover and release the sensor by finger, to switch your device's screen on and off.
Please activates the LightLock by "Setting" > "Location & security" > "Select device admin", and remember to inactivates it before uninstall it.
Use it and watch your battery drain fast
Now why would someone want anything like that.Unless your power button stops working.
How could you dont need it if you cant boot the phone without it
Actually you can boot phone without power button if you have 2nd init, plug in charger and wait for blue led and enter bootmenu, select boot, 2nd init.
LightLock kills your battery™
Sent from my MB525 using xda premium
Just use tap tap app.I use it and it works fine
Sent from my MB526 using xda premium
Tap Tap IS Worst Battery life .I Used First Tap Tap only But So Many Bugs .Lightlock Is Best For OUR DEFY BUTTON LIFE
Loool another thanks button runner up
If we used this app for along time could it damage the sensors ?
Sent from my MB526 using xda app-developers app
Threads about apps go in the Themes & Apps section
IT Could Not Damage The Sensors.iam using this apps 1year no problem

Can't receive calls, home button not working, can't lock.

My phone froze on me and I put out the battery but I noticed that :
1. I cannot receive calls. I can make calls, but when anyone calls me, it will ring twice on their end and then go to voice mail. My phone does not react at all.
2. My phone will not use the security grid. It will not enable either by widget or by going to the phones menu > security and enabling it. You can enable it, power phone off and back on and it goes right to the desktop. No lock screen period.
3. The home and search buttons on the bottom of the phone do not function. They vibrate like they are working but will they will not do anything.
4. And finally, when doing a long press on the power button, the airplane mode and other options do not appear. The only option available is the "Power Off" button.
Please, if anyone has experienced this or has an idea on how to fix this issue or what caused it, please let me know.

Screen Off Device Administrator forcibly latching to hardware Search button?

I can't seem to find any sort of way to turn this action off, as it makes my hardware search button unusable for anything else.
for a while I thought I had an issue with the ROM on my phone and this button, but it seems it was Greenify all along. I've been using it since August and must have activated said device administrator down the line.
so, I went in on a similar phone and found that it was Greenify doing it all along.
Now, when I long-press the Search button on either phone, it brings the notification up asking if it can be allowed, and I do not want this.
this is a Motorola Droid 4 and a Motorola Droid Razr MAXX that this is both happening on, running LineageOS 14.1. as I see it, these are among the oldest phones able to run 14.1, but all the more need to run Greenify for screen-off battery savings, especially since these are low-RAM devices (1GB, 838MB of which is able to be utilized).
with Greenify installed, the search button is unmappable in the system settings; Greenify takes it over and never lets go. it also prevents from anything being mapped for short press as well; it becomes a dead button able to do nothing except sleep the phone if the device administrator for Greenify is active and a "hey, do you want to activate it?" nag button otherwise if the button is long-pressed or accidentally long-pressed. this is release, not beta.
Sudosftw said:
Now, when I long-press the Search button on either phone, it brings the notification up asking if it can be allowed, and I do not want this.
....
with Greenify installed, the search button is unmappable in the system settings; Greenify takes it over and never lets go. it also prevents from anything being mapped for short press as well; it becomes a dead button able to do nothing except sleep the phone if the device administrator for Greenify is active and a "hey, do you want to activate it?" nag button otherwise if the button is long-pressed or accidentally long-pressed. this is release, not beta.
Click to expand...
Click to collapse
This is still happening even after the recent update. This is annoying and I do not like it that Greenify is forcibly latching it onto a hardware button that I'd like to use for other things.
I would understand if this was a Bixby button thing for newer Samsung phones, but this is not a samsung phone.
What if you go to Android Settings > Apps > cog wheel > Assist & voice input, under Assist app, does it say Greenify? If yes, try changing it to None.
Edit: Okay I just found out I can add a search button to the on screen navigation bar (am also on LineageOS 14.1). And indeed, long pressing it turns off the screen and hibernates any apps pending hibernation.
This while Settings > Long-press action on nav-bar is unchecked and Assist app is set to None. Then again, I now realize these settings are all about the home button, and you were talking about the search button. So I'm afraid all I can do is confirm the behaviour you described. I'm using the latest version from Play Store, v3.9.9.1.
I don't have a Screen Off Device Administrator though, but my device is rooted. Also,
with Greenify installed, the search button is unmappable in the system settings
Click to expand...
Click to collapse
I don't have an option in Android Settings > Buttons to remap the search button, do you? Might be device specific (I don't have one of the phones you mentioned, nor a hardware search button).

Question a05s SM-A025U Why can't I enable TalkBack instead of Samsung Voice Assistant?

I have unlocked a lot of android phones before but this "A02s" is currently kicking my a$$. When I attempt to turn on TalkBack (where screen switches to "Getting started with TalkBack" and allows the "L" gesture commands) it instead gets a message box on upper screen saying "Voice Assistant turned on. To turn it off, quickly press and release the vol up and power buttons.". The "L" commands don't work for instance: bottom left to right then up "L" gesture brings up Voice Commands. Is there any other way to get to the browser that I don't know of? In my experience, they always leave enough wiggle room to get to the browser & settings but this one makes me wonder.
Try formating memory and cache in recovery it works for me sometimes if a phones acting up
Like that. Also i recently just unlocked a a32 and it too kicked my ass in a different way lol to activate talk back have to hold both volume keys and and not the power and volume up...dont know if that helps

Categories

Resources