Is it possible to force screen to be on, at all times?

Is it possible to force screen to be on, at all times?

Hello,

To understand my question a little better, let me first explain the problem, that led to it. 

We are using a third-party application, which main features are to keep track of routes and deliveries. For example, where & when is it delivered/collected, or tracing of a driver with the possibility of live updates. 
A requirement for most of these features, would of course be a (nearly) constant GPS signal.

Here lies the problem. On our third-party application, the GPS signal is turned off every time we activate lockscreen (screen goes dark, while the device is still operating in the background). Meaning that our application is neither transmitting nor collecting any data.
But this can be avoided as long as the screen stays on active. - Which leads to my question. 

Is it possible to force the screen on our devices, to stay activated at all times, not allowing our drivers to physically turn the screen off by pressing the power button?
Meaning that as long as there is charge on the battery, the screen will stay activated, unless we as an administrator tell it otherwise. 

As a bit of wishful thinking, we would like to take it even further, so that the screen could switch between maximum brightness and minimum brightness, with the press of a button. I do understand this might would be asking too much, so a feature like that, is defiantly only a second priority. 

Hope someone can support us with our "little" problem.

Kind regards 
Joachim

7 Answers

Order By:   Standard | Newest | Votes
Raymond Chan | posted this 18 November 2020

The root cause may be related to low-power mode rather than lockscreen timeout.  There may be solution/workaround, depending on the following:

- whether you are using OEM-specific Android+ or the generic Android-Enterprise device agent on the device

- the brand and model of your device (especially when using OEM-specific Android+ device agent)

- the version and build number of your MobiControl server

- whether you are using kiosk/lockdown menu and whether you allow the device end-user to go to Settings

- is your device power-off or reboot at least once every 1 or 2 days

Please provide more details.

  • 1
  • 0
JCMOD@SOTI | posted this 18 November 2020

Hi Joachim,

 

On top of what Raymond has already asked, can you try running the batteryoptimize script on the app itself? For example, it'll be batteryoptimize disable com.microsoft.office.outlook. Also, try changing the lockdown type to "Activity Suppression" within the lockdown profile configuration.

 

References:

https://www.soti.net/mc/help/v15.2/en/scriptcmds/reference/androidplus_classic.html

https://www.soti.net/mc/help/v15.2/en/console/reference/dialogs/profiles/androidplus/profile_lockdown_addmenuitem_androidplus.html

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 1
  • 0
Joachim Harder | posted this 18 November 2020

Hi All,

Firstly, thank you for the response.

In regards to our issues with the GPS on our devices, it is related to our third-party App.
We have tested the functions using the device without SOTI and with a separate tracking application. 

The results of these tests showed that the issue most likely was down, to the third-party developer.
An issue they are currently investigating. 

What I would like to know, is if it´s possible to force the screen to stay activated, unless told otherwise by administrator. 
It has proven, that it would fix our issues as a temporary solution. 

Kind regards 
Joachim

  • 0
  • 0
JCMOD@SOTI | posted this 18 November 2020

Hi Joachim,

 

Try this script: Writesecuresetting –sys screen_off_timeout 1800000 (30 minutes) or Writesecuresetting –sys screen_off_timeout 120000 (2 minutes) for example.

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 1
  • 0
Raymond Chan | posted this 19 November 2020

Hi Joachim,

As you haven't provide information related to all the questions in my last post, it's hard to provide any solid suggestion on workaround relevant to your case.

 

However, if the writesecuresetting –sys screen_off_timeout  script command works on your device, and if your device is powered off or reboot at least once every 1 or 2 days, then you can use the script command to set a timeout of say 7 days, thus effiectively forcing the screen to be always on (as timeout will never be reached before both the device and timer get restarted).  This can be your temporary workaround.

 

  • 1
  • 0
John Doe | posted this 19 November 2020

Hi Raymond,

is it really possible to exceede the android limit of 30 minutes as display timeout limit?

If so how would accomplish that exactly? Just use a higher number then 1800000 ?

Kind Regards John

  • 0
  • 0
Raymond Chan | posted this 19 November 2020

Hi John,

What you said is right for quite many of the device models I have tested in the last few years, though I can't guarantee it applies to whatever the device models you have.  You have to do your own test to confirm.

 

If it works, there is still the drawback that the device end-user cannot see what value is currently active from the corresponding device Settings page.  All selectable timeouts  in the GUI will just be shown as non-selelcted.

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback