I think due to sleeping features on my Android phone (and despite my best efforts to turn it off) I note that my Linux peer almost always claims that my Android phone is off / unreachable / unavailable. I assume this is because the TCP connection has been terminated and neither side bothered to re-establish a connection. For something that relies upon power-saving devices like mobile phones, I would think that the network architecture would leverage connectionless UDP communication, since no app can reasonably control the sleep settings of the mobile device anyway.
In order to work around this, I have to open up KDE Connect on the phone, and also open up the KDE Connect Settings on my Linux desktop, sometimes also hitting the refresh button. This makes many features of KDE Connect effectively useless, such as ringing the device to locate it.
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3
Kernel Version: 6.8.0-51-generic (64-bit)
Graphics Platform: offscreen
Processors: 32 × Intel® Core™ i9-14900K
Memory: 125.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2
kdeconnect.app: 1.0
this is just how it works… you have a fair point about the "locate my phone’ feature.
i mean if was logged into my phone, it would probably be in my hand.
Could this be a potential difference between the desktop client version (old, from 2021 or early 2022 depending on the sources used) and the phone app (likley very current, most recent is 1.32.10)?
While 22.04 does have Plasma 5.27 available via PPA, that does not include applications and other KDE bits, or not many of them.
This usually isn’t an issue but the difference IS pushing a three year gap now, so is worth a look.
for what its worth, the behavior is the same with kde connect 24.05
if the phone is sleeping, then kde connect cant find it or send anything to it.
if the screen is on but you haven’t opened it yet, then you can use find it… but that’s like a 3s window with the phone in your hand.
I don’t know.
I don’t have this issue, or have never noticed it.
My phone has been sitting here idle/locked/ for about 2 hours now and have no issues using the ring feature, sending or browsing files, and even sending texts apparently.
I do note that I have the app set to allow background usage in the battery section on the app’s info page. I have no recollection if I set this myself (by a prompt from the app?) , but I must have done so. It isn’t something I would have done on my own other than to fix an issue. I really don’t remember either way.
Android 15 on a Pixel 7
I’m using this to get around it by constantly * pinging the desktop from the phone:
* - “constantly” meaning one ping every 10 seconds or something. Just enough that the phone doesn’t put the wifi to sleep.
Mine has that setting off, but Connect still works fine. I only usually have to open it once in the morning, when I’ve just turned the PC on, for it to connect, and then it stays there all day. Or after I’ve returned home, sometimes.
can confirm that if the PC wakes up from suspend to RAM, all paired devices are “unreachable” again, and no options are available… phone only appears as available once the screen is on
sending a ping or the clipboard works even without changing the battery setting from the default (optimized), but it will not send files tho…
for that, the screen at least needs to be on but the phone does not need to be unlocked.
so here is the trick:
use remote input and tap the center mouse button to turn on the screen
while the screen is on you can send files or use the find my phone feature.
the real hindrance here is the fact that kde connect does not reestablish connection with paired devices when waking up from suspend, and so renders the find your phone feature useless (this even occurs with phone battery setting to Allow background).
1 Like
