+ Variable > variable Set > name "%WantLight%, To "0"
+ Tasker > Profile Status > Name "GetLight", Set "On"
You can add a few values and IF's here. This example has 3. Just ensure you start with the lower values and build up. Don't add too many though.
I am aware there is a "Wait Until" task that probably makes more sense than the "Wait" with 1MS. Truth is I hadn't noticed it until writing this up. I'm sure it works but I haven't tested it so....
I can't get this to work, and everything matches perfectly.
I turned off Auto Brightness, turned it up high, and covered the sensors. But nothing changed.
__________________ Sync your phone and your computer, Dropbox
================================================== ===========================THANKS
================================================== ==============================| |
================================================== ==============================| |
================================================== ============================== V
Yes, we want GetLight off so it's not getting light from sensor constantly. We turn it on for a moment when we want light.
I'm a little confused about this. It seems to work (when I'm in the house brightness is at 39%, and outside in the shade it's at 71%), but, after it's set, when I look at the profiles in Tasker, GetLight is active. According to what you said, shouldn't it be inactive?
I'm a little confused about this. It seems to work (when I'm in the house brightness is at 39%, and outside in the shade it's at 71%), but, after it's set, when I look at the profiles in Tasker, GetLight is active. According to what you said, shouldn't it be inactive?
I've noticed a glitch where getlight wasn't deactivated. I manually deactivated and then tested. It was fine after that. I'll do some testing to see if I can tidy it up or something.
It only checks the light sensor when the display comes on.
i tried testing that too. i set the display to max brightness. turned off screen. covered up the sensor and unlocked. the screen was still at max brightness.
i tried testing that too. i set the display to max brightness. turned off screen. covered up the sensor and unlocked. the screen was still at max brightness.
Well thats wrong on both accounts. It doesn't turn the brightness down if its dark. It turns the brightness up if its light.
You could add a "less than" if you wanted.
The Following User Says Thank You to SUroot For This Useful Post:
Thx for the files, but it still ill doesn't work properly for me. Why is brightness @ 180 listed twice in the WantLightOn task? Also, even with setting brightness to 0 (why would I want to do this anyway), my display only goes down to 8%? Is that a limitation of my phone (HTC Vivid on ICS)?
Last edited by bruce73; September 13th, 2012 at 01:41 PM.
Why is brightness @ 180 listed twice in the WantLightOn task?
Because I've made a mistake....
Quote:
Originally Posted by bruce73
with setting brightness to 0 (why would I want to do this anyway)
Why wouldn't you want the brightness as 0 (lowest setting) in a dark room? Its not like you need brightness to overcome the abundance the light in the room.
Quote:
Originally Posted by bruce73
my display only goes down to 8%? Is that a limitation of my phone (HTC Vivid on ICS)?
Maybe it is a limitation of your phone.
Last edited by SUroot; September 13th, 2012 at 01:54 PM.
I left Tasker open on the variables tab then locked and unlocked my phone. You can see the variables change if they're going to. It didn't work very often for me.
Think I have a solution. Seems to be working for me so far.... Variable updates at every screen on.
3x profiles.
1) GetLight
Event Display On
Task %LightValue To %LIGHT
2) Display On
Event Variable Set %LightValue
Task Display Brightness whatever if Greater than whatever
Task tasker Profile Status GetLight Off
3) Display Off
Event Display Off
Task Tasker Profile Status GetLight On*
* GetLight will continue to Poll %LIGHT if the display is on and The GetLight Profile is On so we turn off the Profile. We turn it on When the Display is off as it Does not Poll %LIGHT until the display is turned back on...
Will upload test Profiles in a bit...
Last edited by SUroot; September 14th, 2012 at 05:07 AM.
The Following User Says Thank You to SUroot For This Useful Post:
Still not working properly for me. I went outside, turned the display on, and it popped up to 75%. But when I came back in and turned the display on in a darkened room, it didn't change from 75%.
Did the variable change? If so, to what? There's no less than in the test profile so you'll only see a drop if its below the step its on and above the lowest step.
Lets keep it simple and confirm it goes up properly
Last edited by SUroot; September 14th, 2012 at 09:48 AM.
That was it. The variable was changing, but the ambient light in my apartment is only around 200. So I brought down the first value to 150 (@75 brightness) and it works. Cool. Thanks.
I was getting unpredictable results so I changed the Context for GetLight to Display Unlocked. It seems to work now.
I also cut the brightness choices down to two. Above 1500 and below. I use 100 for the lower setting. I'll probably add back the really low setting for levels below 160.
I have a Pattern lock. For me, one of the biggest reasons to create this profile was to be able to see what I'm entering on teh pattern unlock screen. The Unlock context wouldn't help me there.
The point of the else is to skip the other checks if the first one matches.
Yes I know how it works. I use it in places too. However if is the last value, it checks everything before it first.
I'm not sure why you see 3 different brightness settings on your device. Theres no way your device is too slow, so why its acting so slow is beyond me.
Sure if this works for you better, use it. But I would still recommend having the less than setting first if you're having trouble getting it to run
My issue now is that, while the brightness setting will change, the screen won't usually show the change until I go into Display settings and pull up the slider (or access it through my Widgetsoid widget) and hit cancel. I don't know if this is a issue with my phone (HTC Vivid) or ICS.
I mentioned that problem earlier with touching my notification bar. Also sometimes, it would be at 0 but the slider would register one of the profile values.
This happened a lot when I was testing alternative methods looking for a v2 candidate. Sometimes a reboot fixed. Other time I had to restore the entire app data.
I never got passed that to be honest. Thsts why v2 is how it is. It works reliably for me
My version seems to be working now. So far on the low end I've seen lightvalues of 160, 225 and 320. The high is 10240 or something like that. Do your phones have the same range of values?
* This is cool. I just tweaked my lowest level to < 230 to catch the 225 level because it was a bit bright. This is how auto-brightness should work.
Last edited by bberryhill0; September 15th, 2012 at 11:10 PM.
I changed the context for GetLight back to Display On and it didn't apply until the second time I turned the display on. Weird. Back to Display Unlocked.
On my phone Tasker takes about a second to process each line of code. I added a %Brightness variable so I can monitor %BRIGHT and the variable changes a second after the screen brightness changes.
4Likes
[Profile] [Light Sensor] V2 - Brightness adjust on Screen on
