Screen dim instead of power off
Gathering feedback
The feature is that the screen is alwasy on, but the back-light is set to low (user defined level). Everything other works as normal, for example the screen off/on gesture just ramps the back-light up or dims the screen. Less brightness for back-light means less power and with high contrast themes (or high contrast dashboards) some of the locus features are still visible with the screen dimmed.
Good day Krzysztof,
thank you for sharing this idea. I personally can't imagine it's usage to be true. Backlight is quite well automatically handled by Android system itself and if not, I may always quite easy slide top system bar and modify backlight manually by myself.
So why should I need some additional settings directly in Locus Map application? Also how this should be correctly set? By some slider that will setup backlight intensity? If so, then it is just a copy of already existing settings that is directly in Android devices, isn't it?
Good day Krzysztof,
thank you for sharing this idea. I personally can't imagine it's usage to be true. Backlight is quite well automatically handled by Android system itself and if not, I may always quite easy slide top system bar and modify backlight manually by myself.
So why should I need some additional settings directly in Locus Map application? Also how this should be correctly set? By some slider that will setup backlight intensity? If so, then it is just a copy of already existing settings that is directly in Android devices, isn't it?
Good day Krzysztof,
to be true, I still miss the point.
Situation: I sit on bike, attach device on it and start recording in Locus Map ( for example ). Now I see that automatic screen backlight is too shiny, so I slide top system bar, modify backlight and finally start my ride happy with setup.
Now, how may your settings help here? Based on what you wrote "another setting to screen on/off settings which would be something like
"Screen power when off: N%" whicn corresponds to 0-100% of screen
brightness, 0 when screen is really off, and 100% is the current screen brightness value" , I understand that you wants from Locus not to completely turn off screen, but just reduce backlight to your defined value, right?
Does it make really sense? Screen will still be turned on and Locus Map will still draw map and it's content = almost zero battery save, and screen will be a lot darker so I'll see nothing...
Good day Krzysztof,
to be true, I still miss the point.
Situation: I sit on bike, attach device on it and start recording in Locus Map ( for example ). Now I see that automatic screen backlight is too shiny, so I slide top system bar, modify backlight and finally start my ride happy with setup.
Now, how may your settings help here? Based on what you wrote "another setting to screen on/off settings which would be something like
"Screen power when off: N%" whicn corresponds to 0-100% of screen
brightness, 0 when screen is really off, and 100% is the current screen brightness value" , I understand that you wants from Locus not to completely turn off screen, but just reduce backlight to your defined value, right?
Does it make really sense? Screen will still be turned on and Locus Map will still draw map and it's content = almost zero battery save, and screen will be a lot darker so I'll see nothing...
If somebody want to use the acuall power button, an android system wide app for replacing power off with screen dim would be great. But I didn't find anything. I guess this would require root anyway.
But again this will only make sense if you already force your phone to stay online and keep getting data from expensive receivers like GPS for example by track recording or navigation without standby.
Like @0709 already ask for, please don't vote for this idea if you search for an power saving issue workarround. You will find the solution for these things here: http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6
And if you search for BT GPS related issues, you will need even more stupid exceptions in your power management: http://help.locusmap.eu/topic/create-faq-entry-for-solving-bt-sleep-issues
If somebody want to use the acuall power button, an android system wide app for replacing power off with screen dim would be great. But I didn't find anything. I guess this would require root anyway.
But again this will only make sense if you already force your phone to stay online and keep getting data from expensive receivers like GPS for example by track recording or navigation without standby.
Like @0709 already ask for, please don't vote for this idea if you search for an power saving issue workarround. You will find the solution for these things here: http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6
And if you search for BT GPS related issues, you will need even more stupid exceptions in your power management: http://help.locusmap.eu/topic/create-faq-entry-for-solving-bt-sleep-issues
This idea could be solved with tasker. After I did learn that my phone does have an even larger gap between min and max LCD (12 hours screen on time vs 45 hours) I did start to implement this idea in tasker.
I did change it a little bit. Instead of automatically dim based on time, I like to control it direcly.
Good to have a 2-step camera button on my phone :)
half click will loop through 3-step display brightness:
full click will show dashboard and min brightness
Is there an API or any kind of import simulation for tasker to enable dashboard? I don't like simulating touch screen inputs because they would not work during screenlock.
This idea could be solved with tasker. After I did learn that my phone does have an even larger gap between min and max LCD (12 hours screen on time vs 45 hours) I did start to implement this idea in tasker.
I did change it a little bit. Instead of automatically dim based on time, I like to control it direcly.
Good to have a 2-step camera button on my phone :)
half click will loop through 3-step display brightness:
full click will show dashboard and min brightness
Is there an API or any kind of import simulation for tasker to enable dashboard? I don't like simulating touch screen inputs because they would not work during screenlock.
Here is an System Dim instead of power off for Sony Z3 Compact with 2-Step Camera+Focus button.
You need to use AutoInput to get access to Focus Button and Camera Button Events. And you may need to disable one of Sony Camera App Services depending on your ROM.
BrightSelect_Toggle.prf.xml loop through as many brightness levels as you like to enter there.
Locus_Dashboard_Toggle.prf.xml does call 2 presets alternating, one for power saving and one for active usage. Because a 2-step would click trigger both profiles, the BrightSelect loop does look for running Locus Dashboard Toggle Tasks. Feel free to implement timers instead of button triggers or if you are crazy enoght, overwrite Android power button with root access :DHere is an System Dim instead of power off for Sony Z3 Compact with 2-Step Camera+Focus button.
You need to use AutoInput to get access to Focus Button and Camera Button Events. And you may need to disable one of Sony Camera App Services depending on your ROM.
BrightSelect_Toggle.prf.xml loop through as many brightness levels as you like to enter there.
Locus_Dashboard_Toggle.prf.xml does call 2 presets alternating, one for power saving and one for active usage. Because a 2-step would click trigger both profiles, the BrightSelect loop does look for running Locus Dashboard Toggle Tasks. Feel free to implement timers instead of button triggers or if you are crazy enoght, overwrite Android power button with root access :DI guess this can't be implemented in Locus, even if the Android APIs would be capable becuase we have so many different requirements which would result into a painfull configuration UI:
- replace android power button
- auto dim after time X + don't turn screen off
- open dashboad and dim screen on power toogle
- open dashboard and dim after time X
- open dashboard and dim on any hardware key
- switch screen brightness with any hardware key
- prevent multible action execution if 2 hardware keys are presset (2-step buttons)
I guess tasker is the only tool to handle all of it.
Should we add an advise to use automation software to combine timebased and hardware key based events with locus preset usage over action task to knowlage base as idea solution? Maybe add examples for some usecases like I did. It would help if any adjustet tasker configurations for all the other usecases could be shared too.
I guess this can't be implemented in Locus, even if the Android APIs would be capable becuase we have so many different requirements which would result into a painfull configuration UI:
- replace android power button
- auto dim after time X + don't turn screen off
- open dashboad and dim screen on power toogle
- open dashboard and dim after time X
- open dashboard and dim on any hardware key
- switch screen brightness with any hardware key
- prevent multible action execution if 2 hardware keys are presset (2-step buttons)
I guess tasker is the only tool to handle all of it.
Should we add an advise to use automation software to combine timebased and hardware key based events with locus preset usage over action task to knowlage base as idea solution? Maybe add examples for some usecases like I did. It would help if any adjustet tasker configurations for all the other usecases could be shared too.
And here is the tasker solution with power btn overwrite:
Locus_PwrBtn_ScreenDim
If the task is fast enoght, it would turn screen back on before the non removeable action "enter sleep on power button press" put the device into sleep mode. Then it does trigger an screen dim toggle to dim screen on power botton press and will undim on another power botton press. This solution doesn't need root, but switich from screen dim to screen active can't be triggered by a touch action because global touch action event listening would require root, you need to hit power btn again to switch from screen dim to screen bright.And here is the tasker solution with power btn overwrite:
Locus_PwrBtn_ScreenDim
If the task is fast enoght, it would turn screen back on before the non removeable action "enter sleep on power button press" put the device into sleep mode. Then it does trigger an screen dim toggle to dim screen on power botton press and will undim on another power botton press. This solution doesn't need root, but switich from screen dim to screen active can't be triggered by a touch action because global touch action event listening would require root, you need to hit power btn again to switch from screen dim to screen bright.If you don't have anoght hardware buttons to trigger screen dim instead of power off, you could try something like "Mi Key" for less then 1$ to have another input for tasker plugin "auto input" if your device does support headphone buttons.
If you don't have anoght hardware buttons to trigger screen dim instead of power off, you could try something like "Mi Key" for less then 1$ to have another input for tasker plugin "auto input" if your device does support headphone buttons.
Replies have been locked on this page!