In the spirit of wag
in the stack I see the following in threads:
usc::MirScreen::set_screen_power_mode(MirPowerMode, PowerStateChangeReason) () usc::MirScreen::keep_display_on_temporarily() usc::MirScreen::dimmer_alarm_notification()
is it possible a couple of these threads deadlock due to an unlucky timing of events, like the screen dimming as an sms comes in
In the spirit of wag
in the stack I see the following in threads:
usc::MirScreen: :set_screen_ power_mode( MirPowerMode, PowerStateChang eReason) () :keep_display_ on_temporarily( ) :dimmer_ alarm_notificat ion()
usc::MirScreen:
usc::MirScreen:
is it possible a couple of these threads deadlock due to an unlucky timing of events, like the screen dimming as an sms comes in