Skip to content
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

Open
valentino-90 opened this issue Jan 14, 2024 · 6 comments · May be fixed by #267
Open
Labels
bug Something isn't working

Comments

@valentino-90
Copy link

Devices: One Plus Nord 3 - MacBook Air (Mid 2013 - Catalina OS)

  • Same file transfer (37MB video)
  • Same WiFi Network (5ghz)

-----> 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 ???

@valentino-90 valentino-90 added the bug Something isn't working label Jan 14, 2024
@akashkroos970
Copy link

yeah same issue

@schlagmichdoch
Copy link
Owner

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.
Would you be open to test the new version before release?

@valentino-90
Copy link
Author

valentino-90 commented Feb 6, 2024

yes! i can test it

---- off topic ----
Could it be compiled for windows and mac as if it were a native application (with electron or nodejs, or even if it were rewritten in flutter you could write a single code for android, ios, windows, mac and web). At this moment, it's a PWA, if I clean the Chrome history it also deletes the PWA history making permanent device pairing useless...

@schlagmichdoch
Copy link
Owner

yes! i can test it

Great! I will get back to you tomorrow!

---- off topic ----
Could it be compiled for windows and mac as if it were a native application (with electron or nodejs, or even if it were rewritten in flutter you could write a single code for android, ios, windows, mac and web). At this moment, it's a PWA, if I clean the Chrome history it also deletes the PWA history making permanent device pairing useless...

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:

@schlagmichdoch schlagmichdoch linked a pull request Feb 9, 2024 that will close this issue
42 tasks
@schlagmichdoch
Copy link
Owner

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/

@valentino-90
Copy link
Author

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.

screen1
screen2

SPEED IS OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants