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
I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
the only explanations i can come up with are:
-accidental touching the area in some way (unlikely)
-getting some substance stuck on the screen in that area (unlikely)
-a faulty touch panel (unlikely and very specific defect)
-a hickup in the software (again unlikely)
then again, if the OS (for whatever reason) thinks the home button is pressed, on default it should not only pull you back to the homescreen, but continue and send you right through to google. the conclusion of which would be, that this UI area is triggered repeatedly rather than continuously.
keep an eye out for what could have triggered it in case it occurs again.
check your settings what build exactly you are running (settings -> about phone -> build number).
ans lastly, if it happens again, you should still be able to hold your power button to hard-reboot it (no further interaction with the UI required).
RockinAmigo14 said:
I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
Click to expand...
Click to collapse
Try to clean your screen also with a towel
That is extremely weird. It really sounds like a faulty digitizer, but you'd be the first... Maybe it's a rogue app, but unlikely.
Were you doing something before this starts to happen?
I haven't noticed any consistent apps or behaviors when this would occur. This most recent time, I was low on battery (10%) and I had just flipped on my data.
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
dpj52190 said:
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
Click to expand...
Click to collapse
appreciate the tip! I'll keep this in mind if it happens again.
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
RockinAmigo14 said:
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
Click to expand...
Click to collapse
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The icon is a picture for my user profile on the phone.
I don't use anything like that. I had Clean Master installed briefly but it's been uninstalled for a couple of days now.
so it seems like this issue pops up whenever the camera crashes. happens occasionally when using the camera shortcut (double power tap) or in an app that uses the camera.
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
exninja said:
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
Click to expand...
Click to collapse
right, that's what's confusing me. i did a factory reset last week, set up the phone as a new device. haven't installed a new camera app, just the stock google camera. the issue occurred again last night when using an app called Shopkick, which accesses the camera but crashed.
Hey all, my ring doorbell app wakes the screen anytime I get an alert. I want to keep the notifications on but don't want the screen to wake. It wakes even in my pocket which I want to of course avoid. It may just be a bug in the app but I should be able to limit that from happening. Or so I hope anyway.
I have tried the following.
1. Switched all notifications pertaining to the app and individual cameras to "sound only"
2. In the app I have disabled "alerts open full screen video"
3. I have disabled heads up notifications globally through ADB.
4. Disabled ambient display.
5. Disabled notifications on lock screen.
I'm at a loss on what to do next. Any ideas are appreciated at this point.
TIA
ifly4vamerica said:
Hey all, my ring doorbell app wakes the screen anytime I get an alert. I want to keep the notifications on but don't want the screen to wake. It wakes even in my pocket which I want to of course avoid. It may just be a bug in the app but I should be able to limit that from happening. Or so I hope anyway.
I have tried the following.
1. Switched all notifications pertaining to the app and individual cameras to "sound only"
2. In the app I have disabled "alerts open full screen video"
3. I have disabled heads up notifications globally through ADB.
4. Disabled ambient display.
5. Disabled notifications on lock screen.
I'm at a loss on what to do next. Any ideas are appreciated at this point.
TIA
Click to expand...
Click to collapse
I've struggled with the same thing for months. It never used to do it, but after an update earlier this year it became the new normal for me.
I'm glad I'm not the only one. Hopefully somebody chimes in with some sort of work around.
I'm having the same problem with a Sony XZ1 phone (Android 8.0.0). I spoke with Ring at length and it's 'apparently' a problem with my phone, not their App.
I think that's a load of rubbish and something they need to address and fix. I installed the App on another Android phone running an earlier version of software, the App installs with different options and doesn't wake up the screen. So it's obviously dependent on the OS version but as other Apps don't have the same problem I can only conclude that it's an issue with the Ring App.
Has anyone tried uninstalling the app and then install an older version from APK mirror? Not even sure its on there but it's worth a go
hatdrc said:
Has anyone tried uninstalling the app and then install an older version from APK mirror? Not even sure its on there but it's worth a go
Click to expand...
Click to collapse
That's a great idea. There are plenty of versions to try on APK mirror, one or two per month from 2018. Not a good sign for a reliable and stable app.
I'll give it a go later unless anyone gets there first and can suggest a 'good' version to try
Were you able to find an older version that doesn't have the screen wake behavior?
edit: Pixel 2 - going back to 2.0.66.8 still has the screen wake behavior regardless of notification setting.
edit 2: 2.0.57.2 does the same thing...
Looks like the latest ring version finally let's you fix this. Select your devices, go to notification settings, then select sound only. The default is sound plus pop up. I no longer have the issue after making the change.
Can anyone confirm if turning off the 'plus pop' in the ring app settings works? I have a new pixel 3 on Android pie and the app is still turning on the screen at every alert event with settings set to just sound or just silent.
I'm having the same issue with the ring app. It wakes the screen. Really sucks when phone is in my pocket. I have tried every option and or combo of options. I have a pixel 3a on Android 10. Android 10 does have a option to wake screen for notifications found under display advanced, lock screen. But it is turned off
Still a problem on Android 10, No combinations of settings has been able to stop this for me. Of course Ring denies this even though I have sent a logcat to them.