This has been discussed before, but hasn't been talked about for Marshmallow. Plus everything about this seems abandoned. It is quite unfortunate. It is very convenient to be able unlock my phone just by putting it over a nfc tag. I was able to do this on kitkat with an xposed module, but since development stopped on that module, it hasn't been possible. The module allowed me to scan an nfc tag while the screen was off and Tasker would dismiss the passcode and lockscreen. It would unlock directly to the home screen. If nobody else has any idea on how to do this, I guess I can try learning xposed and continue development on that module, but it definitely seems over my head since I've never made an xposed module before.
Bump
suicidal acorn said:
This has been discussed before, but hasn't been talked about for Marshmallow. Plus everything about this seems abandoned. It is quite unfortunate. It is very convenient to be able unlock my phone just by putting it over a nfc tag. I was able to do this on kitkat with an xposed module, but since development stopped on that module, it hasn't been possible. The module allowed me to scan an nfc tag while the screen was off and Tasker would dismiss the passcode and lockscreen. It would unlock directly to the home screen. If nobody else has any idea on how to do this, I guess I can try learning xposed and continue development on that module, but it definitely seems over my head since I've never made an xposed module before.
Click to expand...
Click to collapse
seconding this.
I used it to turn off or on my Hue Lights! THAT was the way its supposed to work, the closest I had to flipping the switch
Related
So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that?
EDIT: Mod can move this to Q & A, it's getting late over here.
From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc.
I can understand why they have changed it, though IMO it should be an editable setting.
eddie_gordo said:
From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc.
I can understand why they have changed it, though IMO it should be an editable setting.
Click to expand...
Click to collapse
Ah, ofcourse now i see why but yeah it should be editable, though NFC is not that widely used yet i'd like to turn that security feature of until i connect a creditcard to my phone.
Pliind said:
So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that?
EDIT: Mod can move this to Q & A, it's getting late over here.
Click to expand...
Click to collapse
Every demo in the xperia video shows the screen on as far as I can tell, and unlocked.
The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts.
If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.
krohnjw said:
Every demo in the xperia video shows the screen on as far as I can tell, and unlocked.
The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts.
If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.
Click to expand...
Click to collapse
Well now that you said it and i checked the video again..your right.
Think I got the idea from when he stepped out of the car and just flashed the badge.
Pliind said:
Well now that you said it and i checked the video again..your right.
Think I got the idea from when he stepped out of the car and just flashed the badge.
Click to expand...
Click to collapse
To be fair they do make it seem like that's how it would work. Who would turn their phone on, unlock it and then turn it upside down BEFORE they get out of their car just to scan an NFC tag once they got out.
I don't see that being a reality though as the rest of the demos clearly show the device on and what appears to be unlocked. Given this is how the NFC service works within ICS, I'd suspect this will be the behavior as well.
Hi there!
I am about to upgrade to Lollipop, two good months after it's officially out for our M8s. Unless I missed something, the wonderful s2s module seems to be discontinued and I am desperately looking for an alternative.
There are a lot of apps around that let you lock the screen reacting to gestures or just by launching them, but all of them are implemented by using the "Lock screen" device administrator, which literally locks the screen. This means that if you need your phone 10 seconds later, you have to unlock with your pattern or PIN again. This seems to be because of an intentional restriction in Android, and I couldn't find any root application circumventing it.
I found this Xposed module, but people write in the thread that it doesn't work with Xposed for Lollipop.
Does anybody have a better solution? Did you all give up the possibility of sleeping your phone with a gesture without locking it?
On body detection works good for that. Phone won't lock if you set a pin until you place it down for a few minutes.
Sent from my HTC One_M8
Cool, I didn't know of this feature! Thanks!
But does this really solve the problem? If an app with device administrator permissions explicitly locks the screen I guess it will be locked anyway, won't it?
Hi,
My girlfriend's Nexus proximity senor seems to be broken and her screen is black all the time when she's calling someone.
Is there an easy way (root or not, I don't care) to easily disable the sensor all the time or in Caller app ?
She's on latest stock Oreo 8.1.
Thank you
Experiencing this as well. From what I have read, it is an issue with 8.1 specifically and the 5X.
Google haven't really acknowledged the problem yet, which sucks.
Related reddit thread
For calls, pressing the power button twice seems to bring the screen back for use again - doing this too quickly starts the camera, if you have that enabled.
This probably won't help for other use cases, like whatsapp.
I can understand that it's a bug for WhatsApp (she has that bug too), but for the dialer too ?
I don't experience such issues. My prox sensor is working like it should. Though I have a friend who has some minor problems with it, but he has a glass screen protector on top of it. Mine has a cutout for the sensors
Sebacestmoi said:
Hi,
My girlfriend's Nexus proximity senor seems to be broken and her screen is black all the time when she's calling someone.
Is there an easy way (root or not, I don't care) to easily disable the sensor all the time or in Caller app ?
She's on latest stock Oreo 8.1.
Thank you
Click to expand...
Click to collapse
My old original Nexus 5 had this problem and I got around it with an Xposed Module called Disable Proximity Sensor. That module has since evolved to something called Sensor Disabler (Link: https://forum.xda-developers.com/xposed/modules/mod-disable-proximity-t2798887). It doesn't say that it has been tested on the Nexus 5x, but it might still work. I am not sure how compatible it is with the new Oreo version of Xposed. Installing Xposed might be a bit overkill, but if it fixes the problem, it might be worth it.
I know how frustrating and annoying a busted proximity sensor can be, so I hope you can find a solution.
I have been using my 3a xl for a couple weeks and very happy overall with the speed and performance. I am having one issue trying to overcome that's very disappointing. I do a lot of of walking with my phone in my pocket. When ever I get a call or notification while my phone is in any of my pockets it will either answer it or because it's moving around it will go thru the menus etc. Even if I don't pull my phone out it will always do this. The pocket dial/proximity programming is not good. If you test the prox sensor by covering it up you can open, unlock, make calls etc. with it covered. I am coming from a LeMax 2 and never ever had a single problem with that phone. It had a setting in there and wouldn't allow you to accidently open, unlock, do anything if the sensor was covered. Does anyone have any workarounds for this or insight. I should be able to carry it in my pocket without it doing this. Thanks for any input.
You must have a detective prox sensor or something else is not working correctly with your phone. When I cover my prox sensor (with my hand or in my pocket) the screen does not come on for notifications, calls, or when I tap to wake.
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
retrov said:
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
Click to expand...
Click to collapse
Yes
I just tested my phone today and my screen does wake for incoming calls even when the prox sensor is covered.
This is very annoying.
It does not wake for notifications.
Very annoying for me as well. I guess it's the software program. With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
creeve4 said:
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
Click to expand...
Click to collapse
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
duh1 said:
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
Click to expand...
Click to collapse
It's all open source now. I have not experienced any bugs, it's working really well for me.
Search the magisk repo for Riru - Exposed. I use the sandhook variant. You can find links to more information in the module description.
GravityBox Pie has a thread on XDA.
retrov said:
With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
Click to expand...
Click to collapse
Sounds like an annoying bug to me as well.
Google / Pixel has a bug reporting system...
https://support.google.com/pixelphone/answer/6398243/
If we all submit reports, hopefully they'll take notice and the issue will be fixed in an update...
Just submitted a report on the issue. Thanks
Try the gravity screen app & see if it fixes your issues. I use it & the phone doesn't wake in my pocket for text notifications - but I'm not sure how it will respond to phone calls/notifications; it has options for proximity sensor & a "pocket sensor" feature as well.
retrov said:
Just submitted a report on the issue. Thanks
Click to expand...
Click to collapse
If we want this bug fixed in future updates, everyone should send in a report, especially with Google, squeeky wheel gets their attention...
Anyone that has a pixel 3a 3axl please submit a report on this issue.
My Pixel 3a ja behaving the same way. Coming from a OnePlus 5 with a splendid pocket mode this phone is really getting on my nerves. I love everything about this phone but the constant pocket answering is really bad. Thinking about stop using it...
I've tried every app in Play named pocket mode but nothing seems to work properly.
I've submitted feedback report a couple times hopefully everyone on here can do the same. Won't get fixed until they update on there end. That's the only bad thing I don't like about this phone so far.
Sent.
FYI - for others looking to do this, you file the report under your phone's Settings/About Phone/"Send feedback about this device"
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
acejavelin said:
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
Click to expand...
Click to collapse
Android 10 didn't fix this. I really hate Google right now.
I keep my current N6 phone in a wallet like case with a front cover. Do you guys think that might help?
I have just replaced my screen as my other developed a random crack in it... No I didn't drop it and it wasn't huge but I'm anal and ocd so I bought a replacement.
The replacement seemed to go well although I did get some of the factory glue on the sensor. I carefully cleaned it with microfiber and isopropyl alcohol. It looked good. Attached it to my new screen and connected the cable.
It seemed fine. Before glueing my new display down I tested it and the display worked but it didn't even see my fingerprint sensor. Reseated it multiple times and I've had no luck.
The fingerprint calibration won't work and it reports my version is too new. I'm tempted to factory reset but I don't know if it will work and I don't want to if I can help it. Any thoughts? It just doesn't see it at all.
awarman said:
I have just replaced my screen as my other developed a random crack in it... No I didn't drop it and it wasn't huge but I'm anal and ocd so I bought a replacement.
The replacement seemed to go well although I did get some of the factory glue on the sensor. I carefully cleaned it with microfiber and isopropyl alcohol. It looked good. Attached it to my new screen and connected the cable.
It seemed fine. Before glueing my new display down I tested it and the display worked but it didn't even see my fingerprint sensor. Reseated it multiple times and I've had no luck.
The fingerprint calibration won't work and it reports my version is too new. I'm tempted to factory reset but I don't know if it will work and I don't want to if I can help it. Any thoughts? It just doesn't see it at all.
Click to expand...
Click to collapse
Yes, this is a known issue. And it happened to me as well in February. My phone slipped off my desk and caused a big crack at the top corner, and me being anal like you, I took it to the local authorized screen repair. I didn't research beforehand, and learned that replacing the screen breaks the fingerprint sensor. The fingerprint calibration software doesn't seem to work for most people. What I learned is that it's a software issue and could be fixed with a software update. I haven't seen any update since then as there is still no fix.
I look forward to any others' feedback or knowledge because with no Face ID and no fingerprint unlock it gets annoying unlocking via PIN all the time.
darbylonia said:
Yes, this is a known issue. And it happened to me as well in February. My phone slipped off my desk and caused a big crack at the top corner, and me being anal like you, I took it to the local authorized screen repair. I didn't research beforehand, and learned that replacing the screen breaks the fingerprint sensor. The fingerprint calibration software doesn't seem to work for most people. What I learned is that it's a software issue and could be fixed with a software update. I haven't seen any update since then as there is still no fix.
I look forward to any others' feedback or knowledge because with no Face ID and no fingerprint unlock it gets annoying unlocking via PIN all the time.
Click to expand...
Click to collapse
I hoped for the best with it. I guess it's better than having a cracked screen but even this triggers me. Did you try a factory reset?
Have you tried installing a custom ROM? I'm currently using Spark OS and it has Face-ID enabled. I ran into the same problem but since I got face id I even forgot my phone had a fingerprint sensor haha
awarman said:
I have just replaced my screen as my other developed a random crack in it... No I didn't drop it and it wasn't huge but I'm anal and ocd so I bought a replacement.
The replacement seemed to go well although I did get some of the factory glue on the sensor. I carefully cleaned it with microfiber and isopropyl alcohol. It looked good. Attached it to my new screen and connected the cable.
It seemed fine. Before glueing my new display down I tested it and the display worked but it didn't even see my fingerprint sensor. Reseated it multiple times and I've had no luck.
The fingerprint calibration won't work and it reports my version is too new. I'm tempted to factory reset but I don't know if it will work and I don't want to if I can help it. Any thoughts? It just doesn't see it at all.
Click to expand...
Click to collapse
I know it's a little late but when something like this happens, its best to contact Google. There have been many reports of people getting replacements for small cracks or screens that won't turn on.
As for your issue - this is a known problem with the calibration tool. Some users have stated it takes 20 tries (on a windows system) in order to get it to work. A few also stated that they re-flashed Android with the web flash tool, and it worked after that.
Your last option would be to contact Google Support and see if they can provide any fix for the calibration tool.
There are a lot of users who are experiencing this issue on Google's Issue Tracker. Hopefully we'll see an update soon enough.
Alekos said:
I know it's a little late but when something like this happens, its best to contact Google. There have been many reports of people getting replacements for small cracks or screens that won't turn on.
As for your issue - this is a known problem with the calibration tool. Some users have stated it takes 20 tries (on a windows system) in order to get it to work. A few also stated that they re-flashed Android with the web flash tool, and it worked after that.
Your last option would be to contact Google Support and see if they can provide any fix for the calibration tool.
There are a lot of users who are experiencing this issue on Google's Issue Tracker. Hopefully we'll see an update soon enough.
Click to expand...
Click to collapse
There wasn't really any point for me to reach out to them because I don't have insurance and it's outside of the warranty period. They'd want me to send it in for repair which is not an option because I can't be without my phone due to work. It was a crack in the screen so there wasn't any way for them to fix remotely.
Perhaps I can try the android flash tool. Just didn't want to do a factory reset.
I might look into the custom rom. I heard about a rom having face ID, so I may head that direction
darbylonia said:
I might look into the custom rom. I heard about a rom having face ID, so I may head that direction
Click to expand...
Click to collapse
You can do it without a custom ROM. It's an Xposed module. I'm not running it and it's much better than fingerprint. I don't even care anymore about my fingerprint reader.
awarman said:
You can do it without a custom ROM. It's an Xposed module. I'm not running it and it's much better than fingerprint. I don't even care anymore about my fingerprint reader.
Click to expand...
Click to collapse
Can you link the module?
BlakeSm said:
Can you link the module?
Click to expand...
Click to collapse
Here it is. I'm using lsposed.
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com
awarman said:
You can do it without a custom ROM. It's an Xposed module. I'm not running it and it's much better than fingerprint. I don't even care anymore about my fingerprint reader.
Click to expand...
Click to collapse
I've been using it on my P6P and 3xl for a couple weeks now. It works awesomely
awarman said:
Here it is. I'm using lsposed.
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com
Click to expand...
Click to collapse
Wow this works flawlessly. This is a whole new phone now. Fingerprint reader can suck it
awarman said:
Here it is. I'm using lsposed.
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com
Click to expand...
Click to collapse
Awesome! I shall try this out! Thanks!
Hi all! I wanted to come back to this thread and report that I installed this module yesterday and it is fantastic! After installing the June build and I installed Lsposed then the Universal Face Unlock module and it's much better than a fast fingerprint unlock! Totally worth trying out!
Wanted to share in case this helps anyone with a replaced screen or anyone who wants to try another option to FP unlock
Something similar happened to me. The solution was to use the fingerprint calibration tool and instantly reboot the phone. Not sure if it will work, but worth a shot.
mkhcb said:
Something similar happened to me. The solution was to use the fingerprint calibration tool and instantly reboot the phone. Not sure if it will work, but worth a shot.
Click to expand...
Click to collapse
I tried that solution but it didn't work for me. It was reported to have minimal success rate. This face unlock module has been great so far for me!
awarman said:
I hoped for the best with it. I guess it's better than having a cracked screen but even this triggers me. Did you try a factory reset?
Click to expand...
Click to collapse
I did a factory reset which didn't resolve the fingerprint detection issue after my screen replacement last week. It did resolve the "newer version" message but resetting took me back to Android 12 as I was on 12 quarterly.
The calibration tool will not download and errors out. As @roirraW "edor" ehT mentioned, there is a defect opened in bug tracker since February but no status on ETA. A user reported success downloading the calibration tool when using a Chromebook. For me, download failed on both Mac and Windows.
johninsf said:
I did a factory reset which didn't resolve the fingerprint detection issue after my screen replacement last week. It did resolve the "newer version" message but resetting took me back to Android 12 as I was on 12 quarterly.
The calibration tool will not download and errors out. As @roirraW "edor" ehT mentioned, there is a defect opened in bug tracker since February but no status on ETA. A user reported success downloading the calibration tool when using a Chromebook. For me, download failed on both Mac and Windows.
Click to expand...
Click to collapse
Since my phone was still under warranty I went into a ubreakifix and after several trips, because my spectral sensor was bad too, I now have a fully repaired phone. Everything is working great on it now. Nice to have the fingerprint sensor back but I'm still using the face unlock mod except for with banking apps and gpay.
Ubreakifix let me know that you can't successfully move your old fingerprint to a new display as it won't pair. They had to replace using a kit with the display and a new fingerprint sensor included.
Thank you!
Interesting that ubreakifix said that you can't "move" a fingerprint to a new screen. Maybe that is what they did for you since you didn't factor reset? Honestly, I don't understand much of this but I performed a full factory reset so, for me, this isn't about moving a fingerprint. What do I know though!
The screen installed on my phone has a fingerprint reader and came from the screen supplier. I have read that others successfully installed and calibrated their screens if they got the calibration tool to download. I am hoping I can do the same once Google fixes the issue with the calibration tool download. I will also borrow a Chromebook from work and give it a try on there in the interim.
Thanks again for the insight! I appreciate your response.
I think that the calibration tool only work if the fingerprint setting still available and when the enrollment fail.
If the fingerprint setting is gone seems like the sensor is damaged or not connected correctly.
I have same problem after replacing my screen,the fingerprint print setting has gone.