I am searching for something that can dim the screen, not like the factory setting that turns off the screen after... 30 seconds. Just something so if i am searching for something, like 10 seconds later it'll dim to like 10%, then anything i do brings it back to where it was.
I used to have this hack in my Treo 750 and it really expanded my battery life like crazy.
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!
I am having a few difficulties with my s4 which I picked up at a Telus store last week. First, my mms app (stock) used to show reply/read buttons in notifications, and now it doesn't show up anymore. Next, and the most annoying is the auto dim. I do not have auto brightness set, and the screen is set to 2min before it shuts off, however, it will dim in less than 10 seconds of no touch activity, then shut off a few seconds later. This is such a frustrating thing to deal with, but I am unable to prevent it from doing so.
The only things I have changed is installing nova launcher (touch wiz is horrible) and using swiftkey due to the lack of autocorrect in the stock keyboard.
Any help is appreciated. Thank you.
I'm having a couple issues with my nexus 4 after upgrading manually to Lollipop with the system image from Google Developers.
Sometimes, when the screen goes idle and turns off automatically or when it's turned off manually using the power button, the screen flashes on a higher brightness and shows the lockscreen before turning off. (I'm guessing the desired result is that the lockscreen should appear 'on screen' after the backlight is completely off).
What this causes is that when turning off the screen, the screen dims with the animation (fade to black and turn off), but before (and sometimes after) the animation is complete, it flashes for a few milliseconds displaying the lockscreen/background, even when locking the phone inside an app.
I could upload a video of the issue at a later time.
This bug didn't happen on any version/rom that went through my phone (many stock, many custom). Although I haven't tried installing another 5.0 ROM / AOSP.
The update also brought back a [hardware?] issue this Nexus 4 unit also has had since I got it. When dimming the screen using the brightness slider, sliding to the lowest setting turns off the backlight completely (effectively making the screen pitch black instead of dimming). This issue has been reported before and I was using Gravitybox to override the system lowest brightness level. Could these two issues be related? (Note that this issue didn't trigger this behavior before).
This issue has been reported by other users here:
http://forum.xda-developers.com/nexus-4/help/zero-brightness-t2168071
http://forum.xda-developers.com/nexus-4/help/problem-nexus-4-brightness-t2052857
https://www.youtube.com/watch?v=dvgt17sKQsU < this shows the screen going pitch black at lowest brightness, it happens either from the widget, the slider, and the option in settings.
Any ideas on why it happens or how can it be corrected?. Do you also have this issue?.
Many thanks in advance.
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.