Back Key Malfunction

 

Not in compliance with the following Validation guidelines.
• Application should not crash or cause malfunctions due to
H/W usage. (e.g. MENU, HOME, BACK, VOLUME, HOLD key)
• H/W key itself should work as user can normally expect
when user executes application.
 

Defect Examples

  1. Back Key does not work.
    - Defect: Application does not work properly with Back Key event.
    - Solution: Application should go to the previous pageor be terminated with Back key interruption.
  1. Malfunction of Back Key.
    - Defect: Application is terminated by force when user presses Back key.
    - Defect: Application gets frozen when user presses Back key.
    - Defect: Application shows pop-up or error message when user presses Back key.

Self-check List

  • [Ⅳ-6] Application should operate without any problems when user presses H/W KEY while application is running (BACK, CAMERA, etc.).

TIP to Solve This Issue:

  • Since Tizen 2.2, the physical Menu and Back keys are mandatory part of Tizen. Therefore, your application should be built on higher than SDK 2.2 version to handle physical keys properly.
  • For web application, you can bind event handlers on the ‘tizenhwkey’ event to handle physical Menu and Back key. Please refer to below code example.
    // Javascriptcode
    $( window).on( "tizenhwkey", function ( ev ) {
        if ( ev.originalEvent.keyName === "back" ) {
            //call browser back if webApp dev. wants back behavior
            window.history.back(); 
            //add script if there is a need to add another behavior 
            // on H/W back key press
        }
    }
    
  • For native application, you can use the EFL Extension functions which let visible objects without focus get events from the Menu and Back keys. To use the functions and data types of the Efl Extension API, include the <efl_extension.h> header file in your application. 
  • For more details on how to handle Menu and Back key on the target device, please refer to the Managing Menu and Back Key Events. And also it would be helpful to check how to handle Efl extension Event.