https://bugs.kde.org/show_bug.cgi?id=527012
Bug ID: 527012
Summary: Android mDNS discovery holds an app-level multicast
lock for its entire lifetime
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Android
OS: Android 16.x
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
I tested KDE Connect Android 1.35.17 on a OnePlus 13 running Android 16 and
OxygenOS 16.0.10.600.
In a local debug build, I removed only the explicit WifiManager.MulticastLock
creation, acquisition and release from MdnsDiscovery.kt. I left NsdManager
discovery and registration, UDP discovery and TCP connections unchanged.
Normal paired-device use has continued to work. The patched app no longer holds
KDE's multicast lock, and the phone can restore APF multicast filtering when no
other app requires multicast reception.
I have not established a measurable battery saving. Other background activity
and test conditions changed between measurements. I also have not separately
verified discovery of new peers while filtering is active, or compatibility
with other Android versions and OEMs.
Is this additional app-owned lock required for NsdManager discovery on all
supported devices? If it is only needed in some cases, could KDE avoid holding
it continuously where unnecessary?
I can provide the small patch and redacted lock/filter diagnostics.
--
You are receiving this mail because:
You are watching all bug changes.
