I recently switched over to this phone from a Note 8. I've been happy with it except I don't use the Google Assistant. It's not entirely useful for me and I miss being able to remap the Bigsby Button on the Note 8, so I looked for a method of trying to remap it on the LG V50. I found this thread by cavalloz which used Tasker to remap they key, so all credit goes to him. I figured I would let you guys know about it, and then lay out a tutorial-like post in case some people needed more guidance.
First, you will need to disable the google assistant. Settings->General Tab-> Apps & Notifications->Default Apps->Assist & Voice Input. At the bottom, I turned off the open assistant (one press), talk to google (two presses), show visual snapshot (three presses). I have not tested to see if you can disable only the first button press method, because I don't use any of them, but you can try it because I know some of you like Google Lens.
Second, you will need Tasker. It is a paid app, but I feel like it is well worth it for what it provides.
Third, you will need to give Tasker some permissions. You can follow this guide they provide here.
Once Tasker has been closed, you can disconnect your phone from the computer, and then reopen the app. In the Profiles Tab, click the plus button at the bottom to create a new Event in the dropdown menu.
You will need to select System->Logcat Entry, select No in the popup, and you should have an Event Edit screen that says Output Variables, Component and Filter. Click the little magnifying glass icon, grant permissions for writing over other apps, and select OK in the Tasker pop-up.
Now try to be quick to minimize what is captured, but click the orange floating play-button on your screen to start recording, and press the assistant button. Then press the orange button again(now a square) which will stop recording. Tasker will pop-up again, and you will be given a panel containing everything that was recorded, including a response to you pressing the assistant button. In the filter text box field, start typing InputReader and the panel will be reduced to the relevant 'key events' we need.
It should read like
Code:
InputReader: Key event: device=4 type=0x0001 value=0x00000000 when=2087698767908
with the numbers being dependent on your phone (I think).
Select one of the events in the pop-up panel, and it will be loaded into the filter portion of the previous Event Edit screen. You should only keep
Code:
device=4 type=0x0001 value=0x00000000
in the filter text-field.
Click the back arrow in the top left-hand corner of the screen. You may get a small little box next to the new entry New Task +. Click it, and just click the check mark of the small box that appears at the bottom.
Now in the Task Edit panel, you should be able to click the plus button and add a response to the button press. I used Alert->Torch to toggle the flash-light. In the Action Edit panel, you should be able to change the action from Off to Toggle. Click the back button in the top-left again
Your button should now be able to toggle the flash-light. Let me know if this has worked for you guys. You could get more advanced and set it up for single press, double press, hold, etc.
Any other app than Tasker that can be used? Can it be used with force widemode application
I am only able to get this to work with the screen on... Is there a way to do this with the device locked and the screen off?
That's pretty cool, thanks for the guide. Works well on my LG G8. Also works when screen is off.
Played around with it a bit on my V60
Fantastic guide! Couldn't get the dual screen working at first, but I was eventually able to track down a log that corresponded to the button in all states (Locked/Unlocked, Case On/Off)
Honestly not 100% what I'm doing, so if anyone has any input that would be great! I can't post the URL yet because I just registered here, but I just linked to this thread on reddit /r/LGV60
TLDR; I found that using the Component "LGPhoneWindowManager" and Filter "hotKeyRelease count= : 0" works as a trigger while the phone is both locked and unlocked, and whether the case is on or off. Let me know if there's anything else I should know!
Do we need to add this for Tasker to read logs?
Code:
adb shell pm grant net.dinglisch.android.taskerm android.permission.READ_LOGS
Well I don't seem to be able to narrow down what actually works with this.
Code:
InputReader: Key event: device=5
was working ok to start with then I rebooted and device changed to 4!?
I've also tried
Code:
LGPhoneWindowManager hotKeyRelease count= : 2
for double tap and
Code:
HotKeyController HOTKEY_LONG_PRESS
for long press and they seemed to work initially but something stops them from working with the screen off after a while.
Just got my V50. I can't make it to work with your instructions
Done everything step by step.
Edit: Nevermind, now it works.
Morphy99 said:
Well I don't seem to be able to narrow down what actually works with this.
Code:
InputReader: Key event: device=5
was working ok to start with then I rebooted and device changed to 4!?
I've also tried
Code:
LGPhoneWindowManager hotKeyRelease count= : 2
for double tap and
Code:
HotKeyController HOTKEY_LONG_PRESS
for long press and they seemed to work initially but something stops them from working with the screen off after a while.
Click to expand...
Click to collapse
Double tap works for me, but it still keeps trying to open google assistant (even if its disabled from assistant itself and phone settings)
Does this also happens to you?
Anyway, ended using Button Remapper Pro from the Playstore. It also needs a PC and ADB, but it worked for long press with screen off.
Thanks XP_2, your instructions are impeccable! This worked well on my LG G8S - I used the Google Assistant button to launch my SatNav.
thanks a lot. I did all steps but, I have a problem. I can't turn off the snapshot (three clicks)
Make the video tutorial please
Sorry to revive an old thread. But can you remap the button to open a specific app, such as UAPP? By the way I own a V60, not V50.
I'm sorry but I can only get to the moment when I record my button press and go back to tasker.
Then I,m completely stuck. Please help.
What I can see is:
Code:
%lc_text
Text
The text that corresponds to the matched logical entry
COMPONENT [arrow button and magnifying glass button]
ViewRootlmpl
FILTER [arrow button]
ViewRoot's touch event: action down
GREP FILTER (check help) [tick place where I can turn it on or off]
And what to do now???
Clicking back button pops up missing permissions screen - but I can't grant any from this screen
Please help
Related
UPDATE!!! There's a new XPosed Framework module in town that makes this whole thread obsolete. Check out the new NFC Unlock module, forked from the NFC LockScreenOff Enabler module already used in this project. Way simpler, fewer moving parts to configure, and works well. Check it out. Otherwise, this has been a fun way to learn how to use Tasker! Thanks, all!
Original Post
This is a guide to show you how to set up your phone to be unlocked by an NFC tag. There are several other threads on the subject for various phones and carriers, but it took me several weeks worth of research and testing to come up with something that actually worked on my phone, and this tutorial is the culmination of that effort. In theory, it should work for a wide variety of ROMs (including Stock), phones and carriers, and even survive ROM updates (provided you maintain root), but I have only tested it on a Sprint Galaxy S3 (model d2spr) that is rooted and running CyanogenMod 10.1.
DISCLAIMER! I am NOT responsible for any damage to your phone, loss of data, use of your phone, or spontaneous sharknadoes that may occur if you try these steps! It worked for me, but I make no guarantees that it will work for you! Back up all your data and your ROM, and use this at your own risk!
HARDWARE REQUIREMENTS
An NFC capable phone, like your Sprint Samsung Galaxy S3 with Root Access enabled
An NFC tag, such as Samsung TecTiles
SOFTWARE REQUIREMENTS
XPosed Framework
ONE of these XPosed Framework plugins:
MoDaCo Toolkit Plugin for the XPosed Framework (NFC Always On or On When Unlocked)
NFCLockscreenoffEnabler.apk for the XPosed Framework (lets you choose between Always On, On When Unlocked OR On At Lockscreen for better battery life)
NFC Task Launcher from the Play Store
Tasker from the play store
Secure Settings Plugin for Tasker
STEP 1: Install the software!
Install all of the software listed above.
Open XPosed Framework and enable the MoDaCo Toolkit OR the NFCLockscreenoffEnabler.apk in the Modules tab
STEP 2: Turn on NFC scanning all the time
Normally, Android only scans for NFC tags when the phone is unlocked. We need to scan for NFC tags when the phone is locked, and in our case, when the screen is off. Open the MoDaCo Toolkit app and check the box to Enable NFC when screen is off under Settings -> Wireless
WARNING!!! Turning on NFC scanning when the screen is off may adversely affect your battery life!
STEP 2 ALTERNATIVE: Turn on NFC scanning at Lockscreen
Open the NFCLockscreenoffEnabler.apk app and select Enable NFC when phone is locked, but the screen is on. This option should be a little easier on your battery. (Thanks to @nacron for finding this!)
STEP 3: Make Secure Settings a Device Administrator
Open Secure Settings and go to the Configuration Menu by tapping the wrench icon in the upper-right hand corner. Once there, check the box next to Device Administrator and select "Activate" on the confirmation screen.
STEP 4: Teach Tasker how to Lock and Unlock your phone
We can either do this the easy way, or the hard way.
Easy Way - Import the Tasks
Download and unzip NFC-Unlock-Tasker-Tasks.zip and copy the enclosed XML files to your phone
Open Tasker and long-press the Tasks tab
Select Import and open the files that you just copied
There is no step 4.
Hard Way - Manually Enter the Tasks
If you don't trust the import function, or just want to learn more about creating tasks in Tasker, you can create the tasks manually.
Open Tasker and select the Tasks tab. Create a new Task by tapping the big "+" sign, name it "LOCK", and add the following actions:
Select Task -> If
Under Condition on the LEFT side of the condition, type TRUN (the variable for Tasks Running)
Tap the Condition Operator icon (the grey button in the middle) and select Doesn't Match, or !~
On the RIGHT side of the condition, type *Unlock*
Under the If statement, select Plugin -> Secure Settings then tap Edit.
Select Keyguard and set the following options:
Select radio button On
Select Plugin -> Secure Settings then tap Edit.
Select Lock Device and set the following options:
Box for Device Admin Enabled is checked
Select Task -> End If
Create a new Task named "Unlock", and add the following actions:
Select Task -> Stop And select the Lock Task that we created earlier.
Select Plugin -> Secure Settings then tap Edit.
Select Wake Device and set the following options:
Wake Type: Screen & Keyboard Lights On
Duration: 30 seconds
Select Task -> Wait and set duration to 100 MS
Select Plugin -> Secure Settings then tap Edit.
Select Keyguard and set the following options:
Select radio button On
Select Task -> Wait and set duration to 100 MS
Select Plugin -> Secure Settings then tap Edit.
Select Keyguard and set the following options:
Select radio button Off
Check box Run in background (No Notification)
If you run this Task now, you probably won't notice anything different right away. However, if you lock your phone and then unlock it, you'll notice that any security that you had set up is now bypassed. That's why we needed to teach Tasker how to lock your phone, as well.
STEP 5: Teach NFC Task Launcher to Unlock your phone
Open NFC Task Launcher and create a new task for NFC named "Unlock Phone".
Take your NFC tag and follow the instructions on the screen to write the tag for this task.
Add a new Task by tapping the big "+" icon in the upper right corner.
Select Category Tasker
Check "Tasker Task" and tap "Next"
Type "Unlock" in the field next to the magnifying glass icon under Tasker Task and tap "Add to Task"
Congratulations! You can now unlock your phone with your NFC tag! Of course, as we mentioned above, this leaves your phone without any passcode protection that you may have previously enable. Which leads us to our final step...
STEP 6: Teach Tasker to Lock your phone
Open Tasker and select the Profiles tab
Create a new Profile with the big "+" at the bottom of the screen and select Event
Select Display -> Display Off
Go back to the Profiles page by tapping the "< Event Edit" icon in the upper left corner.
Select the Lock Task that you made earlier
Now when the screen goes off, your phone is secure again.
That's it! My hope is that this tutorial is easy to follow so that anyone who wants to unlock their phone with an NFC tag can get it working. While there are a lot of steps, I tried to make them clear and specifically looked for a method that was flexible enough to allow me to update my phone or even use a different phone with this method, without having to track down a modified NFC.apk for my specific firmware every time I wanted to update.
In regards to how battery life is affected by having NFC turned on all the time, my personal experience shows no appreciable decrease in battery life. I went all day yesterday without charging (about 15 hours) with typical usage for me, which includes 2-3 hours of podcast playback over both wired and bluetooth headphones, occasional GMail and Facebook usage, Solitaire, and 45-60 minutes of phone calls, which is on par with what I was getting before the hack. As with all things, your mileage may vary. If battery life becomes an issue, try the new NFCLockscreenoffEnabler.apk plugin that @nacron found instead of the MoDaCo one which gives you the On At Lockscreen option in addition on Always On. It should save you a bit on battery life.
Many thanks to the authors of the software I used (XPosed Framework, MoDaCo Toolkit Plugin, NFCLockscreenoffEnabler.apk, NFC Task Launcher, Tasker, Secure Settings Plugin), as well as this thread and this web page for giving me the framework to construct this rather elaborate NFC hack.
I would love to hear from others if this works on other phones.
Changelog:
2013-09-05 - Add NFCLockscreenoffEnabler.apk option for NFC on at Lockscreen (thanks @nacron for this!)
2013-08-14 - Changes to the Tasker Tasks that make the lock and unlock functions run a bit more smoothly by avoiding collisions. (i.e., if you're unlocking the phone, it won't try to lock it until the unlock is done.) I've also added easy-to-import XML files for the Tasks, so you don't have to type them in manually anymore!
2013-08-09 - Initial release (can you "release" a process?)
Wow, thanks for the info.
New instructions and importable task files make getting this set up a whole lot easier! Updates in the OP!
I've attached a cheap NFC tag to my watch wristband, cleverly disguised by gold nail polish, and unlock by NFC is now my preferred unlock method.
I like this. Posting to keep track of it.
Well, as soon as root is found for the DROID MAXX, I will be using this.
Sent from my Nexus 7 using Tapatalk 2
Hello,
After trying this on a Samsung Galaxy S3 Stock 4.1.2 and Slim Bean (worked like a charm), I have found a glitch on the stock firmware. When making a call the screen would go off via the Proximity sensor so <b>Tasker</b> would lock the phone.
So I made a little addon to the following part and the problem stoped:
Original:
STEP 6: Teach Tasker to Lock your phone
Open Tasker and select the Profiles tab
Create a new Profile with the big "+" at the bottom of the screen and select Event
Select Display -> Display Off
Go back to the Profiles page by tapping the "< Event Edit" icon in the upper left corner.
Select the Lock Task that you made earlier
Modified:
STEP 6: Teach Tasker to Lock your phone
Open Tasker and select the Profiles tab
Create a new Profile with the big "+" at the bottom of the screen and select Event
Select Display -> Display Off
Go back to the Profiles page by tapping the "< Event Edit" icon in the upper left corner.
Select the Lock Task that you made earlier
[*] Select Display off (long-press) -> Add -> State -> Sensor -> Proximity sensor -> Check invert
That's it!
Now when you get a call and answer it Tasker will know that the proximity sensor is used and will not lock the phone
Hope it works for you too.
Thanks,
[/QUOTE]
stealthdave said:
New instructions and importable task files make getting this set up a whole lot easier! Updates in the OP!
I've attached a cheap NFC tag to my watch wristband, cleverly disguised by gold nail polish, and unlock by NFC is now my preferred unlock method.
Click to expand...
Click to collapse
Thats slick man. I may have to use that for myself lol :good:
This is great, thanks man but one problem. When I use my tag to unlock the phone, use the phone then hit the android home button to return to my default screen, it locks the phone instead. If I unlock it normally (Entering PIN) it doesn't display this behavior. What am I doing wrong.
Deleted
LevanG said:
Hi, can I use this method to unlock my LG Lucid2?
I want to use it on GSM network...
Click to expand...
Click to collapse
Wrong kind of "unlock", I'm afraid. This unlocks your screen so that you can bypass the lock screen; it doesn't do anything for carriers locking the phone to their network. Think of this as using an NFC tag as your password.
OK, sorry and thanks for your reply
lloydcabraham said:
This is great, thanks man but one problem. When I use my tag to unlock the phone, use the phone then hit the android home button to return to my default screen, it locks the phone instead. If I unlock it normally (Entering PIN) it doesn't display this behavior. What am I doing wrong.
Click to expand...
Click to collapse
Try adding a 200ms delay to the beginning of the LOCK Task. This seemed to make things a bit more predictable on my phone.
stealthdave said:
Try adding a 200ms delay to the beginning of the LOCK Task. This seemed to make things a bit more predictable on my phone.
Click to expand...
Click to collapse
Actually, already have added a delay at the beginning to the Lock task but it didn't do anything to correct the behavior to the Home button. I should probably add that I'm using this with an HTC One that already has a funky Home / Menu button configuration. Home button works fine when I unlock normally but seems to get remapped to go back to the lock screen when I unlock it using NFC.
lloydcabraham said:
Actually, already have added a delay at the beginning to the Lock task but it didn't do anything to correct the behavior to the Home button. I should probably add that I'm using this with an HTC One that already has a funky Home / Menu button configuration. Home button works fine when I unlock normally but seems to get remapped to go back to the lock screen when I unlock it using NFC.
Click to expand...
Click to collapse
Likewise. I have the same problem as well. The physical Home button just takes me back to my pin lockscreen if I had unlocked via NFC. If I unlocked my phone manually by entering my pin then everything just works fine.
EDIT: Should also say that my phone is the S3.
@lloydcabraham and @bleAf! , what version(s) of Android are you running? I'm on 4.2.2 (CM 10.1.2), and my Home button is working as expected. I'm also using Nova Launcher as opposed to the stock Android launcher. Also, I presume that you haven't inadvertantly remapped the Home button, either by Tasker or some other setting or app? (Forgive me if some of this sounds like basic tech support stuff; just spitballing ideas since I can't reproduce.)
stealthdave said:
@lloydcabraham and @bleAf! , what version(s) of Android are you running? I'm on 4.2.2 (CM 10.1.2), and my Home button is working as expected. I'm also using Nova Launcher as opposed to the stock Android launcher. Also, I presume that you haven't inadvertantly remapped the Home button, either by Tasker or some other setting or app? (Forgive me if some of this sounds like basic tech support stuff; just spitballing ideas since I can't reproduce.)
Click to expand...
Click to collapse
Not at all, I appreciate your help. I'm using ElementalX kernel that remaps the HTC logo as a menu button but leaves the back and home button alone. Maybe that's the issue? It's just funny that I only have the problem if I use my NFC to unlock the phone using the supplied scripts. Oh well, no biggie but if you can help me figure it out, it would be great. I can send you a cwm backup (wiped of course) if you'd like to try my setup?
lloydcabraham said:
Not at all, I appreciate your help. I'm using ElementalX kernel that remaps the HTC logo as a menu button but leaves the back and home button alone. Maybe that's the issue? It's just funny that I only have the problem if I use my NFC to unlock the phone using the supplied scripts. Oh well, no biggie but if you can help me figure it out, it would be great. I can send you a cwm backup (wiped of course) if you'd like to try my setup?
Click to expand...
Click to collapse
Actually, it would probably be easier for you to just try a different kernel and see if it still works. Given the description of what it does, my guess is that might be the issue.
It also might be an issue with the XPosed Framework or MoDaCo plugin on the HTC One specifically. (It does have its own special installation procedure.)
- Dave
stealthdave said:
@lloydcabraham and @bleAf! , what version(s) of Android are you running? I'm on 4.2.2 (CM 10.1.2), and my Home button is working as expected. I'm also using Nova Launcher as opposed to the stock Android launcher. Also, I presume that you haven't inadvertantly remapped the Home button, either by Tasker or some other setting or app? (Forgive me if some of this sounds like basic tech support stuff; just spitballing ideas since I can't reproduce.)
Click to expand...
Click to collapse
I'm on 4.1.2 (Samsung based rom with stock kernel). I'm also using Nova launcher and I just tried stock Touchwiz launcher but same result.
I'm thinking it may be just something to do with Samsung Touchwiz or HTC Sense based rom (If lloydcabraham is also running HTC based rom or stock).
Thanks for your help stealthdave.
For some reason I can't get my phone to recognize the NFC tag when the screen is off or even in the lock screen. Only when I'm past the lock screen will the NFC tag recognize. The xposed framework was part of the ROM i'm using (M.O.A.R.) and I just installed the MoDaCo mod via the link. I checked off NFC on always and restarted several times but it still won't recognize when the screen is off.
[EDIT]
Got it to work using this xposed module instead of the MoDaCo one for always on NFC.
http://forum.xda-developers.com/showthread.php?t=2122019
Also having issues of lock coming back on after doing any action post unlock via NFC. I think it's a hack Samsung put together for the latest firmware upgrade after the whole problem with the bypassing the lockscreen by going through the emergency screen. The op wouldn't have this issue as he's not using a TW rom. I wonder if there is a way to have it input the key instead of bypassing the key.
[EDIT 2]
Overcame this issue by using the secure settings to reset the pin to nothing when unlocking via NFC and enable the pin when the screen goes off. This method even prevents the phone from locking during a call. I have a new issue of the swipe screen coming back right after NFC unlock. I'll post my findings a little later. It's not the most elegant of fixes but it prevents the lock screen from coming up when pressing the home button. I also removed all the waits and made lights and keyboard on for 5 seconds, makes unlocking faster.
The action for password/pin reset in Secure Settings is in All Actions > Dev Admin Actions > Password/Pin. You just select disabled when unlocking and it removes your existing pin and when you select enabled for lock, it prompts you to enter your pin twice in the settings. Not sure how secure this is or where it stores your password/pin. The only problem with this method is that you'll have to change the password/pin in secure settings if you decide to change your password/pin in the android settings or you'll end up with 2 different passwords/pins
Not sure if this works if you have pattern unlock. Haven't had time to test that.
So this is how my unlock task looks like:
1. Stop task lock
2. Secure Settings > configuration > Screen and keyboard lights on for 5 seconds
3. Secure Settings > configuration > clear password
4. Secure Settings > configuration > Keyguard disabled
and my lock is simply
1. Secure Settings > sonfiguration > Set Pin
and my profile is
Display Off > Lock
[EDIT3]
Figured out why it was presenting the swipe lock screen when doing a quick NFC unlock removal . I'm using the hacked version of AnyTAG NFC Launcher, instead of the NFC Tag Task Launcher, that detects NFC Tag removal as well as placement. Thought this app would be more extensible in the future. The only problem with this is that it will keep insisting on launching on NFC Tag removal if you don't set something so I just set the task to do nothing and that was locking the swipe screen again. I just set it to the same task as unlock and it doesn't pull up the swipe screen anymore.
Also, the battery replacements from Sprint suck. It's a generic sprint branded battery that DOES NOT have an NFC antenna in it. Picked up the replacement along with tectiles yesterday and couldn't figure out for the longest time why this unlock thing wasn't working. Their battery part number is BSML71021L. Gotta call them up to see if they can give me back my old battery or give me a real samsung replacement.
[EDIT 4]
After trying to get this to work consistently, I've disabled it. I can get tasker to remove/reenable the pin consistently but only sometimes will it clear the lockscreen automatically.
nacron said:
For some reason I can't get my phone to recognize the NFC tag when the screen is off or even in the lock screen. Only when I'm past the lock screen will the NFC tag recognize. The xposed framework was part of the ROM i'm using (M.O.A.R.) and I just installed the MoDaCo mod via the link. I checked off NFC on always and restarted several times but it still won't recognize when the screen is off.
[EDIT]
Got it to work using this xposed module instead of the MoDaCo one for always on NFC.
http://forum.xda-developers.com/showthread.php?t=2122019
Click to expand...
Click to collapse
Thanks for this find! I've added it to the OP for others. It's worked pretty consistently for me with this new module for the 30 minutes I've had it installed, and hopefully it will lead to better battery life. (Battery life wasn't too bad, but I was starting to notice a difference with NFC always on.)
nacron said:
[EDIT 4]
After trying to get this to work consistently, I've disabled it. I can get tasker to remove/reenable the pin consistently but only sometimes will it clear the lockscreen automatically.
Click to expand...
Click to collapse
I'm sorry to hear that it's not working for you. Hopefully Google will eventually enable this functionality in Android proper. The Moto X certainly shows that it's not only possible, but practical.
- Dave
Is there any place (or a best place?) to submit feature requests for Wear? I can post here but I do not know if anyone from Google will get the message. OTOH, I've seen some mentions of feature requests here and other members posted apps or tips and tricks to meet the need. The features I'm thinking of are:
- double tap on the screen or the button to bring up the most recent app. (Someone else mentioned this and I really like it.) I use my watch when running so to bring up my running app I need to (1) opening the screen, (2) expanding the notification, (3) swipe to the side to get the "open app" screen and (4) tap on the "open screen button." This is a real PITA while running and is further exacerbated by profuse perspiration confusing the watch WRT my touch. It would be nice if the app could cooperate and return to the last active screen as well. An alternative to this would to tie a particular app to the double tap via configuration entry.
- Ability to turn the screen off during charging. The 'tips and tricks' answer to this is just too involved when I'm ready to slip into bed! Maybe if I could program or script the actions... There are times when the screen turns off when I place the watch in charger and that would be fine as a configuration option. Other times it seemed like I can do that by palming the screen or tapping the button (but this doesn't normally work.) That would be useful too.
- Single button press to activate the button on a screen. Back to my use case for running... It can be difficult to get the pause/stop button to register due to perspiration. This one is a little problematic because it conflicts with the existing function to turn the screen off with a button tap. However palming the screen with sweaty hands seems to be easily recognized vs. scrolling or tapping a button.
I'd like to have an option to have the mic on the watch turn on when accepting a call from the watch. There are times when my phone is upstairs and I get an incoming call on my watch. It would be nice to be able to answer the call and give the person on the other line a heads up that you need a second or two to get your phone. Once the call is accepted on the watch, there could be a button that transfers the live mic to the phone.
Hello everyone,
While I was testing my phone and pressing everywhere, I might found a feature I didn't read anywhere.
I know there is the ZenMotion, and it works great. By writing a "C" on the screen, you launch the camera app. But I don't talk of that (and I disabled this shortcut)
After locking the screen, press the volume button twice (down-down, up-up or even up-down and down-up). It launches also the camera app.
This isn't a ZenMotion feature (I disabled everything and the shortcut still works).
Is someone having this shortcut too? Did someone know how to disable the shorctcut?
matias49 said:
Hello everyone,
While I was testing my phone and pressing everywhere, I might found a feature I didn't read anywhere.
I know there is the ZenMotion, and it works great. By writing a "C" on the screen, you launch the camera app. But I don't talk of that (and I disabled this shortcut)
After locking the screen, press the volume button twice (down-down, up-up or even up-down and down-up). It launches also the camera app.
This isn't a ZenMotion feature (I disabled everything and the shortcut still works).
Is someone having this shortcut too? Did someone know how to disable the shorctcut?
Click to expand...
Click to collapse
The setting for the double click volume key to launch camera from sleep is in Settings -> Lock Screen
At least on the US version running the WW firmware. See attached image.
Ohhh. Got it. The setting is here.
Thanks!
I've tried various screen off apps and they all require secondary security to turn back on when using the fingerprint scanner. Any ideas?
Would love for an option where the fingerprint scanner can also turn the screen off or even an OK Google command, but then allows the fingerprint scanner to reopen without secondary security.
+1
Sent from my Nexus 5X using Tapatalk
hmmm, you can try to use command 'input keyevent 26' , for tasker task...
this will required root though.
Jackpot! A widget pointing to a tasker task that uses secure settings to run command 'input keyevent 26' as root works like a charm!
Sent from my Nexus 5X using Tapatalk
minnemike said:
I've tried various screen off apps and they all require secondary security to turn back on when using the fingerprint scanner. Any ideas?
Would love for an option where the fingerprint scanner can also turn the screen off or even an OK Google command, but then allows the fingerprint scanner to reopen without secondary security.
Click to expand...
Click to collapse
I was just going to post a similar question. I don't have the phone yet, but i thought maybe someone can create something that allows the fingerprint scanner to turn off the screen. The finger is already in that area so it would be cool to either hold fingerprint scanner for a second to turn screen off or double tap the scanner.
jpen said:
I was just going to post a similar question. I don't have the phone yet, but i thought maybe someone can create something that allows the fingerprint scanner to turn off the screen. The finger is already in that area so it would be cool to either hold fingerprint scanner for a second to turn screen off or double tap the scanner.
Click to expand...
Click to collapse
Any solutions yet?
scottfreeze said:
Jackpot! A widget pointing to a tasker task that uses secure settings to run command 'input keyevent 26' as root works like a charm!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for this! Added it as a Tasker shortcut for double-tap gesture in Nova and it works like a charm.
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
solara1973 said:
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
Click to expand...
Click to collapse
Thanks for this detailed description. I've never used Tasker before either, so I'll give it a try. It's a shame such a step is required.
How was it determined that "input keyevent 26" would solve the problem? Will doing this interfere with OTA updates, since it may change a system setting?
Can I use Soft Lock Screen to turn the screen off?
Pumpino said:
Thanks for this detailed description. I've never used Tasker before either, so I'll give it a try. It's a shame such a step is required.
How was it determined that "input keyevent 26" would solve the problem? Will doing this interfere with OTA updates, since it may change a system setting?
Can I use Soft Lock Screen to turn the screen off?
Click to expand...
Click to collapse
There's a known list of Android commands that software can use to simulate some hardware presses, etc.: http://thecodeartist.blogspot.com/2011/03/simulating-keyevents-on-android-device.html
Tasker or using the keyevent 26 will not interfere with the system in any way. By sending the keyevent 26 you are doing exactly what pressing the Power button does - only with software. It does nothing to change any system settings. Not sure about the Soft Lock Screen app, but I suspect that like other software, if you use that, you will prob need to re-enter your password/pattern/pin and the fingerprint won't work. By sending the keyevent 26, you can still unlock it using the fingerprint sensor.
solara1973 said:
Great tip. Got tasker set to Nova pinch out to turn off. But also have option to run task from Notification menu as well.
For those who have never used tasker before like me here is a quick note on how to set it up:
Select TASKS tab at top, select + button at bottom, give it a name (screen off) and press check mark.
You will then enter Task Edit. Press + to add an action, then select Code as your action category, then choose Run Shell.
Paste in the text: 'input keyevent 26' under the Command field. Check the Use Root option. Back out once and choose an icon for it if you want at the right lower corner. You can now place a widget for the task or launch the task with Nova etc. And/or go into Preferences and under the Monitor tab you can add it to the Notification Action Buttons.
Click to expand...
Click to collapse
Thank you for explaining it. Does this require a root? And does it require Nova Launch?
minnemike said:
Thank you for explaining it. Does this require a root? And does it require Nova Launch?
Click to expand...
Click to collapse
It does require root to be able to let Tasker run a shell command. You would not need Nova launcher as you can easily put a widget to launch the Task within Google Now Launcher or any other launcher. Nova launcher is nice because it enables gestures and double tap to do certain actions. I have Nova to launch my phone app when I tap the Home button on the main home screen. Double tap runs my Task to turn off the phone. Pinch in, pinch out, two finger swipe down/up, etc.
Could you have something trigger Tasker to temporarily change the screen timeout to 1 second (and then change it back after the screen is off)?
solara1973 said:
It does require root to be able to let Tasker run a shell command
Click to expand...
Click to collapse
I guess I won't be using this technique then, as I don't want to root at this stage.
Is it possible to get Nova to turn the screen off by something like double-tapping on the status bar (without root and Tasker)?
Pumpino said:
I guess I won't be using this technique then, as I don't want to root at this stage.
Is it possible to get Nova to turn the screen off by something like double-tapping on the status bar (without root and Tasker)?
Click to expand...
Click to collapse
Nova launcher does not have a function to send keyevents or turn off the screen etc.
You can always try some of the Screen Off apps on the playstore and see if anyone of those allow you to unlock the phone again using Imprint. Swipe-Lock, Screen Off and Lock, Screen Lock, etc.
this one works (experimental) https://play.google.com/store/apps/details?id=com.iglint.android.screenlockpro&hl=en
it is paid one
Hello everybody,
Soon after getting the Pie update, after the first security small update, i noticed that on my wife's Galaxy S9 the setting "Single tap to swipe" option is gone. Anybody else having this problem ?
Thanks!
Same here. I have also preferred tap instead of swipe... Definitely i am going to change this Samsung brand...
Mee too! I'm very angry...
LOL, you guys break me up, so fickle that you'll change phones because of single tap to swipe feature missing. There is no way you could have even liked the phone if you'll drop it for this.
Same on S9+. It worked on One UI security patch January 1, but it is gone after February 1 update.
Lame, I thought my phone got stuck, took me few days until I tried to swipe, LOL...
I am used to end the call with Power key but never got the hang of using the Volume up key for answering calls, so I just used tap instead of swipe.
Now I guess I am doomed.
My workaround will be to try to get used to using Bixby key for answering calls since bxActions app has such an option.
Until they break that with some update also.
On Note 9 still working after the last update, hope they will not mess with it.
For some reason in latest update they moved it under: Interaction and dexterity -> assistant menu -> Single tap to swipe ....
but now i am stuck with useless menu on my screen (kept only one option in the menu) but when disabling the menu - single tap stops working
Thanks kabangena, with your help i found it. I have set the maximum transparency to the small assistant menu and i moved it in the upper right corner. I cannot see the icon anymore. It's a temporary fix, hope Samsung will do something about it.
florio1960 said:
Thanks kabangena, with your help i found it. I have set the maximum transparency to the small assistant menu and i moved it in the upper right corner. I cannot see the icon anymore. It's a temporary fix, hope Samsung will do something about it.
Click to expand...
Click to collapse
same here , but it's still very annoying
Is anyone solved the issue, even with the third-party app? That's really annoying; why don't left that useful option "as is"?
You can hide the assistant menu by long press on it and a circle with "X Hide Here" appears in top center of the screen, drag it into the circle. This hides assistant menu in the notification panel. You have to see the notification every time you swipe down to open the panel, but it is completely hidden from the home screen.
damnpoor said:
You can hide the assistant menu by long press on it and a circle with "X Hide Here" appears in top center of the screen, drag it into the circle. This hides assistant menu in the notification panel. You have to see the notification every time you swipe down to open the panel, but it is completely hidden from the home screen.
Click to expand...
Click to collapse
Except, after the screen closes and I hit Home to open it again, this little piece of worthless junk is back.
I'd just leave it somewhere and ignore this POS, but it covers parts of apps that I regularly use.
Why do people think that deleting functionality is a good thing?
Finally I found the solution (not a permanent but still affordable).
- turn Settings->Accessibility->Interaction and dexterity->Assistant menu on and (inside "Assistant menu") set Single tap to swipe is on
- weird floating icon should appear but don't worry
- go to Settings->Apps, press "3 dots" in the top right corner and tap on Show system apps
- find an app called Accessibility, tap on, scroll all way down and remove Appear on top advanced permission (I've also disabled Change system setting)
- now scroll up, and tap on Force stop button
Weird button will disappear and re-appear after reboot only (you should repeat last step again after reboot but it's OK, I believe so)
Enjoy!
P.S. Thanks to user drmusou for his post.
[UPDATE] There is a permanent solution! Set Single tap to swipe option and disable package com.samsung.accessibility by Package Disabler Pro+ (Samsung).
Or just with ADB shell:
c:\adb>adb shell pm disable-user --user 0 com.samsung.accessibility
If you tap and hold the assistant menu you will have the option to hide it " it will re appear after reboot" but can do the same again ?