Android 屏蔽Power键 Home键

在PhoneWindowManagerjava中处理
在InputDispatchercpp中处理

在Android开发中，我们通常需要对发往工厂的Android软件进行工厂测试；这其中就要去测试各个按键的功能，例如：测试HOME/BACK/MENU/POWER。但是问题在于：这些按键基本上都是有系统负责处理的，或者在系统处理了之后在向上分发的。也就是说，不论怎样系统都会对此类按键进行处理。
这里给出如下方法：

在PhoneWindowManager.java中处理

frameworks/base/services/core/java/com/android/server/policy/PhoneWindowManager.java

// First we always handle the home key here, so applications
// can never break it, although if keyguard is on, we do let
// it handle it, because that gives us the correct 5 second
// timeout.
if (keyCode == KeyEvent.KEYCODE_HOME) {// If we have released the home key, and didn't do anything else// while it was pressed, then it is time to go home!if (!down) {cancelPreloadRecentApps();mHomePressed = false;if (mHomeConsumed) {mHomeConsumed = false;return -1;}if (canceled) {Log.i(TAG, "Ignoring HOME; event canceled.");return -1;}// If an incoming call is ringing, HOME is totally disabled.// (The user is already on the InCallUI at this point,// and his ONLY options are to answer or reject the call.)TelecomManager telecomManager = getTelecommService();if (telecomManager != null && telecomManager.isRinging()) {Log.i(TAG, "Ignoring HOME; there's a ringing incoming call.");return -1;}// Delay handling home if a double-tap is possible.if (mDoubleTapOnHomeBehavior != DOUBLE_TAP_HOME_NOTHING) {// just in casemHomeDoubleTapPending = true;mHandler.postDelayed(mHomeDoubleTapTimeoutRunnable,ViewConfiguration.getDoubleTapTimeout());return -1;}// deal with key.... beforeif (isTopActivityFactoryTool(win)) {Log.d(TAG,"factory tool return");return 0;}// deal with key.... endhandleShortPressOnHome();return -1;}// If a system window has focus, then it doesn't make sense// right now to interact with applications.WindowManager.LayoutParams attrs = win != null ? win.getAttrs() : null;if (attrs != null) {final int type = attrs.type;if (type == WindowManager.LayoutParams.TYPE_KEYGUARD_SCRIM|| type == WindowManager.LayoutParams.TYPE_KEYGUARD_DIALOG|| (attrs.privateFlags & PRIVATE_FLAG_KEYGUARD) != 0) {// the "app" is keyguard, so give it the keyreturn 0;}final int typeCount = WINDOW_TYPES_WHERE_HOME_DOESNT_WORK.length;for (int i=0; i<typeCount; i++) {if (type == WINDOW_TYPES_WHERE_HOME_DOESNT_WORK[i]) {// don't do anything, but also don't pass it to the appreturn -1;}}}// Remember that home is pressed and handle special actions.if (repeatCount == 0) {mHomePressed = true;if (mHomeDoubleTapPending) {mHomeDoubleTapPending = false;mHandler.removeCallbacks(mHomeDoubleTapTimeoutRunnable);handleDoubleTapOnHome();} else if (mLongPressOnHomeBehavior == LONG_PRESS_HOME_RECENT_SYSTEM_UI|| mDoubleTapOnHomeBehavior == DOUBLE_TAP_HOME_RECENT_SYSTEM_UI) {preloadRecentApps();}} else if ((event.getFlags() & KeyEvent.FLAG_LONG_PRESS) != 0) {if (!keyguardOn) {handleLongPressOnHome(event.getDeviceId());}}return -1;
}

其中
isTopActivityFactoryTool函数的实现方式

public boolean isTopActivityFactoryTool(WindowState win) {if(win != null){String topPackageName = win.getOwningPackage();if(("com.cp.packagename1".equals(topPackageName)|| "com.cp.packagename2".equals(topPackageName))){Log.d(TAG,"top activity is " + topPackageName);return true;}}return false;
}

在InputDispatcher.cpp中处理

frameworks/base/native/services/inputflinger/InputDispatcher.cpp

