https://bugs.kde.org/show_bug.cgi?id=471313
--- Comment #4 from Andy3153 <andy3...@protonmail.com> --- (In reply to Pedro V from comment #3) > I'm guessing that in both cases the issue is with broadcasting though, just > not sure how would that happen in the hotspot case with just one interface. > Maybe there are multiple interfaces in that case too even if they are not > connected to the same network, or there are interfaces not considered by the > users as they may not belong to physical connections. It clearly is an issue about broadcasting, and possibly just an issue about looking farther than the first network interface the computer connected to. As I said in the additional info part of my bug report, the problem is fixed if I disconnect the Ethernet, connect to the routerx then restsrt kdeconnectd. > Look at the findings I described in bug 470085 , you might have the same > issue, and it's actually not hard to check, it's not even necessary to > disconnect anything, the "Refresh" menu point on the phone side triggers > discovery, so you can either: > - Just spam and see if you can see a connection on either side for a > fraction of second > - Check the phone with logcat which is likely most feasible to use through > adb > - Check the PC by (optionally?) killing kdeconnectd and running: > QT_LOGGING_RULES="*.debug=true; qt.*.debug=false" > /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd --replace > > I'm suspecting all these issues to be related even if the hotspot one is not > clear, but even there the remarks of adding by IP address suggests that > skipping the broadcast discovery phase is what fixes the issue. I'll try these when I get back home to my laptop, but, until then, could you point me to some documentation about android logcats? I have minimal ADB experience, none of which was related to logging/debugging android apps -- You are receiving this mail because: You are watching all bug changes.
