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

Skip to content

redfin : Blisslauncher crash observed on Android 11 after an OTA update

  • /e/ version: 1.1-rc.2-r-20220620198226-stable-redfin
  • Device model(s): redfin
  • Device rooted: no

Summary

Blisslauncher crash observed on Android 11 after an OTA update

The problem

Steps to reproduce

What is the current behavior?

What is the expected correct behavior?

Technical informations

Relevant logs (adb logcat)

06-21 15:12:19.790  1482  2788 W ActivityManager: Background start not allowed: service Intent { cmp=foundation.e.blisslauncher/.features.notification.NotificationSe        rvice } to foundation.e.blisslauncher/.features.notification.NotificationService from pid=2200 uid=10107 pkg=foundation.e.blisslauncher startFg?=false
   3089 --------- beginning of crash
   3090 06-21 15:12:19.791  2200  2200 E AndroidRuntime: FATAL EXCEPTION: main
   3091 06-21 15:12:19.791  2200  2200 E AndroidRuntime: Process: foundation.e.blisslauncher, PID: 2200
   3092 06-21 15:12:19.791  2200  2200 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{foundation.e.blisslauncher/foundation.e.blisslaun        cher.features.launcher.LauncherActivity}: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=foundation.e.blisslauncher/.features.notificatio        n.NotificationService }: app is in background uid UidRecord{50dde56 u0a107 TPSL idle change:idle|cached procs:1 seq(0,0,0)}
   3093 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3431)
   3094 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3595)
   3095 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
   3096 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
   3097 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
   3098 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
   3099 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
   3100 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:223)
   3101 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7664)
   3102 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
   3103 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
   3104 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
   3105 06-21 15:12:19.791  2200  2200 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=foundation.e.blisslauncher/.fe        atures.notification.NotificationService }: app is in background uid UidRecord{50dde56 u0a107 TPSL idle change:idle|cached procs:1 seq(0,0,0)}
   3106 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1715)
   3107 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ContextImpl.startService(ContextImpl.java:1670)
   3108 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.content.ContextWrapper.startService(ContextWrapper.java:720)
   3109 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.content.ContextWrapper.startService(ContextWrapper.java:720)
   3110 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at foundation.e.blisslauncher.features.launcher.LauncherActivity.onCreate(LauncherActivity.java:323)
   3111 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7994)
   3112 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7978)
   3113 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1313)
   3114 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3404)
   3115 06-21 15:12:19.791  2200  2200 E AndroidRuntime:        ... 11 more
   3116 06-21 15:12:19.795  1482  3994 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
   3117 06-21 15:12:19.795  1482  2788 W ActivityTaskManager:   Not force finishing home activity foundation.e.blisslauncher/.features.launcher.LauncherActivity
   3118 06-21 15:12:19.864  1482  2788 I ActivityManager: Process foundation.e.blisslauncher (pid 2200) has died: fg  TPSL
   3119 06-21 15:12:19.883  1482  2618 D ConnectivityService: requestNetwork for uid/pid:10227/3620 NetworkRequest [ TRACK_DEFAULT id=26, [ Capabilities: INTERNET&NOT_RESTRI        CTED&TRUSTED Uid: 10227 AdministratorUids: [] RequestorUid: 10227 RequestorPackageName: org.telegram.messenger] ]

Full Logs : pixel5.log

Relevant screenshots

Solutions

Workaround

Possible fixes