https://bugs.kde.org/show_bug.cgi?id=461083
--- Comment #4 from qsabip...@mozmail.com --- (In reply to Michael from comment #3) > (In reply to qsabipb02 from comment #2) > > (In reply to Michael from comment #1) > > > have you tried, on your phone, setting the screen not to sleep when USB > > > connection is active? > > > or any other phone configuration which might shutting down the usb port > > > for > > > any reason > > > > > > when the phone is not set to stay active or just dimmed happens what you > > > apparently are saying, there is eventually a charging battery setting for > > > holding the screen dimmed while charging, that can also help > > > > > > if there's is no setting, activate developer mode where you can find then > > > more usb related settings > > > > I've found some configurations there, but I don't think they'll help much, > > because KDE Connect uses LAN, rather than USB, to connect to PCs. Maybe it's > > a problem in some network scan module? like, the app can't find the phone > > straight away because it doesn't rescan the LAN or something. > > > > If it were a problem with the phone config, it would keep getting > > disconnected every time the phone screen sleeps or dims, but it only happens > > after my PC wakes up or powers on. It has never happened back on Gnome when > > I used GSConnect, so I am pretty sure it's a problem somewhere in KDE > > Connect, don't you agree? > > so your phone is connected via LAN (Eth)? > read again what you wrote: " I have to turn the phone screen on and unlock > it to get availability back" > I also think that Kde Connect is to connect a phone to the computer, not for > PC-PC No, it is connected via Wi-Fi as usual. By LAN I meant my home's network. I would like to update that issue by saying that unlocking the phone is not necessary, as only turning the screen on is enough for KDE Connect on my PC to connect to its app on my phone. I read it and I know it, but it's still inconvenient, considering that the connection to the phone should be easily restored after the PC wakes up or powers on. Yes, that's its purpose, it doesn't support PC to PC connection. But that doesn't matter, because I have only one PC at home, which is the desktop I am using now to write this. I think you got confused with the "LAN" (or "eth") part; no, I'm not using it on a laptop. It's on my Android. Is there any fix or plan to fix that connection issue? -- You are receiving this mail because: You are watching all bug changes.
