You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
This isn't a feature request or a discussion topic
Bug description
I was on a voice call with another person using Signal on IOS. I had microphone and speaker on. In order to save battery and the screen, I turned off the screen using the power button (like you can with a normal Android voice call). Turning on the screen again showed that on the Android side the call had apparently ended. On the IOS side, the call was still there. Trying to call from Android to IOS Signal raised the call, but when picked up, there was no audio sent from Android to IOS Signal. Only after waiting for a little while was the microphone usable in the next call again.
Reproduce:
Have voice call with IOS Signal user
Press power button to turn off screen
IOS Signal user still saw the call being active
Turning on the Pixel screen showed no open call indicators anywhere
Guidelines
Bug description
I was on a voice call with another person using Signal on IOS. I had microphone and speaker on. In order to save battery and the screen, I turned off the screen using the power button (like you can with a normal Android voice call). Turning on the screen again showed that on the Android side the call had apparently ended. On the IOS side, the call was still there. Trying to call from Android to IOS Signal raised the call, but when picked up, there was no audio sent from Android to IOS Signal. Only after waiting for a little while was the microphone usable in the next call again.
Reproduce:
Screenshots
No response
Device
Pixel 9 Pro
Android version
15
Signal version
7.25.2
Link to debug log
https://debuglogs.org/android/7.25.2/e33b41ec3956d7115d6e8670809478cc73394f6da54348a88df1d4c8ff5c8249
The text was updated successfully, but these errors were encountered: