https://bugs.kde.org/show_bug.cgi?id=470085
--- Comment #3 from Axel <thas5egh2chae...@pm.me> ---
That's a different but maybe not completely separate issue. Both my computer
and the phone have only one link to the local network. If my phone does
connect, only one TCP connection is established.
Your comment got me to look at this closer again, and I might have been misled
by the Background execution not allowed message. I still get that message, but
a few seconds later I also get onNetworkChange from the KDE Connect service:
08-14 16:48:00.436 965 1031 W BroadcastQueue: Background execution not
allowed: receiving Intent { act=android.net.wifi.WIFI_STATE_CHANGED
flg=0x4000010 (has extras) } to
org.kde.kdeconnect_tp/org.kde.kdeconnect.KdeConnectBroadcastReceiver
[...]
08-14 16:48:05.194 30572 30623 D KDE/BackgroundService: onNetworkChange
I checked with Wireshark and my computer does not receive any broadcasts from
the phone (it does if I restart the KDE Connect service on the phone).
There are no later log messages from the KDE Connect app.
I don't see anywhere in LanLinkProvider.sendUdpIdentityPacket(List<InetAddress>
ipList) that the socket for broadcasting the identity packet is bound to an
interface resp. address.
If I interpret Android's logs correctly at the time onNetworkChange is called
the wifi network is not yet the default, a few hundred ms later I see messages
like these:
08-14 16:48:05.416 965 1248 D SemHotspotMobileDataLimit: Default network
changed to : 507
[...]
08-14 16:48:05.425 965 1213 D ConnectivityService: Sending DISCONNECTED
broadcast for type 0 [502 CELLULAR] isDefaultNetwork=true
[...]
08-14 16:48:05.427 965 1213 D ConnectivityService: Sending CONNECTED
broadcast for type 1 [507 WIFI] isDefaultNetwork=true
I guess the broadcast gets send over the wrong link, cellular instead of wifi.
I'll try if I can validate if this is the cause for this issue.
--
You are receiving this mail because:
You are watching all bug changes.
