I use a one minute screen timeout, which is a bit long for the screen to stay on every time you put it back in your pocket. It also gets a little annoying hitting the power button every time after I'm done using it, for example if I'm frequently taking it out and putting it away during a text conversation. So, I used Tasker to tell it to lock the screen every time the proximity sensor fires, combined with WidgetLocker set to its own 10 sec screen timeout. I also told it to NOT do this while on a phone call so the proximity sensor would just turn the screen off but not lock it like normal in that case. So this way, you can keep a longer normal screen timeout, put the phone back in your pocket, and the proximity sensor will fire, lock the screen, and the screen will turn off in 10 seconds. The only issue here is the occasional accidental proximity sensor activation, but it's not too frequent. I'd be curious if anyone else finds this useful.
The Tasker profile:
Context: Proximity Sensor
Task:
1. If %WIN !~ Phone (if not in the phone app)
2. WidgetLocker Cmd Activate (lock screen)
Detecting if the Phone app is open does require enabling the Tasker accessibility service in Settings -> Accessibility -> Accessibility services (check Tasker).
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
You shouldn't have this issue really unless you frequently overshoot the top of the screen when going for the notification bar.
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
God i wish XDA had a "like" button
mrono said:
I would shoot someone in the face every time i went to pull down the notification bar and the screen locked :/
Click to expand...
Click to collapse
Yep, I had a profile like this set up before, but abandoned in very quickly due to this issue. Every time I went near the sensor my screen shut off, no bueno.
Hey... This thing makes phone calls too!
JTNiggle said:
Yep, I had a profile like this set up before, but abandoned in very quickly due to this issue. Every time I went near the sensor my screen shut off, no bueno.
Hey... This thing makes phone calls too!
Click to expand...
Click to collapse
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
initial said:
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
Click to expand...
Click to collapse
Good idea, works pretty nice, Thanks! Seems that 7 seconds is the minimum timeout allowed though, not that that's a problem, running it now. Unless there's is another way to do it that
I must recommend this setup for everyone now.
Context: Proximity Sensor
Task: Display Timeout = 7 Seconds
Handy for work/school too, I just lay my phone face down on my desk and the display takes care of itself.
JTNiggle said:
Good idea, works pretty nice, Thanks! Seems that 7 seconds is the minimum timeout allowed though, not that that's a problem, running it now. Unless there's is another way to do it that
I must recommend this setup for everyone now.
Context: Proximity Sensor
Task: Display Timeout = 7 Seconds
Handy for work/school too, I just lay my phone face down on my desk and the display takes care of itself.
Click to expand...
Click to collapse
Actually, wouldn't that profile change the display timeout to 7 seconds, effective immediately when the proximity sensor activates? So you could accidentally activate it, not be aware, and then have the display suddenly go off on you 7 seconds later. I think what initial was saying was to make it so the proximity sensor itself must be active for at least 3 seconds before anything happens, THEN do what you wish - in my case, I don't actually change the display timeout at all, I just lock the screen with WidgetLocker, at which point a 10 second timeout is in effect from that app.
xdp said:
Actually, wouldn't that profile change the display timeout to 7 seconds, effective immediately when the proximity sensor activates? So you could accidentally activate it, not be aware, and then have the display suddenly go off on you 7 seconds later. I think what initial was saying was to make it so the proximity sensor itself must be active for at least 3 seconds before anything happens, THEN do what you wish - in my case, I don't actually change the display timeout at all, I just lock the screen with WidgetLocker, at which point a 10 second timeout is in effect from that app.
Click to expand...
Click to collapse
That's true. The display timeout does change to 7 seconds. How would you set it so that the proximity sensor must be activated for a certain amount of time?
initial said:
Make a timeout so the proximity sensor has to be activated for at least 3 seconds
Click to expand...
Click to collapse
How do you do this in Tasker?
WillJitsu said:
How do you do this in Tasker?
Click to expand...
Click to collapse
I haven't been able to figure it out, anyone?
WillJitsu said:
That's true. The display timeout does change to 7 seconds. How would you set it so that the proximity sensor must be activated for a certain amount of time?
Click to expand...
Click to collapse
It does just change the display timeout, but only while the proximity sensor is covered. So if you uncover it before 7 seconds, the display stays on like normal, works well for now until I learn some more about Tasker.
Hey guys, I think I figured out how to do this. It requires using variables. Basically, you set a "proximity sensor active" variable that you create to true when it's activated (the context enter task), and set it to false when it's deactivated (the context exit task). Then in the enter task, after setting that variable, you wait 3 seconds, and then test if the variable is still true. If it is that means the exit task has not executed which means the sensor is still active and your task can proceed. If it isn't that means the exit task did execute which means you uncovered the sensor before the 3 second wait time elapsed and so you don't want to proceed. It looks like this:
Context: Proximity Sensor
Enter Task:
1. Variable Set, Name %PROXACTIVE to 1
2. Wait 3 seconds
3. If %PROXACTIVE ~ 1
4. If %WIN !~ Phone
5. If %WIN !~ Voicemail
6. WidgetLocker Cmd Activate
Exit Task:
1. Variable Set, Name %PROXACTIVE to 0
This works fine for me using WidgetLocker, since I only need the task to continue executing after the 3 second wait time, but if you are trying to actually change the display timeout, you'll still have the issue of the value reverting once you uncover the sensor. To get around this, create a separate task that changes the value (Tasks button at the bottom, then New Task), and call this task from the enter task (Tasker -> Perform Task). This puts the action behind a sort of wall that makes your main task oblivious to the fact that it's setting a revertible value, and the value will stick even after you uncover the sensor. Of course, this also means your display timeout will now remain at 7 seconds, so you'll have to create another task to restore that value on screen unlock or something like that.
Let me know if you have any questions, this seems to work okay for me!
Running the Alliance rom, clean install on stock slot. No other major issues that I can think of. I've got it set to maximum brightness, not on auto dimmer. When the screen dims after 30 seconds or so, when its about to turn off due to inactivity, half the time when I tap the screen, it recovers to full brightness. The other half the time, it gets a little brighter than the dim mode, but not much. It stays way dimmer than the full brightness setting that I keep it on. I have to pull the notification bar down, slide the dimmer down, and back up to maximum, and I'm good to go until the next time it does it. Which could be in 30 seconds when it dims again.
Anybody else having this issue?
scott_65 said:
Running the Alliance rom, clean install on stock slot. No other major issues that I can think of. I've got it set to maximum brightness, not on auto dimmer. When the screen dims after 30 seconds or so, when its about to turn off due to inactivity, half the time when I tap the screen, it recovers to full brightness. The other half the time, it gets a little brighter than the dim mode, but not much. It stays way dimmer than the full brightness setting that I keep it on. I have to pull the notification bar down, slide the dimmer down, and back up to maximum, and I'm good to go until the next time it does it. Which could be in 30 seconds when it dims again.
Anybody else having this issue?
Click to expand...
Click to collapse
I have the same thing happening. Personally I have been too lazy about it to check through settings to see if I've done something. I'll check on it and see if I can find a fix.
*Update*
I've checked through all my settings and can find nothing that might cause it. I don't have Auto Brightness set, nor do I have Auto Adjust Screen Tone turned on. I saw nothing in the Alliance Settings either. I believe it is a system setting that is probably buried in code somewhere (far beyond my knowledge).
**Update** I reported the bug in the Alliance Forum.
I tend to agree. I've looked through settings, etc. just as you have, to no avail. I'm nearly certain it's done it since install, so I don't think it's something that I've changed. But I could be wrong. I've also tried it with auto adjust turned on, does the same thing. Auto adjusts to a dimmer setting sometimes
I have a couple of questions about this.
1) With Ambient display enabled, the screen pops on when a notification comes through, or when I pick up the device. If Ambient display is disabled, the screen doesn't wake for either circumstance.
- The way I would like to have it, is where the screen only comes on when a notification comes through, and not when I move the phone. For me, it's a bit annoying most times. Is there a setting or another way to achieve this?
2) When Ambient display is enabled and I get the sound or vibration for a notification, it takes a few seconds (3-5) for the screen to come on.
- Is this normal? I'd prefer it to come on right after the notification sound/vibration.
I'm currently on build MDA89D, and have fingerprint/pin set for lock screen security.
Yeah that sounds normal. It definitely needs some advanced settings to make it less annoying. I foresee custom roms in our future
coltronathon said:
Yeah that sounds normal. It definitely needs some advanced settings to make it less annoying. I foresee custom roms in our future
Click to expand...
Click to collapse
Thanks for the response. I just wanted to make sure that it is working as intended, even though I'd like to tweak it a bit.
Realized this as I use a timer constantly at work - it'd be really useful to have it show the remaining time on the 2nd screen. Right now all that shows is a little hourglass icon, but I have to unlock the screen to see remaining time.
Same question for me as well. I currently have the Note Edge. My edge displays the countdown time on the edge screen. I was wondering if the V20 has the same capability on the second screen as well?
probably a bit off topic (but not too much)
I use the timer a lot and can't disable the vibration in it nor change the tune (both options are available in the Alarm)....any idea? Of course I'd like to have the timer on the second screen too.
Timer tone can be changed on a rooted device. I'm going to see if I can find Timer vibrate and maybe disable it.
Hi guys, so I'm currently running a translated Norma rom and I've been having this issue for a while. When I make a call, the screen will dramatically dim 5 seconds into the call, then at 25 seconds the screen will go black like I put it up to my ear, but the phone is actually 5 feet away from me. I have a job where I make and answer hundred of calls daily, and it's extremely tedious to have to keep unlocking the phone after each call.
I have my display timeout set for 5 minutes, but it seems that the dialer isn't going by the display setting, which it usually did in the past. I ended up pulling the others.xml file from another version of the same rom, when the dialer timeout was using the display timeout as it should, and that seemed to solve the issue, but it created other problems.
So I've been trying to figure out what line or lines in the xml, from the previous version that worked, I'd need to copy to my current other.xml to make it work correctly. I've been searching for a while now, but I haven't been able to find any line that blatantly shows a timeout setting. I know there are apps in the playstore that can set the screen for no timeout, but I'd really like to get the native timeout working, if possible. Any insight from you guys would be greatly appreciated.