Environment:
Issue Description:
When opening the system "Text-to-speech output" settings page, the Settings app crashes.
While I have also reported this to the LineageOS team because their Settings app fails to handle the exception gracefully, the logcat clearly shows a DeadObjectException, which indicates that the TTS Engine process itself is crashing/dying when the system service queries it.
Logcat Analysis:
The system's WindowManager throws a DeadObjectException while trying to dispatch visibility to the TextToSpeechSettingsActivity. This means the Binder connection to the TTS Engine was lost because the engine process died during the initialization/query phase.
07-13 12:08:24.805 1995 3047 W WindowManager: Exception thrown during dispatchAppVisibility Window{f7f4f33 u0 com.android.settings/com.android.settings.Settings$TextToSpeechSettingsActivity EXITING}
07-13 12:08:24.805 1995 3047 W WindowManager: android.os.DeadObjectException
07-13 12:08:24.805 1995 3047 W WindowManager: at android.os.BinderProxy.transactNative(Native Method)
...
07-13 12:08:25.244 1995 2170 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{160523612 u0 com.android.settings/.Settings$TextToSpeechSettingsActivity t1146 f} isExiting}
Environment:
Issue Description:
When opening the system "Text-to-speech output" settings page, the Settings app crashes.
While I have also reported this to the LineageOS team because their Settings app fails to handle the exception gracefully, the logcat clearly shows a
DeadObjectException, which indicates that the TTS Engine process itself is crashing/dying when the system service queries it.Logcat Analysis:
The system's
WindowManagerthrows aDeadObjectExceptionwhile trying to dispatch visibility to theTextToSpeechSettingsActivity. This means the Binder connection to the TTS Engine was lost because the engine process died during the initialization/query phase.