Comments (34)
Stop treating the developer like a machine that works for you, you are not even paying for anything here. Don't forget that anyone also could open PRs to fix it.
@grishka I think you are not able to reproduce it because of your network speed is already on the limit to the speed during the bug. If you can get somewhere a faster connection maybe you can reproduce it.
from neardrop.
Oh, so there is now a bug of sudden... typical
from neardrop.
@ Geisha
whoa.... easy on the language "Comrade", no tears in your "Borscht"
from neardrop.
jesuslopezxing : Not treating the Developer like a "Machine". Its about taking "Ownership" of an issue the developer has a duty to do for its users.
There are numerous reports of issues, and the developer denies it ? he is using a "special" mac we dont have ? LOL
Its about accountability
from neardrop.
Can you try this build to see whether it fixes anything? NearDrop.app.zip
from neardrop.
Maybe there is, maybe there isn't. We don't know until someone could both reproduce this issue and debug it. So far I've only seen people complain with the "fix your crap bro" attitude, with no attempts whatsoever made to pin down the cause.
from neardrop.
pushback, again typical
from neardrop.
@grishka just want to say, thanks very much for sharing your project. Don't let someone's ingratitude stop you doing that! It's great.
from neardrop.
@macmanjimmy any chance you could try to debug this issue? Set up Xcode, set up the project, try to run it. A tool like Wireshark might help you find what is happening and you could report it here or, better yet, find a solution. It would be very helpful to anyone trying to solve the issue and significantly reduce the time involved, plus it would be an opportunity for you to contribute to a very interesting open source project.
from neardrop.
Looks good.
--- 192.168.1.1 ping statistics ---
104 packets transmitted, 104 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.275/2.250/8.589/1.240 ms
from neardrop.
Can you post evidence as to the app being responsible for this change?
from neardrop.
I have been able to reproduce the same issue. With the app running my speed average drops from 400-500 to 100-200. I have done several attempts.
from neardrop.
Have the Same issue, this classifies as a "pattern" set as a "Login" app now have to start and quit manually....
Neardrop on 116mps off 590mbps
from neardrop.
IDK, I can't reproduce this problem. I pay for 200 mbit, I get 200 mbit.
NearDrop just running shouldn't affect your network speed. The only thing it does is listen on a TCP port for incoming connections (that's fully passive) and advertise a service via mDNS (a.k.a. Bonjour, how Apple calls it). The mDNS part supposedly only responds to broadcast packets that Android devices send when looking for receivers, otherwise doing nothing. But that's implemented by the system, in the daemon called mDNSResponder
.
from neardrop.
IDK, I can't reproduce this problem. I pay for 200 mbit, I get 200 mbit.
NearDrop just running shouldn't affect your network speed. The only thing it does is listen on a TCP port for incoming connections (that's fully passive) and advertise a service via mDNS (a.k.a. Bonjour, how Apple calls it). The mDNS part supposedly only responds to broadcast packets that Android devices send when looking for receivers, otherwise doing nothing. But that's implemented by the system, in the daemon called
mDNSResponder
.
is the app running at the same time? running 13.2.1
from neardrop.
IDK, I can't reproduce this problem. I pay for 200 mbit, I get 200 mbit.
NearDrop just running shouldn't affect your network speed. The only thing it does is listen on a TCP port for incoming connections (that's fully passive) and advertise a service via mDNS (a.k.a. Bonjour, how Apple calls it). The mDNS part supposedly only responds to broadcast packets that Android devices send when looking for receivers, otherwise doing nothing. But that's implemented by the system, in the daemon called
mDNSResponder
.
Created a "NEW USER" account no other apps running/ fresh OS same result
Im paying 500mbps, Blessed to get close to 600, but drops like a rock to 116mbs definitely an issue
How about you fly me to Alaska we can meet there and i can show you LOL JK.
Seriously the app needs work, worked at Apple Tier2 before i became disabled and would not bring this issue to light unless its valid...
from neardrop.
I have been able to reproduce the same issue. With the app running my speed average drops from 400-500 to 100-200. I have done several attempts.
You running OCLP what year is your Macbook?
from neardrop.
OCLP
I don't know what it... I am running 14" M1 Pro 2021
from neardrop.
then you not Running it LOL its a bug... developer just needs to recognize and fix it.. we'll see...
I just run and quit when i need it.. app has a serious leak
from neardrop.
I am also seeing a significant speed drop!
from neardrop.
awe, everyone except the developer, interesting LOL have to launch and quit each time I use it..
from neardrop.
I'm experiencing the same issue, however, I'm at the limit of my WiFi range, so it's happening at lower speeds: I get about 32 Mbps, dropping to about 17 when I open NearDrop.
from neardrop.
The license for this app explicitly says that nothing is guaranteed. I'm just putting this stuff out there for everyone to use but I have no obligations whatsoever.
If you want to debug this problem, go for it. Pull requests that fix bugs are welcome too.
from neardrop.
Acting entitled as fuck again, typical
from neardrop.
if you're experiencing drops in your bandwidth, just remember to quit after use.
DO NOT USE this app as a "Login item"
Since the developer (obviously) will not correct this bug, this is the method we have to use...
from neardrop.
whoa.... easy on the language "Comrade", no tears in your "Borscht"
If you want to bring out my Russian-ness, then I have to say that we have a term in our internet slang for the state of mind you're experiencing — "пукан бомбанул". I encourage you to do an image search for this.
And, @davystrong is right. Go get Xcode and Wireshark and try debugging the thing that makes you so upset. If you manage to fix it, or at least determine the cause, we'll be thankful.
from neardrop.
Probably my issue is related to this one. When the app is running, I observe increased network latency. It's visible everywhere, even when I ping a router:
NearDrop is running, min/avg/max/stddev = 1.407/51.946/251.638/74.576 ms
$ ping -c 20 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=33.123 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=75.757 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=122.260 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=163.116 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=207.407 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.797 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.627 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.720 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.102 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.481 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.829 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.679 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=44.561 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=88.844 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=8.853 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=251.638 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=7.148 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.748 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=20.817 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=1.407 ms
--- 192.168.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.407/51.946/251.638/74.576 ms
No NearDrop, round-trip min/avg/max/stddev = 1.237/1.591/2.055/0.206 ms
$ ping -c 20 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.703 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.401 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.704 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.643 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.358 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.615 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.543 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.409 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.818 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.613 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.355 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2.055 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.731 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.237 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.404 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.657 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.657 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.310 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.885 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=1.719 ms
--- 192.168.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.237/1.591/2.055/0.206 ms
I suppose it could be caused by wifi scanning. Topic with similar issue https://developer.apple.com/forums/thread/97805
from neardrop.
Shhhhhh "Developer" is sensitive
from neardrop.
When an Apple STA is coordinating peer-to-peer Wi-Fi work
That's an interesting clue. I just did a packet capture on awdl0
, the interface for Apple's proprietary P2P Wi-Fi extension, and there are some MDNS packets when NearDrop exits and launches. I'm not sure about the specifics of how MDNS works, but maybe there are network configurations when this happens more often. Now I need to find a way to only advertise my MDNS service on specific network interfaces to test this hypothesis 🤔
Also why the hell did I do this?
Shhhhhh "Developer" is sensitive
Have you downloaded Xcode yet or are you just going to keep feeling entitled to other people's work for free while being entirely unhelpful?
from neardrop.
@macmanjimmy иди нахуй 😘
from neardrop.
@grishka - looks good here also. Thanks for all your hard work on this - such a useful utility 👍
from neardrop.
Can you try this build to see whether it fixes anything? NearDrop.app.zip
Tested here too and looking good. Thanks!
from neardrop.
Tested and seems to work here too. Thanks!
from neardrop.
Not working for me... I can see my M1 Mac mini from my Samsung phone but nothing appears in my mac after trying to send a file...
from neardrop.
Related Issues (20)
- "Open Anyway" on Mac's system settings still brings up "can't be opened" message HOT 1
- SwiftProtobuf.BinaryDecodingError error 3. Failed to receive file
- SwiftProtobuf.BinaryDecodingError error 3. Failed to receive file HOT 2
- Quick Share support? HOT 53
- Stops working after the first share. Android -> Mac HOT 1
- How to Implementing Nearby Connection SDK in Android
- Macbook not showing in android's nearby share option HOT 4
- Android device not visible on mac after new google file update HOT 17
- Donation options? HOT 2
- Neardrop not working with Samsung devices
- Android not available when sharing from Mac HOT 2
- not working anymore, after the release of quickshare HOT 9
- Not working after the update of Quick Share. HOT 20
- Can't send from Mac to a Samsung device after the Quick Share update HOT 22
- The google file app removed shortcut to nearby sharing HOT 10
- Discovery of Android devices from Windows - without Google Files or Activity Intent HOT 12
- Communication error: Transferring files from Samsung to Mac by using Quick Share HOT 28
- Not Working in Catalina - 10.15.7 (19H15) HOT 1
- Same "Communication Error" HOT 2
- Cannot send from SamSung S23 to Mac HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from neardrop.