Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Black screen bug when call is answered elsehwere #11768

Open
4 tasks done
SepticFuddy opened this issue Nov 15, 2021 · 4 comments
Open
4 tasks done

Black screen bug when call is answered elsehwere #11768

SepticFuddy opened this issue Nov 15, 2021 · 4 comments

Comments

@SepticFuddy
Copy link

SepticFuddy commented Nov 15, 2021

Bug description

When I answer an incoming call on desktop, my phone often gets stuck with the screen on until I turn it off manually. This of course needlessly drains battery. It has been happing for the past few releases at least.

Steps to reproduce

Receive a Signal call
Answer it on the Desktop client
Actual result: The incoming call screen lingers in a blank form, keeping the screen turned on indefinitely

Expected result: The incoming call screen should terminate itself and allow the screen to turn off

Screenshots

The outline for the contact avatar can still be seen on an otherwise black screen:
signal-2021-11-10-143352

Device info

Device: Unihertz Atom XL

Android version: unofficial LineageOS 17.1

Signal version: 5.25.8

App state

SMS enabled, Wi-Fi compatibility enabled, PIN locking disabled

Link to debug log

https://debuglogs.org/a823c680048c7e7746e3086d2bfbccd72c6cd94484c753bd2ce5433dea5cc5c0

@stale
Copy link

stale bot commented Jan 25, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Jan 25, 2022
@SepticFuddy
Copy link
Author

Still occurs on latest version. Unfortunately I have no further information to provide unless someone requests something from me.

@stale stale bot removed the wontfix label Jan 26, 2022
@stale
Copy link

stale bot commented Mar 27, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Mar 27, 2022
@SepticFuddy
Copy link
Author

Still relevant. No change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants