Bug 465582

Summary:	Kde Connect doen't reconnect
Product:	[Applications] kdeconnect	Reporter:	Michael <michael.hmich>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	REPORTED ---
Severity:	normal	CC:	andrew.g.r.holmes, kde-bugs
Priority:	NOR
Version First Reported In:	22.12.2
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	device selection - not connected

Description Michael 2023-02-11 12:14:36 UTC

on system start, after logging in, Kde Connect works properly, notifications appear, everything ok

Connection is USB, devices are paired 

after reconnecting a device before disconnected it is not reconnecting
Network Manager is re-connecting immediately the USB Tethering connection
to reconnect KDE Connect it is necessary  to open KDE Connect Settings, manually select the paired device, wait some seconds and then it works normally
it doesn't matter if there is just one or more devices in the paired device list
the computer nor the phone were hybernated 

I can not say how long that is now, but some Neon upgrades before it was working fine

Comment 1 Michael 2023-03-15 12:27:41 UTC

still not working v22.12.3

Comment 2 Albert Vaca Cintora 2023-03-23 17:52:17 UTC

Reconnection on Android 9+ should be much better since https://invent.kde.org/network/kdeconnect-android/-/commit/fd34e56675dd7e982e22abb051400804ab5ede67 

Please reopen if it isn't.

Comment 3 Michael 2023-04-13 09:03:36 UTC

Created attachment 158064 [details]
device selection - not connected

hi, reconnect is not working

I'm on Android 11, but believe the problem is not with the phone, pairing is ok and kde network manager is reestablishing the network tethering immediately 

it just connect by itself once, when logging into plasma, but then disconnecting the usb cable and reconnecting it, kde connect says "no device selected", I need to click on the configured connection and then it connects, if my description is bad please look at the screen print

Comment 4 Michael 2023-05-31 12:50:47 UTC

well, seems nobody has interest in solving this, I can understand that there are not much people using it, but since kdeconnect is there it should work, agree?

in fact, it doesn't seem to have a reconnect routine and that should be corrected

a cmd line like "/usr/bin/kdeconnect-cli -n Moto E7 --refresh" does it, but for some reason I can not automate it, I believe that is so because udev runs as root and the command needs to be run as the user 

inside the script to be run from udev_rule  (as root) this command should, but is not working
su hm -c  '/usr/bin/kdeconnect-cli "-n Moto E7 --refresh"'
the options are interpreted as two, or as a diretcory depends on how I set the quotes

that's in my udev_rules file
KERNEL=="rndis_host", ACTION=="add", ENV{ID_SERIAL}=="0e8d:2005", RUN+="/usr/sbin/kdeconnect.sh"

the kernel event in my case:

rndis_host 1-2:1.0 usb0: register 'rndis_host' at usb-0000:00:12.2-2, RNDIS device, 5a:c0:6b:31:9a:5c
rndis_host 1-2:1.0 enx5ac06b319a5c: renamed from usb0

the kdeconnect reconnect should run after the renaming of usb0, the device ID "enx*' is random

if somebody here has a better idea or knows how to make it work from udev, it would be nice

thanks