The launcher name on Android 11 is returned as com.android.settings instead of the actual launcher package name

`getLauncherPackagename()` returns `com.android.settings`. So `mDevice.wait(Until.hasObject(By.pkg(launcherPackage).depth(0)), LAUNCH_TIMEOUT);` doesn't really wait for the launcher package.
I believe this is due to the package visibility changes on Android 11.

Our test setup consisted of this check before starting with the tests:
`String currentPackageName = device.getCurrentPackageName();
if (currentPackageName != null) {
assertEquals(packageName, currentPackageName);
}`

This failed as currentPackageName returned as `com.google.android.apps.nexuslauncher` and getLauncherPackagename() returned `com.android.settings`.

Commencez par suivre getLauncherPackagename() et l’appel mDevice.wait(Until.hasObject(By.pkg(launcherPackage).depth(0)), LAUNCH_TIMEOUT), puis reproduisez la vérification de configuration à l’aide de device.getCurrentPackageName() sur Android 11. C’est terminé lorsque le package du launcher est identifié comme étant le launcher réel plutôt que com.android.settings et que l’attente cible ce package.

Rédigé par le modèle d'indexation à partir du texte de l'issue.