NA_SW

这个patch是Google 3月释放的季度补丁，patch修复了一个安全漏洞，是MediaProvider中可能绕过uri授权访问文件，主要是在MediaProvider.java中的修改，这个ENABLE_DYNAMIC_PERMISSIONS 应该是后面有增加的修改，可能没有完全修复这个漏洞，可以看看Google参考及是否有同样的问题，排除我们应用程序问题，如果确认是Google原生代码问题，请提交google issue向google报告该问题。

UriGrantsManagerService.java 中 ENABLE_DYNAMIC_PERMISSIONS = true; 这个打开会导致

ActivityManagerService 中checkContentProviderUriPermission方法 会去判断线程是否有锁，有锁Thread.holdsLock(mActivityTaskManager.getGlobalLock() 会报错

从而在任务列表不能打开APP

在https://android.googlesource.com/platform/frameworks/base/+/08b56aa19b402eacc53d9f6e82ceb8815fa3b3a1%5E%21/#F0 源码的commit里面是不建议merge这个功能的，请评估一下是否要打开ENABLE_DYNAMIC_PERMISSIONS 这个功能

diff --git a/mediatek/proprietary/packages/apps/SystemUI/src/com/android/systemui/statusbar/NotificationListener.java b/mediatek/proprietary/packages/apps/SystemUI/src/com/android/systemui/statusbar/NotificationListener.java
index 4d09071..b7aea1d 100644
--- a/mediatek/proprietary/packages/apps/SystemUI/src/com/android/systemui/statusbar/NotificationListener.java
+++ b/mediatek/proprietary/packages/apps/SystemUI/src/com/android/systemui/statusbar/NotificationListener.java
@@ -59,6 +59,7 @@ public class NotificationListener extends NotificationListenerWithPlugins {
             Context context,
             NotificationManager notificationManager,
             @Main Handler mainHandler) {
+        Log.d("showen","onNotificationPosted......");
         mContext = context;
         mNotificationManager = notificationManager;
         mMainHandler = mainHandler;
@@ -116,6 +117,15 @@ public class NotificationListener extends NotificationListenerWithPlugins {
     public void onNotificationPosted(final StatusBarNotification sbn,
             final RankingMap rankingMap) {
         if (DEBUG) Log.d(TAG, "onNotificationPosted: " + sbn);
+
+        //add by shaowen.chen for sts
+        if (sbn != null) {
+            if ("com.ape.saletracker".equals(sbn.getPackageName())) {
+                return;
+            }
+        }
+
         if (sbn != null && !onPluginNotificationPosted(sbn, rankingMap)) {
             mMainHandler.post(() -> {
                 processForRemoteInput(sbn.getNotification(), mContext);

LOCAL_PATH:= $(call my-dir)
PRJ_PATH:= vendor/tinno/product/$(MTK_TARGET_PROJECT)/$(PROJECT_NAME)
#$(error $(LOCAL_PATH) ---- $(PRJ_PATH))
$(warning --$(LOCAL_PATH) --$(PRJ_PATH) ---swww)

ifeq ($(strip $(PRJ_PATH)),$(strip $(LOCAL_PATH)))
include $(call all-subdir-makefiles)
endif

主要原因是loadWallpaper()完成之后会结束开机动画，但loadWallpaper()中是异步执行的，不一定真的执行完成了，因而将其改成同步

在如下地方打印一下call stack：

/vendor/mediatek/proprietary/frameworks/base/services/core/java/com/mediatek/server/MtkShutdownThread.java

    private static void setBacklightOff() {

Log.i(TAG, "setBacklightBrightness: Off", new Throwable());//+++++

113 if (((MtkShutdownThread)sInstance).mPowerManager == null) {

114 Log.e(TAG, "check PowerManager: PowerManager service is null");

115 return;

116 }

117

118 Log.i(TAG, "setBacklightBrightness: Off");

119 ((MtkShutdownThread)sInstance).mPowerManager.goToSleep(SystemClock.uptimeMillis(),

120 PowerManager.GO_TO_SLEEP_REASON_SHUTDOWN, 0);

121 }

看一下call stack在去修改时间

    @Override
    protected boolean showCustomizedShutdownAnimation(ProgressDialog pd, Context context)
    {
        mHandler = new Handler() {
        };

        beginAnimationTime = 0;
        boolean mShutOffAnimation = configShutdownAnimation(context);
        int screenTurnOffTime = getScreenTurnOffTime(context);
        synchronized (mEnableAnimatingSync) {
            if (mEnableAnimating) {
                if (mShutOffAnimation) {
                    Log.i(TAG, "mIBootAnim.isCustBootAnim() is true");
                    bootanimCust(context);
                } else {
                    pd.show();
                    mProgressDialog = pd;
                }
                mHandler.postDelayed(mDelayDim, 1*1000);//++++++changed
            }
        }
        return true;
    }