Bug 382365 - kdeconnect does not connect automatically
Summary: kdeconnect does not connect automatically
Status: CONFIRMED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-15 07:50 UTC by Philippe ROUBACH
Modified: 2023-11-26 13:14 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2017-07-15 07:50:08 UTC
opensuse leap 42.2
linux kdeconnect 1.0.3
android kdeconnect 1.6.5

Samsung s2 plus android 7.1.2
Samsung s7 android 7.0

android kdeconnect is not battery optimized.

my smartphone is permanently in its dock station thus never stops.

in the evening i stop my pc
in the morning i start my pc
i open a kde session
then
kdeconnect is not in the systray
in kdeconnect settings my smartphone is not green
if i refresh then my smartphone stays gray
if i take in hands my smartphone
then
kdeconnect is in the systray
Comment 1 Philippe ROUBACH 2017-12-25 07:05:34 UTC
android kdeconnect is battery optimized => same problem
Comment 2 Philippe ROUBACH 2017-12-27 16:26:37 UTC
kde apps 17.12
kde framework 5.41
plasma 5.11.4

i did this experiment:

i  disable disconnect pc from network by unplugging the ethernet cable
then
kdeconnect icon disappears from systray
then
i connect pc to network by plugging the ethernet cable
then
kdeconnect icon does not appear in systray

i assume the device discovering feature of keconnect is not launched after lan reconnecting or get a bug.

also manual "refresh" does not work.
Comment 3 Philippe ROUBACH 2019-03-09 09:38:46 UTC
kde app 18.12.2
kde plasma 5.15.2
kde framework 5.55.0
qt 5.12.1

kde kdeconnect 1.3.3
android kdeconnect 1.10.1
Comment 4 Philippe ROUBACH 2019-03-13 09:17:08 UTC
android kdeconnect 1.11

problem still there.
Comment 5 Philippe ROUBACH 2019-03-14 09:30:49 UTC
android 8.0 (samsung s7) + kdeconnect 1.11
lineage 14.1 (android 7.1.1) (samsung s2 plus) + kdeconnect 1.10.1
opensuse 15.1 + kdeconnect 1.3.3

no problem with lineageos 14.1

problem still there with android 8.0: samsung problem ? android 8.0 problem ? saving energy feature problem ?
Comment 6 Philippe ROUBACH 2019-03-14 09:51:57 UTC
it is true also (see my comment #5) with opensuse 15.0 + kdeconnect 1.3.3 with:

kde app 18.12.3
kde plasma 5.15.3
kde framework 5.55.0
qt 5.12.1
Comment 7 Philippe ROUBACH 2019-03-26 14:23:16 UTC
android kdeconnect 1.12.6

problem still there.
Comment 8 Philippe ROUBACH 2019-03-26 17:14:37 UTC
another case:

i switch to another user
then
i come Bach to the previous user
then
kdeconnect-ke disappeared. it is no more in the systray.

i must take in my hand smartphone then kdeconnect-kde appears again in the systray.
Comment 9 Philippe ROUBACH 2019-03-28 10:16:04 UTC
kdeconnect-kde 1.3.4
kdeconnect-android 1.12.6

- Samsung S2 Plus, lineageos 14.1 (android 7.1.1)
 when opening a kde session then kdeconnect-kde connects to S2

- Samsung S7 (android 8.0)
 when opening a kde session then kdeconnect-kde does  not connect to S7

i must take in my hand the S7 according to connect S7 and PC
Comment 10 Pivert 2019-12-25 20:43:02 UTC
Same problem on Android 9, one OnePlus. This Kdeconnect stops working some minutes after the phone locks... I removed any battery optimisation for the app, but this does not help.
Comment 11 Philippe ROUBACH 2019-12-27 13:54:53 UTC
A complement for :
- does not connect during kde session opening
- does not stay connected

In PC, I use "Messages.web.com" to send and receive SMS's.
With Chrome, we can install this site as an application in PC
We can pair this application to the Google android application "Messages".
The application in PC uses via Wi-Fi the application in Android to send/receive SMS's.

Even if smartphone is in sleep mode "Messages" in PC stays connected. Then it is not a smartphone problem: Android version or model.

I assume kde kdeconnect does not use the good way to connect and to stay connected.
Comment 12 kde 2020-11-15 09:53:13 UTC
KDE Connect used to auto connect, but it doesn't auto connect anymore. 

My desktop runs 24/7. In the past when as soon as I connect to wifi on the phone I will get a notification on desktop from KDE Connect to say my phone has connected.

But now, for the past maybe 18-24 months, it has stopped doing that. Now every time I want it to connect to the phone I have to go into KDE Connect Settings. Once in the settings then:

- sometimes the phone will "magically" be shown as connected and then I can just click "Close"
- sometimes I have to use the "Refresh" button (maybe more than once) before the phone will be shown as connected and then I can click "Close"

On the phone, battery optimisation etc is disabled for KDE Connect. This is confirmed by the fact when phone is on standby I still get notifications going both ways Desktop <-> Phone. Both ways, because eg if I pause a media player on desktop, it sends a notification to the phone, phone displays notification and same notification also pops up on desktop.

One thing I have noticed is that for KDE Connect to make the initial connection to the phone, the phone has to be out of standby - it doesn't have to be unlocked, eg if phone is in "enter PIN" screen, I can go to KDE Connect Settings to connect to it. Once connected phone can be in standby and notifications etc will continue to work normally.
Comment 13 Juha Tuomala 2023-04-27 06:55:09 UTC
Same with iPhone, I think there is also a problem that phone-app doesn't start itself automatically.
Comment 14 Puspam Adak 2023-11-26 13:14:19 UTC
The problem is still there in version 23.08.3.
If my device is connected to the PC during login, then KDE connect is refreshed and it gets connected. If I disconnect & reconnect my phone (by disconnecting WiFi), then it does not get connected automatically. Then I need to manually invoke the command "kdeconnect-cli --refresh" in order to connect.
I think this problem can be fixed by continuously monitoring the connection status and refreshing the devices after specific intervals.