Hi guys, the fingerprint scanner was working fine when I first got the device. I could unlock the device just by doing a soft touch on the home button and it would unlock from a dead screen. After taking the t-mobile update, I would have to wake the device first then do the soft touch in order to unlock it. Has anyone gotten this problem or is it just me? It is starting to bug me with would like others to let me know if they can unlock the device without waking it by just doing a soft touch on the home button. Your input would be much appreciated.
akong702 said:
Hi guys, the fingerprint scanner was working fine when I first got the device. I could unlock the device just by doing a soft touch on the home button and it would unlock from a dead screen. After taking the t-mobile update, I would have to wake the device first then do the soft touch in order to unlock it. Has anyone gotten this problem or is it just me? It is starting to bug me with would like others to let me know if they can unlock the device without waking it by just doing a soft touch on the home button. Your input would be much appreciated.
Click to expand...
Click to collapse
Re-Register your print
Brava27 said:
Re-Register your print
Click to expand...
Click to collapse
Tried it, also did a factory reset and you still have to wake the device and have your finger scanned. When I first got the phone and set it up, I was able to unlock the device just by soft touching the home button, but after the update that t-mobile pushed, I'd have to wake the device then have my finger scanned. If anyone can confirm that you can unlock the device just by soft touching the home button, before you took the update that would be appreciated.
akong702 said:
Tried it, also did a factory reset and you still have to wake the device and have your finger scanned. When I first got the phone and set it up, I was able to unlock the device just by soft touching the home button, but after the update that t-mobile pushed, I'd have to wake the device then have my finger scanned. If anyone can confirm that you can unlock the device just by soft touching the home button, before you took the update that would be appreciated.
Click to expand...
Click to collapse
i thought you had to turn the phone on first?
Akong, I'm having the same issue. Updated and now I have to click to open the phone, even after a hard reset.
entropism said:
Akong, I'm having the same issue. Updated and now I have to click to open the phone, even after a hard reset.
Click to expand...
Click to collapse
I just cant remember if it was like this before or if it is indeed the updates fault, are you sure it worked with screen off before?
tenxo said:
I just cant remember if it was like this before or if it is indeed the updates fault, are you sure it worked with screen off before?
Click to expand...
Click to collapse
Going to put it at pretty sure. Say, 90% certain?
Scroll to 2:15 seconds he says press and leave on the button...Also he has his finger on it before he presses it, but it doesnt unlock until he presses it. Not saying you guys are wrong just trying to help figure it out.
https://youtu.be/_Kc4NgYS1rs
you have to wake the device first. that has been my experience with it thus far.
mrvirginia said:
you have to wake the device first. that has been my experience with it thus far.
Click to expand...
Click to collapse
You have the S6? last I saw of you was in the s4 your slim downed rom, you planning on DEV if you have it?
tenxo said:
You have the S6? last I saw of you was in the s4 your slim downed rom, you planning on DEV if you have it?
Click to expand...
Click to collapse
yes, i do have the S6. there's a possibility but i'm more interested in taking advantage of Samsung's theming tools once they are released.
tenxo said:
Scroll to 2:15 seconds he says press and leave on the button...Also he has his finger on it before he presses it, but it doesnt unlock until he presses it. Not saying you guys are wrong just trying to help figure it out.
https://youtu.be/_Kc4NgYS1rs
Click to expand...
Click to collapse
For all we know, he updated the software before doing the video. Not saying it's right or wrong, just putting that out there.
Yes, I am 100% sure that a soft touch on the home button would wake and unlock the device. I set my finger print at first start and I was playing with the scanner for a good 30 minutes. A soft touch would unlock the device without waking it, but after taking the update I would have to wake the device to unlock it. Maybe the update changed it?
Sent from my SM-G920T using XDA Free mobile app
Just tested this on brand new AT&T 64GB Edge
Must press button first and leave thumb on. It unlocks in about half a second.
Related
Hi All,
Been having this issue for a while now.
Basically with my tablet docked and the option which disabled keyboard wake up in the settings UNTICKED I cannot wake my screen once the screen has been locked for longer than 30seconds.
No matter what I do i.e use the touchpad or press keys the only way to wake the screen is via the power button.
It's extremely frustrating has anyone had the same issue previously?
KinetiClutch said:
Hi All,
Been having this issue for a while now.
Basically with my tablet docked and the option which disabled keyboard wake up in the settings UNTICKED I cannot wake my screen once the screen has been locked for longer than 30seconds.
No matter what I do i.e use the touchpad or press keys the only way to wake the screen is via the power button.
It's extremely frustrating has anyone had the same issue previously?
Click to expand...
Click to collapse
Are you using custom kernel?
buhohitr said:
Are you using custom kernel?
Click to expand...
Click to collapse
Yeah CROMI. Tried both thats and hunds kernels both with same result.
KinetiClutch said:
Yeah CROMI. Tried both thats and hunds kernels both with same result.
Click to expand...
Click to collapse
And you UNCHECKED the MobileDock Battery saving mode located in settings--> Asus customized settings?
buhohitr said:
And you UNCHECKED the MobileDock Battery saving mode located in settings--> Asus customized settings?
Click to expand...
Click to collapse
100% I made sure. I've been through all other options and can't figure out why this is happening. Is been the same across numerous full wipes. I could make a video to show the issue if it helps?
KinetiClutch said:
100% I made sure. I've been through all other options and can't figure out why this is happening. Is been the same across numerous full wipes. I could make a video to show the issue if it helps?
Click to expand...
Click to collapse
try the key with the lock see if that works.(top right handside of the keyboard).
buhohitr said:
try the key with the lock see if that works.(top right handside of the keyboard).
Click to expand...
Click to collapse
Tried it only works to unlock when the screen is on. Then it works. The issue is turning the screen on via the keyboard.
I don't think ths has worked since JB came in. The behaviour you are describing is default I believe. If the screen self locks then you don't get much time to use the touchpad to unlock it.
On mine when I open the lid it unlocks the screen. Does yours do this?
KinetiClutch said:
Tried it only works to unlock when the screen is on. Then it works. The issue is turning the screen on via the keyboard.
Click to expand...
Click to collapse
OK, last try, disabled the screen lock (no lock screen) and see if it wakes.
sbdags said:
I don't think ths has worked since JB came in. The behaviour you are describing is default I believe. If the screen self locks then you don't get much time to use the touchpad to unlock it.
On mine when I open the lid it unlocks the screen. Does yours do this?
Click to expand...
Click to collapse
Yeah when I open the lid this does wake the screen.
I guess this must be it, weird is it even worth the bother of emailing ASUS?
It's weid that when THAT tried it for me he had no issues with it, unless he wasn't leaving it for long enough. Noticed that tonite i've had no issues with using the trackpad to wake the screen however, spotify is running so maybe that interferes with the locking process?
Thanks for the help Buh, but don't think it's worth disabling the lock screen completely just to get this working!
KinetiClutch said:
It's weid that when THAT tried it for me he had no issues with it, unless he wasn't leaving it for long enough.
Click to expand...
Click to collapse
I tried it this morning (after 6 hours sleep time), and it still worked - I hit the lock key, and the tablet was awake instantly - how unfair, I was still sleepy.
_that said:
I tried it this morning (after 6 hours sleep time), and it still worked - I hit the lock key, and the tablet was awake instantly - how unfair, I was still sleepy.
Click to expand...
Click to collapse
I hate you
I guess this is my tablet punishing me for using such poor stock ROM's on it for so long
I also have this problem when I use Cromi. I found that I can "fix" it by clicking and unclicking "MobileDock Battery saving mode" whenever I reboot the tablet-doing so allows me to wake the screen using the keyboard. Also, see if you have the same problem with Cromi-X. I recently upgraded to Cromi-X and the keyboarding waking screen problem went away.
I had the same issue, and fixed it with a clean wipe and install...
Hey guys,
I flashed my OnePlus One to 5.02 (TimOs) and it has been working alright for now (ignoring the somewhat reduced internet speed) but now I've noticed that every 15-20 unlocks, it just won't unlock. I can hold down the power button and eventually it will reboot or wait for around 30-60s and eventually the screen will turn on.
I have tap to wake enabled but neither the power button nor the double tap wakes the phone.
Anyone got any suggestions as to why this might be happening?
Thanks
Cheesus182 said:
Hey guys,
I flashed my OnePlus One to 5.02 (TimOs) and it has been working alright for now (ignoring the somewhat reduced internet speed) but now I've noticed that every 15-20 unlocks, it just won't unlock. I can hold down the power button and eventually it will reboot or wait for around 30-60s and eventually the screen will turn on.
I have tap to wake enabled but neither the power button nor the double tap wakes the phone.
Anyone got any suggestions as to why this might be happening?
Thanks
Click to expand...
Click to collapse
This happens in some specific ROMs,flash another and it should be gone.
I've tried 2 ROMs, it always happens, only on lollipop though.
Cheesus182 said:
I've tried 2 ROMs, it always happens, only on lollipop though.
Click to expand...
Click to collapse
Did you try from official CMmod webpage?
How did you flashed your ROMs,dirty install or clean?
I havent tried official one yet no, might give that a try later.
Clean install, wiped everything.
I heard that it could be something to do with the proximity sensor?
Cheesus182 said:
I havent tried official one yet no, might give that a try later.
Clean install, wiped everything.
I heard that it could be something to do with the proximity sensor?
Click to expand...
Click to collapse
It`s a bul**** i had the same issue and tried another rom that fixed it. But now i`m on official nightly and it`s fine. Give it a go
I have this problem that, whenever I press the power button to turn on the screen, I have to swipe twice in order to unlock the phone. I turned on "Show Touches" in the dev menu and it shows that my XA thinks that there is a touch already on the lockscreen so I have to touch it once to get it to realize that it isn't bring touched so I can then unlock the screen with a second touch.
I've also encountered an issue when swiping down from the top to get the notification menu to pull down but it freaks out and jumps around until the third swipe to get it to come down.
Anybody else have this problem or even just a workaround?
I'm on 33.2.A.3.81. and I'm unable to update.
Battery is also crap without Stamina Mode on too.
goldblot said:
I have this problem that, whenever I press the power button to turn on the screen, I have to swipe twice in order to unlock the phone. I turned on "Show Touches" in the dev menu and it shows that my XA thinks that there is a touch already on the lockscreen so I have to touch it once to get it to realize that it isn't bring touched so I can then unlock the screen with a second touch.
I've also encountered an issue when swiping down from the top to get the notification menu to pull down but it freaks out and jumps around until the third swipe to get it to come down.
Anybody else have this problem or even just a workaround?
I'm on 33.2.A.3.81. and I'm unable to update.
Battery is also crap without Stamina Mode on too.
Click to expand...
Click to collapse
Do you use glass protector?
You can you test the touchscreen w/o the glass protector.
settings > about phone > diagnostics > test > test the touch screen
With the battery Unfortunately it is true that the battery is not a super long lasting device, but with moderate use of the device(not stressing it) the battery last me through out the day.
Siam4k said:
Do you use glass protector?
You can you test the touchscreen w/o the glass protector.
settings > about phone > diagnostics > test > test the touch screen
With the battery Unfortunately it is true that the battery is not a super long lasting device, but with moderate use of the device(not stressing it) the battery last me through out the day.
Click to expand...
Click to collapse
I don't use any protectors at all.
And, for some reason, there isn't a "diagnostics" under "about phone" in the settings.
The battery drain is weird because it can drain really quickly (with verrrrrry little use, literally just turning it on every hour to check the time).
If you want to test your touchscreen, you can open diagnostics by press *#*#7378423#*#* in phone app.
Hope this help! but I never faced this problem before, better check with Sony service.
civilzaza said:
If you want to test your touchscreen, you can open diagnostics by press *#*#7378423#*#* in phone app.
Hope this help! but I never faced this problem before, better check with Sony service.
Click to expand...
Click to collapse
For some reason, it checks out fine. It just acts weird like in the op only at the lock screen.
goldblot said:
I don't use any protectors at all.
And, for some reason, there isn't a "diagnostics" under "about phone" in the settings.
The battery drain is weird because it can drain really quickly (with verrrrrry little use, literally just turning it on every hour to check the time).
Click to expand...
Click to collapse
Did you get the last firmware update for your phone?
try to install the latest firmware for the phone and get security patch.
Siam4k said:
Did you get the last firmware update for your phone?
try to install the latest firmware for the phone and get security patch.
Click to expand...
Click to collapse
Does root still work with the latest update?
And trying to update via Flashtool doesn't work, don't know why.
goldblot said:
Does root still work with the latest update?
And trying to update via Flashtool doesn't work, don't know why.
Click to expand...
Click to collapse
You can use Flashtool to update your device after root and use the included Xperifirm to download the firmware.
http://www.xperiablog.net/2017/02/2...te-33-2-x-4-70-with-january-security-patches/
download the lastest update for your device(depend on your phone .model )and follow instructions
i have this problem how i can fix it ? Any soliton ?
PislickB3 said:
i have this problem how i can fix it ? Any soliton ?
Click to expand...
Click to collapse
No solution just yet for me even updated to Nougat 7.0 update through flashtool. I think I'll just break down and send it in to Sony soon but I'm exploring other options before I do that.
goldblot said:
I have this problem that, whenever I press the power button to turn on the screen, I have to swipe twice in order to unlock the phone. I turned on "Show Touches" in the dev menu and it shows that my XA thinks that there is a touch already on the lockscreen so I have to touch it once to get it to realize that it isn't bring touched so I can then unlock the screen with a second touch.
I've also encountered an issue when swiping down from the top to get the notification menu to pull down but it freaks out and jumps around until the third swipe to get it to come down.
Anybody else have this problem or even just a workaround?
I'm on 33.2.A.3.81. and I'm unable to update.
Battery is also crap without Stamina Mode on too.
Click to expand...
Click to collapse
This is called Ghost Touch. I read you don't use any kind of protectors so it is a hardware problem and you can't fix it with software repair. If you have warranty use it, if not you will need to open it and remove connectors and put them back. Most of time that will solve problem, but my advice is to send it to service (there is electricity problems from you and all other things that you can screw up if you are not careful). You can try to google for more informations, but mostly you will end up with what I wrote you.
Edit: Because you have that problem, phone thinks you are using your screen whole time and it never goes to sleep could be a problem for a battery drain.
An hour or so ago everything worked fine, and then I updated my playstores pending apps (only Fleksy was pending) and the "force touch" feature of the phones seems to have completely stopped working, no matter what setting I turned on or off it didn't work...
Anyone has a clue as to what can cause this?
General notes:
1. Using stock Exynos unlocked variant
2. I am using package disabler (which btw didn't improve much my battery life, but that might be just me using the phone too much ) so maybe one of the packages decided that it depends on a disabled one?
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
RazoE said:
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
Click to expand...
Click to collapse
Mine also stop working after I restart my S8 Plus, it will again work if I wait around 20 minutes. Is this software or hardware problem? Any solutions?
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Ady1976 said:
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Click to expand...
Click to collapse
How does it act up on your part? Mine would just stop working if I restart the phone & I should wait sometimes hours before it would work again.
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Ady1976 said:
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Click to expand...
Click to collapse
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
bladefrost said:
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
Click to expand...
Click to collapse
Unless your phone is unlocked no pins etc the phone will just go to the lockscreen, it's a useless feature, most people have the phones locked and thus it's a complete waste of time, it sounds to me the capacitive home button part of the screen was an afterthought because they couldn't install the fingerprint reader under the screen, just had a software update yesterday and still can't turn it off, basic stuff Samsung should enable an ON/OFF toggle switch for this.
Had the same problem with my S8 Plus India Variant(SM-G955 FD), I got my screen replaced from service center, Device was not rooted back then, so was under warranty.
But it is an hardware issue, as since then it has never gone off.
I mean when I press the home button hard it doesn't wake the phone up & no vibration. It happens when I restart the device then it would stop working for few minutes to a few hours sometimes, then it would start working again normally until I restart the phone again. I think this is just a software issue.
I have my Smart Lock enabled on my phone with my watch as a trusted device, and several times a day it randomly stops working. Rebooting fixes it for a while.
Anyone one else experiencing this and have found a fix?
I read on Reddit that the March security update broke something and there is no fix yet.
I try to go into it and it doesn't give me any options to add devices, places, or anything like that.
Wonder if this may be one reason why some are having troubles...
https://twitter.com/i/web/status/1648044309382418432
Superguy said:
I try to go into it and it doesn't give me any options to add devices, places, or anything like that.
Click to expand...
Click to collapse
Try pressing Power + Volume up to bring up the power menu, then press lockdown. Enter your screen lock code and then hopefully your smart lock options should be available again. It worked whne this happened to me.
synesthete said:
Try pressing Power + Volume up to bring up the power menu, then press lockdown. Enter your screen lock code and then hopefully your smart lock options should be available again. It worked whne this happened to me.
Click to expand...
Click to collapse
That worked. Thanks!
Thx, had this same problem on my 6a, even after upgrading to April update.
But honestly I always have some kind of issue with Smart Lock...
The reason why Google doesn't allow this when connected to a trusted WiFi network is beyond my understanding...
Have issues with Smart Lock all the time. Have it set so that my phone remains unlocked at home and in the car and it really only seems to work 50% of the time which is just annoying.