Summary: | Not all devices were found | ||
---|---|---|---|
Product: | [Applications] kdeconnect | Reporter: | Quadrant1737 <sp657yjetjp> |
Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andrew.g.r.holmes, devel2020 |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Android | ||
OS: | Android 14.x | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Quadrant1737
2025-03-19 13:53:39 UTC
Confirmed here. this issue is still or again present in v1.33.2 of the Android app, although some reported this to be fixed in 1.33.1. Between v1.32 and the current v1.33.2 of the Android app there seems to be a new bug (or by intention?) introduced, Android devices (tested/verified with 5 devices Huawei,Xiaomi,Samsung), can't discover/connect each other anymore, regardless if successfully paired before or not. Completely bypassing/disabling Blockada and AFWall+ doesn't have an effect on this either. Interestingly the desktop app (in KDE, Kubuntu 22.04 and 24.04 and 25.04) is still able to connect and even see the filesystems and battery status and so on (likely all modules) from all Android devices and from Android the modules for remote input work as well. So "just" the Androids (10-14) don't see each other anymore, which is weird. I often used that for sharing the clipboard between mobile and pad :-/ Most of the times i use access to the Android's filesystem from the Laptop or Desktop, which still works, so to me it currently is not a major issue, but i think others may see a large impact to functionality. "component" should be changed to "android-application" as the desktop components (at least on Linux/Kubuntu) are not affected and can communicate between each other. Sounds like the same symptoms in the android app as in https://bugs.kde.org/show_bug.cgi?id=501635 *** This bug has been marked as a duplicate of bug 501635 *** |