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/
Related
Ever since i had my t-Mobile varioIII the backlight light never goes completely off. It will go to the lowest dim setting from bright but not off. I've tried using Phonealarm and use the setting 0% but this does not help. Going directly to backlight in settings and using the slider all the way left just makes the screen backlight go dim too, not off. Does this happen on all Kaisers?
While I'm here, I have in settings>today>items a 'program' called
[email protected] listed along with the usual Date, owner info, etc but if i tick it on nothing appears on the today screen. Any body know what this is for?
same problem with backlight! (mda vario3)
my htc kaiser does that when charging and I have not got the registry keys to change it
Apologies for asking something you guys most probably already checked:
Go Start->Settings->System->Power. Then select the Advanced tab and see if "Turn off device if not used for" is checked and what amount of time has been set for this.
It's normal, Kaisers screen is not transreflective so if the backlight is off there will be no display (unlike the previous 8525/Hermes which had a transreflective screen that could be seen with the backlite off) so they keep it always on when the phone is on. If you are connected to a charger, you can set the phone to turn itself off after a set time, but that's all you can do.
On my TyTN II the setting I showed above works fine. It switches off the screen after the set period.
Yes, the display goes off because the phone is now in off/standby. If you were connected to active sync, it would just dim but stay on.
...and that's because the setting Start->Settings->System->Power->Advanced->On external power. This is by default unchecked.
The problem is how to get the screen to go off and save battery, but remain connected e.g. to WiFi for those of us who receive VoIP calls.
Hi all,
I've had a search around but couldn't find this particular issue discussed.
I have a N1 running CM7. When the phone is plugged in (either on my desk, or in the car) the screen will auto dim to a very low level after approx. 20 seconds after last touch.
This happens if the brightness is set to auto or a manual level. I've gone through all the settings I can find but couldn't find anything regarding this. I have got developer > stay awake enabled, which I guess stops the screen from actually sleeping, but it still goes dim.
The CM7 auto dim settings are disabled.
Any advice folks? I want the screen to not auto-dim after 20 seconds. Out of interest, the 'Car Widget Pro' widget seems to be able to force the brightness if you choose something other than 'auto' in the widget settings. So perhaps I am missing something somewhere else?
It's a real PITA when trying to navigate in the car with google maps as whenever I touch the screen to get the brightness back it disables gps tracking and I have to re-hit the icon, which is distracting whilst driving..
Here's hoping..
Hey, I'm only posting because I had a very similar issue. What I did was go into display settings (while connected via USB) and changed the timeout to one minute (or whatever you want). For me, when I went to change the timeout, no item was selected by default. This happened to me after I installed WidgetLocker for some reason. I doubt I will help but I had a very similar issue...
xd_sjo said:
Hi all,
I've had a search around but couldn't find this particular issue discussed.
I have a N1 running CM7. When the phone is plugged in (either on my desk, or in the car) the screen will auto dim to a very low level after approx. 20 seconds after last touch.
This happens if the brightness is set to auto or a manual level. I've gone through all the settings I can find but couldn't find anything regarding this. I have got developer > stay awake enabled, which I guess stops the screen from actually sleeping, but it still goes dim.
The CM7 auto dim settings are disabled.
Any advice folks? I want the screen to not auto-dim after 20 seconds. Out of interest, the 'Car Widget Pro' widget seems to be able to force the brightness if you choose something other than 'auto' in the widget settings. So perhaps I am missing something somewhere else?
It's a real PITA when trying to navigate in the car with google maps as whenever I touch the screen to get the brightness back it disables gps tracking and I have to re-hit the icon, which is distracting whilst driving..
Here's hoping..
Click to expand...
Click to collapse
There's an app for that. Search Google Play for screenwake or something. I dunno I'll search up the name for you tommorow
Sent from my Nexus One using XDA
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
Hi
I made a project to turn my phone to airplane mode automatically at night.
That would be very simply if I'd go to sleep at the same time every day.
My project uses the motion sensor to detect whether I am still awake.
Tasker checks if the phone was moved within the last 10 min and turns the phone to airplane mode if not. If the phone is being moved again tasker turns off airplane mode again. (Sensor is only alive until it was moved. Any move should turn the sensor off until next 10min check. So it won't drain too much battery)
To narrow down the sensor time I defined time dependent night mode which is turned off by an alarm event or rather late in the morning (in case no alarm was set)
There is also a sleep now task which can be triggered (with a widget if setup) to put the phone in airplane mode until it is picked up again.
I had to play around with sensor sensibility, length and accelerometer (which is now set to "no")
http://cloud.tapatalk.com/s/5897254d3b91d/Airplane_Night.prj.xml.zip
(Could not upload it as xml ...)
2 tasks are not part of the project but used anyways: silent and loud: these are to make the phone silent and loud again in the morning. I am not using taskers reset settings here because I want the phone to become loud 5 min after the alarm goes off because otherwise I get a sound notification about anything that happened straight away after the alarm goes off which I don't really like ... (plus if I look at the phone in the middle of the night I get a loud notification as well - even the phone turns itsself silent after max 20min again ...)
For airplane mode I use secure settings. My phone allows airplane mode with either secure settings or tasker itsself. If you don't have secure settings try taskers internal airplane mode: Net - airplane mode
Please check it out and comment ...
Regards
Nice
Can't wait to try this. Thanks for sharing.
Still one of my favorite projects on Tasker and never stopped using it.
Thanks again, Daniu.
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.