spieglt
Transfer between Windows and Android failed.
I tried to transfer files between Windows and Android devices, but it always failed. I tried:
- Replacing the Android device (Samsung Tab S9FE and Xiaomi 13).
- Enabling or disabling Bluetooth assistance.
After testing, file transfers between the above two Android devices were always successful.
After looking up some information, I noticed that using the command netsh wlan show drivers in Windows will return
...
Hosted network supported : No
...
Furthermore, my network card (Intel AX211) no longer supports Hosted Network and Ad-Hoc modes (source questionable). Is this the cause of the problem?
Attaching logs, first using Bluetooth and second not using.
Welcome to Flying Carpet!
Once other options are selected, drag and drop can be used to send a folder.
Bluetooth is supported.
Advertising Bluetooth service...
Started advertising Bluetooth service
Peer's OS is android
Peer read our SSID
Peer read our password
Firewall rule already in place.
Hosted network flyingCarpet_fe4d has started
Waiting for connection...
Transfer cancelled
Start the transfer on the other device and scan the QR code when prompted.
Firewall rule already in place.
Hosted network flyingCarpet_e6c0 has started
Waiting for connection...
Transfer cancelled
Finally, I would like to thank the author. If this program is available, it will be the best transfer software I have been searching for.
Hi, yes, unfortunately the lack of hosted network support means it won't work. When Android and Windows are used, the Windows device hosts the hotspot. I've considered making this able to be overridden, but it would make the UI confusing. Thank you for the kind words!
Something was wrong. In another Windows computer, transfer to Android is completely successful. And It also does not support Hosted network.
> netsh wlan show drivers
接口名称: WLAN
驱动程序 : Realtek 8822CE Wireless LAN 802.11ac PCI-E NIC
供应商 : Realtek Semiconductor Corp.
提供程序 : Realtek Semiconductor Corp.
日期 : 2020/12/25
版本 : 2024.0.9.230
INF 文件 : oem20.inf
类型 : 本机 WLAN 驱动程序
支持的无线电类型 : 802.11n 802.11g 802.11b 802.11ac 802.11n 802.11a
支持 FIPS 140-2 模式: 是
支持 802.11w 管理帧保护 : 是
支持的承载网络 : 否
基础结构模式中支持的身份验证和密码:
开放式 无
WPA2 - 个人 CCMP
开放式 WEP-40bit
开放式 WEP-104 位
开放式 WEP
WPA - 企业 TKIP
WPA - 个人 TKIP
WPA2 - 企业 TKIP
WPA2 - 个人 TKIP
WPA - 企业 CCMP
WPA - 个人 CCMP
WPA2 - 企业 CCMP
WPA3 - 个人 CCMP
供应商定义的 TKIP
供应商定义的 CCMP
供应商定义的 供应商定义的
供应商定义的 供应商定义的
WPA2 - 企业 供应商定义的
WPA2 - 企业 供应商定义的
供应商定义的 供应商定义的
供应商定义的 供应商定义的
支持的频段数：2
2.4 GHz [ 0 MHz - 0 MHz]
5 GHz [ 0 MHz - 0 MHz]
支持的无线显示器: 是 (图形驱动程序: 是，WLAN 驱动程序: 是)
Are there other places that could cause transmission problems?
I'm sorry, you're right, the Hosted network supported : No output is for the legacy hotspot created by netsh wlan start hostednetwork. The Flying Carpet hotspot on Windows now uses WiFi Direct which is supported on newer cards. Maybe the AX211 is using WiFi 6 and the Android phone can't? Is the WiFi card in the Windows computer that works older? I don't know, that's a total guess unfortunately. I'll let you know if I think of anything else. What is the output of Flying Carpet on the Windows computer that doesn't work?
Another Windows and Android transmission uses 5240MHz (48CH), while Android-to-Android transmission uses 2412MHz (1CH), and both work well. Unfortunately, my computer uses 5765MHz (153CH) for transmission with Android. This may be the reason why the phone cannot establish a connection normally, I guess.
It seems that my network card is slightly more advanced than the other computer's, allowing it to support higher frequency channels. This inadvertently caused an error, because Windows always tends to use higher frequencies to establish WiFi direct. I will try to test it on more computers.
Currently, there does not seem to be any API or setting that strictly limits the frequency band used by WiFi Direct without affecting normal WLAN connections. (source questionable)
One more thing: During the fail connection process between Windows and Android, Android always goes through the following steps:
- Search for devices.
- Ask the user to connect to a specific device named
flyingCarpet_xxxx. - Spend some time trying to connect, but ultimately fail.
Below is the log from a failed connection:
All permissions granted
Device connected
Stopped advertising
Bluetooth initialized
Joining flyingCarpet_d06d
Failed to connect to hotspot