Android6.0 wakelock深入分析.doc

Android6.0 wakelock深入分析 一、PowerManager的持锁接口 我们先来看下PowerManager对应用提供的接口： [cpp] view plain copy 在CODE上查看代码片派生到我的代码片 public WakeLock newWakeLock(int levelAndFlags, String tag) { validateWakeLockParameters(levelAndFlags, tag);//验证wakelock的flag是否有效 return new WakeLock(levelAndFlags, tag, mContext.getOpPackageName()); } validateWakeLockParameters函数如下：主要对flag没有下面这些flag做过滤 [cpp] view plain copy 在CODE上查看代码片派生到我的代码片 public static void validateWakeLockParameters(int levelAndFlags, String tag) { switch (levelAndFlags WAKE_LOCK_LEVEL_MASK) { case PARTIAL_WAKE_LOCK://cpu锁 case SCREEN_DIM_WAKE_LOCK://屏幕微亮，键盘暗 case SCREEN_BRIGHT_WAKE_LOCK://屏幕亮，键盘暗 case FULL_WAKE_LOCK://全亮 case PROXIMITY_SCREEN_OFF_WAKE_LOCK: case DOZE_WAKE_LOCK: case DRAW_WAKE_LOCK: break; default: throw new IllegalArgumentException(Must specify a valid wake lock level.); } if (tag == null) { throw new IllegalArgumentException(The tag must not be null.); } } 我们再看WakeLock类，先看下面两个持锁，第二个timeout的持锁，先持锁，然后发送一个延迟消息再解锁。 [cpp] view plain copy 在CODE上查看代码片派生到我的代码片 public void acquire() { synchronized (mToken) { acquireLocked(); } } public void acquire(long timeout) { synchronized (mToken) { acquireLocked(); mHandler.postDelayed(mReleaser, timeout); } } [cpp] view plain copy 在CODE上查看代码片派生到我的代码片 private final Runnable mReleaser = new Runnable() { public void run() { release(); } }; 再来看acquireLocked，流程最后是调用了service的acquireWakeLock，但是有一个细节我们注意下，这里有一个mCount的计数。也就是没调用一次这个函数，都会对wakelock的mCount加1。 [cpp] view plain copy 在CODE上查看代码片派生到我的代码片 private void acquireLocked() { if (!mRefCounted || mCount++ == 0) { // Do this even if the wake lock is already thought to be held (mHeld == true) // because non-reference counted wake locks are not always properly release