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

BUG: black screen during incomming calls #14

Closed
Moostek opened this issue May 10, 2023 · 4 comments
Closed

BUG: black screen during incomming calls #14

Moostek opened this issue May 10, 2023 · 4 comments

Comments

@Moostek
Copy link

Moostek commented May 10, 2023

Hello, since some time - since some update - happening to me that when I have the incomming call, the screen is black (it is active, so not completely switched off, but black). It does not occur pernamently, just sometimes, but it is definitely annoying. I have to push the phone's hardware button to activate the screen and many times I miss the volume button and I switch off the screen completely with the power button.

Can you examine this and fix it, please?

Thank you.

p.s.: LineageOS 16.0

@Goodwy
Copy link
Owner

Goodwy commented Jun 5, 2023

Can you send me a screenshot of a similar problem?

@Moostek
Copy link
Author

Moostek commented Jun 5, 2023

The problem is that this black screen during incomming call occurs irregulary, only sometimes. It will be hard to make a screenshot.

I will try to describe: Sometimes during incomming calls the phone/screen is woke up, but without incomming call options (i.e. without Right Dialer incomming screen). I can see only Status Bar icons and "active" black background, that's all. The only solution I found is to tap on the Power button to lock the screen and then tap on the Power button again, to wake it up. After this I can see the incomming call options.

And there is one more thing. I use the black skin, but the incomming call screen backround colour is grey. In one moment it turn from black to this grey background colour.

@Goodwy
Copy link
Owner

Goodwy commented Feb 17, 2024

Does this problem exist in the latest versions of 5.0.0+?

@Moostek
Copy link
Author

Moostek commented Feb 17, 2024

No, the problem did disappear. I do not face the issue with version 5.0.0+.

@Goodwy Goodwy closed this as completed Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants