• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Profile] [Light Sensor] V2 - Brightness adjust on Screen on

i need brightness full or close to full only when i am outdoors in the house min brightness is great. Maybe its an issue with the light sensor of my phone. not got a chance to check it on a friends s3.
 
1. You need to work out what the highest value %LightValue variable returns whilst indoors firstly.

2. If you just want indoor dull / outdoor bright, you can get rid of all the inbetween values and just have Level 0 if Lux < 120* and level 255 if lux > 120*

* see point 1. Where 120 is a little bit higher than the maximum %LightValue you get at home... It could be 30 I dunno. You have to test.
 
ok i tried it out on a friends phone and mine side by side my phone shows about 10 less than his does in tasker. So it might be some issue with my light sensor. will just setup the profile like u suggested it would be easier.
 
Hi,

Thanks a lot!
Great profile.

I just downloaded the trial version of Tasker (gonna buy it of course...) and trying to learn it.
This profile helped me understand some things.

I have a few questions:

1. Why did you stop the "get light" profile twice? on profile 2 and profile 1?
Is it just to make sure it stops and doesn't eat the battery...?

2. On profile 3 ,"Display off", you said in the description that when the display is off the profile should be set to off.
It supposes to be "on" like in the screenshot, right?
Just wanted to be sure I understood this and it's just a typo....

3. I'm still trying to understand this variables issue :)
Was it possible if I didn't set the %LightValue variable and start directly from profile 2 when the brightness levels check is made with the %LIGHT variable?
Then profile 2 would set itself to off and profile 3 will turn profile 2 back to on....

4. last question...
If I'm outside and in bright sunlight,and I get a phone call while the phone is in my jeans pocket - the light value will be set to the one that in my pocket... right? :)
I thought about creating another profile:
context: phone ringing
task: wait 30 seconds and then stop.
Then, in the beginning of the "get light task" I thought of adding a 10 seconds wait with an if TRUN matches my "phone ringing" task. That way I'll have the chance to get it out of my pocket and let it set the light value then.

What do you think?
Looks ok? Is there a better/more efficient way to do it?
I checked it and it works but I wondered if it can make any problems when I answer the phone before the 10 seconds wait ends...

Thanks a lot and sorry for the long post.... :)
 
gabi25 said:
Hi,

Thanks a lot!
Great profile.

I just downloaded the trial version of Tasker (gonna buy it of course...) and trying to learn it.
This profile helped me understand some things.

I have a few questions:

1. Why did you stop the "get light" profile twice? on profile 2 and profile 1?
Is it just to make sure it stops and doesn't eat the battery...?

2. On profile 3 ,"Display off", you said in the description that when the display is off the profile should be set to off.
It supposes to be "on" like in the screenshot, right?
Just wanted to be sure I understood this and it's just a typo....

3. I'm still trying to understand this variables issue :)
Was it possible if I didn't set the %LightValue variable and start directly from profile 2 when the brightness levels check is made with the %LIGHT variable?
Then profile 2 would set itself to off and profile 3 will turn profile 2 back to on....

4. last question...
If I'm outside and in bright sunlight,and I get a phone call while the phone is in my jeans pocket - the light value will be set to the one that in my pocket... right? :)
I thought about creating another profile:
context: phone ringing
task: wait 30 seconds and then stop.
Then, in the beginning of the "get light task" I thought of adding a 10 seconds wait with an if TRUN matches my "phone ringing" task. That way I'll have the chance to get it out of my pocket and let it set the light value then.

What do you think?
Looks ok? Is there a better/more efficient way to do it?
I checked it and it works but I wondered if it can make any problems when I answer the phone before the 10 seconds wait ends...

Thanks a lot and sorry for the long post.... :)
Click to expand...

1) yes, to make double sure.
2) Well spotted :)
3) One profile arises the variable then the other is triggered by that variable being written. I tried many different methods before I came to the conclusion that this is the best way to do it. I found other methods less reliable. Have a play though, see what you can do.

4) I've never really thought about that, perhaps that will work.
 
Old thread, but still like it :) Used this as a base for my battery friendly auto brightness task, thanks! One problem I encountered was that the LIGHT variable isn't updated immediately after turning on my screen, so I enabled 'Light sensor' on Display Off monitoring in Tasker to 'fix' this. But than my device barely went to Deep Sleep anymore, without showing a visible wake lock (?). I guess that makes sense if the device is really constantly monitoring for light changes with the screen off :P.

Now I've disabled this Display Off monitoring setting and simply put a 500ms wait before setting the LightValue variable, which is the big trick to make this work. Probably it takes a while (on some devices?) to get a new value after the screen turns on (which, now I think about it, also totally makes sense :D). Maybe this will help someone struggling with this as I did!
 
You must log in or register to reply here.
Back
Top Bottom