Related
Last week I have released the Screen Dimmer kernel modification. While the feedback was very positive, it became clear that this mod had the limitation that the FLAG_KEEP_SCREEN_ON (set in apps, which prevents the screen lock from activating) was not preventing Screen Dimmer from blanking the screen. So if you wanted to watch a movie and did not want the screen to be dimmed all the time, you had to manually deactivate the Screen Dimmer for this period and re-enable it afterwards. Also the battery drain while the screen was dimmed was much higher compared to a proper screen lock, since only the display and the access to the framebuffer was disabled - the other hardware was still enabled and most importantly the Android OS and the apps were still running.
I thought that I could do better than that and tried to find a way to achieve the same what Screen Dimmer was doing without running into its limitations. Since the Android OS power manager handles the FLAG_KEEP_SCREEN_ON and also suspends the OS and running apps on a screen lock, I thought why not letting the power manager do its jobs and just prevent the touch controls (screen and keys) from suspending. Then one could wake the device from screen lock by emulating a power button press on touch. After a user defined delay after screen off the touch controls also get suspended. The only complication was to monitor the power button, so one can differentiate between screen timeouts, for which the touch controls should be kept enabled for a certain time, and a screen lock manually triggered by the user by pressing the power button, for which the touch controls should be disabled right away.
So with Touch Wake, one can wake the device from suspend (for a certain user-defined time after screen off) by touching the touchscreen or the touchkeys. Combined with a OS level tweak which disables the lock screen on timeout for a certain time or altogether (for example in CM 7.03, but also available as standalone apps from the Market), one can achieve the same functionality as Screen Dimmer. Compared to Screen Dimmer, Touch Wake has the advantage that the screen will not be blanked as long as the FLAG_KEEP_SCREEN_ON is set and also the battery drain while the screen is off will be significantly less because only the touch controls are kept enabled and the Android OS and running apps are properly put to sleep. For the record, with Touch Wake, while the touch controls are still enabled, the kernel is kept in a wake lock, so the battery drain will still be a little higher than for the normal stock screen lock, however it is a significant improvement over Screen Dimmer.
To enable (disable) wake on touch pass 1 (0) to 'enabled' in /sys/class/misc/touchwake. Pass the delay (until the touch controls will be disabled after screen off) in ms (this is milliseconds; 1000ms = 1s) to 'delay'; a value of 0 for the delay means the touch controls will be kept enabled indefinitely. The default state is disabled and a delay of 45000 = 45s.
Changes to the source (based on kernel with BLD 3 and Screen Dimmer 1):
http://www.pastie.org/2445282
BUGFIX:
Fixed BLN not working properly anymore.
Bug fix: http://www.pastie.org/2446398
BUGFIX #2:
Fixed the problem with the proximity sensor not reactivating the screen when making calls. Also, since I was in the neighborhood I also fixed the problem with BLD on the i9023.
Bug Fix: http://www.pastie.org/2457092
BUGFIX #3:
I cleaned up the code a bit for all three mods BLD, Screen Dimmer and Touch Wake.
Bug fix: www.pastie.org/2488785
BUGFIX #4:
Fixed the BLD problem for the i9023 of the touchkey backlights not being re-enabled on touchkey press.
Bug fix: http://www.pastie.org/2499956
BUGFIX #5:
Fixed the problem of the touch controls misbehaving after the proximity sensor has blanked the screen during a call.
Bug fix: http://www.pastie.org/2528577
BUGFIX #6:
Fixed the problem with BLD on the i9023 of the touchkey backlights getting activated when the bottom of the touchscreen was touched.
Bug fix: http://www.pastie.org/2544546
BUGFIX #7:
For Touch Wake, call the suspend function a bit earlier to prevent a rare hiccup happening when the touch controls are pressed in exactly the same moment the screen is disabled.
Bugfix: http://www.pastie.org/2641540
BUGFIX #8:
For BLD, Screen Dimmer and Touchwake, use mutex_trylock instead of mutex_is_locked/mutex_lock combo to avoid race conditions.
Bugfix: http://www.pastie.org/2710096
No further patches will be published here. I have set up a git repo for all my tweaks. Each mod has its own branch to keep the tweaks cleanly separated and one can simply pull the latest patches from the corresponding branch.
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/touchwake
Get Jonathon Grigg's 'Spark Mod Manager' GUI for controlling Touch Wake: http://forum.xda-developers.com/showthread.php?p=17291034
I do not accept donations and since I reached my 50GB limit of free space on SpiderOak, thanks to all of you kind people who got an account using my referral link, I could not ask for more.
Instead if you really want to donate your hard earned money to someone who deserves and needs it, consider donating to the Free Software Foundation at fsf.org: These guys are at the frontline when it comes to keeping Linux free and fighting these greedy bastards who think they are entitled to collect royalties and other fees from Linux users due to some silly patents - and if Linux falls, Android will be next.
Does this depend on screen dimmer code? Cause I'd like to maybe remove screen dimmer and just have this mod.
Also, thanks for putting all this time on these mods. Love your work.
Sent from my Nexus S using xda premium
The patch file I have provided is for a kernel already including BLD 3 and Screen Dimmer 1 (+ all bugfixes), but the code of Touch Wake does not depend on either Screen Dimmer or BLD - so you can enable BLD, Screen Dimmer and Touch Wake independently from each other in the kernel config and also could remove one tweak entirely from the kernel source if you want.
Can you stop copy pasting this "couldn't reach morfic"
That would be awesome.
Sent from my Nexus S using Tapatalk
Fixed BLN not working properly anymore.
Bug fix: http://www.pastie.org/2446398
This sounds amazing.
Probably the biggest "mod" to our phones since BLN.
If the battery drain isn't terrible with this mod, I think you have a winner on your hands.
Goodjob.
EDIT: Think you should make an app that allows users to easily change the values. I could see this catching on as much as BLN has.
Bump sounds ballin
Sent from my Nexus S 4G using xda premium
works great!
pinned a shortcut to the on/off script onto my homescreen using gscripts. one press turns it on, second press turns it off..
expr "(" $(cat /sys/class/misc/touchwake/enabled) - 1 ")" \* -1 > /sys/class/misc/touchwake/enabled
Click to expand...
Click to collapse
morfic said:
Can you stop copy pasting this "couldn't reach morfic"
That would be awesome.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I think those are deleted already. lol.
cool stuff.
so... I presume, when the screen dimmed. the crt animation will appear as well ?
and to mr simms and mr reddv1 , can i have ur test kernel included this TouchWake MOD for any ROM since i used MIUI ROM
Sounds like an awesome mod
Sent from my Nexus S using XDA App
what is this kernel??? the file touchwake there isn't in my rom.
please help me.
tonno16 said:
what is this kernel??? the file touchwake there isn't in my rom.
please help me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17104132
Fixed the problem with the proximity sensor not reactivating the screen when making calls. Also, since I was in the neighborhood I also fixed the problem with BLD on the i9023.
Bug Fix: http://www.pastie.org/2457092
Ezekeel said:
Fixed the problem with the proximity sensor not reactivating the screen when making calls. Also, since I was in the neighborhood I also fixed the problem with BLD on the i9023.
Bug Fix: http://www.pastie.org/2457092
Click to expand...
Click to collapse
Thanks for the quick fix. Is this a combined bugfix for proximity sensor and i9023 bld?
Sent from my Nexus S using xda premium
Yeah, they both needed modifying of include/linux/input.h and instead of having two patch files in two different threads which would need to be applied in a certain order I decided to simply make one patch for both problems and put it in this thread. It does not make a difference for you guys and if later people want to include this in their kernel they probably simply pull the up-to-date files from my git instead of applying these gazzilion patches one after each other.
Hope this really fixes the problem with the i9023. I had to guess what the problem was and if this does not solve it, I am all out of ideas. Unfortunately, I do not know anyone with a i9023 I could borrow. The next best thing would be to get someone on gtalk or similar with a i9023 who is willing to go through a painful process of flashing a test kernel with debug statement and passing the logs on to me, then wait until I have compiled the next test kernel... rinse and repeat - lets say about ten times. Not really looking forward to this.
If it will be nessecary I can help on Google Talk. But I'm not capable to compile kernel. If we go for this, you have to send me flashable zip
Using Touch Wake right now with the Lucid kernel and it works perfectly.
Not sure if this is possible, but here's my idea:
Is it possible to somehow wake the phone through touching the touch keys when BLN is active (as in touch keys are on)?
I thought of this as you said that the touch keys (and screen) are not suspended when Touch Wake is active. So now I'm going further to assume that maybe the touch keys are also not suspended when BLN is active so that maybe it can be coded to allow touching the keys to wake the phone?
I know nothing about programming so I may be talking out of my ass here but just an idea.
Thanks!
I think I found a bug with Touch Wake. I'm on 9020, with latest touch wake bugfixes.
After the screen goes off and the touch wake timer has passed, if I touch the soft keys they light up and stay lit while the phone sleeps. I tried to grab a logcat with the phone plugged in to my PC, but the bug can't be replicated while the phone is plugged in.
Sent from my Nexus S
reddv1 said:
I think I found a bug with Touch Wake. I'm on 9020, with latest touch wake bugfixes.
After the screen goes off and the touch wake timer has passed, if I touch the soft keys they light up and stay lit while the phone sleeps. I tried to grab a logcat with the phone plugged in to my PC, but the bug can't be replicated while the phone is plugged in.
Sent from my Nexus S
Click to expand...
Click to collapse
It seems having bln installed (and disabled for me) solves this
Enhanced said:
Using Touch Wake right now with the Lucid kernel and it works perfectly.
Not sure if this is possible, but here's my idea:
Is it possible to somehow wake the phone through touching the touch keys when BLN is active (as in touch keys are on)?
I thought of this as you said that the touch keys (and screen) are not suspended when Touch Wake is active. So now I'm going further to assume that maybe the touch keys are also not suspended when BLN is active so that maybe it can be coded to allow touching the keys to wake the phone?
I know nothing about programming so I may be talking out of my ass here but just an idea.
Thanks!
Click to expand...
Click to collapse
I would be possible, however this could lead to the possible problem of accidentally unlocking the device when you carry it around in a pocket and get a notification. I do not think it is worth the trade-off
reddv1 said:
I think I found a bug with Touch Wake. I'm on 9020, with latest touch wake bugfixes.
After the screen goes off and the touch wake timer has passed, if I touch the soft keys they light up and stay lit while the phone sleeps. I tried to grab a logcat with the phone plugged in to my PC, but the bug can't be replicated while the phone is plugged in.
Sent from my Nexus S
Click to expand...
Click to collapse
I cannot reproduce the problem with my reference kernel. Does it happen every time you try it?
Hi XDA,
I thought I'd create a thread to share a useful app (at least for myself) that I came across recently. I did not create this app, nor am I in any way affiliated with the creator.
It's called "Smart Cover".
https://play.google.com/store/apps/details?id=smart.cover&hl=en
What it does is turn your screen off when it detects something blocking the proximity sensor. As soon as the obstruction is removed, your screen turns back on.
Why would this be useful? Well if you're concerned about your power button wearing out, using this app would definitely minimize your total number of power button actuations.
In my day-to-day usage over the past week or so, I've found it incredibly useful to have my phone turn on as soon as I take it out of my pocket, and shut off as soon as I put it back. Also, when at my desk I now just need to turn my phone face down.
I should note that if the screen times out by itself, or you turn your screen off manually (i.e. without interacting with the sensor), then to turn your screen back on, you just need to wave over the proximity sensor with your hand/finger. For those who are unaware, the proximity sensor on the Nexus S is directly above the screen, on the left.
This app provides the option to disable itself while in landscape mode, to avoid accidentally shutting off the screen while typing, playing games, watching movies, etc.
Of course, it's important to realize that since this app uses the prox. sensor constantly, it will have an effect on battery life. From my experiences though, it's drain has been minimal. Inspection of processor state with "CPU Spy" shows that the NS is still able to reach the Deep Sleep state with this app enabled.
Probably not everyone will enjoy this app however. The first day or so of using it was a bit tricky, as it forced me to use my device differently. I have since gotten used to it. Anyways, I recommend you check this app out.
EDIT:
After searching around there appear to be a number of similar apps on the Play Store, each with different options/features. Here are some others:
(I have not tried any of these yet).
Proximity Screen Off https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff&feature=search_result
Tap Tap App https://play.google.com/store/apps/details?id=net.maicas.android.wsleep&feature=related_apps#?t=W251bGwsMSwxLDEwOSwibmV0Lm1haWNhcy5hbmRyb2lkLndzbGVlcCJd
Smart Screen Off https://play.google.com/store/apps/details?id=it.android.smartscreenoffpro&feature=search_result#?t=W251bGwsMSwxLDEsIml0LmFuZHJvaWQuc21hcnRzY3JlZW5vZmZwcm8iXQ..
This one looks interesting as it combines both the proximity sensor and light sensor. Battery drain would probably be higher though.
Feel free to share your experiences with any of these apps, or post if you discover better ones.
Taptap seems to work best for me
Having this constantly running and using constant hardware I'd imagine this drains quite a bit of battery.
are you seeing any dramatic saving in battery? or does running the program kill batt life?
mauiyob said:
are you seeing any dramatic saving in battery? or does running the program kill batt life?
Click to expand...
Click to collapse
??
This app does not save any battery life.
At the end of each day, I find that the app uses about 5% of my battery.
developersdevelopers said:
??
This app does not save any battery life.
At the end of each day, I find that the app uses about 5% of my battery.
Click to expand...
Click to collapse
It's not a battery saver app. it's a feature app, I personal don't like hitting the power then slide to unlock. When i take it out of belt clip it turns on.
that's the feature.. worth 5% [imhp]. using Smart cover and working good.
Thinking only useful feature if you have a clip.
I'm using Tap Tap App
Tap Tap App is great. It just does what I need.
No need of Power button
Loving my HTC One, but I have such small hands that I can hardly reach the Power button to wake it up after it goes to sleep!
Does anyone know of an app where I can use the Volume button instead?
Thanks in advance.
Only way to possibly assign the sleep/wake function to the volume buttons would mean having to be rooted. I don't know if anyone's made that change yet though, it might just require editing a single file. Don't have any experience with This myself so not 100%. Just know it requires root.
Sent from my iPhone using Tapatalk 2
After a quick search online I've discovered Auto Screen On in the Play Store, which lets me double tap the proximity sensor (left of top speaker) to wake it up.
Works perfectly but an app using the Volume button would be much better.
With this app your screen has to be awake all the time and will drain your battery i think.
On TrickDroid v2.0.0 u can choose VolWake in Aroma
LG, Helmut
Moved your thread to the proper section for you. Please remember to post only in the correct sections. Thanks.
I've heard of some app for a nexus 4 that allows you to just swipe the screen and it turns on. Not sure what it was called, but you get the concept.
Good job I have big hands really because this nor generally using the phone is an issue due to its size.
Sent from my HTC One using xda premium
I'm assuming sweep2wake or swipe2wake will eventually be implemented. It's basically swiping left to right on the capacitive buttons to wake the phone.
The One X had it, but it was a bit buggy when I used it in terms of it not working if the phone was asleep for a long time. I got rid of my One X a while ago though so idk how the feature works now and if they figured it all out., but I expect it to get implemented on the HTC One eventually.
The proximity sensor isn't a bad idea, jailbroken iPhone 5 etc...have the always on proximity where if you cover the proximity it'll turn the screen off and eventually lock the phone after a while. So you can put it in your pocket and it will turn the display off, bring it out of pocket and it comes on without needing to slide to unlock or anything. It's good if your messaging constantly.
pewpewbangbang said:
I'm assuming sweep2wake or swipe2wake will eventually be implemented. It's basically swiping left to right on the capacitive buttons to wake the phone.
The One X had it, but it was a bit buggy when I used it in terms of it not working if the phone was asleep for a long time. I got rid of my One X a while ago though so idk how the feature works now and if they figured it all out., but I expect it to get implemented on the HTC One eventually.
The proximity sensor isn't a bad idea, jailbroken iPhone 5 etc...have the always on proximity where if you cover the proximity it'll turn the screen off and eventually lock the phone after a while. So you can put it in your pocket and it will turn the display off, bring it out of pocket and it comes on without needing to slide to unlock or anything. It's good if your messaging constantly.
Click to expand...
Click to collapse
iirc showp1984 said he's getting a htc one, and see oz did too so hopefully one of them will bring sweep to wake Zarboz did an excellent job on the incredible s and he doesn't even have the device
Sweep to wake generally doesn't work sometimes in deep sleep. I use vol wake and the. Sweep to go to sleep on my incredible s now s2w is actually the greatest thing ever
MOD EDIT: Removed
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
FWIW, Exodus and I'm sure some other ROMs, have a setting to prevent pocket wake ups by using the proximity sensor.
WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
Are you sure it's not ambient display waking your phone?
Eh... "ambient display" doesn't wake your phone. Ambient display just shows WHEN your phone is awoken by... tap to wake, shake to wake, incoming notification.
OP: Some people confuse tap to wake and shake to wake. Nexus 6 implements shake to wake by default. Problem is that tapping on the screen can.... shake the phone.
This generally should NOT be going off in your pocket. Either, that is. Reason is that it is *supposed* to use the state of the proximity sensor as a CONDITION on whether or not it should start up ambient display. The proximity sensor will read as "near" when the phone is in your pocket, thus prevent tap or shake to wake from triggering ambient display.
So sounds like you probably tried a couple of different sysimages that both contain a bug that stops it from taking the proximity sensor into account. My guess would be something that is based on cyanogenmod (aka "the buggiest android ever conceived"). Try stock and see if the problem goes away.
Personally, I prefer to use a custom ROM with native LED control and disable ambient display.
danarama said:
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
Click to expand...
Click to collapse
what do you even mean?
slamsal said:
what do you even mean?
Click to expand...
Click to collapse
What part don't you understand?
If you haven't got a modified Nexus 6 with this problem, then this isn't relevant to you.
Please help let me know if screen activating in pocket is a bug or if this is intended design (i.e., design flaw)?
Now that it's summer my leg can get a little sweaty. But my phone in pocket triggers off my leg due to the moisture! Then the phone will randomly edit various things as the phone bounces around in my pocket.
WTF, why won't the phone just detect the darkness and know it's in my F*ING pocket! My S9+ was really good about this, it knew when it was in the pocket and ignored my sweaty leg.
But with this retarded S21 Ultra, it doesn't seem to know when it's in your pocket. I've already lost several important appointments and tasks (my calendar and task lists widgets are on the main screen) because the dumb phone let my *LEG* edit/destroy/delete the important tasks and calendar entries.
I'm holding out hope that maybe this is not how the phone is designed to work, maybe I can fix it by doing a factory reset. But I recall other posts complaining about how the phone is too retarded to detect being in the pocket when it comes to the Always On Display (AOD) and just keeps the display on while in the pocket too. So maybe it's a fatal design flaw of the phone, where if it is hot outside and you have moisture on your leg, your phone will think your leg is typing and just randomly change things.
Please help me understand whether this is a fatal design flaw or just some bug or what!?
please disable the option to activate the phone/unlock phone via sensory detection
i believe you need to deactivate that first from the smart lock - on body detection
and then also go in advanced features, motions and gestures and deactivate lift to wake
KingFatty said:
Please help let me know if screen activating in pocket is a bug or if this is intended design (i.e., design flaw)?
Click to expand...
Click to collapse
Used to happen to me too. Ofter i would only realise phone was awake and messing around by the beeping sounds of the dialer going off in the pocket, or the increasing temperature of the phone against my thigh - screen on for God knows how long.
Pocket detection is dubious at best - doesn't work consistently. All this happened despite it being set to "on"
Turning off double-tap-to-wake screen helped me.
Now the phone only wakes up for calls and will show lockscreen only if I hit the power button (side key) - I have never used AOD, so screen stays off no matter how hard you tap away at the screen.
Unfortunaltely this puts a lot of mechanical wear on the side key (waking up the phone to unlock)
TO solve this, I have set my Fingerprint scanner "always on" enabled, so if i want to unlock phone without wearing out the side key, I just hit the screen with my thumb where i know the fingerprint scanner is, and it takes me to the home screen without showing the lock screen. I've developed muscle memory now and can hit the correct spot on the screen 90% of the time without the fingerprint icon displayed on screen. No perceptible differnence in battery life as opposed to keeping fingerprint scanner always on disabled.
This has worked for me. Maybe you can try it out and see if it solves your issue.
enigmaamit said:
Used to happen to me too. Ofter i would only realise phone was awake and messing around by the beeping sounds of the dialer going off in the pocket, or the increasing temperature of the phone against my thigh - screen on for God knows how long.
Pocket detection is dubious at best - doesn't work consistently. All this happened despite it being set to "on"
Turning off double-tap-to-wake screen helped me.
Now the phone only wakes up for calls and will show lockscreen only if I hit the power button (side key) - I have never used AOD, so screen stays off no matter how hard you tap away at the screen.
Unfortunaltely this puts a lot of mechanical wear on the side key (waking up the phone to unlock)
TO solve this, I have set my Fingerprint scanner "always on" enabled, so if i want to unlock phone without wearing out the side key, I just hit the screen with my thumb where i know the fingerprint scanner is, and it takes me to the home screen without showing the lock screen. I've developed muscle memory now and can hit the correct spot on the screen 90% of the time without the fingerprint icon displayed on screen. No perceptible differnence in battery life as opposed to keeping fingerprint scanner always on disabled.
This has worked for me. Maybe you can try it out and see if it solves your issue.
Click to expand...
Click to collapse
I dont think that would put any mechanical stress on the power key.
Phones are tested for upto millions of press of buttons which you woudnt be able to achieve in your lifetime .
I have my aod on always , and double tap to wake on always .
Best possible way to avoid accidental wakeup is to insert your phone with screen facing away from the body i.e towards the fabric of pants/jeans/lower
tim2london said:
please disable the option to activate the phone/unlock phone via sensory detection
i believe you need to deactivate that first from the smart lock - on body detection
and then also go in advanced features, motions and gestures and deactivate lift to wake
Click to expand...
Click to collapse
Yes, lift to wake was already disabled while the problem happens. The phone still wakes from "taps" caused by the leg.
I want to clarify, the problem is not caused by the phone unlocking or locking.
The problem is because the phone is not ignoring screen taps when in the pocket. It thinks I'm double-tapping to wake the phone.
I'd like to keep enabled the smart lock on body detection, and keep enabled the double-tap to wake. I can see how keeping the phone locked would help, but the root problem is still there - the phone wakes up even though it is inside the pocket.
Keeping the phone locked would just transform this to a new problem - how do I prevent my phone from waking up in my pocket and wasting energy while my leg enters various unlock codes by itself.
enigmaamit said:
Pocket detection is dubious at best - doesn't work consistently. All this happened despite it being set to "on"
Click to expand...
Click to collapse
Yes, the S21 Ultra refers to this as "Accidental Touch Protection." The flavor text explains "Protect your phone from accidental touches when it's in a dark place, such as a pocket or bag."
Accidental Touch Protection has been turned on when I had the problems.
Does anyone know why Accidental Touch Protection is not working, even though it's turned on?
The setting is found under Settings - Display (scroll down, 4th from the bottom).
Keep the back of the phone towards your leg, problem solved.
aj7400 said:
I dont think that would put any mechanical stress on the power key.
Phones are tested for upto millions of press of buttons which you woudnt be able to achieve in your lifetime .
I have my aod on always , and double tap to wake on always .
Best possible way to avoid accidental wakeup is to insert your phone with screen facing away from the body i.e towards the fabric of pants/jeans/lower
Click to expand...
Click to collapse
Yup, you may be right. Ideally they should last a lifetime. But all mechanical parts are prone to failure. Same thing holds true with charging ports - they shouldn't fail, but often do. Doesn't happen to everyone, but it's something to keep in mind.
I've had my HTC power key fail on me due to constant use over 2 years, and ever since then I've stuck to using the screen for wake-up. Needn't happen to everyone, but once bitten, twice shy, right?
The screen facing outwards is a good idea and it was the first solution that came to mind when I was having accidental wake-up issues. Tried it for a few days but stopped using it because it's awkward for me (camera bump irritates thigh) and it was un-intuitive to take out the phone, then turn it around in the hand to start using it. I just wasn't comfortable using it that way.
Like I said, this set-up works best for me, everyone might have their own way of doing things
All I know is that with this set-up, I don't have any more accidental wake-ups while the phone is in the pocket. That was the main requirement.
KingFatty said:
Yes, the S21 Ultra refers to this as "Accidental Touch Protection." The flavor text explains "Protect your phone from accidental touches when it's in a dark place, such as a pocket or bag."
Accidental Touch Protection has been turned on when I had the problems.
Does anyone know why Accidental Touch Protection is not working, even though it's turned on?
The setting is found under Settings - Display (scroll down, 4th from the bottom).
Click to expand...
Click to collapse
Yes, that's the one I was talking about. Like you said, it doesn't work consistently. No idea why. I've always had it on.
KingFatty said:
I'd like to keep enabled the smart lock on body detection, and keep enabled the double-tap to wake. I can see how keeping the phone locked would help, but the root problem is still there - the phone wakes up even though it is inside the pocket.
Click to expand...
Click to collapse
If you'd like to keep the tap to wake feature on, then the best solution for now appears to be what @aj7400 and @blackhawk have suggested - Keep the phone screen facing away from the thigh.
The screen of my phone frequently turns on when it is in my pocket and the phone starts performing some tasks like playing music.
Does anyone of you experience the same problem ? Is there any method to prevent accidental touches when the phone is locked ?
Edit: sorry I didn't notice this thread, so I created another one for the same problem. I'll try some of the solutions you proposed guys, hopefully it will fix the problem.
Was there any pattern to when Samsung's "accidental touch protection" failed to keep the phone screen inactive?
I'm trying to find out if there is anything going on that might affect the accidental touch protection. Normally, accidental touch protection keeps the phone screen off when the phone is in your pocket, to protect against unwanted touches or "butt dialing."
But in my case, my leg was a little sweaty and the phone screen activated and deleted some of my important info.
Has anyone else seen anything in terms of a pattern when your accidental touch protection fails to protect against accidental touches?
Maybe you had see-through pants with white pockets with direct sunlight glistening off your sweaty thighs?
KingFatty said:
Was there any pattern to when Samsung's "accidental touch protection" failed to keep the phone screen inactive?
I'm trying to find out if there is anything going on that might affect the accidental touch protection. Normally, accidental touch protection keeps the phone screen off when the phone is in your pocket, to protect against unwanted touches or "butt dialing."
But in my case, my leg was a little sweaty and the phone screen activated and deleted some of my important info.
Has anyone else seen anything in terms of a pattern when your accidental touch protection fails to protect against accidental touches?
Maybe you had see-through pants with white pockets with direct sunlight glistening off your sweaty thighs?
Click to expand...
Click to collapse
Nope. Happened to me in Dark blue denims as well as black trousers.
It's not consistent. Works most of the time but fails every once in a while.
For me, usually I become aware of it when i hear the dialer beeps (somehow the screen taps end up on the emergency call dialer screen) go to town.
Funnily enough, I turned the feature off and was roaming around the city for more than 2 hours. No accidental wake-ups at all. This is even after I have temporarily restored double tap to wake screen. Need to watch this for a few more days and if i don't get any more ghost wake-ups, i'm keeping it turned off.
enigmaamit said:
Funnily enough, I turned the feature off and was roaming around the city for more than 2 hours. No accidental wake-ups at all. This is even after I have temporarily restored double tap to wake screen. Need to watch this for a few more days and if i don't get any more ghost wake-ups, i'm keeping it turned off.
Click to expand...
Click to collapse
What did you do, i didnt understand ?
ELp2 said:
What did you do, i didnt understand ?
Click to expand...
Click to collapse
Turned off Accidental Touch Protection
Have you also tried just initiating LOCKDOWN MODE via the power button before a run?
I'm guessing that your leg and the sweat and the fabric combine to give the electric feel of a skin's surface that activates the phone?
You could also use a Bixby Routine to disable double-tap to wake?
enigmaamit said:
Turned off Accidental Touch Protection
Click to expand...
Click to collapse
Let us know your conclusion...I went the EXACT ane route (before finding this post): disable ATP and created a routine button to disable double tap to wake when I take the phone out for a walk.
Seems to be working, but it's another source of frustration as my previous Huawei mate 20 pro had the ATP feature but never started playing muzak in my pocket.
Samsung...good hardware plagued by half-baked software.
Ipse_Tase said:
Let us know your conclusion...I went the EXACT ane route (before finding this post): disable ATP and created a routine button to disable double tap to wake when I take the phone out for a walk.
Seems to be working, but it's another source of frustration as my previous Huawei mate 20 pro had the ATP feature but never started playing muzak in my pocket.
Samsung...good hardware plagued by half-baked software.
Click to expand...
Click to collapse
The Huawei mate 20 has much more major issues than our SK allies flagship phones do in more ways than one
I don't have these issues on the 10+ unless a put the phone facing my leg on the display side.
You should have a good case that has side protectors slightly higher than the display plus end display protection in the case ie Zizo Bolt case. Otherwise a face plant can easily destroy the display. These phones need case protection... before they kiss the concrete.
This also help stop accidental touches both when on and off. It makes the phone easier to hold and use as well.
Face the display away from your body. That should be more than enough...
If it's really still a problem limit display timeout to 1 minute.
Use only the power button or volume control buttons to activate the phone.
-or-
Use a case clip holster.
Ipse_Tase said:
Let us know your conclusion...I went the EXACT ane route (before finding this post): disable ATP and created a routine button to disable double tap to wake when I take the phone out for a walk.
Seems to be working, but it's another source of frustration as my previous Huawei mate 20 pro had the ATP feature but never started playing muzak in my pocket.
Samsung...good hardware plagued by half-baked software.
Click to expand...
Click to collapse
Well, in conclusion I can only say that the setup is working... Haven't changed anything since then and no accidental pocket mishaps yet. ATP and Double tap to wake are still off.
BTW, your idea of a Bixby routine trigger to disable double tap when heading out to walk is quite neat