Weird unlocking issue - Galaxy S6 Q&A, Help & Troubleshooting

I have a weird issue when I'm unlocking my regular s6 with the finger print scanner. Pretty much 50% of the time when I unlock the phone, it's unlocks the in some app. Chrome, Facebook, message, gallery, app drawer or even in a folder. When I lock the phone it's on the main home screen. It's Like the touch screen is working when the screen is turned off. I have no issues with the touch screen when the screen is turned on. Anyone having similar issues?

Same problem here. It's weird... It seems random the application starting.

Related

Touch screen doesn't work when device woken up (Intermittent)

I've got an intermittent problem - sometimes when I wake the phone up, the touch screen doesn't work. It happens when I wake it up with the power button, when someone calls, or when an alarm wakes up the screen. That means when the problem happens, I can't answer the call, or turn off the alarm (sometimes locking the screen and waking it up immediately works).
It doesn't seem to be affected by whether or not the phone is or has been charging, whether it's been in my pocket or the temperature of the device. I've not been able to discern a pattern at all. Once the phone is unlocked and the touchscreen is working though, it works perfectly. The problem never returns while I'm using it, only if I lock it, and only sometimes.
If I leave the screen on while touch is unresponsive, I can tell when it is responsive to touch again by a line that quickly flashes along the top edge of the screen. At that point, the screen operates entirely normally.
In what may be a related item, when I'm on a call, sometimes the proximity sensor doesn't work properly and the screen turns back on and starts working. I get off the call and find my phone in a different app.
Does the Nexus 5 use the proximity sensor while the screen is off as a way to weed out unintended touches while the phone is in a pocket?
I'm going to try and store it face up over the next couple of weeks and see if the problem continues, but I was hoping that someone might have some insight.
About the phone:
I cracked the screen over the summer and had it replaced, but I didn't have any issues with it at all until I installed Lollipop. 5.0.1 hasn't made a difference

[Q] Leagoo Lead 1 unlock screen unresponsive

Hi All,
I've got a leagoo lead 1 here. Phone works great however it has a developing problem.
When turning on the screen the phone won't unlock by swiping or pin patterns or anything that involves screen contact.
Turning the screen repeatedly on/off/on/off etc gets the screen to respond. once the phone is unlocked everything works fine as it should be. I'd reckon it is not a screen failure then because it is very repsonsive once unlocked.
The problem only occurs when the screen needs to be unlocked. Tried the stock launcher as I suspected nova launcher to be the culprit but the problem remained.
Anyone usefull tips/tricks?
btw. Restart and batterypull didn't resolve the matter

Lockscreen Bug

Can anyone confirm whether this happens to them. I have fingerprint lock with either a pin or pattern as backup.
If on the lockscreen I swipe the screen rather than use the fingerprint lock the pin/pattern screen comes up with the blurb "Use Fingerprint or draw unlock pattern" However when i then put my finger on the scanner it doesn't register, its as if i haven't put my finger on the button. The only way I can access is via inputting pattern/pin. Once i have done this i can repeat by locking the screen and swiping and the reader registers.
However if i leave the phone for 10-15 minutes it then goes back to not registering the fingerprint on the pin/pattern screen again?
Anyone else getting this?
Getting the exact same issue on the Galaxy S7Edge with Australian firmware, and it completely ruins the usefulness of the fingerprint unlock method.
It's definitely a bug in the software - a few people have already experienced the exact same issue we have encountered over at:
http://forum.xda-developers.com/verizon-s7-edge/help/fingerprint-reader-half-lockscreen-t3341574
Hopefully Samsung are at least aware of the issue and can patch it..
I had something called lock screen launcher or something like that I did uninstall it and it was normal again
Sent from my SM-T700 using Tapatalk

[SOLVED] Half of the screen flickers black between unlock and home screen

Couldn't find any similar topic except in forums for s10+, OnePlus and other phones. Sorry if I missed anything.
As in the subject, after unlocking, approximately half of the screen flickers black and goes to the home screen. It takes less than a second. Always top half, bottom half shows home screen right after unlock. This does not happen on each unlock, but also, there is no pattern - it can be after 5 or 30 unlocks, it can be after 5 minutes or 10 hours of not using the phone. It started mid-July and not only annoys but is starting to worry me. Solutions from other threads didn't help. For example:
Fingerprint sensor problem - I don't use it, I have pin lock.
Samsung Pay issue - I don't even have it available, so, don't use it either .
Animations - setting them off did not help.
I cannot guess anymore what would be the cause, if it's some app which wakes up after unlock or what else. The only thing I've changed (except updating apps) was adding another sim card, but my tiny little brain cannot find connection. I didn't test removing it as I need this sim active and don't have backup phone right now. Also, I would really like to avoid resetting the phone...
Did you experienced anything similar?
Thanks a lot for any help or suggestion.
are using Samsung or some third party launcher. Did you wipe cache? Latest firmware updates?
Yes, I did both, firmware update and cache wiping, no change. I'm using stock launcher.
did you try in safe mode to exclude some app causing it
Yes, I tried safe mode without success.
i would take it to Samsung repair centre if pos
Thanks for trying and all the steps. There's nothing like that where I live, neither any advisory place except for hotline. I can drop it at their service but will need to wipe it down before, which I keep as the last resort. I'll keep waiting for another firmware update and if nothing changes then I'm willing to do the hard reset. I just hope it's not a symptom of some virus - I'm trying to be most careful, scanning device periodically, didn't root, so I naively count on being safe...
i don't think it's virus. fingers crossed it's just software issue
hi again, just to let you know, I think I know what was causing this flickering and now I feel silly . Home screen rotation. I had this option turned on, and it's possible that sometimes, when I put my phone on the table, home screen rotates to horizontal position. Of course it locks after few seconds. I've noticed it completely accidentally, because one time, when screen flickered black there was slow-motion rotation animation in the background (which I've never seen before). That's why flickering was completely random to me, not connected to any type of notification whatsoever. Well, it's not, it has a pattern . I've checked it plenty of times and each time I lock my phone with home screen in horizontal view, but unlock in vertical, half of the screen is flickering black. That's it, at least I believe it must be this, because it happens each time and never when I lock my screen in vertical position.
Once again thanks for all the help!

Question Fingerprint scanner issue, s22 ultra

my touch screen stops working from exact fingerprint scanning area,then i have to press lock button then unlock by finger scanning, and it starts working again, it happens very frequently. its very annoying it doesnt let me scroll the web page, facebook or twitter, whenever my finger reaches scanning area either it register a click and opens the link or it does not scroll, again i have to do locking unlocking and it works fine again. restarted my device, wipe cache partition, but couldn't solve my problem.
Samsung s22 ultra
Do you have a screen protector and if so what type
Yes , hydrogel screen protector.
Then possibly it to blame
But it works fine after locking unlocking,may be its a software bug

Categories

Resources