Bug 472234 - Long delay in sending a notification to desktop when receiving a phone call
Summary: Long delay in sending a notification to desktop when receiving a phone call
Status: RESOLVED DUPLICATE of bug 464432
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (other bugs)
Version First Reported In: 23.04.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-13 23:02 UTC by andk
Modified: 2026-02-07 13:05 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andk 2023-07-13 23:02:20 UTC
SUMMARY
KDE-Connect works generally fine, except when I receive a phone call. In that case, the notification appears after 30/60 seconds. Therefore it fails to automatically stop the media player like it should and I have to do it manually.

STEPS TO REPRODUCE
1. Connect computer and phone using KDE-Connect
2. Play some music or videos
3. Receive a phone call

OBSERVED RESULT
The phone rings but the computer seems to not being aware of it, so the music/video doesn't automatically stop. During the phone call, after a bit, the notification appears, but if I wait for it I'll definitely miss the call.

EXPECTED RESULT
The notification of the call should appear immediately when the phone is ringing, and it should automatically stop the media player.

SOFTWARE/OS VERSIONS
Linux: 6.4.3-arch1-1 (64-bit)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
I'm using Mullvad VPN if it matters, but as I said KDE-Connect works fine except for this issue, so I don't think this is related to the problem.
On Android, I already disabled the battery optimizations.
Comment 1 Unknown 2025-11-18 09:34:42 UTC
** Removed at reporter request **
Comment 2 aristsakas 2026-02-07 13:05:54 UTC

*** This bug has been marked as a duplicate of bug 464432 ***