Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Changing to different default launcher app results in restart loop of Blisslauncher

  • /e/ version: 2.1-t-20240605406922-dev-gta4xl
  • Device model(s): SM-P615
  • Developer mode enabled: yes
  • Device rooted: no
  • Trackers blocker enabled: yes

Summary

Changing to different default launcher other than the BlissLauncher results in what seems like a "restart loop" of Blisslauncher due to an exception, resulting in the very bottom white line popping up and down all the time, constantly bobbing up and down the picture on the screen by a few pixels.

The problem

Steps to reproduce Install alternative Launcher, I have tried this with Nova Launcher, and ADW Launcher. Go to Settings > Apps > Default apps > Home Apps, change to Nova Launcher for example.

I have not entered my murena credentials into the system.

What is the current behavior?

Please see summary.

What is the expected correct behavior? BlissLauncher not restarting after it is no longer default home app.

Technical informations

Relevant logs (adb logcat)

I think this is the relevant exception. I have the full logcat here, it's probably revealing way too much, but I narrowed it down to the time where I did the steps mentioned above.

07-07 18:51:19.362   595   619 E AndroidRuntime: FATAL EXCEPTION: launcher-loader
07-07 18:51:19.362   595   619 E AndroidRuntime: Process: foundation.e.blisslauncher, PID: 595
07-07 18:51:19.362   595   619 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'com.android.launcher3.LauncherModel com.android.launcher3.Launcher.getModel()' on a null object reference
07-07 18:51:19.362   595   619 E AndroidRuntime:        at u2.a$c.onLoadAllAppsEnd(MultiModeController.kt:24)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at s2.b.onLoadAllAppsEnd(LauncherAppMonitor.java:26)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at com.android.launcher3.model.LoaderTask.run(LoaderTask.java:157)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:942)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:201)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:288)
07-07 18:51:19.362   595   619 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:67)
07-07 18:51:19.366  5189  8033 W ActivityTaskManager:   Force finishing activity foundation.e.blisslauncher/com.android.quickstep.RecentsActivity
07-07 18:51:19.367  5189   678 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
07-07 18:51:19.373   595   619 I Process : Sending signal. PID: 595 SIG: 9

Relevant screenshots

screenrecord_20240711_15-55-12

Solutions

Workaround

Haven't found a workaround.

I tried deleting the user data of BlissLauncher, destroying all my customizations (ordering of app icons), it didn't help.

Possible fixes

Maybe someone knows a solution to this? Thank you for considering in advance. Other than this issue, e OS is an excellent experience for me. Everything has worked out of the box, so far. No fiddling required. This is an amazing project. Keep up the good work! 😄

Edited by Aude M