Override Power button just like Home button

Phew. This is quite a contended question, with a great deal of commentary behind it.

Let me begin by rephrasing your question a bit. If I understand clearly, you'd like to disable all physical buttons on the device for the duration of your activity. This is inclusive of the power button, which you detect by handling the ACTION_SCREEN_OFF intent. Your current (successful) workaround for this scenario is to broadcast an ACTION_SCREEN_ON, kicking the screen back to life when it's turned off, provided the host implements this correctly.

You'd now like to go the extra mile, by rendering this action unnecessary, if (and only if) you are able to catch and handle ACTION_SCREEN_OFF before it gets sent to the system. Is this possible, and if so, how?

This bears some discussion. The short version, however, is simple: this is not possible, without custom modification to your firmware or the core of the Android operating system, for a limited number of devices.

The Android system, as far as is documented, defines this as a broadcast action. Following the publish-subscribe pattern of message propagation, this message will notify all concerned parties of this action. Because this message is sent by the system, because the message stack is managed by the system, and because the message is also received by the system, your code simply isn't injected in the right place to block the reception of this message.

Furthermore, for some devices, this will be a physical switch that has no programmatic interrupt whatsoever. At best, the Android system can hope to handle for the event when it happens, which is precisely why this broadcast message is something of a special case in the service stack. To the best of my knowledge and based upon the sparse documentation on this scenario, this is why it's not an out-of-the-box, supported feature, before we consider any of the possible vectors for abuse.

Your best recourse is actually a much simpler one, if you have the ability to modify the physical hardware for the device in question: restrict access to, mangle, or otherwise disable the physical power button. In many scenarios this is undesirable, but this works in situations where your Android device is being used, for example, as a point-of-sale or a public service machine. If this is unworkable, placing physical restrictions on access to the power button may be all that's required, handling for the remainder of cases (for example, spot attempts to toggle the screen) by sending ACTION_SCREEN_ON.

Just remember, this strategy isn't foolproof. Do this competently and document the procedure well, lest you become fodder for the next 2600 exposé.

Best of luck with your application.

On the contrary to all the answers .. Check this out:

@Overridepublic boolean dispatchKeyEvent(KeyEvent event) {        if (event.getKeyCode() == KeyEvent.KEYCODE_POWER) {                Log.i("", "Dispath event power");                Intent closeDialog = new Intent(Intent.ACTION_CLOSE_SYSTEM_DIALOGS);                sendBroadcast(closeDialog);                return true;        }        return super.dispatchKeyEvent(event);}

What it does:

Whenever the user presses the power button. We cancel the Dialog before its even seen!! :) . This works for me.. (Tested on note2)

Here is what I have done:

(1) Create a receiver class:

public class ScreenReceiver extends BroadcastReceiver {    @Override    public void onReceive(Context context, Intent intent) {        String action = intent.getAction();        switch (action) {            case Intent.ACTION_SCREEN_OFF:                BaseActivity.unlockScreen();                break;            case Intent.ACTION_SCREEN_ON:                // and do whatever you need to do here                BaseActivity.clearScreen();        }    }}

(2) The two methods that are called above looked like this:

public static void unlockScreen () {    if (current == null) return;    Log.i( Constants.TAG, "Turning on screen ... " );    Window window = current.getWindow();    window.addFlags( WindowManager.LayoutParams.FLAG_DISMISS_KEYGUARD );    window.addFlags( WindowManager.LayoutParams.FLAG_SHOW_WHEN_LOCKED );    window.addFlags( WindowManager.LayoutParams.FLAG_TURN_SCREEN_ON   );}public static void clearScreen () {    if (current == null) return;    Log.i( Constants.TAG, "Clearing screen flag when on ... " );    Window window = current.getWindow();    window.clearFlags( WindowManager.LayoutParams.FLAG_DISMISS_KEYGUARD );    window.clearFlags( WindowManager.LayoutParams.FLAG_SHOW_WHEN_LOCKED );    window.clearFlags( WindowManager.LayoutParams.FLAG_TURN_SCREEN_ON   );}private static BaseActivity current;@Overrideprotected void onResume () {    current = this;}

(3) In the main activity class onCreate() method register the receiver:

    IntentFilter filter = new IntentFilter( Intent.ACTION_SCREEN_ON );    filter.addAction( Intent.ACTION_SCREEN_OFF );    registerReceiver(new ScreenReceiver(), filter);