Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was closed and archived. Please ask a new question if you need help.

Need to prevent phone from ever blanking screen..

  • 1 reply
  • 2 have this problem
  • 7 views
  • Last reply by Andrew

more options

locking as duplicate of /questions/971909

We have set the screen saver to "never". After a phone call the screen blanks and requires a on.off button push and unlocking. After a call the screen is blank. This is undesirable behavior for us and I am seeking a way to prevent it. I am writing an ap for a mildly disabled person. They cannot operate the on.off button on the zte open. They also have problems with the unlock mechanism for the screen which requires swiping from bottom towards the top. All swiping is dificult. They can successfully click on icons and anything bigger than the standard 60X60 icons used by the os. I want them to simply be able to make a phone call with a preset number. Currently the application I have pushed to the device does the following. It displays a screen with three commonly called emergency numbers with large icons. The user chooses one of these icons and the dialer is brought up with number already dialed in. The user then simply touches the green dial button and the number is dialed. This works exactly once. After the first time the disabled user cannot restart the application since the screen blanks and requires an on.off push and unlock to get back to a previous state.

Current problems.

1. The screen blanks after a call and requires too many unachievable steps to recover the full app. Recovering the app requires normally a push on the on.off and the unlock procedure, then a reclick to start the application. This is unachievable by disabled user. Incoming calls always work. Both incomming and utgoing calls remove ability of disabled user to make an outgoing call without intervention from care-taker. If screen did not blank during a call, the application would work .

2. Miscellaneous problems.

 a. typing keyboard is difficult for abled users and impossible for disabled user.
 b. application could be better if the dial step was removed.  We understand the security problem.
 c. We would like option for oversized icons, oversized text which we would balance with fewer applications on a single page.

Any solutions would be helpful. I/we are knowledgable programmers but we would prefer to write the a first application as a simple ap and not have to change the operating system in any way. If the above is only achievable with a change and reflashing OS we would consider that approach but currently we have not dived into that code and would prefer to avoid that approach. Is there a simple solution to force the phone to not turn off the display during or after a call that does not require a change to the OS?

Regards Ottojas

locking as duplicate of [/questions/971909] We have set the screen saver to "never". After a phone call the screen blanks and requires a on.off button push and unlocking. After a call the screen is blank. This is undesirable behavior for us and I am seeking a way to prevent it. I am writing an ap for a mildly disabled person. They cannot operate the on.off button on the zte open. They also have problems with the unlock mechanism for the screen which requires swiping from bottom towards the top. All swiping is dificult. They can successfully click on icons and anything bigger than the standard 60X60 icons used by the os. I want them to simply be able to make a phone call with a preset number. Currently the application I have pushed to the device does the following. It displays a screen with three commonly called emergency numbers with large icons. The user chooses one of these icons and the dialer is brought up with number already dialed in. The user then simply touches the green dial button and the number is dialed. This works exactly once. After the first time the disabled user cannot restart the application since the screen blanks and requires an on.off push and unlock to get back to a previous state. Current problems. 1. The screen blanks after a call and requires too many unachievable steps to recover the full app. Recovering the app requires normally a push on the on.off and the unlock procedure, then a reclick to start the application. This is unachievable by disabled user. Incoming calls always work. Both incomming and utgoing calls remove ability of disabled user to make an outgoing call without intervention from care-taker. If screen did not blank during a call, the application would work . 2. Miscellaneous problems. a. typing keyboard is difficult for abled users and impossible for disabled user. b. application could be better if the dial step was removed. We understand the security problem. c. We would like option for oversized icons, oversized text which we would balance with fewer applications on a single page. Any solutions would be helpful. I/we are knowledgable programmers but we would prefer to write the a first application as a simple ap and not have to change the operating system in any way. If the above is only achievable with a change and reflashing OS we would consider that approach but currently we have not dived into that code and would prefer to avoid that approach. Is there a simple solution to force the phone to not turn off the display during or after a call that does not require a change to the OS? Regards Ottojas

Modified by John99

All Replies (1)

more options

Thank you for contacting Mozilla Support. Please wait for a response on your original thread here. This thread will be closed. Somebody will be with you to your original thread on a business day.

Thanks!