Frequent crashes of Bliss Launcher (logcat available)
- /e/ version: Android 10, 0.19-q-20211027142973 and 0.20-q-20211215151800
- Device model(s): FP2
- Device rooted: yes
Summary
Since some time, the Bliss launcher has started to crash frequently.
The problem
Sometimes, the crash seems to be "harmless" -- when I leave an app to turn back to the home screen, only the background and a spinning wheel is displayed for some 2 seconds, then I see the icons again. I am not sure whether that is indeed a crash; no logcat available for this.
However, sometimes (actually twice today!) also the ordering of the icons is affected. A few days ago, I lost most of my folders -- all the contained icons were "spread" on several pages of the home screen. Today, the icons (including folders) "only" got shuffled; within the folders, everything kept its place; the bottom area with the favorite icons got emptied.
Steps to reproduce
No idea. Please note that the logcat shows messages related to telephony right before and after the crash report. Maybe the issue is related to #3819 (closed) (my second SIM card is currently selected for mobile data; see #3819 (closed) to understand this comment)?
What is the current behavior?
See above.
What is the expected correct behavior?
Bliss should not crash; especially it shall not corrupt my artistic arrangement of icons ;-)
Technical informations
Relevant logs (adb logcat
)
12-12 15:29:05.793 3182 3182 I TelecomFramework: PstnPhoneCapabilitiesNotifier: handleVideoCapabilitesChanged. Video capability - false
12-12 15:29:05.793 3182 3182 I chatty : uid=1001(radio) com.android.phone identical 1 line
12-12 15:29:05.804 3182 3182 I TelecomFramework: PstnPhoneCapabilitiesNotifier: handleVideoCapabilitesChanged. Video capability - false
12-12 15:29:05.893 3182 3182 I TelecomFramework: PstnPhoneCapabilitiesNotifier: handleVideoCapabilitesChanged. Video capability - false
12-12 15:29:05.958 767 4937 I chatty : uid=1000(system) Binder:767_F expire 4 lines
12-12 15:29:05.997 231 2765 I vold : Trimmed 13542391808 bytes on /data in 15441ms
12-12 15:29:06.001 231 2765 D vold : Starting trim of /cache
12-12 15:29:06.116 231 2765 I vold : Trimmed 645054464 bytes on /cache in 115ms
12-12 15:29:06.117 231 2765 D vold : Starting trim of /persist
12-12 15:29:06.117 231 2765 I vold : Trimmed 0 bytes on /persist in 0ms
12-12 15:29:06.117 767 4912 I chatty : uid=1000(system) Binder:767_9 expire 7 lines
12-12 15:29:06.188 767 1660 I chatty : uid=1000(system) android.fg expire 4 lines
12-12 15:29:06.916 3182 3182 D MccTable: updateMccMncConfiguration mccmnc='26203
12-12 15:29:06.916 3182 3182 D MccTable: updateMccMncConfiguration: mcc=262, mnc=3
12-12 15:29:06.916 3182 3182 D MccTable: updateMccMncConfiguration updateConfig config={0.0 262mcc3mnc ?localeList ?layoutDir ?swdp ?wdp ?hdp ?density ?lsize ?long ?ldr ?wideColorGamut ?orien ?uimode ?night ?touch ?keyb/?/? ?nav/? winConfig={ mBounds=Rect(0, 0 - 0, 0) mAppBounds=null mWindowingMode=undefined mDisplayWindowingMode=undefined mActivityType=undefined mAlwaysOnTop=undefined mRotation=undefined}}
12-12 15:29:07.095 767 4931 I chatty : uid=1000(system) Binder:767_E expire 2 lines
--------- beginning of crash
12-12 15:29:07.243 4983 4983 E AndroidRuntime: FATAL EXCEPTION: main
12-12 15:29:07.243 4983 4983 E AndroidRuntime: Process: foundation.e.blisslauncher, PID: 4983
12-12 15:29:07.243 4983 4983 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{foundation.e.blisslauncher/foundation.e.blisslauncher.features.launcher.LauncherActivity}: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=foundation.e.blisslauncher/.features.notification.NotificationService }: app is in background uid UidRecord{a74ad4a u0a35 TPSL idle procs:1 seq(0,0,0)}
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3270)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3409)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=foundation.e.blisslauncher/.features.notification.NotificationService }: app is in background uid UidRecord{a74ad4a u0a35 TPSL idle procs:1 seq(0,0,0)}
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1616)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1571)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:669)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at foundation.e.blisslauncher.features.launcher.LauncherActivity.onCreate(LauncherActivity.java:314)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7824)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7813)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3245)
12-12 15:29:07.243 4983 4983 E AndroidRuntime: ... 11 more
12-12 15:29:07.258 767 4904 I chatty : uid=1000(system) Binder:767_8 expire 1 line
12-12 15:29:07.275 767 5447 I chatty : uid=1000 system_server expire 1 line
12-12 15:29:07.784 4961 5161 E ActivityThread: Failed to find provider info for android.media.tv
12-12 15:29:08.085 3182 3182 I TelecomFramework: : onSubscriptionsChanged - update accounts
12-12 15:29:08.085 3182 3182 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.android.internal.telephony.GsmCdmaPhone) {8d6ff11}
12-12 15:29:08.085 3182 3182 I TelecomFramework: PstnIncomingCallNotifier: Unregistering: Handler (com.android.internal.telephony.GsmCdmaPhone) {d67f876}
12-12 15:29:08.085 3182 3182 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Found 2 phones. Attempting to register.
12-12 15:29:08.086 3182 3182 I TelecomFramework: TelecomAccountRegistry: setupAccounts: Phone with subscription id 1
12-12 15:29:08.182 3182 3182 I TelecomFramework: AccountEntry: Registered phoneAccount: [[ ] PhoneAccount: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0} Capabilities: CallProvider MultiUser PlaceEmerg SimSub Audio Routes: BESW Schemes: tel voicemail Extras: Bundle[{android.telecom.extra.SUPPORTS_VIDEO_CALLING_FALLBACK=true, android.telecom.extra.SORT_ORDER=0}] GroupId: ***] with handle: ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}
12-12 15:29:08.182 3182 3182 I TelecomFramework: PstnIncomingCallNotifier: Registering: Handler (com.android.internal.telephony.GsmCdmaPhone) {8d6ff11}
Screenshot before the crash
Screenshot after the crash
Note the four dots (above the emptied "favorites") which indicate that there is one more page on the home screen due to the scattered icons.
Solutions
Workaround
Rearrange the icons manually; possibly after wiping the data of the Bliss app.
Possible fixes
No idea.