I recently got a new Pixel 3 (unlocked). KDE Connect always shows incoming calls as originating from "unknown number", even though the correct number shows up on the phone itself. Laptop: KF 5.52, Plasma 5.14.3, kdeconnect-1.3.3 Phone: Google Pixel 3 (Android 9), kdeconnect-1.10 STEPS TO REPRODUCE 1. Pair a Pixel 3 with kdeconnect. 2. Receive an incoming call. OBSERVED RESULT kdeconnect's popup on the desktop shows "Incoming call from [contact/number]" EXPECTED RESULT kdeconnect's popup on the desktop shows "Incoming call from unknown number" SOFTWARE/OS VERSIONS Linux: Kernel 4.19.0 KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION This worked as expected on my LG G2 (VS980) and Samsung Galaxy S III (SCH-I535).
Same situation on Xiaomi A2 Lite (Android 9). PC side tested on : - Solus GNOME 3.9999 with GSConnect 17 - KDE Neon 5.14.5 with KDE Connect 1.3.3 Android side tested with KDE Connect versions : - 1.10.1 - 1.7.1 - 1.6.6 Debug log of GSConnect reveal that none of above app version does not send contact name nor phone number in packet sent to PC, when there's incoming call : DEBUG: [core.js:receive/<:404]: xiaomi: { "id": 1547125458472, "type": "kdeconnect.telephony", "body": { "event": "ringing" } } while it should looks like : DEBUG: [core.js:receive/<:404]: Samsung SM-A310F: { "id": 1547126528778, "type": "kdeconnect.telephony", "body": { "contactName": "Test number", "phoneNumber": "555666777", "event": "ringing" } } Also for outgoing call there is no info about contact : DEBUG: [core.js:receive/<:404]: xiaomi: { "id": 1547126522752, "type": "kdeconnect.telephony", "body": { "event": "talking" } }
For reference, this was fixed here: https://invent.kde.org/kde/kdeconnect-android/commit/17e9892c80300e89ccd3dc2cd9f5a7450869a67b commit 17e9892c80300e89ccd3dc2cd9f5a7450869a67b Author: Nicolas Fella <nicolas.fella@gmx.de> Date: Thu Mar 21 23:13:27 2019 +0000 Fix showing callers number on Pie