Anyone else having trouble with Double Tap to Wake?
Mine will work but I have to tap in a very specific way, and even then I only get success 50% of the time. On my Z3 compact it worked flawlessly regardless of how I tapped.
I flashed to UK firmware so maybe that is an issue? I only used the original US firmware for 5 min before flashing to UK so I never tried Double Tap to Wake before the flash.
I just tested it and mine works fine. Fast double tap or slower double tap, it works for me.
It seems to only work well for me if the screen was already on shortly before trying it.
Ok, thanks for checking. I ended up returning my phone
Related
I used the update.zip from the Samsung site to update to EB13, everything went off just fine except my Epic now takes an average of 2 seconds to wake from sleep after pressing the power button, sometimes going up to 4 or 5. Not the worst thing in the world, but pretty annoying.
I narrowed it down to my non-usage of the lock screen. I typically run without using a lock screen at all (disabled via SwitchPro Widget). If I turn the lock screen back ON, my Epic wakes from sleep either instantly or within 1/2 a second. With the lock screen disabled (no pattern lock either), it's super slow to wake.
Anyone have any ideas on what I could try?
Mine works just fine, but I'm using the lock screen, try uninstalling that widget and see if it corrects the problem when you use the lock screen.
Small update to this. I had an idea to move all the apps that I had moved to the SD card back to the phone to see if that helped. It does. With the lock screen on, my Epic comes back from sleep instantly every time. With lock screen off it varies between 1/2 and 1 second.
The apps I moved to SD were ones I hardly used.. I don't know why that would have an effect on the wake time?
Mine seems a bit slow too. But it's not the 4 or 5 seconds you described. It seems like it's about one second, when it used to be anywhere between instantly and half a second.
It's kind of annoying because the delay is just barely too long to where I start second guessing myself on whether or not I pushed the button in all the way or not.
Go to your display setting and reset your horizantal calibration accelerometer... that fixed my phone waking up issue...
Sent from my SPH-D700 using XDA App
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
toxicsociety said:
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
Click to expand...
Click to collapse
I use the same program as you do and I have the exact same problem So your not alone.
Mine is slow to wake also, about a second. When its plugged into the charger its instant, weird.
I'm glad we aren't alone though. Hopefully if this is a big enough issue, people will look into it. And also, they've pulled the EB13 update from Sprint and Samsung's website.
It's causing problems with reading media from the SD card and also has data issues. So hopefully in the new one, they will fix this problem too?
Looks like it's No Lock, from what I can tell. If you disable it, it comes on instantly. If it's enabled, it takes it a moment to wake up.
Well those of you like myself that were having the issues of hitting the power button only to see a black screen, here is all I did and its been working flawless for 24 hours. Turn of the screen lock! I haven't tested other screen locks yet so maybe its just the default one
If this dose not work for you please post.
Trying this myself now. It had previously happened 3 times to me with the default lock screen. If this does work, that sucks cause I really liked the lock screen... Does anyone know if either of the firmware updates addresses this particular issue? I haven't done them yet was waiting for the new root method which was just released yesterday.
maybe that's why i never had that problem... i always had a pin from day1
I am updated to the latest firmware and the issue still existed. Are you running a battery monitor widget?
turning off screen lock didn't do the trick for me
what worked for me is disable wifi before turning the screening off or go into option and change it so that it never disconnect from wifi will fix the issue for me though
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
fhblake04 said:
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
Click to expand...
Click to collapse
Surprised you're the first to bring this up, lol! Been watching this device closely on on youtube reviews on this device you can see it right infront of your eyes. Doesn't ALWAYS wake on double tap but does ALWAYS turn off, weird. Idk what to tell ya but yes it isn't just you...
Are you using the stock launcher?
I switched to Nova and noticed its very finicky for me ever since I stopped using the stock launcher.
Still on stock launcher.
I just tap it 4 times when turning on, no big deal.
The only time it fails for me is if I tap too softly. I notice that when turning it on, it does take two distinct forceful taps. It seems to register anything else as a touch. So, while I think it could be better, I don't see it as inconsistent. If it was too sensitive, it might end up turning on in your pocket.
I think it has to do with the motion sensor in the phone. Mine works fine if I just tap it twice while it's in a steady position (even in my hand), but when I'm riding my bicycle I can't get it to tap "on" most of the time (unless I stop). Tap off works much more reliably.
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Tapping near top of screen seems to work much better.
geoff5093 said:
I just tap it 4 times when turning on, no big deal.
Click to expand...
Click to collapse
Exactly.
Can't have both battery life and also expect the Knock feature not to go to deep sleep. I prefer to eat my cake.
Also, I like that it does not accidentally turn in my pocket or when gripping the screen in my hands, etc.
The Korean version has gotten a few updates to make KnockOn smoother, so you might not have that update yet.
Well, I have a VZW version so updates will not be plentiful lol. Knocking on it several times, rather than twice seems to work better. Thank you guys for your suggestions.
jayochs said:
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Click to expand...
Click to collapse
Maybe we should shake it a few times and then double-tap the screen. It would be like a Moto X/LG G2 hybrid!
I’m doing a study right now with this feature by recording the time and results. So far 3 quick knocks resulted in successful power ups 100% of the time (7 for 7). When doing 2 knocks (prior to the study) it was intermittent to the point of driving me crazy.
Come to think about it when you knock on someone’s door do you knock 3 times or 2? I always knock 3 times but the video reviews of this feature messed my thought process up with 2. First world problems I guess. LOL
I will report back with my results tonight.
BaronInkjet said:
Tapping near top of screen seems to work much better.
Click to expand...
Click to collapse
Same for me. It says you need to either tap in the middle or top of screen. Anywhere else doesn't work as well.
Sent from my LG-D801 using xda app-developers app
Seems to work best if you tap where the lock screen widgets are located -- top center, but not at very top.
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
I have an explanation. I think this happens because when the phones asleep (screen and touch panel is off), knockon uses the motion of the phone, read by the accelerometer, to recognize that two-tap pattern and subsequently turn on.
When the phone and screen are on though, the mechanism happens by direct touch input and is much more reliable, so it should happen every time.
This would explain why in moving situations like riding a bike, or when I was trying to turn it on while it was on the bed, which probably absorbed the motion from the taps it doesn't work as well.
I did hear that the Korean version got a firmware update that helped, though who knows when we'll see that in America.
razball said:
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like a defective phone.
Factory reset time!
Good to know dam lol that's annoying well I guess I'll wait till it happens again to be really sure
Sent from my LG-D801 using Tapatalk 2
I got my S7 Edge less than a week ago and am loving it so far. Prior to this phone, I had an LG G3 for over 2 years. One feature I miss from that phone is the ability to double tap the screen when it was asleep and wake it up as if I had pressed the power button. It's nice if the phone is sitting on the table and I just want to quickly wake it up to check my notifications. I even find myself trying to double tap the screen to wake it out of habit. I've seen a few solutions on the Play Store, but some of them ask for questionable permissions and I won't be free to play around with them for a while.
TL;DR - Do any of you have suggestions for a means to get double tap to wake on the S7? I'm rooted in case that makes a difference.
Double tap to wake is implemented in the kernel, Samsung does not have it in the kernel. You cannot use a kernel that is not signed by Samsung so it is not going to happen.
nrage23 said:
Double tap to wake is implemented in the kernel, Samsung does not have it in the kernel. You cannot use a kernel that is not signed by Samsung so it is not going to happen.
Click to expand...
Click to collapse
That's unfortunate, but makes sense. Thanks for the reply.
This worked perfectly out of the box but recently has stopped working. Not sure if it has to do with the QD9 update or maybe some other crap that installed. I can set the location fine and it clearly shows me inside the boundary but every time I get to the locks screen it still doesn't unlock automatically.
Anyone else have the same issue?
mobilehavoc said:
This worked perfectly out of the box but recently has stopped working. Not sure if it has to do with the QD9 update or maybe some other crap that installed. I can set the location fine and it clearly shows me inside the boundary but every time I get to the locks screen it still doesn't unlock automatically.
Anyone else have the same issue?
Click to expand...
Click to collapse
I've had the same issue on my last phone and now the S8 as well. From what I've heard it's a Google issue and they are supposedly working on a fix.
Sent from my SM-G950U using Tapatalk
I'm noticing this issue too. A reboot fixes it, but annoying none the less.
WorldIRC said:
I'm noticing this issue too. A reboot fixes it, but annoying none the less.
Click to expand...
Click to collapse
The problem with Trusted Place is that it’s very spotty! It only works for a day or two then fails to unlock the device. I’ve set two different locations, one for home and another using the latitude and longitude location. Only way to get it working is to reboot the device. Regrettably, it only works for a day before reverting back to my lock screen method again.
this not related to the galaxy s8. even my nexuw 6p and pixel. had this problem. it works when u set it up the. it jist stoppwd working after a few days. a restart or setting it uo again does work but same issue will happen next oe a few days after. bluetooth trusted device works but location is a problem. related to nougat.
Yep can agree with everything said here seems to work sometimes then other times not...Also I can't believe that google won't allow your home wifi network to be used as a trusted device.
I t seems like a obvious choice to me to use your home wifi as a trusted device but hey what do I know.
Let's wait for an update
Same issues here in India also.
Google Play Services 11 fixes this issue. I'm on 11.0.55 and it works consistently every time.
mobilehavoc said:
Google Play Services 11 fixes this issue. I'm on 11.0.55 and it works consistently every time.
Click to expand...
Click to collapse
I have 11.0.55 on my new S8+ and it doesn't work for me.
Mine suddenly started working today for no particular reason.
I hadn't changed any settings but when I came home it just unlocked.
Strange or what!
mine still isnt working, its infuriating as I wear glasses at work do I have to take my glasses to unlock.
Anyone else got location unlock working properly?
Note to future self
Note to future self :
found the solution on the Samsung community web site (cannot post links...).
us[dot]community[dot]samsung[dot]com/t5/Galaxy-S8-Questions-and-Answers/Smart-Lock-Not-Working-Reliably/td-p/103398
need to do a "Wipe Cache":
* Turn off phone
* Press Volume Up key and the Bixby key, then press the Power key
* When the logo appears, release all keys
* Press the Volume down key several time to highlight "wipe cache partition"
* Press the Power key to restart phone
Another way that does not require to go into recovery mode but seems to fix the problem for shorter time :
* Settings -> Apps -> Google Play Services -> Delete cache
* Reboot
I've also added bunch of points in all corners around my house in the Trusted Places settings