Screen Off Device Administrator forcibly latching to hardware Search button? - Greenify

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).

Related

Phone wakes up after pushing any button?

I'm running DCD 3.0.1 rom, is this normal that my phone will wake up from standby whenever I push any button on it like a call or anything button? I don't really like that cause I'm always hitting keys and changing stuff while my phone is in my pocket and I rather just have it be the power button on the side like it used to work...is there a simple fix for this?
t0mmyr said:
I'm running DCD 3.0.1 rom, is this normal that my phone will wake up from standby whenever I push any button on it like a call or anything button? I don't really like that cause I'm always hitting keys and changing stuff while my phone is in my pocket and I rather just have it be the power button on the side like it used to work...is there a simple fix for this?
Click to expand...
Click to collapse
Hit Start, Settings then System Tab. Click Key Lock and make sure "Lock all buttons expect Power button" is selected.
start-settings-system-keylock-
choose "lock all buttons except power button."
thank you both! that fixed it, funny i never opened that settings option to look what was in there, i always thought that had to do with the stock sprint lock feature that i never used

[Q] Long press headset does not start Google Now when screen locked

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.

menu button for old apps

Hi Guys,
I have to use an old app, designed for Android 2.x, which still uses these ****ty three dots on the right bottom site to enter some settings, while using software navigation bar.
Now, I really like the invisible capacitive buttons and would like to continue using them. On the other hand, I also need to use this menu every now and then.
As the OPX is not heaving a menu button by default, like Samsung phones, what can I do?
Any advice?
If you are rooted then use Xposed + Force 3 dots menu, otherwise I wouldn't know a way to force that.
Yes, I noticed the same thing in Firefox. On the stock OS, it seems impossible to assign the "open menu" function to one of the buttons, (I mean with i.e. long press) while (if I'm not wrong) I had this set before the last ota update.

How to open in app menu?

Hi all. It may seem a silly question and probably it is but there are apps (in this case Touchdown mail client) that haven't an icon to open the in app settings menu. With my previous phones I used a physical button, usually long press on the back button, to open it. But how to do it with the single button p9000? Thank you.
Very good question, they seem to have forgotten about apps that need a physical key for menu, have you tried enabling the softkeys to see if the menu button appears on them for you? Can the "Smart Button" not be setup to be the menu key? or is it only to open apps? I not played with it myself..
Still searching how to have the MENU inside applications, softkeys does not work !
I would ask the software maker! The phone maker won't add more physical buttons.
And multiple press are always software driven!
Even if the phone maker did, that won't help you out with the old hardware...
Doesn't seem to be an answer anywhere online so here goes:
Go to settings > Navigation bar > Turn On.
Go to app you need a menu on > swipe up from bottom to bring up the Nav bar.
Three dots appear on the end of the nav bar. Done.
If the three dots don't appear; click on the recent tasks button and then go back into the app and they should come up.
Tried and tested with EZ Drop.
- Doesn't seem to work with apps with the built in "three dots" menu.
I use ‘Menu Button (No root)’ by JetToast free on the Play store, to get round this problem.
https://play.google.com/store/apps/details?id=jettoast.menubutton

Draw Over apps

this is about pokemon go. so i try using some xposed module. so this apps required overlay. but the problem i cant toggle pokemon go to overlay an apps due to the permission is greyed out. is there any way for me to toggle it on. i already rooted my phone and was on android 6.1. any help will be great thanks
I've had this error on many apps. Only solution I've found so far is to hold the power button until the power off option come up then hold long press power off until "safe mode" option comes up. You can set permissions once in safe mode.

Categories

Resources