void InputDispatcher::notifyKey(const NotifyKeyArgs* args) {
#if DEBUG_INBOUND_EVENT_DETAILSALOGD("notifyKey - eventTime=%lld, deviceId=%d, source=0x%x, policyFlags=0x%x, action=0x%x, flags=0x%x, keyCode=0x%x, scanCode=0x%x,metaState=0x%x, downTime=%lld",args->eventTime, args->deviceId, args->source, args->policyFlags,args->action, args->flags, args->keyCode, args->scanCode,args->metaState, args->downTime);
#endifif (!validateKeyEvent(args->action)) {return;}uint32_t policyFlags = args->policyFlags;int32_t flags = args->flags;int32_t metaState = args->metaState;if ((policyFlags & POLICY_FLAG_VIRTUAL) || (flags &AKEY_EVENT_FLAG_VIRTUAL_HARD_KEY)) {policyFlags |= POLICY_FLAG_VIRTUAL;flags |= AKEY_EVENT_FLAG_VIRTUAL_HARD_KEY;}if (policyFlags & POLICY_FLAG_FUNCTION) {metaState |= AMETA_FUNCTION_ON;}policyFlags |= POLICY_FLAG_TRUSTED;int32_t keyCode = args->keyCode;if (metaState & AMETA_META_ON && args->action == AKEY_EVENT_ACTION_DOWN) {int32_t newKeyCode = AKEYCODE_UNKNOWN;if (keyCode == AKEYCODE_DEL) {newKeyCode = AKEYCODE_BACK;} else if (keyCode == AKEYCODE_ENTER) {newKeyCode = AKEYCODE_HOME;}if (newKeyCode != AKEYCODE_UNKNOWN) {AutoMutex _l(mLock);struct KeyReplacement replacement = {keyCode, args->deviceId};mReplacedKeys.add(replacement, newKeyCode);keyCode = newKeyCode;metaState &= ~AMETA_META_ON;}} else if (args->action == AKEY_EVENT_ACTION_UP) {// In order to maintain a consistent stream of up and down events, check to see if the key// going up is one we've replaced in a down event and haven't yet replaced in an up event,// even if the modifier was released between the down and the up events.AutoMutex _l(mLock);struct KeyReplacement replacement = {keyCode, args->deviceId};ssize_t index = mReplacedKeys.indexOfKey(replacement);if (index >= 0) {keyCode = mReplacedKeys.valueAt(index);mReplacedKeys.removeItemsAt(index);metaState &= ~AMETA_META_ON;}}KeyEvent event;event.initialize(args->deviceId, args->source, args->action,flags, keyCode, args->scanCode, metaState, 0,args->downTime, args->eventTime);mPolicy->interceptKeyBeforeQueueing(&event, /*byref*/ policyFlags);bool needWake;{ // acquire lockmLock.lock();if (shouldSendKeyToInputFilterLocked(args)) {mLock.unlock();policyFlags |= POLICY_FLAG_FILTERED;if (!mPolicy->filterInputEvent(&event, policyFlags)) {return; // event was consumed by the filter}mLock.lock();}int32_t repeatCount = 0;//add your control code hereif(false){//origin source code}else{//your self source code}#ifdef CONTROL_KEY_CODE//your self source code#else//origin source doce#endifKeyEntry* newEntry = new KeyEntry(args->eventTime,args->deviceId, args->source, policyFlags,args->action, flags, keyCode, args->scanCode,metaState, repeatCount, args->downTime);needWake = enqueueInboundEventLocked(newEntry);mLock.unlock();} // release lockif (needWake) {mLooper->wake();}
}

详细的添加规则可以根据自己需求，伪代码如下所示

        //add your control code hereif(false){//origin source code}else{//your self source code}#ifdef CONTROL_KEY_CODE//your self source code#else//origin source doce#endif

有关InputDispatch的处理参见 Android 中处理POWER/HOME流程

Android 屏蔽Power键 Home键相关推荐

android4.2 拦截power键,Android 屏蔽Power键 Home键
2014-04-18 17:22 1557人阅读评论(0) 收藏举报分类: Android(46) 版权声明:本文为博主原创文章,未经博主允许不得转载. 最近正在处理工厂测试的功能,里面有个功能 ...
android 屏蔽home键操作
1.重写onAttachedToWindow public void onAttachedToWindow() { this.getWindow().setType(WindowManager.Lay ...
android 9.0 10.0 去掉音量键+Power键组合键的屏幕截图功能
1.概述在10.0的系统中由WindowManagerService这个系统服务来循环读取窗口获取的消息(包括按下,弹起,双击,单击等)然后分发到各个类接收处理这些消息,在这个过程中PhoneWin ...
直播源码开发，Android 屏蔽返回键（后退键）
直播源码开发,Android 屏蔽返回键(后退键) 方案一在Activity中重写onBackPressed方法(推荐使用). @Override public void onBackPressed ...
android怎么模拟返回,Android中障蔽返回键，HOME键以及模拟HOME键返回效果的方法...
Android中屏蔽返回键,HOME键以及模拟HOME键返回效果的方法在Android开发中,有时需要屏蔽一些实体的按键,如HOME键,返回键等实体的按键,实现的方法如下. 1. 屏蔽实体按键屏蔽 ...
Android 关于长按back键退出应用程序的实现
Android 关于长按back键退出应用程序的实现最近在做一个Android上的应用,碰到一个问题就是如何实现长按back键退出应用程序.在网上查找了很多资料,发现几乎没有这样的实现,大部分在处理 ...
android动态加home,Android 解决监听home键的几种方法
Android 解决监听home键的几种方法前言: 以下两种方法可以完美解决监听back键,home键,多任务键(最近任务键). 一.使用注册广播监听home键.多任务键演示图创建一个广播代码如 ...
Android 禁用电源键音量键与模拟
/base/services/core/java/com/android/server/policy/PhoneWindowManager.java 模拟在PhoneWindowManager中注册 ...
android设置返回按钮无效,Android onKeyDown监听返回键无效的解决办法
Android onKeyDown监听返回键无效的解决办法当我们的Activity继承了TabActivity,在该类中重写onKeyDown是监听不到返回键的, 具体解决方法如下: 重写dispa ...
android获取spinner的值_在Android的Spinner中实现键值对的正确方法是什么
这是在Android中为Spinner实现键值对的正确方法吗? package com.mypackage import android.app.Activity; import android.os ...

Android 屏蔽Power键 Home键

在PhoneWindowManager.java中处理

在InputDispatcher.cpp中处理

Android 屏蔽Power键 Home键相关推荐

最新文章

热门文章