X
Tap here to go to the mobile version of the site.

Support Forum

Screen saver is set to "never". -- This fails after a phone call and phone locks.

Posted

We have set the screen saver to never. After a phone call the screen blanks and requires a on.off button push and unlocking. 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 unlock mechanism for the screen. 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 can not restart the application since the screen blanks and requires an on.off push and unlock to get back to 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.  Wee 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 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?

Regards Otto

We have set the screen saver to never. After a phone call the screen blanks and requires a on.off button push and unlocking. 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 unlock mechanism for the screen. 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 can not restart the application since the screen blanks and requires an on.off push and unlock to get back to 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. Wee 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 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? Regards Otto

Modified by ottojas

Additional System Details

Application

  • User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0

More Information

Question owner

Problem partially solved. No longer need to use physical on.off button. I still need to unlock the phone a restart the ap. It would be nice if the dial activity could return to the invoking application.

Problem partially solved. No longer need to use physical on.off button. I still need to unlock the phone a restart the ap. It would be nice if the dial activity could return to the invoking application.

Question owner

Actually not partially solved. Sometimes after a call the phone will simply be locked but on and require unlocking. Other times the phone requires a push on the on.off button. The best behavior would be for the dialer to return to the calling application. I downloaded Gaia and started walking through the dialer code looking for a way to hook my application in, but it is hard and painstaking work and I would prefer to spend time elsewhere. Any help suggestions welcome.

Actually not partially solved. Sometimes after a call the phone will simply be locked but on and require unlocking. Other times the phone requires a push on the on.off button. The best behavior would be for the dialer to return to the calling application. I downloaded Gaia and started walking through the dialer code looking for a way to hook my application in, but it is hard and painstaking work and I would prefer to spend time elsewhere. Any help suggestions welcome.
mluna 70 solutions 486 answers

Hi Ottojas,

Thanks for your detailed posting and for using Firefox OS, I apologize for the delayed response. We are working on the answering calls UI and also voice recognition for Firefox OS, thanks for your patience.

I have passed on your comments to the quality engineer who has posted some videos about this, who may have some suggestions that will help. Here is his blog: http://www.marcozehe.de/2013/07/19/small-demo-video-about-firefox-os-accessibility/

Best regards, Michelle Luna

Hi Ottojas, Thanks for your detailed posting and for using Firefox OS, I apologize for the delayed response. We are working on the answering calls UI and also voice recognition for Firefox OS, thanks for your patience. I have passed on your comments to the quality engineer who has posted some videos about this, who may have some suggestions that will help. Here is his blog: http://www.marcozehe.de/2013/07/19/small-demo-video-about-firefox-os-accessibility/ Best regards, Michelle Luna

Question owner

The suggestions have nothing to do with our problem. It is great that mozilla is working to provide access to the blind. The disability that we are dealing with is palsy and highly inaccurate and weak fingers. The application we have built allows for the dailer to be preloaded with important numbers the user may wish to call. The application has large buttons. The call button on the dialer is large enough. The problem is returning to the previous state and screen with the large buttons. If the phone screen blanks the user can not make a second call. If the application quits the user is barely able to restart the application. If the screen locks up after a call the user can not unlock the screen. The problem is in the interaction of the application with the dialer and the default behavior of the dialer that over-rides the user preferences and turns off the screen.

The suggestions have nothing to do with our problem. It is great that mozilla is working to provide access to the blind. The disability that we are dealing with is palsy and highly inaccurate and weak fingers. The application we have built allows for the dailer to be preloaded with important numbers the user may wish to call. The application has large buttons. The call button on the dialer is large enough. The problem is returning to the previous state and screen with the large buttons. If the phone screen blanks the user can not make a second call. If the application quits the user is barely able to restart the application. If the screen locks up after a call the user can not unlock the screen. The problem is in the interaction of the application with the dialer and the default behavior of the dialer that over-rides the user preferences and turns off the screen.