-
-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Same file, same devices, same network but different transfer speed from mobile to desktop #244
Comments
yeah same issue |
Once your devices are connected the same connection is used for either transfer direction so the transfer speed should be the same. To improve the current behavior and speed, I have completely rewritten the code that is responsible for sending and receiving the files which was quite basic. |
yes! i can test it ---- off topic ---- |
Great! I will get back to you tomorrow!
There are plans for a flutter app (#198) but I'm not sure how fast this will be implemented as it's adding a lot of complexity. Regarding your situation:
|
As the repository was falsely flagged and hidden for the last month I could not notify you. @valentino-90 I would appreciate it, if you could test this feature on this instance: https://pairdrop-dev.onrender.com/ |
HI! sorry for delay. Yes the speed is definitely improved from mobile ---> to ---> web. The problem now is that once I receive a file it asks me to download it, but when i click "download" i get an error "check internet connection" (i don't know if just for this dev testing step). I attach some screenshots. SPEED IS OK |
Devices: One Plus Nord 3 - MacBook Air (Mid 2013 - Catalina OS)
-----> From Chrome on Macbook -> to One Plus (acceptable transfer speed with 37MB video)
-----> From One Plus (Chrome browser or mobile app Snapdragon & pairdrop) -> to MacBook (unacceptable transfer speed with 37MB video)
Considerations: analyzing the transfer speed, it is as if from mobile (browser or app) it does not use the local network, preferring via the internet. Why ???
The text was updated successfully, but these errors were encountered: