It's not a fault though. User can choose to resume, rinseback or end tx but will the alarm just trigger again immediately if you haven't resolved the h/w problem? With the 2 properties set to TRUE, user can choose to rinseback or end tx and they will not be bothered by this alarm again until rinseback and post-tx are completed.
Bruce as we had discussed, please investigate if we forking the CAN, BT, WiFI, Touchscreen helps from a startup time, i.e. the individual process could wait for a certain state to happen or you could reorder the startup sequence.
