element-hq / element-hq/element-call

Eager ringing

Open
#3,848 1 comment 0 reactions 0 assignees View on GitHub
A-Matrix2.0 T-Enhancement
Dominant language
TypeScript
Stars
996
Forks
213
Avg merge
1d 8h
Merged PRs (30d)
55

Description

### Your use case

User [observation](https://matrix.to/#/!NOGZYBedfuPsideoi2PSA_ouduzbb2mKrhu3fbUIeWk/$Hl8cH0479axQInl7wrR0GgyrkkruempA9KO6m3V_r9w?via=matrix.org&via=tchncs.de&via=unredacted.org)

> At least on my own device, I've checked all the configurations, including battery, background processes, notifications, and lock screen. I even converted ntfy and EXA to system apps to prevent the app from being killed by the system (my device has root access, so I can do this), but the effect was minimal (the delayed incoming call UI issue persists). In other words, I've tried everything I could (except for drastic adjustments to the Doze policy). Text notifications are relatively timely (the screen lights up within seconds), but the delayed call notification issue remains.

Comment:

> Before we can can show a call we need some additional data (if the call is still ongoing most importantly. If everyone has left already we do not want to ring)
> This is a tradeoff:
>
> - ring and potentially stop ringing 3s after (once we know there is no ongoing call)
> - dont ring until we know for sure the ringing is appropriate **THIS** is what we have today

### Have you considered any alternatives?

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.