恢复出厂设置后Launcher数据错乱

最新推荐文章于 2024-07-15 20:23:45 发布

原创最新推荐文章于 2024-07-15 20:23:45 发布 · 907 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#数据库 #应用

Launcher 专栏收录该内容

5 篇文章

订阅专栏

本文探讨了车载设备恢复出厂设置后出现的数据错乱及丢失现象，并深入分析了其原因，尤其是在加载数据过程中接收到特定广播时触发的问题。文中详细记录了故障排查过程及临时解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

最近有个问题困扰的比较久，车载设备在恢复出厂设置之后，加载数据的时候回概率性的有数据错乱和丢失应用。

打开Launcher数据库看了一下，数据全是乱的，只要不恢复出厂设置，就没有问题。不清楚恢复出厂设置是怎么删除数据库的。

现在的解决方案就是规避这个问题，数据错乱肯定是数据库出了问题。那就在创建数据库后全部清空一边数据库

最近跟了一下问题，问题的根源就是在load数据的时候同时收到一条广播

 public void onReceive(Context context, Intent intent) {
        if (DEBUG_LOADERS) Log.d(TAG, "onReceive intent=" + intent);
//        Toast.makeText(mContext, "收到广播 ------ " + intent.getAction(), Toast.LENGTH_LONG).show();
        final String action = intent.getAction();

        if (Intent.ACTION_PACKAGE_CHANGED.equals(action)
                || Intent.ACTION_PACKAGE_REMOVED.equals(action)
                || Intent.ACTION_PACKAGE_ADDED.equals(action)) {
            final String packageName = intent.getData().getSchemeSpecificPart();
            final boolean replacing = intent.getBooleanExtra(Intent.EXTRA_REPLACING, false);

            int op = PackageUpdatedTask.OP_NONE;

            if (packageName == null || packageName.length() == 0) {
                // they sent us a bad intent
                return;
            }

            if (Intent.ACTION_PACKAGE_CHANGED.equals(action)) {
                op = PackageUpdatedTask.OP_UPDATE;
            } else if (Intent.ACTION_PACKAGE_REMOVED.equals(action)) {
                if (!replacing) {
                    op = PackageUpdatedTask.OP_REMOVE;
                }
                // else, we are replacing the package, so a PACKAGE_ADDED will be sent
                // later, we will update the package at this time
            } else if (Intent.ACTION_PACKAGE_ADDED.equals(action)) {
                if (!replacing) {
                    op = PackageUpdatedTask.OP_ADD;
                } else {
                    op = PackageUpdatedTask.OP_UPDATE;
                }
            }

            if (op != PackageUpdatedTask.OP_NONE) {
//              Toast.makeText(mContext, "收到广播 ------ " + PackageUpdatedTask.OP_NONE, Toast.LENGTH_LONG).show();
                if("com.autonavi.amapauto".equals(packageName) || "com.android.settings".equals(packageName)){
                    return;
                }
                enqueuePackageUpdated(new PackageUpdatedTask(op, new String[] { packageName }));
            }

        } else if (Intent.ACTION_EXTERNAL_APPLICATIONS_AVAILABLE.equals(action)) {
            // First, schedule to add these apps back in.
            String[] packages = intent.getStringArrayExtra(Intent.EXTRA_CHANGED_PACKAGE_LIST);
            enqueuePackageUpdated(new PackageUpdatedTask(PackageUpdatedTask.OP_ADD, packages));
            // Then, rebind everything.
            startLoaderFromBackground();
        } else if (Intent.ACTION_EXTERNAL_APPLICATIONS_UNAVAILABLE.equals(action)) {
            String[] packages = intent.getStringArrayExtra(Intent.EXTRA_CHANGED_PACKAGE_LIST);
            enqueuePackageUpdated(new PackageUpdatedTask(
                        PackageUpdatedTask.OP_UNAVAILABLE, packages));
        } else if (Intent.ACTION_LOCALE_CHANGED.equals(action)) {
            // If we have changed locale we need to clear out the labels in all apps/workspace.
            forceReload();
        } else if (Intent.ACTION_CONFIGURATION_CHANGED.equals(action)) {
             // Check if configuration change was an mcc/mnc change which would affect app resources
             // and we would need to clear out the labels in all apps/workspace. Same handling as
             // above for ACTION_LOCALE_CHANGED
             Configuration currentConfig = context.getResources().getConfiguration();
             if (mPreviousConfigMcc != currentConfig.mcc) {
                   Log.d(TAG, "Reload apps on config change. curr_mcc:"
                       + currentConfig.mcc + " prevmcc:" + mPreviousConfigMcc);
                   forceReload();
             }
             // Update previousConfig
             mPreviousConfigMcc = currentConfig.mcc;
        } else if (SearchManager.INTENT_GLOBAL_SEARCH_ACTIVITY_CHANGED.equals(action) ||
                   SearchManager.INTENT_ACTION_SEARCHABLES_CHANGED.equals(action)) {
            if (mCallbacks != null) {
                Callbacks callbacks = mCallbacks.get();
                if (callbacks != null) {
                    callbacks.bindSearchablesChanged();
                }
            }
        }
    }

enqueuePackageUpdated这个方法对数据库有操作。导致数据错乱，收到的广播action是Intent.ACTION_PACKAGE_CHANGED.equals(action)
|| Intent.ACTION_PACKAGE_REMOVED.equals(action)
|| Intent.ACTION_PACKAGE_ADDED.equals(action)

所以导致数据错乱。