[Android Head-Units] okij:
@SpeedFire- One week after my last report, FCC became unresponsive again (this time on the latest test69) and the system prompted me "FCC Launcher not responding, do you want to close it Y/N", which I eventually did after driving for half an hour. During this time I didn't close FCC yet to see if it settles again, which it didn't. When e.g. swiping up and down the screen, it always took about a minute until FCC reacted and showed the next home screen. The Minimap also reacted only with a delay of about a minute when touching or swiping it. The Player widget didn't show any song updates and was unresponsive too. Eventually the situation became even worse, because for the last 5 or 10 minutes before restarting FCC, the home screen didn't show anything (like widgets) at all and also didn't react at all.

I attached a Logcat for you again and hope that you can find something this time.

Until 09:19 this morning, when I parked my car, FCC Launcher was perfectly working. After waking the head unit again at 10:46, FCC Launcher didn't react anymore. At 11:20 I eventually agreed to restart FCC launcher by pressing "Y" on the prompt, after which I had to choose FCC as home launcher again.

Also Tasker reported an error as notification ("can't deliver broadcast"), which might be related or just a coincidence, because this didn't happen last week when I had the same issue with FCC Launcher. Anyway, I also attached the report which has been auto-generated by Tasker and which I filed with some additional information, so I might send it to the developer of Tasker. Please have a look at it too.

Maybe the relation between the simultaneous FCC and the Tasker problems is that they both have to do with broadcasts and notification service!? Here are some related snippets of my Logcat:

09-22 10:50:08.980 2172 2172 E AndroidRuntime: FATAL EXCEPTION: main

09-22 10:50:08.980 2172 2172 E AndroidRuntime: Process: net.dinglisch.android.taskerm, PID: 2172

09-22 10:50:08.980 2172 2172 E AndroidRuntime: android.app.RemoteServiceException: can't deliver broadcast

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1745)

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6718)

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)

09-22 10:50:08.980 2172 2172 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

...

09-22 10:57:27.803 465 1940 W ActivityManager: Scheduling restart of crashed service net.dinglisch.android.taskerm/.MonitorService in 1206ms

09-22 10:57:53.940 465 483 W ActivityManager: Timeout executing service: ServiceRecord{32f6974 u0 ru.speedfire.flycontrolcenter/.AchievementNotificationService}

09-22 10:58:02.825 465 483 E ActivityManager: ANR in ru.speedfire.flycontrolcenter

09-22 10:58:02.825 465 483 E ActivityManager: PID: 1465

09-22 10:58:02.825 465 483 E ActivityManager: Reason: executing service ru.speedfire.flycontrolcenter/.AchievementNotificationService

09-22 10:58:02.825 465 483 E ActivityManager: Load: 7.93 / 8.09 / 8.44

09-22 10:58:02.825 465 483 E ActivityManager: CPU usage from 0ms to 8845ms later (2021-09-22 10:57:53.941 to 2021-09-22 10:58:02.785):

...

09-22 11:05:29.643 465 483 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{432c9d1 u0 com.android.music.metachanged} to ReceiverList{87a7505 16450 net.dinglisch.android.taskerm/10139/u0 remote:4d0687c}: process gone or crashing

09-22 11:05:31.005 465 483 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{8c9320d u0 com.android.music.metachanged} to ReceiverList{87a7505 16450 net.dinglisch.android.taskerm/10139/u0 remote:4d0687c}: process gone or crashing

09-22 11:05:32.628 465 483 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{7ff362f u0 com.android.music.metachanged} to ReceiverList{87a7505 16450 net.dinglisch.android.taskerm/10139/u0 remote:4d0687c}: process gone or crashing

...

09-22 11:20:08.020 465 484 W ActivityManager: Force finishing activity ru.speedfire.flycontrolcenter/com.android.fcclauncher.FccAlias

09-22 11:20:08.032 465 484 I ActivityManager: Killing 1465:ru.speedfire.flycontrolcenter/u0a115 (adj 0): user request after error

09-22 11:20:08.293 465 465 V NotificationListeners: notification listener connection lost: ComponentInfo{ru.speedfire.flycontrolcenter/ru.speedfire.flycontrolcenter.notifications.NotificationListenerLoli}

09-22 11:20:08.293 465 826 D NotificationListeners: Removing active service ComponentInfo{ru.speedfire.flycontrolcenter/ru.speedfire.flycontrolcenter.notifications.NotificationListenerLoli}

09-22 11:20:08.293 465 555 I WindowManager: WIN DEATH: Window{5df5391 u0 ru.speedfire.flycontrolcenter/com.android.fcclauncher.FccAlias}

09-22 11:20:08.311 465 476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.assistant_volume.FccAccessibilityService in 1000ms

09-22 11:20:08.311 465 476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.notifications.NotificationListenerLoli in 11000ms

09-22 11:20:08.311 465 476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.AchievementNotificationService in 21000ms

09-22 11:20:08.311 465 476 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.FCC_Service in 30999ms

I also had a look at the Locat that @tonimontoia posted here today. Here are some of his crashes, interestingly also several related to broadcasts and notification service:

09-21 15:01:57.170 642 8517 W ActivityManager: Scheduling restart of crashed service com.mgoogle.android.gms/com.google.android.gms.cast.media.CastMediaRouteProviderService in 1000ms

...

09-21 15:01:57.173 642 8517 W ActivityManager: Scheduling restart of crashed service com.mgoogle.android.gms/org.microg.gms.gcm.McsService in 938568ms

...

09-21 15:01:57.314 642 8517 W ActivityManager: Scheduling restart of crashed service org.telegram.plus/org.telegram.messenger.NotificationsService in 1000ms

...

09-21 15:01:57.400 642 8517 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService in 1000ms

...

09-21 15:01:57.694 642 8517 W ActivityManager: Scheduling restart of crashed service com.spotify.music/com.spotify.mobile.android.service.SpotifyService in 1000ms

...

09-21 15:01:57.862 642 8517 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.notifications.NotificationListenerLoli in 1000ms

...

09-22 09:43:17.422 642 6534 I WindowManager: WIN DEATH: Window{be68033 u0 ru.speedfire.flycontrolcenter/com.android.fcclauncher.Launcher}

09-22 09:43:17.469 642 6798 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.FCC_Service in 1780ms

09-22 09:43:17.470 642 6798 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.notifications.NotificationListenerLoli in 11780ms

09-22 09:43:17.470 642 6798 W ActivityManager: Scheduling restart of crashed service ru.speedfire.flycontrolcenter/.assistant_volume.FccAccessibilityService in 21779ms

I really hope that you can make sense of the Logcats and fix the FCC not responding / crashing issue, because currently this is a real problem and the reworked FCC should not be released until this is fixed.

Please let me know what you think and if we can provide any more infos.