[Android Head-Units] Scopesys:
The Notification issue does not cause a crash, it just hangs the UI when it is running.

Easy way to reproduce.

Setup:

Say, set Radio to give Freq Change Notification, and set for long time (say max)

Test: Tune radio with external means, ie steering wheel key.

You can change multiple times, and the Notifications will Buffer nicely, and each one will display in their own time, and even when displaying, you can tune radio to next freq (with Steering wheel button) and it will change instantly, and just add that notification to the buffer for display in sequence. PERFECT OPERATION :)

However, while the notifications are displaying, the Touch Screen UI is locked out.

If you had changed the radio Frequency with the Touchscreen, you would have to wait for the Animation to finish, before the HU would accept the next Touch.

Note: If you don't have Steering Wheel controls in your test setup, ( No problem) you can still see and verify that when you cause a Notification (or one occurs from some other event), the Touch Screen UI is locked out for the duration of the animation -- which is the issue.

Conclusions:

This is particularly troublesome, if you are using the Touch screen for a series of operations, and a Notification starts (ie Time, Mileage, new Song Title & Artist or whatever)

You find the Touchscreen goes DEAD on you till that Notification animation finishes running.

This would possibly suggest that the Notification animation is running in the main UI thread, and is blocking other UI functions, till it finishes running.

If so, putting Notifications and their animation, and Buffering, into their own thread, might be the a reasonable (and stable) solution.

Note: Having Notification Animations run for a longish time is a bid advantage, if driving, and have limited attention span to look at the display.

I really like the (long) Notifications, but currently they are causing a UI issue.

---------- Post added at 10:43 PM ---------- Previous post was at 10:19 PM ----------

Not had many, or a reproducible crash since I uninstalled FCC, clear cache, re-booted and loaded 072 version (My Currently running version)

However in setting up my screens again from scratch, a few times I had random issues when editing a Widget. On exiting the edit, some (not all) widget text size instantly changed to some large size, and for each one I had to go back and edit and set back to the original size.

Since it was on exit of the edit when this happened, (with my limited knowledge of the internals of FCC), I would suspect some type of SQL database corruption when it was being updated ?

That, and when restoring setting from a saved Google Drive backup, has often cause me to get random items inserted into the Screen, that cannot be selected, moved, edited or deleted, make be again suspect that the database is not that stable when being updated, by either a restore, or an exit from editing.

Fair enough, Backup & Restore may not be working 100% and have some issues that need addressing in the future, but editing a widget should not randomly cause just SOME other widgets on the screen to change their parameters (like Text Size)

Hope this is not TMI (Too much Info) but giving you a full report should hopefully make it easier to track down ..