Fix ensure incoming call screen wakes device #14316
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First time contributor checklist
Contributor checklist
Description
This PR fixes an issue where the incoming call screen was not displayed when the device screen was off on Android 15 (API 35). Although the ringtone, vibration, and notification were triggered correctly, the full-screen intent activity was not shown because the device screen remained off.
To resolve this, the setTurnScreenOn(true) flag was added to the incoming call activity. This ensures that the device wakes up and the call screen becomes visible even when the device is locked or the screen is off.
How I tested ?
I had multiple phones and tested them.
First, I downloaded the latest version of Signal on a phone and created a group. Then I locked the phone and turned off the screen. After that, I started a video call in that group. The screen of the Android 15 phone did not turn on; only the vibration and sound came through. The Android 14 phone vibrated, made a sound, and the screen turned on, and I saw webrtccallactivity. However, the same thing did not happen on the other phone. It used to happen before the operating system update, but it stopped happening after installing the Android 15 update.