| Summary: | KDE connect does not discover PC and Android (each other) if the connection is Mobile Hotspot Tethering started from Android and Windows laptop connected to it. | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | darkphoenix534 |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | cwo.kde, roxov65293, testing1237a-c |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Android | ||
| OS: | Android 11.x | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=468434 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
darkphoenix534
2022-03-05 06:13:25 UTC
i can confirm this happening on my system as well over mobile hotspot. kde connect refuses to open occasionally and then works all of a sudden Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 i found something. i i manually add the IP of the laptop as trusted that i get in its wifi from the phone hotpspot (192.168.121.215 in my case), kde connect immediately worked flawlessly. i suspect there is a problem in the ip address recognition/dhcp whatever that kde connect gets confused. note: i turned on mobile hotspot, connect my laptop and wrote down its ip address. on the phone, kde connect app, i manually added the same ip as trusted and then it worked, (In reply to johnathan from comment #2) > i found something. i i manually add the IP of the laptop as trusted that i > get in its wifi from the phone hotpspot (192.168.121.215 in my case), kde > connect immediately worked flawlessly. > > i suspect there is a problem in the ip address recognition/dhcp whatever > that kde connect gets confused. > > note: i turned on mobile hotspot, connect my laptop and wrote down its ip > address. on the phone, kde connect app, i manually added the same ip as > trusted and then it worked, yes it works. but i am on a custom rom and in custom rom with each new session of Hotspot. The IP address gets changed, so its not feasible to keep adding ip address in kde app. (In reply to darkphoenix534 from comment #3) > (In reply to johnathan from comment #2) > > i found something. i i manually add the IP of the laptop as trusted that i > > get in its wifi from the phone hotpspot (192.168.121.215 in my case), kde > > connect immediately worked flawlessly. > > > > i suspect there is a problem in the ip address recognition/dhcp whatever > > that kde connect gets confused. > > > > note: i turned on mobile hotspot, connect my laptop and wrote down its ip > > address. on the phone, kde connect app, i manually added the same ip as > > trusted and then it worked, > > yes it works. but i am on a custom rom and in custom rom with each new > session of Hotspot. The IP address gets changed, so its not feasible to keep > adding ip address in kde app. oh yes. since i added the last comment, i saw the same problem happening again. turns out my stock android 11 motorola does the same. it had changed the IP address of the laptop to 192.168.166.215 and hence it was failing. i changed that to updated ip in kde connect and now its working again but i agree, this is a terrible workaround because dynamic ip is the norm and we should expect kde connect to understand that, dunno why its happening KDE Connect on Android states that since I'm not connected to a Wi-Fi network, I will not see available devices. I wish it would check for available devices when wireless hotspot is turned on. Turning on static IP is not an option on newer Android versions. I hope this will get fixed because the workaround is very time consuming. Thank you for the bug report! This issue has already been filed; please follow the linked bug report for updates on a fix. *** This bug has been marked as a duplicate of bug 421186 *** |