So I am new to Tasker. I am using it to set the capacitive button backlights to stay on when the screen is on and turn off when the screen is off
So I set up 2 profiles, one for Display On, and another for Display off.
Display On has 2 tasks
1: su
2: echo 40 > /sys/class/leds/button-brightness/brightness
Display Off has 2 tasks
1: su
2: echo 0 > /sys/class/leds/button-brightness/brightness
When the phone is running, it works decently, I haven't done a bunch of tweaking but the concept seems to be working OK
However, upon first boot, it seems Tasker is not reading the very first Display On event, and the lights aren't turning on. Any ideas how to get that to work?
Thanks!
Tasker is probably not yet running at the time the screen on occurs.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Why not set a separate condition? "On device boot" for "display on".
Related
When I soft-reset my TD2, leave it be for a while so that backlight dims and then press a HW button or tap the display, backlight comes up back again. However, if the device enters standby the "resume backlight on user activity" function stops working properly for some reason. (I am not sure for how long TD2 has to be left alone - maybe 30 minutes, 1 hour?) Specifically, if the backlight dims and I go to Settings > System > Power > Advanced tab and uncheck "Dim screen after X s", the screen will light up, but if I check this checkbox again, the screen will dim even though I just interacted with the phone and the screen should therefore remain lit up. The only other way to get a fully lit screen (at least until it dims again due to user inactivity) is to lock the phone and unlock it back.
I should also add that this happens with the official stock WM6.5 ROM.
Is there anything in phone settings I should enable or disable, or is there any registry key I should set to some specific value for this feature to work properly again?
Thanks for any help.
nvx
nvx2004 said:
When I soft-reset my TD2, leave it be for a while so that backlight dims and then press a HW button or tap the display, backlight comes up back again. However, if the device enters standby the "resume backlight on user activity" function stops working properly for some reason. (I am not sure for how long TD2 has to be left alone - maybe 30 minutes, 1 hour?) Specifically, if the backlight dims and I go to Settings > System > Power > Advanced tab and uncheck "Dim screen after X s", the screen will light up, but if I check this checkbox again, the screen will dim even though I just interacted with the phone and the screen should therefore remain lit up. The only other way to get a fully lit screen (at least until it dims again due to user inactivity) is to lock the phone and unlock it back.
I should also add that this happens with the official stock WM6.5 ROM.
Is there anything in phone settings I should enable or disable, or is there any registry key I should set to some specific value for this feature to work properly again?
Thanks for any help.
nvx
Click to expand...
Click to collapse
I think, you could try to use Lumos that exist in this Thread http://forum.xda-developers.com/showpost.php?p=2955401&postcount=1
Hakim,
thanks for the suggestion, however, in the meantime I learned that the issue is caused by the WM auto-lock feature (it is a bug that nobody cared to fix :-/ ). I was not able to find any useful work-around so I decided to install an application called LockDevice (it should be here somewhere on XDA Devs) which works very well and seems to be relatively light-weight.
Anyway, thanks again for your response.
nvx
Screen dimming - requires single tap to "wake" - looking for a way to disable
So I am running a stock Sprint HTC One (Android 4.4.2, software version 5.03.651.3) and for months now (for some reason, I thought I first noticed this behavior right after 4.3 got pushed out), there is a single behavior that has perplexed me, and despite trying various configuration changes, I cannot seem to get it to resolve.
I currently have all power-saving features disabled, screen timeout set to 1 minute, automatic brightness enabled (slider, which shouldn't make any difference, is set to the middle), daydream is disabled, and developer options are on with no screen timeout while charging enabled.
What seems to happen is that after about 1 minute (also the duration set for screen timeout, which initially made me wonder), the screen (while plugged in and charging) will dim slightly, maybe about 50% of the standard brightness when the phone is actively being used, and I have to tap the screen (not the double-tap I have been reading about, which supposedly isn't even implemented yet) just once to dismiss the dimming in order to register touch input.
At first, I checked Daydream a bunch of times, enabled it, disabled it, changed settings, and it seemed to have nothing to do with it, because when I did enable Daydream, I got the real screensaver or colored screensaver that I had chosen in the options.
I then disabled auto-brightness, set the manual brightness level to minimum, maximum, and a dozen levels in between, and I still got the dimming that required a single tap to restore use of the screen and brought the brightness back up to its normal level.
I made a bunch of power saving changes, enabled, disabled, to no avail.
Three factory resets later, (tested with no installed apps) I still have the same behavior. It seems like there is a setting that is enabling some sort of screen saver (that only dims the screen to about 50% of the set brightness level, but disables interaction from the user until the screen is tapped a single time) that is dismissed with that single tap.
I've gotten used to it, but it's really infuriating, especially in the car when I have it mounted on the dash for things like GPS, streaming audio (I just want to be able to see what song is playing if it's a new album), and other things that require a glance over to the phone. Sadly, in the car is probably the worst time for the dimming, since the ambient light outside makes the screen appear off when this "feature" kicks in.
I've spent a great deal of time searching/reading threads not only here, but on other mobile forums as well, and I cannot even find a reference to this issue that behaves the same way mine does.
This is my Hail Mary in the hopes that I really have missed something simple.
Thanks in advance for any ideas!
I'm trying to get nightmode to run at a specific time in the evening, as well as some other tasks, then turn off in the morning along with using intent radio as a radio alarm.
I'm using the run shell action (with root): "settings put global night_mode_enabled 1" to turn on night mode and changing the "1" to "0" to turn it off. All this does is put the shortcut in the quick settings to appear on, but doesn't actually tint the screen, same with turning it off - appears off in quick settings, but still tinted.
I know I can work around it with autoinput, but I'd rather a solution that doesn't require the screen to be on.
Cheers for the help
https://forums.oneplus.net/threads/display-night-mode.452908/
I've made some tasks to let me switch location settings between off, battery saving and high accuracy, when I'm home, go to bed or leave for work. I'm on an unrooted OnePlus 5 running OxygenOS (Android 7.1.1), and am currently using AutoTools by joaomgcd to accomplish this, through its Secure Settings module after granting it permissions via ADB.
I've noticed it being unreliable though, several times when running my 'sleep mode' task, it won't successfully toggle my location settings as setup, leaving them unchanged. If I re-add that Action in the task and run it again, it seems to work, but fails again arbitrarily at some point in the future.
Is there a more reliable way to toggle location settings without root? Or alternatively, a way to make this current method work reliably?
Anyone?
Phosphenetre said:
I've noticed it being unreliable though, several times when running my 'sleep mode' task, it won't successfully toggle my location settings as setup, leaving them unchanged.
Click to expand...
Click to collapse
I regularly switch settings using root and shell commands, so my initial suspicion is to figure it may be something other than the AutoTools Secure Settings changes. For example I changed all my long waits to global variable timers, which ended up having an issue that occasionally timer tasks weren't triggering with the screen off. It turned out my issue was that the instantaneous times worked with the screen on, but they were sometimes being missed with the screen off. Things started working correctly after I got rid of the "To" times and just used "From" for the profile times. Basically I figure you might be getting into some sort of similar issue, where power saving features could interfere with expectations in the routines. Without knowing more about the sleep mode task, it's difficult to really give much useful information, but I'd suspect it could be something like Doze interfering. Whitelisting Tasker and Secure Settings might fix that sort of thing, but it probably wouldn't be my approach.
The only other item that comes to mind is if the phone has the popup when switching modes. I think the screen has to be on for AutoInput to work. That repeated popup finally went away on my phone, so I might add high accuracy when plugged in.
Quick question for you smarter people. I have Tasker setup to disable 3 apps when I turn the screen off, and turn them back on when the screen comes on. For whatever reason, they don't want to actually work. Here is how I have it set up.